Testing Issuing
Learn how to test your integration and simulate purchases.
You can issue cards and simulate purchases using your own Stripe integration in a sandbox environment. This allows you to test your integration before you go live without having to make real purchases. You can only use these cards for testing within your Stripe account and not for external purchases.
Caution
When testing your authorisation endpoint, make sure that you have set the test endpoint in your Issuing settings. You can view test data by switching into your sandbox environment.
Fund your test Issuing balance
Before you create test transactions, you must add test funds to the Issuing balance on your account. These aren’t real funds, and you can only use them for simulating test purchases.
Issuing users in the US
Issuing users in the US use “pull” funding, and use Top-ups to fund their Issuing balance. You can create test top-ups in the Dashboard, or with the Top-ups API. Learn more about funding Issuing balances for US users.
Issuing users in the UK and euro area
To top up their balance, Issuing users in the UK and Europe “push” funds using Funding Instructions. You can do this in your sandbox environment, which you access from the Dashboard, or with the Funding Instructions API. Learn more about funding Issuing balances for UK and euro area users.
Create a cardServer-side
Create a cardholder with a name, billing address, and entity type. You can also provide additional information, if necessary.
Next, create a Card for the cardholder.
Create an authorisationServer-side
An Authorisation represents a cardholder’s attempt to make a purchase on a card. You can simulate the creation of an authorisation in test-mode with the Authorisation test helpers API.
After you configure real-time authorisations, Stripe sends the issuing_
webhook event. You can respond to this event directly to approve or decline it. Learn more about the real-time authorisation endpoint builder.
Capture an authorisationServer-side
After approval, an Authorisation is in a pending
state while it waits for capture. You can simulate capture of the authorisation with the API.
This generates a new Transaction resource and the Authorisation status updates to closed
.