Infor CloudSuite and PayPal integration

What moves between them

The main flow moves from PayPal into Infor CloudSuite. Orders placed through PayPal are read via the orders API and synced into CloudSuite customer invoices. When a PayPal order is authorized and captured, the capture event flows via webhook into CloudSuite as a payment against the matching invoice. Invoices can also be sent from CloudSuite to PayPal to request payment. Refunds and adjustments flow back into CloudSuite to update the receivable balance. Reconciliation happens automatically as transactions arrive, and CloudSuite GL postings reflect PayPal settlements.

How ml-connector handles it

ml-connector caches bearer tokens for both systems and refreshes them proactively before expiry, since CloudSuite tokens can last 1-24 hours and PayPal tokens around 8 hours. PayPal webhooks are configured once in the Developer Dashboard to post to an ml-connector endpoint, which verifies the RSA-SHA256 signature before processing. Orders and captures are mapped by PayPal order ID to CloudSuite invoice and customer records. Because CloudSuite has no webhooks and per-customer OAuth endpoints, ml-connector polls CloudSuite for invoices and payments on a schedule and also receives PayPal events to trigger immediate updates. PayPal order amounts map to CloudSuite invoice line items and GL accounts. Refunds are tracked separately and posted as negative payments. ml-connector deduplicates transactions by PayPal transaction ID and CloudSuite invoice number.

A real-world example

A mid-sized e-commerce retailer runs CloudSuite Financials for order-to-cash, with invoicing and GL. They sell through a Shopify store that collects payments via PayPal. Before integration, accounting staff exported PayPal transaction reports daily and manually entered each payment into CloudSuite, then traced unpaid orders against PayPal captures to find reconciliation gaps. With CloudSuite and PayPal connected, each order confirmation creates a CloudSuite invoice automatically, and each PayPal capture triggers a payment post in the same instant. Month-end reconciliation takes minutes instead of days, and the manual entry step is eliminated.

What you can do

• •Sync PayPal orders and captures into Infor CloudSuite customer invoices and payments on receipt of webhook events.
• •Map PayPal transaction amounts and dates to CloudSuite GL accounts and receivables by customer and order ID.
• •Authenticate against PayPal OAuth 2.0 and CloudSuite ION API Gateway with per-customer tenant URLs and credentials.
• •Verify PayPal webhook signatures using RSA-SHA256 and process events idempotently to prevent duplicate postings.
• •Poll CloudSuite and PayPal on a schedule, track payment state across both systems, and audit every transaction.

Questions

How does ml-connector verify PayPal webhook signatures?

PayPal includes an RSA-SHA256 signature in the paypal-transmission-sig header on every webhook. ml-connector retrieves the public key from PayPal and verifies the signature before processing the event. If the signature is invalid, the webhook is rejected with a 401 response and PayPal retries it later.

How does the integration handle Infor CloudSuite's tenant-specific base URLs and lack of webhooks?

ml-connector stores the tenant URL and ION credentials per customer and uses them to construct the OAuth token endpoint and API calls. Since CloudSuite has no native webhooks, ml-connector polls for new invoices and payments on a schedule. When a PayPal webhook arrives, it can trigger an immediate CloudSuite lookup to speed up posting.

What happens if a PayPal capture arrives before the matching CloudSuite invoice is created?

ml-connector queues the capture and retries it at intervals until the invoice appears. Each retry includes a full audit log entry. Customers can also send CloudSuite invoices to PayPal via the integration to ensure invoices are created before payment is expected.