Accounting and bookkeeping
Flint records money in two ledgers, and every row in both has a stable ID, a signed amount in minor units, and a link to the order, payment, refund, dispute, or invoice behind it. That's enough to keep complete books in any general ledger: post each row once, to the accounts suggested below, and tie every bank deposit back to the sales inside it.
- The balance ledger holds every movement of your Flint balance: payments, refunds, disputes, payouts, and the processing fees taken out of each. Read it as balance transactions.
- Merchant billing holds what you owe Flint and the account credit you hold: event fees, Flint's invoices to you, credits, and collections. Read it as merchant billing entries.
Flint doesn't include a QuickBooks, Xero, or NetSuite connector. You import the CSV reports each period, or build a sync from the API with the recipe at the end. The accounts and journal entries here are a starting point for that work; your accountant decides how your business books revenue, tax, and gift cards.
Choose your accounts#
Most businesses need these accounts for Flint activity. Rename them to fit your chart of accounts, and leave out the ones you'll never use, such as platform fee accounts if you don't run a partner app.
| Account | Type | What posts to it |
|---|---|---|
| Flint balance | Asset (clearing) | Every balance transaction's net_money. It should equal pending_money plus available_money plus held_money on your balance. |
| Flint reserve | Asset | reserve_hold and reserve_release rows: money Flint holds back that's still yours. It should equal reserve_money. |
| Payouts in transit | Asset | A payout between its payout row and the deposit landing in your bank. Optional: post straight to Bank if you prefer. |
| Bank | Asset | Payout deposits, inbound payouts, checks and wires you record on invoices. |
| Disputed funds | Asset | Chargeback principal Flint took while a dispute is open. |
| Accounts receivable | Asset | Issued invoices, until they're paid, credited, or written off. |
| Credit with Flint | Asset | Account credit Flint issued you and you haven't used: available_credit_money on the merchant billing balance. |
| Due to Flint | Liability | What you owe Flint: outstanding_money on the merchant billing balance. |
| Sales tax payable | Liability | Tax you collected, less tax you refunded or credited. |
| Tips payable | Liability | Tips you collected for staff, if you pay them out. |
| Gift card liability | Liability | Unspent gift card value. |
| Deferred revenue | Liability | Payments for deliveries or service periods you haven't provided yet. |
| Sales | Income | Merchandise and services, net of discounts if you don't track them separately. |
| Shipping and delivery income | Income | Order charges such as delivery, service, or handling fees. |
| Discounts | Contra-income | Discounts on orders, if you track them separately from sales. |
| Sales returns and allowances | Contra-income | Refunds and credit notes. |
| Chargeback losses | Expense or contra-income | Disputes you lost. |
| Processing fees | Expense | Flint's processing fee and add-on fees on each payment. |
| Platform fees paid | Expense | Fees a partner app charged on your payments. |
| Dispute fees | Expense | Processor dispute fees, and dispute event fees in merchant billing. |
| Flint fees and subscription | Expense | Other event fees, Flint's invoices to you, and the custom domain add-on. |
| Bad debt | Expense | Invoices you write off. |
If you run a partner app that charges platform fees, add three accounts: Platform fee revenue (income), Platform fee receivable (asset), and Platform fee reserve (asset). If you collect payments for other sellers, add an account for marketplace splits.
Group every account's activity by currency. Flint never converts amounts, and each row carries its own currency.
Map the balance ledger#
Each balance transaction becomes one journal entry. Post its net_money to Flint balance, its fee_money to the fee account, and its amount_money to the account in the table. The entry balances because net_money is amount_money minus fee_money. Balance transaction types describes each type in full.
type | Sign of amount_money | Post amount_money against | Post fee_money to |
|---|---|---|---|
payment | Positive | Sales, shipping income, sales tax payable, and tips payable from the order. Accounts receivable for an invoice payment. Gift card liability for a gift card sale. Deferred revenue for prepaid periods. | Processing fees, and Platform fees paid for the platform_fee part of fee_details |
refund | Negative | Sales returns and allowances, and sales tax payable for the tax it refunds | None (fee_money is 0) |
recovery | Positive | Reverse the failed refund: Sales returns and allowances | None |
return | Negative | Reverse the payment: Accounts receivable for an invoice payment, which reopens, otherwise Sales returns and allowances | None |
dispute | Negative | Disputed funds | Dispute fees |
dispute_reversal | Positive | Disputed funds | Dispute fees (a negative fee is a fee returned) |
payout | Negative | Payouts in transit, or Bank | None |
payout_failure, payout_cancellation, payout_reversal | Positive | Payouts in transit, or Bank: the money came back | None |
inbound_payout | Positive | Bank | None |
inbound_payout_failure | Negative | Bank | None |
reserve_hold | Negative | Flint reserve: the money moves into it | None |
reserve_release | Positive | Flint reserve: the money moves out of it | None |
merchant_billing_collection | Negative | Due to Flint | None |
merchant_billing_collection_reversal | Positive | Due to Flint | None |
platform_fee_refund | Positive | Platform fees paid | None |
platform_fee_payout, platform_fee_payout_reversal | Positive, negative | Platform fee receivable | None |
payment_split and the other split types | Either | Your marketplace splits account. See Marketplaces. | None |
adjustment | Either | Read description. A returned processing fee goes to Processing fees. | None |
payout_advance, payout_advance_funding | Either | A liability for the advance. Most accounts never see these. | None |
other | Either | A suspense account, until you've read description | The same suspense account |
Filter on type, not on the sign of amount_money: several types post negative. Reconciliation covers each field.
Map merchant billing#
Each merchant billing entry changes what you owe Flint (outstanding_effect_money) or the credit you hold (available_credit_effect_money). Post the first to Due to Flint and the second to Credit with Flint, against the account in the table.
type | Debit | Credit |
|---|---|---|
event_fee with event_fee_type card_dispute, card_dispute_countered, or ach_dispute | Dispute fees | Due to Flint |
event_fee, any other event_fee_type | Flint fees and subscription | Due to Flint |
invoice | Flint fees and subscription, for subtotal_money | Due to Flint |
custom_domain | Flint fees and subscription | Due to Flint |
custom_domain_collection | Due to Flint | The account that paid it. See the note below. |
correction (positive) | The fee it corrects: Processing fees when it carries payment_intent_id and corrects a processing fee, otherwise the entry named by related_merchant_billing_entry_id | Due to Flint |
correction (negative) | Due to Flint | The fee it corrects |
credit_issued | Credit with Flint | Flint fees and subscription, or other income, as your accountant prefers |
credit_applied | Due to Flint | Credit with Flint |
credit_refunded | The account the money arrived in | Credit with Flint |
collection | Don't post. The merchant_billing_collection balance transaction already did. | |
collection_reversal | Don't post. The merchant_billing_collection_reversal balance transaction already did. | |
write_off | Due to Flint | The expense account of the charge Flint stopped collecting, or other income |
A custom_domain entry and its custom_domain_collection are recorded together for the same amount and carry no balance_transaction_id. Depending on your agreement, Flint takes the charge from your Flint balance or from the billing card on file, so post the collection against Flint balance or the card's account once you've matched the payment.
Your Due to Flint account should equal the sum of outstanding_money across your merchant billing balances, and Credit with Flint should equal available_credit_money.
Don't count the same money twice#
Several Flint records describe the same activity from different angles. Post each from one source:
- Collections live in both ledgers. When Flint collects what you owe, the
merchant_billing_collectionbalance transaction and thecollectionbilling entry are the same money, linked by the entry'sbalance_transaction_id. Post the balance transaction, which moves your Flint balance, and skip the entry. - A dispute fee appears once. A processor dispute fee deducted from your balance is in the
disputerow'sfee_money, and it never also appears as acard_disputeevent fee. A fee Flint paid on your behalf is an event fee in merchant billing instead. Post both sources, and each fee lands once. - The processing fee stays on the payment. It's in the
paymentrow'sfee_moneyand inpayments_itemized_v1. Merchant billing holds only latercorrectionentries to it, so post the correction as a change, not as a second fee. - An invoice and its order are one sale. An invoice can link to an order, and the order's totals describe the same sale. Book invoiced sales from the invoice and its payments, and don't add the order's totals to sales. Reports say the same: don't add invoice totals to order sales.
- A payment is cash, not a second sale. When you book revenue from orders or invoices, the
paymentrow clears that revenue or receivable into Flint balance. It isn't more revenue. - Gift cards move value, not cash, when spent. The cash arrives when the card is sold. A redemption moves value from gift card liability to sales and posts no balance transaction.
- Flint's
invoiceentries are bills to you. Theinvoicetype in merchant billing is Flint invoicing your Flint subscription, not your invoices to customers. - Pick one export per ledger.
payments_itemized_v1,balance_transactions_itemized_v1, andpayouts_itemized_v1overlap. Post from balance transactions, and use the other two to check fees and deposits.
Cash or accrual#
Accrual books record revenue when you earn it; cash books record it when the money arrives. Flint gives you the timestamp for each:
| Activity | Accrual: book it at | Cash: book it at |
|---|---|---|
| Order sale | Order.paid_at, or the fulfillment's completed_at if you recognize goods on delivery | The payment row's occurred_at |
| Invoice | Invoice.issued_at, to Accounts receivable | The payment row's occurred_at, or a manual payment's received_at |
| Refund | Each refund part's succeeded_at in Refund.tender_allocations | The refund row's occurred_at |
| Credit note | Each allocation's allocated_at, or the linked refund's part succeeded_at | The linked refund's refund row |
| Dispute | The dispute row's occurred_at; the outcome at Dispute.status_changed_at | The dispute and dispute_reversal rows' occurred_at |
| Processing fees | The payment row's occurred_at. Fees are final at capture for cards and when an ACH debit succeeds. | The same |
| Flint's charges to you | The billing entry's occurred_at | The merchant_billing_collection row's occurred_at |
| Gift cards | Each gift card transaction's posted_at | The sale's payment row |
| Subscription periods | Spread across the period the charge paid for | The payment row's occurred_at |
| Payouts | A transfer between Flint balance and Bank, at arrival_date | The same |
On either basis, a payout isn't income: it moves money you already booked from Flint balance to Bank. Most bookkeepers treat a sale's cash as received when it reaches your Flint balance, at occurred_at, rather than when the payout lands.
Every timestamp in the API is UTC. Close a period at midnight in your own time zone by sending that instant with its offset, as the report intervals do.
Worked journal entries#
The examples use USD and round example fees. Read the real fee from each payment's fee_money; don't recompute it from your rates.
A sale with tax#
Order 1042 sells $48.00 of goods with a $5.00 discount, a $6.00 delivery charge, $3.72 of sales tax, and a $5.00 tip, for a $57.72 total. The card payment posts a payment balance transaction with amount_money 5772, fee_money 197, and net_money 5575.
| Account | Debit | Credit |
|---|---|---|
| Flint balance | 55.75 | |
| Processing fees | 1.97 | |
| Discounts | 5.00 | |
| Sales | 48.00 | |
| Shipping and delivery income | 6.00 | |
| Sales tax payable | 3.72 | |
| Tips payable | 5.00 |
Take the split from the order's pricing_amounts or an orders_itemized_v1 row: subtotal_money, discount_money, charge_money, additive_tax_money, and requested_tip_money. With inclusive tax, the prices already contain it: move inclusive_tax_money out of Sales, or the charge it's in, and into Sales tax payable. For tax owed to each jurisdiction, use the tax reports.
A refund#
The buyer returns one $20.00 item from order 1042, and you refund it with its $1.73 of tax. The refund posts a refund row with amount_money -2173 and fee_money 0.
| Account | Debit | Credit |
|---|---|---|
| Sales returns and allowances | 20.00 | |
| Sales tax payable | 1.73 | |
| Flint balance | 21.73 |
The original processing fee isn't returned, so it stays in Processing fees. Read the split from the refund's line_item_allocations, charge_allocations, tax_breakdown_refunds, and refunded_tip_money. A refund to store credit, with destination new_gift_card, posts no balance transaction: credit Gift card liability instead of Flint balance. A refund you paid outside Flint has processed_by merchant and posts no balance transaction: credit Bank.
A dispute: opened, won, or lost#
A buyer disputes a $50.00 card payment. The dispute row has amount_money -5000 and, when the processor deducted its $15.00 dispute fee from your balance, fee_money 1500, for net_money -6500.
| When | Account | Debit | Credit |
|---|---|---|---|
| Opened | Disputed funds | 50.00 | |
| Dispute fees | 15.00 | ||
| Flint balance | 65.00 | ||
| Won | Flint balance | 50.00 | |
| Disputed funds | 50.00 | ||
| Lost | Chargeback losses | 50.00 | |
| Disputed funds | 50.00 |
A win posts a dispute_reversal row for the principal. If the processor also returns the fee, that row's fee_money is negative, or a separate row returns it; post that to Dispute fees. A won status alone doesn't mean the fee came back. A loss posts no balance transaction: book it when the dispute reaches lost, at status_changed_at, or when dispute.lost arrives. Inquiries move no money. An ACH bank return also posts a dispute row; on an invoice payment it reopens the invoice, so debit Accounts receivable instead of Disputed funds.
If Flint paid the processor's fee for you, the dispute row has fee_money 0 and the fee arrives as a card_dispute event fee in merchant billing: debit Dispute fees and credit Due to Flint. Disputes shows what each outcome costs.
A payout#
A $132.85 payout posts one payout row with amount_money -13285, and lands in your bank on its arrival_date.
| When | Account | Debit | Credit |
|---|---|---|---|
payout row | Payouts in transit | 132.85 | |
| Flint balance | 132.85 | ||
| Deposit lands | Bank | 132.85 | |
| Payouts in transit | 132.85 |
To show what the deposit carried, list its rows with GET /v1/balance-transactions?payout_id=..., or use payouts_itemized_v1, Flint's settlement report: for each paid payout, its rows' net_money adds up to the deposit. You've already posted each of those rows, so the list is a check, not more entries. Match a deposit to its contents has the steps. If the payout fails or is reversed, post the payout_failure or payout_reversal row against Payouts in transit or Bank.
A platform fee#
A partner app charges a $1.50 platform fee on a $100.00 payment, and Flint's own fees are $3.20. On the merchant's balance, the payment row has fee_money 470, and fee_details splits it into flint 320 and platform_fee 150.
The merchant books:
| Account | Debit | Credit |
|---|---|---|
| Flint balance | 95.30 | |
| Processing fees | 3.20 | |
| Platform fees paid | 1.50 | |
| Sales | 100.00 |
The platform reads its fee with its own merchant's credentials, from GET /v1/platform-fees and GET /v1/platform-fee-balance-transactions. By default, Flint holds 20% of each fee in a reserve for about 120 days. When the fee succeeds, the platform books:
| Account | Debit | Credit |
|---|---|---|
| Platform fee receivable | 1.20 | |
| Platform fee reserve | 0.30 | |
| Platform fee revenue | 1.50 |
Flint pays available fees into the platform's own Flint balance daily. That posts a platform_fee_payout balance transaction on the platform's balance: debit Flint balance, credit Platform fee receivable. When the reserve is released, move it from Platform fee reserve to Platform fee receivable; when it covers a merchant's loss (loss_coverage), expense it.
If the partner app returns its fee on a refund, the merchant gets a platform_fee_refund row (debit Flint balance, credit Platform fees paid), and the platform's ledger debits a platform_fee_refund (debit Platform fee revenue, credit Platform fee receivable). Platform fees has the refund rules.
A gift card sale and redemption#
A buyer pays $50.00 by card for a $50.00 gift card. The payment row has fee_money 175.
| Account | Debit | Credit |
|---|---|---|
| Flint balance | 48.25 | |
| Processing fees | 1.75 | |
| Gift card liability | 50.00 |
Later the holder spends $43.30 of it on an order with $40.00 of goods and $3.30 of tax. No money moves, so there's no balance transaction:
| Account | Debit | Credit |
|---|---|---|
| Gift card liability | 43.30 | |
| Sales | 40.00 | |
| Sales tax payable | 3.30 |
Find gift card sales in orders_itemized_v2, where gift_card_consideration_money is what buyers paid for gift cards and merchandise_subtotal_money excludes it. Find redemptions in the order's gift_card_settlements or in GET /v1/gift-card-transactions?transaction_type=redeem&posted_after=.... A card sold below face value, such as a $25.00 card for $22.00, adds $25.00 of liability and $22.00 of consideration. How to book the difference and unspent value is your accountant's call. Check the account each period against closing_money in the gift_card_liability_v1 report. See Gift cards.
A prepaid subscription#
A gift box plan charges once for six monthly deliveries at $30.00 each, with $6.00 shipping per delivery. The signup order is delivery 1 and carries a "Box, deliveries 2 to 6" line for the other five, plus their shipping as one charge. The buyer pays $216.00 and the payment row has fee_money 656. There's no tax in this example.
| When | Account | Debit | Credit |
|---|---|---|---|
| Payment | Flint balance | 209.44 | |
| Processing fees | 6.56 | ||
| Sales | 30.00 | ||
| Shipping and delivery income | 6.00 | ||
| Deferred revenue | 180.00 | ||
| Each later delivery | Deferred revenue | 36.00 | |
| Sales | 30.00 | ||
| Shipping and delivery income | 6.00 |
Flint creates each later delivery as its own order with prepayment_order_id pointing at the paying order, subscription_delivery_number from 2 to 6, and its merchandise discounted to zero. Recognize the deferred amount when that order's fulfillment completes, and don't book the zero-value order as a sale. Prepaid deliveries has the details.
For a service paid in advance, such as a $120.00 yearly plan, credit Deferred revenue with the whole charge and move $10.00 to Sales each month of the period. The cycle's order has subscription_id and subscription_cycle but not the period's dates, so store current_period_start_at and current_period_end_at from the subscription.payment_succeeded event for that charge.
A credit note#
You issued invoice 0042 for $1,000.00 of services plus $80.00 of tax, then credit $100.00 of it, with its $8.00 of tax, before the buyer pays.
| When | Account | Debit | Credit |
|---|---|---|---|
| Invoice issued | Accounts receivable | 1,080.00 | |
| Sales | 1,000.00 | ||
| Sales tax payable | 80.00 | ||
| Credit allocated | Sales returns and allowances | 100.00 | |
| Sales tax payable | 8.00 | ||
| Accounts receivable | 108.00 |
Each credit note line has its own tax_money. Issuing a note on its own moves nothing: book it when it's allocated or refunded. On a paid invoice, a refund of the note posts a refund row whose refund carries credit_note_id: credit Flint balance instead of Accounts receivable. A refund you record as paid outside Flint posts no balance transaction: credit Bank. Reversing an allocation reverses the entry. See Credit notes.
Invoice payments and write-offs#
| Event | Debit | Credit |
|---|---|---|
| Paid online through Flint | Flint balance (net_money) and Processing fees (fee_money, including the invoice collection add-on fee) | Accounts receivable |
| Check or wire recorded as a manual payment | Bank, or an undeposited funds account | Accounts receivable |
| Manual payment reversed | Accounts receivable | Bank |
| Invoice marked uncollectible | Bad debt | Accounts receivable |
Use receivables_aging_v1 to check Accounts receivable against your invoices as of any date; see Receivables aging.
What you owe Flint#
Flint invoices your $49.00 subscription, applies $10.00 of account credit, and collects the remaining $39.00 from your Flint balance. Merchant billing has an invoice entry, a credit_applied entry, and a collection entry, and your balance has a merchant_billing_collection row for -3900.
| When | Account | Debit | Credit |
|---|---|---|---|
invoice entry | Flint fees and subscription | 49.00 | |
| Due to Flint | 49.00 | ||
credit_applied entry | Due to Flint | 10.00 | |
| Credit with Flint | 10.00 | ||
merchant_billing_collection row | Due to Flint | 39.00 | |
| Flint balance | 39.00 |
The collection entry is the same $39.00 as the balance transaction, so it gets no entry of its own.
Build a sync that's safe to re-run#
A sync reads Flint, writes journal entries into your accounting system, and can run again at any time without creating duplicates. It needs three things: one journal entry per Flint record, keyed by that record's ID; a cursor per list so each pass reads only what may have changed; and a final check at period close.
Key every entry by a Flint ID#
Write the source ID into the journal entry's reference or memo field, and look it up before you create anything:
- One entry per balance transaction, keyed by
balance_transaction_id(btxn_). - One entry per merchant billing entry that you post, keyed by
merchant_billing_entry_id(mbe_). - One entry per accrual event you book from a business object: an invoice by
invoice_id, a credit note allocation bycredit_note_allocation_id, a manual payment byinvoice_manual_payment_id, a gift card redemption by its gift card transaction ID, a lost dispute bydispute_id.
If an entry with that key exists, update or skip it; never create a second. Flint never deletes a ledger row or changes its amounts. Money that comes back posts a new row, such as a recovery or payout_failure, so it gets a new entry.
Read each list with a cursor#
| Records | How to read changes | Notes |
|---|---|---|
| Balance transactions | occurred_after and occurred_before on GET /v1/balance-transactions | Rows can be recorded after they occurred while Flint reconciles your processor's history, so re-read a trailing window, such as the last 24 hours, on every pass. Only status and payout_id change on an existing row. |
| Merchant billing entries | created_after on GET /v1/merchant-billing-entries | Overlap passes by a few minutes. See Sync new entries. |
| Orders, payment intents, refunds, disputes, invoices, subscriptions | updated_after with an overlap of a few minutes | Keep the copy with the higher version where the object has one, or the later updated_at. |
| Payouts | created_after, then re-read each payout that isn't final by ID | The list has no updated_after filter, and a succeeded payout can still be reversed. |
| Credit notes | created_after, plus credit_note.* and credit_note_allocation.* events | The list has no updated_after filter, and an issued note keeps changing as you allocate and refund it. |
| Manual payments | GET /v1/invoices/{invoice_id}/manual-payments for each invoice your updated_after pass returned | There's no list across invoices. |
| Gift card transactions | posted_after on GET /v1/gift-card-transactions | Postings never change. |
| Platform fee ledger | occurred_after on GET /v1/platform-fee-balance-transactions | For platforms only. |
Read every page of a pass, passing next_page_token as page_token until it's absent, and move your cursor only after the last page. A page token only works with the query it came from. Pagination has a loop you can copy.
curl "https://api.withflintpay.com/v1/balance-transactions?currency=USD&occurred_after=2026-11-20T00:00:00Z&page_size=100" \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Flint-Version: 2026-09-07"
Send Flint-Version: 2026-09-07 or later. Earlier versions report fee_money with the opposite sign; see Older API versions.
Use webhooks to start a pass#
Webhooks tell you something changed sooner than a schedule would. Treat each one as a reason to read, not as the record:
Events can arrive more than once, out of order, or late while a delivery is retried. Fetch the object with GET and write what it says now, so a replayed event or one that arrives early changes nothing. Keep the scheduled pass running too: it picks up anything a missed delivery would have carried. Webhooks covers delivery and retries.
Close the period#
Before you lock a month in your accounting system:
- Run a final pass over the month with no cursor shortcuts.
- Check that
meta.historyis absent on the balance transaction list, which means Flint's history is complete. See Close a period. - Generate
balance_transactions_itemized_v1andmerchant_billing_itemized_v1for the month. Flint generates them only once the interval is complete, and fails them withdata_unavailableotherwise. Compare their row IDs and totals with what you posted. - Check that Flint balance and Flint reserve match your balance, and that Due to Flint and Credit with Flint match your merchant billing balance.
Credentials#
Call these routes with the merchant's own API key. Give it read scopes only, such as money_movement.balance_transactions.read, merchant_billing.read, commerce.orders.read, and reports.write if the sync generates reports. A partner app token can read balance transactions and payouts when its grant holds their scopes, but it can't call report routes or read merchant billing. See Authentication and API key security.
Records without their own report#
Some records you'll book have no report type yet. Read them from the API instead:
- Refunds. There's no refunds report.
refundrows inbalance_transactions_itemized_v1carry the refund ID inrelated_resource.resource_id, andGET /v1/refunds?updated_after=...returns the allocations and tax. Refunds you recorded as paid outside Flint post no balance transaction, so read them from the refunds list. - Credit notes. There's no credit notes report. List them with
GET /v1/credit-notes, and check each invoice'scredited_moneyininvoices_itemized_v1. - Checks and wires. There's no report or cross-invoice list of manual payments. Read each invoice's manual payments, or follow
invoice_manual_payment.createdandinvoice_manual_payment.reversed.paid_moneyininvoices_itemized_v1includes them. - Invoice on a payment.
payments_itemized_v1has noinvoice_idcolumn. The payment intent hasinvoice_id, so read it withGET /v1/payment-intents/{payment_intent_id}, or list an invoice's payments withGET /v1/payment-intents?invoice_id=.... When the invoice has an order,order_idalso joins the payment toinvoices_itemized_v1. - Subscription on an order.
orders_itemized_v1andorders_itemized_v2have nosubscription_idcolumn. The order hassubscription_id, andGET /v1/orders?subscription_id=...lists a subscription's orders. For invoiced subscriptions,invoices_itemized_v1hassubscription_id.
Next steps#
ReconciliationReportsMerchant billingPayoutsReady to connect your books? Create a Flint account and run the sync against your sandbox first.