Active (Beta). This integration is available in beta. Coverage depends on market, product, and account permissions. View integration status.
Integration approach
Balance Transactions, Payments, Payouts, and dispute APIs; determine approved account-linking and read permissions.Access and approval
Confirm Connect/platform or Stripe Apps route; public app review ETA ND. Review source. Documentation availability: Public API/docs. ND means the source catalog does not disclose an approval estimate.Data refresh
Provider update cadence: On supported events; API reads for reconciliation. Stripe emits webhooks when supported payment, refund, dispute, and payout events occur. API reads retrieve the corresponding resources; there is no single recurring refresh interval for all payment data. Event delivery can be delayed, duplicated, or out of order. Settlement and funds availability follow the payment lifecycle, so an event does not imply funds have settled. AMLOK synchronization: The enabled refresh mode and schedule are agreed for your connection. Provider timing describes upstream capability; allow for retrieval and processing before changes appear in AMLOK. See data refresh and freshness. Provider references: Stripe webhooks, Stripe event types.Data reference
Open a resource to review its field definitions. Available fields depend on the connected product, account permissions, and source data.Coverage conditions
Documented field mappings
These mappings show how source fields relate to normalized AMLOK fields. Review the source conditions for each mapping.Provider documentation
- docs.stripe.com/api/balance_transactions
- support.stripe.com/questions/how-do-i-submit-an-app-for-review-and-what-does-the-review-entail