Oracle Fusion Cloud ERP and Adyen integration

What moves between them

Payment settlements and disputes flow from Adyen into Oracle Fusion Cloud ERP. Adyen payment capture events are received via webhook and polled via settlement reports, then mapped to Fusion customer accounts and GL accounts for posting as receivables transactions and GL entries. Dispute records such as chargebacks and prearbitration events are logged in Fusion as flagged items for finance team review. Refunds and cancellations flow the same direction, updating the corresponding invoice or transaction state in Fusion. GL postings are read-only in Adyen, so ml-connector never writes payment authorizations or refunds back to the payment platform.

How ml-connector handles it

ml-connector listens for Adyen webhook events and validates each call against the HMAC-SHA256 signature using your Adyen account key, refreshing the API Key if needed. On the Oracle Fusion side, it accepts the customer-specific pod URL per instance, authenticates with OAuth 2.0 Client Credentials, and uses the resulting bearer token to query the Fusion REST API for existing receivables, customers, and GL accounts that match the payment records. Payment captures are mapped to Fusion customer accounts by matching Adyen merchant metadata to Fusion customer numbers or names, then posted as receivables transactions and GL lines to the designated GL account. Disputes are logged with a status flag so finance can filter and review them before closing. Settlement reports are polled periodically to detect bulk reconciliation records and post accruals if your GL setup requires them. Because Fusion uses pod-specific URLs with no shared base hostname, ml-connector stores the full pod URL per customer and validates all API paths against that instance. Retries on rate limits and timeouts are automatic with exponential backoff, and every record carries an audit trail so a failed GL post can be replayed manually if needed.

A real-world example

A mid-sized SaaS company processes monthly subscription billings through Adyen and runs Oracle Fusion Cloud ERP for financial accounting and AR. Before the integration, the AR team received Adyen settlement reports each morning, manually matched payment batches to customer invoices in Fusion, and posted the GL entries for cash received and merchant fees. Disputes required separate investigation in Adyen and manual flagging in Fusion, creating duplicate tracking and delays in dispute resolution. With Adyen and Fusion connected, each day's payment settlements post automatically to AR as customer transactions and GL postings, allocated to the correct customer and GL account. Dispute events in Adyen immediately flag the corresponding transaction in Fusion, so the team knows exactly which customer accounts need follow-up and can resolve disputes before the monthly reconciliation.

What you can do

• •Post Adyen payment captures and settlements into Oracle Fusion as customer receivables transactions and GL entries, mapped to the correct GL accounts.
• •Log Adyen disputes and chargebacks in Fusion as flagged items for finance team review and follow-up.
• •Authenticate Oracle Fusion with OAuth 2.0 on the customer-specific pod URL and Adyen with API key, validating Adyen webhook events with HMAC-SHA256 signature verification.
• •Poll Adyen settlement reports and Oracle Fusion receivables on a schedule you control, with automatic retries and a full audit trail on every record.
• •Reconcile payment amounts and disputed items between Adyen settlement data and Oracle Fusion AR balances for month-end close.

Questions

Which direction does data move between Oracle Fusion and Adyen?

Payment settlements, captures, refunds, and disputes flow from Adyen into Oracle Fusion. Adyen is a payments platform without invoices or GL accounts, so ml-connector maps payment records to Fusion customer accounts and GL accounts for posting. GL entries in Fusion are read-only in Adyen, so no financial records flow back to the payment platform.

How does the integration handle Oracle Fusion's lack of direct webhooks?

ml-connector receives payment and dispute events from Adyen via webhooks with HMAC-SHA256 signature verification, then polls the Oracle Fusion REST API on a schedule to query existing receivables and GL accounts that match the payment records. This hybrid approach keeps settlement postings current without requiring Oracle Integration Cloud middleware.

How are Adyen payments mapped to Oracle Fusion customers and GL accounts?

Adyen payment records carry merchant metadata such as customer reference or invoice number. ml-connector matches that metadata against your Oracle Fusion customer accounts and invoice records, then posts the payment to the appropriate customer account and GL account. Custom mapping rules can be configured if your Adyen record structure differs from the default pattern.