- Breaking change
- API
API version 2026-09-07#
Balance transactions report fee charges as positive amounts (on a payment, the processing fee plus any add-on fees), name their timestamp occurred_at, and name the related resource in related_resource with resource_type and resource_id. Tax categories split into line_item_tax_category for items and charge_tax_category for charges, so the field name tells you which set of values applies.
- Your integrationKeeps working as it does today. Nothing moves to 2026-09-07 until you upgrade.
- Affects129 endpoints and 81 webhook events. See the ones you use
- Upgrade byNo deadline. 2026-02-01 is supported until at least September 7, 2028.
- Roll backFor 72 hours after you switch, the Versions screen can restore your previous version.
What changes
Balance transaction fee charges are positive and fee credits are negative.
Response and request shapeBefore (2026-02-01){ "amount_money": { "amount": 5000, "currency": "USD" }, "fee_money": { "amount": -225, "currency": "USD" }, "net_money": { "amount": 4775, "currency": "USD" } }After (2026-09-07){ "amount_money": { "amount": 5000, "currency": "USD" }, "fee_money": { "amount": 225, "currency": "USD" }, "net_money": { "amount": 4775, "currency": "USD" } }- What to do
- Read a positive
fee_moneyas a fee charged and a negative one as a fee returned.net_moneyis unchanged.
Balance transactions name their related resource in `related_resource`, with `resource_type` and `resource_id`.
Response and request shapeBefore (2026-02-01){ "related_object": { "object_id": "pi_01K1P6G4M7H2N8Q9R3S5T6V7WX", "object_type": "payment_intent" } }After (2026-09-07){ "related_resource": { "resource_id": "pi_01K1P6G4M7H2N8Q9R3S5T6V7WX", "resource_type": "payment_intent" } }- What to do
- Read
related_resource.resource_typeandrelated_resource.resource_idinstead ofrelated_object.object_typeandrelated_object.object_id.
Balance transactions use occurred_at for the transaction timestamp.
Response and request shapeBefore (2026-02-01){ "balance_transaction_id": "btxn_test", "created_at": "2026-09-06T12:34:56Z" }After (2026-09-07){ "balance_transaction_id": "btxn_test", "occurred_at": "2026-09-06T12:34:56Z" }- What to do
- Use
occurred_atinstead ofcreated_at.
Tax categories use line_item_tax_category for items and charge_tax_category for charges.
Response and request shapeBefore (2026-02-01){ "tax_category": "prepared_food" }After (2026-09-07){ "line_item_tax_category": "prepared_food" }- What to do
- Replace
tax_categorywithline_item_tax_categoryon product variants, modifiers, and line item taxes, and withcharge_tax_categoryon delivery methods and charge taxes. The schema list includes historical payloads: bundles no longer have tax category fields, and AvailableModifier is no longer published. - Affects
127 endpoints across 15 resources, most in Orders (24), Customer account (17), Subscriptions (16), Invoices (14).
Webhook events:
bundle.archivedbundle.createdbundle.updatedcheckout_session.closedcheckout_session.createdcheckout_session.expiredcheckout_session.invalidatedcheckout_session.paidcheckout_session.partially_paidcheckout_session.updateddelivery_method.activateddelivery_method.archiveddelivery_method.createddelivery_method.deactivateddelivery_method.updatedinvoice.collection_block_resolvedinvoice.collection_blockedinvoice.createdinvoice.creditedinvoice.issue_failedinvoice.issuedinvoice.late_fee_assessedinvoice.late_fee_dueinvoice.late_fee_waivedinvoice.marked_uncollectibleinvoice.overdueinvoice.paidinvoice.partially_paidinvoice.partially_refundedinvoice.refundedinvoice.reminder_dueinvoice.reopenedinvoice.sentinvoice.updatedinvoice.voidedmodifier_group.archivedmodifier_group.createdmodifier_group.updatedmodifier_set.archivedmodifier_set.createdmodifier_set.updatedorder.closedorder.createdorder.inventory_exception_createdorder.inventory_exception_resolvedorder.paidorder.partially_paidorder.partially_refundedorder.refundedorder.updatedpayment_link.createdpayment_link.updatedproduct.archivedproduct.createdproduct.updatedproduct_variant.archivedproduct_variant.createdproduct_variant.updatedsubscription.activatedsubscription.canceledsubscription.cancellation_scheduledsubscription.createdsubscription.cycle_skippedsubscription.delivery_action_requiredsubscription.delivery_pause_upcomingsubscription.delivery_updatedsubscription.dunning_exhaustedsubscription.end_upcomingsubscription.past_duesubscription.pausedsubscription.payment_succeededsubscription.plan_change_canceledsubscription.plan_change_scheduledsubscription.plan_changedsubscription.reactivatedsubscription.renewal_upcomingsubscription.resumedsubscription.trial_endingsubscription.updated
How to upgrade
- 1Read your impact report on the Versions screen. It lists the routes and webhook events you use that change.
- 2Test in test mode: send
Flint-Version: 2026-09-07, or install the SDK release built for it. - 3Move your merchant default on the Versions screen.
- 4Move webhook endpoints and partner apps that pin an older version.