Oracle Fusion Cloud ERP and Stripe integration

What moves between them

AR customer records flow from Oracle Fusion into Stripe as billing customers so Stripe can collect payments against them. Oracle Fusion invoices become Stripe invoices, either automatically or on demand, so payment processing happens in Stripe. Stripe payment events (payment_intent.succeeded, charge.succeeded, invoice.payment_succeeded) flow back into Oracle Fusion as journal entries posted to the AR suspense or undeposited funds GL account, ready for matching to the original invoice. Subscription events from Stripe can also generate recurring journal entries in Oracle Fusion on the subscription's billing cycle.

How ml-connector handles it

ml-connector stores the Oracle Fusion OAuth credentials and Stripe API key encrypted per cell. Every 5 to 15 minutes, it polls Oracle Fusion's customers and invoices endpoints, filtering by LastUpdateDate to pick up only the changes. New customers are created in Stripe, and new invoices are pushed as Stripe invoice objects with the Stripe customer ID. When Stripe webhooks arrive (Stripe-Signature verified), ml-connector fetches the full payment or subscription resource from the Stripe API to ensure current state, looks up the matching Oracle Fusion invoice by external reference (stored on the Stripe invoice object), and posts a journal entry into Oracle Fusion's general ledger with the payment amount allocated to the correct GL account. If the Oracle Fusion API returns 401 (token expired), ml-connector refreshes the OAuth token and retries. If Stripe rate limits (429), it backs off and retries. Every record sync carries a full audit trail with timestamps and the matched record IDs on both sides.

A real-world example

A B2B SaaS company runs Oracle Fusion Cloud ERP for its complete back office: accounts receivable, general ledger, customer management, and billing. The company uses Stripe for payment processing and subscription billing via API. Before integration, the finance team manually exported customer lists and invoice data from Oracle Fusion, keyed them into Stripe dashboards, and then had to manually reconcile Stripe payments against Oracle Fusion receivables, often finding mismatches because customers paid against the wrong invoice or Stripe had a different customer name. With Oracle Fusion and Stripe connected, each new customer in Oracle Fusion appears in Stripe automatically within 15 minutes, invoices go straight from Oracle Fusion to Stripe for payment collection, and every successful payment in Stripe posts immediately into Oracle Fusion's GL as a suspense entry ready to match. Month-end reconciliation now runs a simple query to find unmatched invoices, and customer payment history is consistent across both systems.

What you can do

• •Sync AR customers from Oracle Fusion Cloud ERP into Stripe as billing customers on every change, with full customer name and billing address.
• •Push AR invoices from Oracle Fusion into Stripe as Stripe invoice objects linked to the correct customer, enabling Stripe payment collection.
• •Pull Stripe payment and subscription events via webhook, match them to Oracle Fusion invoices, and post receipt journal entries to the GL automatically.
• •Authenticate Oracle Fusion via OAuth 2.0 with automatic token refresh, and Stripe via API key with rate-limit backoff and retry.
• •Track every customer sync, invoice push, and payment post in a complete audit log with timestamps and the matched record IDs on both systems.

Questions

Which direction does data move between Oracle Fusion Cloud ERP and Stripe?

The primary flow is Oracle Fusion to Stripe: customers and invoices move from Oracle Fusion into Stripe so Stripe can process payments. Stripe payments flow back into Oracle Fusion as journal entries posted to the general ledger. Subscription events from Stripe can also generate recurring entries in Oracle Fusion, and customer updates in Stripe can sync back to Oracle Fusion (e.g., to update a customer address or contact). The direction is configurable per flow.

Does Oracle Fusion Cloud ERP support webhooks to Stripe, or does ml-connector have to poll?

Oracle Fusion's native Business Events system exists, but direct outbound webhooks to external URLs require Oracle Integration Cloud (OIC) middleware, which many customers do not have. ml-connector defaults to polling Oracle Fusion's REST API every 5 to 15 minutes, filtering by LastUpdateDate to pick up only the changes. If you have OIC enabled, you can configure a flow to consume Business Events instead of polling.

What happens if an Oracle Fusion invoice does not match a Stripe payment?

ml-connector stores a reference ID on the Stripe invoice that links back to the Oracle Fusion invoice. When a Stripe payment arrives, ml-connector looks up the reference ID, finds the Oracle Fusion invoice, and posts the payment into the GL. If no matching invoice is found (e.g., the reference ID is missing or incorrect), the payment is logged to the audit trail with a note and can be resolved manually or replayed once the reference is corrected. The audit trail shows every attempt so the finance team knows exactly what happened.