[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fCgyhyPkEV1-PGWZ549lx_1vJZSDe-VWiAb1bedrOhM8":3,"$fKElXxbqSV-q_AUBewU9Ulk6DvkAJLQR43quH9VN1vQw":21},{"status":4,"source":5,"previous":12,"current":16,"newerSnapshotId":20,"olderSnapshotId":13},"has-previous",{"id":6,"displayName":7,"vendor":8,"kind":9,"apiType":10,"url":11},"stripe-openapi","Stripe API","stripe","openapi-json","rest","https:\u002F\u002Fraw.githubusercontent.com\u002Fstripe\u002Fopenapi\u002Fmaster\u002Fopenapi\u002Fspec3.json",{"id":13,"contentHash":14,"fetchedAt":15},"01KVVBCR06D2TW9RWQ6HX5G8VV","e24a26de4188fd64dec4c043d5d3726277fdcb07556a493ea481c305b0a223d8","2026-06-23T23:00:06.422Z",{"id":17,"contentHash":18,"fetchedAt":19},"01KWFQPP18HDARFGHTQXWG9HYE","612e33747bcff2f538165eb3f89d0c0c99384d68a0659211357f79ef0cafa6d6","2026-07-01T21:00:03.546Z",null,{"alerts":22},[23,30,36,43],{"id":24,"severity":25,"title":26,"summary":27,"contentHash":18,"detectedAt":28,"slug":29},"01KWFQPZ3Z8MDKBP6QV33B91FA","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.","2026-07-01T21:00:14.335Z","2026-07-01-add-bank-connection-and-invoice-fields-expand-payment",{"id":31,"severity":25,"title":32,"summary":33,"contentHash":14,"detectedAt":34,"slug":35},"01KVVBCZKZ1CZ47FRGWS32P1JB","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.","2026-06-23T23:00:15.615Z","2026-06-23-add-new-payment-methods-and-balance-transaction-types",{"id":37,"severity":25,"title":38,"summary":39,"contentHash":40,"detectedAt":41,"slug":42},"01KSAEQWCSMP5VRS1Q3SGVTJFK","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.","7c7b7b0c3b02c899fb3a0301d99b8489b9e5f7bfd2ca699994b459abc09914e8","2026-05-23T13:00:09.497Z","2026-05-23-add-scalapay-payment-method-details-schema",{"id":44,"severity":25,"title":45,"summary":46,"contentHash":47,"detectedAt":48,"slug":49},"01KSABAQ519V08VZGB8FVS15RA","New payment methods, capabilities, and schema fields added to Stripe API","Several additive changes across the Stripe API spec:\n- New **`bizum_payments`** and **`scalapay_payments`** account capability fields added to the account capabilities schema.\n- New **`bizum`** and **`scalapay`** payment method types added to `PaymentMethod` creation requests and type enums.\n- 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`.\n- The `client_secret` and `redirect_on_completion` field descriptions updated to replace `ui_mode: embedded`\u002F`custom` with `ui_mode: embedded_page`\u002F`elements` — this may reflect a renaming of enum values (potentially breaking if clients pass the old values).\n- Several request parameters (`amount`, `charge`, `metadata`, `payment_intent`, `reason`, `refund_application_fee`, `reverse_transfer`) removed from `POST \u002Fv1\u002Fterminal\u002Frefunds`.\n- New `customer` parameter added to test clock creation.\n- New API version `2026-05-27.dahlia` added to the supported versions enum.\n- `mastercard` added to the description of terminal settlement `network` field with `x-stripeBypassValidation: true`.","e36ef23113744a09b4a9101473bd4dc036420180a66256e84fe4670f93a3d536","2026-05-23T12:00:32.417Z","2026-05-23-new-payment-methods-capabilities-and-schema-fields-added-to"]