Developers1 min read
A short orientation to the API surface. Endpoint-level detail is maintained in the API reference and is not duplicated here.
What the API covers
- Creating and reading protected transactions.
- Recording fulfilment and reading the current transaction state.
- Reading settlement records for reconciliation.
- Managing webhook endpoints and their signing secrets.
Authentication and environments
Requests are authenticated with an API key issued to an activated seller account. Keys are environment-scoped; never ship a live key to a browser or a mobile client. Key issuance and rotation are described on the developer platform.
Where the specification lives
Endpoints, request and response shapes, error codes and versioning are documented in the API reference.
Go deeper
Related guides
DevelopersIntegrate ArosaPayOrientation for teams adding protected checkout to a platform, storefront or internal system.DevelopersWebhook eventsHow ArosaPay notifies your system of transaction state changes, and how to consume them safely.DevelopersRetries and idempotencyHow to make transaction creation and webhook handling safe under retries and redelivery.
Last updated