Oracle E-Business Suite and Adyen integration

What moves between them

The flow runs from Adyen into Oracle E-Business Suite. ml-connector consumes Adyen settlement and reconciliation reports and posts the resulting journals into the EBS GL_INTERFACE table: captured payments, refunds, processing fees, and chargebacks, each mapped to the matching GL code combination and operating unit. Capture, refund, and report-available webhooks trigger the work as soon as activity settles, and a scheduled poll of the imported journals backfills anything a webhook missed. Adyen is treated as a read-only accounting source, so ml-connector never writes payment instructions or financial entries back into Adyen, and EBS AP payments stay out of scope because they are read-only in the open interface views.

How ml-connector handles it

ml-connector stores both credential sets encrypted and sends the Adyen X-API-Key on every request, switching to the merchant-specific live URL prefix when the environment is live. On the EBS side it accepts the full instance base URL per customer, logs in for a session token, re-authenticates when a call returns 401 as the token expires, and attaches the operating unit org ID and responsibility context that every EBS REST call requires. Adyen webhooks arrive signed with HMAC-SHA256, so each notification is verified before processing and the pspReference is used as an idempotency key, because Adyen can deliver the same notification more than once. On REPORT_AVAILABLE the settlement report is downloaded from the signed URL, parsed, and its lines mapped to GL code combinations, with the SOURCE column set to a unique connector identifier so duplicate journal rows are detected before insert. Writes go to GL_INTERFACE as XML and rely on the Journal Import concurrent program, which is asynchronous, so ml-connector polls the GL base tables to confirm the journal actually posted rather than trusting the 200. EBS has no rate limiter and is a shared on-premises system, so calls run at low concurrency in off-peak windows, and every record carries a full audit trail and can be replayed if a post fails.

A real-world example

A mid-sized direct-to-consumer manufacturer with roughly 300 staff sells finished goods through its own online store and runs Oracle E-Business Suite R12.2 for finance and procurement, with Adyen as the payment processor at checkout. Before the integration, the finance team downloaded Adyen settlement reports each day and manually keyed the gross sales, refunds, and processing fees into EBS, then spent month-end close reconciling the bank deposit against the orders it was supposed to cover. With Oracle E-Business Suite and Adyen connected, each settlement report posts into GL_INTERFACE and imports automatically, split across the right GL code combinations, so the processing fees are recognized and the deposits already tie out. The daily re-keying step is gone and close starts from reconciled numbers.

What you can do

• •Post Adyen settlement and reconciliation reports into the Oracle E-Business Suite general ledger through GL_INTERFACE and Journal Import after every payout.
• •Record captured payments, refunds, processing fees, and chargebacks against the correct EBS GL code combinations and operating unit.
• •Receive Adyen capture, refund, and report-available webhooks, verified by HMAC-SHA256, and act on them as activity settles.
• •Authenticate Adyen with its API key and live URL prefix, and EBS with a session token plus the required org and responsibility context.
• •Confirm each journal actually imported by polling the EBS base tables, with retries and a full audit trail on every record.

Questions

Which direction does data move between Oracle E-Business Suite and Adyen?

The flow is Adyen into Oracle E-Business Suite. Settlement reports, captures, refunds, fees, and chargebacks move from Adyen into the EBS general ledger as journals. Adyen is treated as a read-only accounting source, so ml-connector does not write payment instructions or financial entries back into Adyen.

Does Adyen post invoices or purchase orders into Oracle E-Business Suite?

No. Adyen is a payments platform with no native invoice, purchase order, or vendor objects. What it provides is payment, refund, payout, dispute, and reconciliation report data, and ml-connector maps that activity into the EBS general ledger as journal lines through GL_INTERFACE rather than as AP documents.

How does the integration handle the fact that EBS writes are asynchronous and have no webhooks?

A POST to GL_INTERFACE only inserts rows; the Journal Import concurrent program then posts them, so ml-connector polls the EBS base tables to confirm the journal actually landed rather than trusting the initial response. Because EBS has no webhook system, Adyen's signed webhooks drive the timing while a scheduled poll of the imported journals backfills anything a webhook missed.