Back to monitors
Additive AI classification

Add bank connection & invoice fields; expand payment method support

Stripe added new optional fields to financial connections sessions (limits, manual_entry, bank_account_token), new invoice setting fields (custom_fields, description, footer) across multiple contexts (quotes, subscription schedules), and made the network field required on dispute payment method details. The changes also expand bank lists for payment methods and add a new API version. Since the network field is now required in a response schema, clients reading dispute data must handle this new field, but as a response field it does not break existing request logic.

Alert history

  • Additive

    Add bank connection & invoice fields; expand payment method support

    Stripe added new optional fields to financial connections sessions (limits, manual_entry, bank_account_token), new invoice setting fields (custom_fields, description, footer) across multiple contexts (quotes, subscription schedules), and made the network field required on dispute payment method details. The changes also expand bank lists for payment methods and add a new API version. Since the network field is now required in a response schema, clients reading dispute data must handle this new field, but as a response field it does not break existing request logic.

  • Additive

    Add new payment methods and balance transaction types

    The Stripe API adds support for new payment methods (sunbit and wechat_pay) in Checkout sessions, a new balance transaction type (tax_fund), new bank account status details structures, and new billing event types. It also adds optional payment method options parameters to the top-ups endpoint and expands API version enumeration. All changes are purely additive—existing integrations remain functional.

  • Additive

    Add Scalapay payment method details schema

    A new schema payment_method_details_payment_record_scalapay has been added to support Scalapay payment records with a transaction_id field. The response schema for payment records now correctly references this new schema instead of a non-existent one. This is purely additive and does not break existing integrations.

  • Additive

    New payment methods, capabilities, and schema fields added to Stripe API

    Several additive changes across the Stripe API spec:

    • New bizum_payments and scalapay_payments account capability fields added to the account capabilities schema.
    • New bizum and scalapay payment method types added to PaymentMethod creation requests and type enums.
    • New schemas added: balance_settings_resource_automatic_transfer_rule, balance_settings_resource_start_of_day; new fields automatic_transfer_rules_by_currency on balance_settings_resource_payouts and start_of_day on balance_settings_resource_settlement_timing.
    • The client_secret and redirect_on_completion field descriptions updated to replace ui_mode: embedded/custom with ui_mode: embedded_page/elements — this may reflect a renaming of enum values (potentially breaking if clients pass the old values).
    • Several request parameters (amount, charge, metadata, payment_intent, reason, refund_application_fee, reverse_transfer) removed from POST /v1/terminal/refunds.
    • New customer parameter added to test clock creation.
    • New API version 2026-05-27.dahlia added to the supported versions enum.
    • mastercard added to the description of terminal settlement network field with x-stripeBypassValidation: true.