Adds support for BLIK recurring off-session payments
What’s new
Adds support for BLIK recurring off-session payments in Poland. You can accept recurring off-session BLIK charges by creating Mandates with your customers.
This release adds the following BLIK functionality:
- Accounts v1 support for the blik_recurring_payments capability.
- Accounts v2 support for blik_recurring_payments in:
- The merchant capabilities configuration
- requirements and future requirements entries that restrict capabilities
- Merchant capability status updates.
- PaymentIntents, SetupIntents, and Checkout Sessions now include a mandate_options parameter in BLIK payment method options.
- PaymentIntents now include off_session as a value for setup_future_usage in BLIK payment method options.
- SetupIntents now include a blik payment method options parameter.
- Mandates now include BLIK payment_method_details including the expires_at and type properties.
- Checkout Sessions now include BLIK payment method options on setup_intent_data and subscription_data
- BLIK descriptions for Subscriptions, Invoices, Customers, and Quotes now reflect support for automatic charge collection.
Impact
To collect recurring off-session BLIK payments in Poland:
- Follow the BLIK recurring payments guide
- Create mandates through PaymentIntents or SetupIntents
- Make sure that both the blik_payments and blik_recurring_payments capabilities are active on your account.
For Accounts v2, request blik_ through configuration.merchant.capabilities. Monitor account requirements and merchant capability status updates to determine when the capability is active.
If your integration already accepts one-time BLIK payments, provide mandate_data.customer_acceptance to create a mandate. You can also pass mandate_ and set setup_ to off_ in your BLIK payment method options.
Changes
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: 2026-09-30.endive
- 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.
Learn more about Stripe API upgrades.
Related changes
- Removes the payment method types parameter from Checkout Sessions
- Adds support for Data Share Only for 3D Secure authentication
- Makes Payment Evaluation signal scores nullable
- Removes PayTo-specific fields from Payment Methods
- Removes the payment method types parameter from Payment Intents and Setup Intents
- Returns specific decline codes for BLIK payment failures
- Deprecates the payment request button
- Shows pending-authorization UI for MB WAY, Bizum, and BLIK with stripe.handleNextAction
- Removes support for the payment method types option in Elements
- Saves Bancontact payment details for future off-session payments in Checkout
- Adds the Standalone 3D Secure API
- Adds support for SeQura payments
- Adds card-present payment methods to allowed payment method types
- Adds Link funding source group details on Payment Records
- Adds early fraud warnings and fraudulent dispute signals for Payment Evaluations
- Adds the ability to report canceled payments
- Adds support for expanding the mandate on card payment method details
- Adds the Payment Record property to the Payment Intent object
- Adds Link wallet details to Payment Records for card payments
- Adds 3D Secure versions 2.3.0 and 2.3.1 to Payment Records
- Adds PayPay support for one-time online payments in Japan
- Exposes the network response electronic commerce indicator on card charges
- Adds payment method type information for failed payments
- Adds MoMo payment method details to Payment Records