Run a payment end to end
Create a sale, read it back, and make the sandbox decline you once, all from one blueprint.
Your answers so far
- What are you testing next?
- A payment going through, start to finish. Change
Choose one
What to build
Run the first-payment blueprint against a sandbox merchant. It creates a card sale at an amount the sandbox always approves, reads the transaction back, and then sends a declining amount so you see both shapes of response before you write code against either.
What this means for PCI
This is guidance rather than a compliance determination. Which questionnaire you are eligible for depends on your full environment, so confirm it with your QSA or your acquirer before you rely on it.
Worth knowing
- The sandbox picks the result from the amount, the billing ZIP, and the security code, not from the card number. Use the blueprint's amounts rather than inventing your own.
- Send an idempotency key from your first request, so it's already in place when you test retries.