Developers1 min read
This guide is a map, not a specification. It describes the shape of an integration and points to the canonical documentation for each part.
The shape of an integration
- 01
Create a transaction
Your system creates the transaction with the amount, description, review window and your own reference.
- 02
Send the buyer to checkout
Use the returned checkout destination. Do not collect payment separately.
- 03
Consume state changes
Subscribe to webhook events rather than polling, and treat them as the source of state.
- 04
Reconcile settlements
Match released settlements to your orders using the transaction identifier and your reference.
Before you go live
- Seller activation must be complete before live keys are issued — see Seller verification & activation.
- Verify webhook signatures on every request you accept.
- Make your handlers idempotent — see Retries and idempotency.
- Run the end-to-end lifecycle in test first — see Testing an integration.
Go deeper
Related guides
DevelopersAPI overviewWhat the ArosaPay API covers, how it is authenticated, and where the full reference lives.DevelopersWebhook eventsHow ArosaPay notifies your system of transaction state changes, and how to consume them safely.DevelopersTesting an integrationWhat to exercise before going live, including the exception path most integrations forget.
Last updated