Deprecates manual capture method for Interac cardsBreaking changes
What’s new
The interac_ payment method type no longer supports the manual capture_method for Payment Intents. We still support synchronous and asynchronous automatic capture methods.
Why is this a breaking change?
We’re deprecating support for the manual capture_method for Payment Intents 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.
Upgrade
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 once 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