Integrate processor-only Issuing
Set up a processor-only Issuing integration.
Before you can move forward with the processor-only model, you must conduct Know Your Customer (KYC) on cardholders. In this model, a Cardholder object represents every end customer.
Create a Cardholder object
Create a Cardholder object to represent the business entity or individual that’s authorised to use the card. The response includes a unique id for the cardholder.
Command Line
Select a language
cURL
Stripe CLI
Ruby
Python
PHP
Java
Node.js
Go
.NET
No results
Issue a card
Issue the card to the Cardholder by passing in the id from the previous step. You must also include the currency and type of card ( physical or virtual). In the following example, we also include the cardholder’s shipping information.
Command Line
Select a language
cURL
Stripe CLI
Ruby
Python
PHP
Java
Node.js
Go
.NET
No results
Track the card
To track the card’s shipping status, use the tracking_url or tracking_number attributes. You can also listen to the issuing_card.updated webhook for updates to shipping.status. For you to receive updates, the shipping carrier must support tracking.
Activate the card
When you receive a webhook indicating that shipping.status equals delivered, activate the card by updating its status. (You can also use this API to temporarily deactivate the card.) By default, cards are inactive when you create them.
Command Line
Select a language
cURL
Stripe CLI
Ruby
Python
PHP
Java
Node.js
Go
.NET
No results
Set up authorisation notifications
Set up the issuing_authorization.request webhook to immediately notify you when someone makes an authorisation request on an issued card. This lets you approve or decline the authorisation instantly, giving you control over whether to allow or block a transaction before it completes. To learn more, see Issuing real-time authorisations.
Subscribe to authorisation updates
Subscribe to issuing_authorization.create webhook events. This webhook notifies you when someone creates a new authorisation for an issued card. It provides details about the authorisation outcome, including whether it was approved or declined. This lets you track authorisations, handle edge cases (such as network declines after approval), and place a hold on the cardholder’s balance when an authorisation completes.
Subscribe to transaction updates
Subscribe to issuing_transaction.create webhook events. This webhook notifies you when a new transaction is created for an issued card, which occurs when Stripe receives the clearing record for an authorisation. You can’t decline the clearing record, but you can dispute the transaction if needed. Use this webhook to track finalised spending, and update cardholder balances accordingly.
A transaction doesn’t necessarily need to be associated with an authorisation (in the case of a force capture). Additionally, the transaction amount doesn’t need to match the amount from a linked authorisation (in the case of a partial_capture or over_capture).