Developers1 min read
A protected transaction has more states than a card payment. Test the whole lifecycle, not just the happy path, before you switch to live keys.
What to exercise
- Create a transaction and confirm your reference is stored on it.
- Complete checkout and confirm your system reacts to payment safeguarded.
- Record fulfilment and confirm the move to awaiting buyer confirmation.
- Confirm receipt and follow release pending through to settlement released.
- Run the exception path: reported problem, under review, evidence requested, refund processing, refund completed.
- Replay a webhook delivery and confirm nothing is double-processed.
Going live
- Seller activation complete and settlement destination in place.
- Live keys held server-side only, with rotation understood.
- Signature verification enabled on the live webhook endpoint.
- Alerting on failed webhook processing, not just failed delivery.
Go deeper
Related guides
DevelopersIntegrate ArosaPayOrientation for teams adding protected checkout to a platform, storefront or internal system.DevelopersRetries and idempotencyHow to make transaction creation and webhook handling safe under retries and redelivery.DevelopersWebhook eventsHow ArosaPay notifies your system of transaction state changes, and how to consume them safely.
Last updated