A checkout session is the controlled payment flow that Swipe Aras creates for each customer purchase. Here's how it works from start to finish.
The Checkout Lifecycle
Create a checkout session — Your system calls the Swipe Aras API to create a session. You receive a checkout URL or session token.
Customer completes payment — The customer enters their payment details through the hosted checkout experience.
Swipe Aras processes the payment — The transaction is authorized (or refused) by Adyen.
You receive the result — Via webhook event and/or redirect URL.
Funds settle — Authorized funds accumulate in your store's balance account and payout on your settlement schedule.
Checkout Session Events (Outbound Webhooks)
Event | Meaning |
|---|---|
| A checkout session was created |
| Payment was successfully authorized |
| Payment was declined by the issuer or processor |
| The session was cancelled before completion |
| An error occurred during processing |
Hosted vs. API Checkout
Swipe Aras offers a hosted checkout experience — the customer is presented with Swipe Aras's secure payment page. This keeps sensitive card data off your systems and reduces your PCI scope.
API Reference: api.araspayment.com/api-docs — see the Checkout section for full request/response schemas.