New Payment Count Limit Control

Stripe has added support for automatically cancelling virtual Issuing cards after a predetermined number of payments. When creating a card, you can now specify the lifecycle_controls.cancel_after.payment_count parameter to define how many non-zero payment authorizations will trigger automatic cancellation.

How It Works

• Cards are cancelled after making the specified number of payment authorizations and transactions
• The count includes penny authorizations but excludes non-payment actions like authorization advice
• Once the payment limit is reached, the card is automatically disabled without requiring manual intervention

Available Across All SDKs

This feature is available through:

• REST API (API version 2026-03-25.dahlia)
• Ruby, Python, PHP, Java, Node.js, Go, and .NET SDKs

Upgrade Instructions

To use this feature:

1. View your current API version in Workbench
2. Upgrade your SDK to the latest version (or update your API requests with the new Stripe-Version header)
3. Update webhook endpoint API versions
4. Test your integration in sandbox mode
5. Perform the upgrade in Workbench (with 72-hour rollback window available)

This addition provides better control over virtual card usage without requiring continuous monitoring and manual lifecycle management.