How does Infor CloudSuite authenticate to GoCardless?

ml-connector stores the CloudSuite OAuth 2.0 credentials encrypted and refreshes the bearer token before it expires. GoCardless authentication is a separate bearer token retrieved from your merchant dashboard. Both tokens are refreshed independently and managed by ml-connector so your customer and payment syncs never interrupt due to token expiry.

When do customers and payments sync between CloudSuite and GoCardless?

Customers are pulled from CloudSuite on a schedule you set, typically hourly. GoCardless webhooks deliver payment events in real time, so successful payments post into CloudSuite within seconds of settlement. Mandate changes flow back from GoCardless to CloudSuite on every webhook event, keeping your customer master current.

What happens if a payment fails in GoCardless or a mandate is revoked?

ml-connector receives the failure or mandate-revoked event via webhook, updates the customer and mandate status in CloudSuite, and tracks the event in the audit log. You can then follow up with the customer to retry the mandate or collect via an alternative method. The full event history is visible in both systems.

Infor CloudSuiteGoCardless

Infor CloudSuite and GoCardless integration

Infor CloudSuite holds your customer list and AR ledger. GoCardless collects payments directly from customer bank accounts via recurring and one-off bank debits. Connecting them keeps your customer master, payment mandates, and cash reconciliation in sync. New customers and mandate changes flow from CloudSuite into GoCardless so you can start collecting immediately, and successful payments flow back as cash receipts posted to your GL without manual re-entry.

How Infor CloudSuite works

Infor CloudSuite exposes customers, invoices, GL accounts, and payment status through the ION API Gateway via REST calls and OAuth 2.0 bearer token authentication. The base URL is customer-specific and extracted from the .ionapi credentials file. CloudSuite has no native webhooks for customer or invoice changes, so ml-connector polls the customer and invoice lists at a configurable interval, filtering by modified date. For each customer and invoice in AR, all required GL account mappings and account strings are read from the GL master tables.

How GoCardless works

GoCardless is a bank debit payment processor that holds customers, bank accounts, mandates, and payment transactions through a REST API. Every request carries a bearer token in the Authorization header, and GoCardless publishes webhooks for payment status changes, mandate updates, and refunds, sent as HMAC-SHA256-signed POST requests. Webhooks include events such as payments failed, payments paid out, and mandate changes, allowing ml-connector to react in real time when payment status changes without polling. Payouts are read-only and generated automatically by GoCardless.

What moves between them

Customer master data flows from Infor CloudSuite into GoCardless whenever a customer record is created or modified. For each active customer in AR, ml-connector creates a GoCardless customer and links the customer's bank accounts as mandates. When a GoCardless mandate is created or updated, the status is tracked in CloudSuite. Successful payment events are received via GoCardless webhooks and posted back into CloudSuite as cash receipts against the matching customer invoice and GL account. Payment failures and refunds also flow back as adjustments so your AR aging and GL are always in sync with the bank.

How ml-connector handles it

ml-connector stores the CloudSuite OAuth credentials and GoCardless bearer token encrypted and handles token refresh before expiry. It polls CloudSuite customers and invoices by modified date on a schedule you set, typically once per hour or after business events. Each new or changed customer is pushed into GoCardless, and matching CloudSuite GL account codes are mapped to GoCardless creditor settings so payments are routed to the correct bank account. ml-connector registers a webhook URL with GoCardless and verifies incoming webhooks using HMAC-SHA256 signature validation. When a payment succeeds, the webhook is received, the amount is validated against the outstanding invoice, and ml-connector posts a cash receipt into CloudSuite's AR module and GL journal. Bank account changes in GoCardless trigger mandate updates in CloudSuite so your master records stay current. The full audit trail is maintained in both systems, and any failed posting can be retried.

A real-world example

A mid-sized B2B services firm runs Infor CloudSuite for finance and AR, and uses GoCardless to collect subscription payments and invoiced services from customers across North America and Europe. Before the integration, the finance team manually entered customer bank account information into GoCardless, managed mandate status in spreadsheets, and reconciled GoCardless payouts against CloudSuite AR by hand, a time-consuming and error-prone process. With CloudSuite and GoCardless connected, customers are synced automatically when added to AR, direct debit mandates are created and tracked in real time, and payment receipts post directly to the ledger, eliminating manual entry and keeping AR aging clean and reconciliation fast.

What you can do

Sync Infor CloudSuite customers into GoCardless as customers and link their bank accounts as payment mandates.
Track mandate status and bank account changes from GoCardless back into CloudSuite for a current customer master.
Post successful GoCardless payments into CloudSuite as cash receipts against the matching invoice and GL account.
Handle mandate failures, refunds, and payment disputes by reflecting them in CloudSuite adjustments and AR aging.
Verify GoCardless webhook signatures and retry failed postings with a full audit trail of every sync event.

Questions

How does Infor CloudSuite authenticate to GoCardless?: ml-connector stores the CloudSuite OAuth 2.0 credentials encrypted and refreshes the bearer token before it expires. GoCardless authentication is a separate bearer token retrieved from your merchant dashboard. Both tokens are refreshed independently and managed by ml-connector so your customer and payment syncs never interrupt due to token expiry.
When do customers and payments sync between CloudSuite and GoCardless?: Customers are pulled from CloudSuite on a schedule you set, typically hourly. GoCardless webhooks deliver payment events in real time, so successful payments post into CloudSuite within seconds of settlement. Mandate changes flow back from GoCardless to CloudSuite on every webhook event, keeping your customer master current.
What happens if a payment fails in GoCardless or a mandate is revoked?: ml-connector receives the failure or mandate-revoked event via webhook, updates the customer and mandate status in CloudSuite, and tracks the event in the audit log. You can then follow up with the customer to retry the mandate or collect via an alternative method. The full event history is visible in both systems.

Connect Infor CloudSuite and GoCardless

Free to use. Add your credentials, ping your real systems, and see if we fit.

Get started