Payments
How payment is taken for a basket, and the payment providers OneBasket supports.
Payment is taken by a payment provider. Each store is configured with one, and that provider takes the payment. OneBasket creates the payment intent, passes the customer to the provider, and completes the basket when the provider confirms the payment.
Payment providers
A store uses one payment provider. OneBasket has integrations for these providers:
| Provider | API reference |
|---|---|
| Worldpay | Worldpay |
| CyberSource | Not published yet |
| Adyen | Not published yet |
| Stripe | Not published yet |
| PayTabs | Not published yet |
Your Stadion technical contact tells you which provider your store uses, and supplies the integration details for providers whose reference is not published yet.
How payment works
The first and last steps are the same for every provider. Only the middle step differs.
Create a payment intent
Call Create a payment intent on the Baskets API. The basket becomes immutable.
When the payment intent reaches the status AwaitingPayment, its pspPayload field holds the data that the payment provider returned for this payment. OneBasket does not interpret this data. Your storefront passes it to the payment provider's own SDK or to the provider endpoints below.
Take the payment with the provider
Use the payment provider's client SDK, together with the OneBasket Storefront endpoints for that provider. These endpoints cover provider-specific steps, such as 3-D Secure, saved payment methods and wallet payments.
OneBasket completes the basket
The payment provider confirms the payment to OneBasket directly. The payment intent moves to PaymentComplete, the basket becomes an order, and order processing starts. See Checkout flow.
To let the customer change the basket before paying, call Cancel a payment intent.