Test data
Test cards and scenarios to test your Griner integration in test mode, without moving real money.
Test your integration with a project in test mode. Test payments run against a sandbox: no money moves and you can't be charged. Test every payment method you plan to offer, and every outcome your checkout has to handle: successful, declined, cancelled and expired payments.
Never use real card data in test mode
Only use the test cards on this page, or the ones Griner gives you. Never enter real card numbers or card details in a test project.
Test cards
Use any expiry date in the future.
| Brand | Card number | CVC |
|---|---|---|
| Mastercard | 5520330000002221 | Any 3 digits |
| Mastercard | 5520330000002254 | Any 3 digits |
| Mastercard | 5520330000002262 | Any 3 digits |
| Visa | 4635440000002207 | Any 3 digits |
| Visa | 4635440000002215 | Any 3 digits |
| Visa | 4635440000002272 | Any 3 digits |
Test scenarios
In test mode, the amount of the order, in cents, decides the 3-D Secure flow of a card payment, so you can trigger each scenario on purpose.
| Scenario | Amount | Result |
|---|---|---|
| Frictionless 3-D Secure | 3000 or less | The payment succeeds without extra authentication. |
| 3-D Secure challenge | More than 3000 | Your customer has to complete a 3-D Secure challenge. See 3-D Secure. |
Apple Pay and Google Pay
To test Apple Pay, use an Apple Pay sandbox tester account: its Wallet holds test cards instead of real ones. See Apple's sandbox testing for how to set it up.
To test Google Pay, use Google's test environment: the Google Pay payment sheet then shows test cards instead of the real cards in your Google account. See Google's test card suite for how to set it up.
To set up the wallets, see Apple Pay and Google Pay on the hosted payment page, or Apple Pay and Google Pay in your own checkout.
Before you go live
When your tests pass, follow the go-live checklist and replace the API key of your test project with the key of your live project.