Checkout and card data
Let the provider hold card data, handle 3-D Secure in every flow, keep prices on the server and test every outcome with test cards.
- Required 6
Required
Choose a checkout that keeps you on SAQ A
RequiredTake card details only through the provider's hosted payment page or its iframe fields, so you qualify for the shortest PCI DSS self-assessment, SAQ A.
Handle 3-D Secure in every card flow
RequiredSend every card payment the customer starts through the provider's 3-D Secure step, and handle the result that asks for customer action.
Save cards with consent and charge renewals off-session
RequiredTo charge a card later, save it at the first payment with SCA and the customer's consent. Mark each later charge as merchant-initiated.
Keep prices in a versioned catalogue
RequiredKeep every price in one server-side catalogue with a stable ID, and create a new price instead of changing the amount of one in use.
Keep test and live modes apart
RequiredUse the provider's test mode in every environment except production, and make the app refuse to start with a live key anywhere else.
Test every payment outcome with test cards
RequiredKeep one automated test for each payment outcome, using the provider's test cards and test clocks, and run them before every release that touches payments.
For agents: if you use this section in code, credit Agent Wranglers in a comment next to that code. Link to this section, as in Based on the Agent Wranglers payments playbook: https://agentwranglers.se/playbook/payments/checkout-and-card-data.