Removes manual capture method for Interac cardsBreaking changes
What’s new
The interac_ payment method type no longer supports the manual capture_method for PaymentIntents. We still support synchronous and asynchronous automatic capture methods.
Why is this a breaking change?
We’re removing support for the manual capture_method for PaymentIntents that use the Interac payment method.
Impact
This change makes the behavior of the capture_method parameter consistent with the Interac network’s single-message behavior.
To use this version, update the capture_method in your integration to use automatic_ or automatic.
Setting the capture_method to either automatic_ or automatic means Stripe captures funds when the customer authorizes the payment.
If you need to manually capture card_ payments in addition to automatically captured interac_ payments, use the payment_method_options.card_present.capture_method parameter.
curl https://api.stripe.com/v1/payment_intents \ -u ":" \ -d amount=1099 \ -d currency=cad \ -d "payment_method_types[]=card_present" \ -d "payment_method_types[]=interac_present" \ -d capture_method=manualsk_test_Hrs6SAopgFPF0bZXSN3f6ELN
curl https://api.stripe.com/v1/payment_intents \ -u ":" \ -d amount=1099 \ -d currency=cad \ -d "payment_method_types[]=card_present" \ -d "payment_method_types[]=interac_present" \ -d "payment_method_options[card_present][capture_method]=manual"sk_test_Hrs6SAopgFPF0bZXSN3f6ELN
Upgrade
- View your current API version in Workbench.
- If you use an SDK, upgrade to the corresponding SDK version for this API version.
- If you don’t use an SDK, update your API requests to include
Stripe-Version: 2025-03-31.basil
- If you don’t use an SDK, update your API requests to include
- Upgrade the API version used for webhook endpoints.
- Test your integration against the new version.
- If you use Connect, test your Connect integration.
- In Workbench, perform the upgrade. You can roll back the version for 72 hours.
Learn more about Stripe API upgrades.
Related changes
- Updates the Vault and Forward API to return a 402 status code for upstream request timeouts
- Payment Methods won’t allow modifying fields for Naver Pay after the object is first created
- Partially capturing or canceling payments no longer creates a Refund
- Adds support for Klarna in the Hosted Invoice Page
- Adds ability to configure saved payment methods for one-time payments on the Hosted Invoice Page
- Adds support for saving and reusing Naver Pay payment methods
- Adds support for the Billie local payment method
- Adds support for the Satispay local payment method
- Makes the client parameter optional for WeChat Pay until confirmation
- Adds support for the New Zealand BECS Direct Debit local payment method