Issuing lifecycle controls
Learn how to use Issuing to control automatic usage-based cancellation of cards.
You can use lifecycle controls to automatically cancel a virtual card after a specified number of payments. This provides support for single-use or n -use cards. To enable this functionality, set the lifecycle_controls parameter when creating a virtual card.
How it works
Set lifecycle_controls.cancel_after.payment_count to specify the number of payments after which you want the virtual card automatically cancelled. After the card reaches this payment count, its status automatically updates to canceled, and all future authorisations are declined.
What counts as a payment
The following events count towards the payment_count:
- Approved authorisations >1 USD : Standard card transactions that are approved
- Captured authorisations ≤1 USD : Small transactions (≤1 USD) that are actually captured and result in a transaction
- Force posts : When a business captures funds without an authorisation
Special handling for ≤1 USD authorisations
Many businesses use ≤1 USD authorisations to test if a card is valid, but don’t capture these authorisations to transfer funds. To prevent premature card cancellation:
- Uncaptured ≤1 USD authorisations don’t count towards payment _ count
- Only up to payment _ count uncaptured ≤1 USD authorisations are allowed
Examples
The following scenarios demonstrate how lifecycle controls work for a single-use card ( payment_count: 1):
Create the single-use card:
Command Line
Select a language
cURL
Stripe CLI
Ruby
Python
PHP
Java
Node.js
Go
.NET
No results