Skip to content

Integration Overview

Stripe is Adventive’s payment processor and the system of record for invoices, payments, and payouts. This section describes how Stripe fits into the wider billing flow, the Stripe objects an operator will touch, and how money moves from a customer to Adventive’s bank account. Read it once before working in the Dashboard so the terms in sections 02 and 03 land in context.

Today, billing line items accumulate in Adventive’s systems through the month. An operator triggers a month-end run, Adventive’s billing_service assembles the line items and calls the Stripe Invoice API, and a custom-branded PDF is generated and delivered by email. Stripe owns everything from the finalized invoice onward: hosting the invoice, collecting payment, holding funds, and paying out. The migration to Stripe-native subscription billing is tracked separately in projects/stripe-billing-transition/; this SOP documents the account as it operates now.

The boundary matters for operations: Adventive owns invoice assembly and presentation; Stripe owns collection, settlement, and reconciliation. Every task in this SOP is on the Stripe side of that line.

Adventive × Stripe, money-in to payout ADVENTIVE Admin / billing_service Line-item rollup, PDF render Mailgun delivery Invoice email to customer create invoice STRIPE ACCOUNT acct_17YHT3CSGXf35AB6 Customer One per invoiced account; holds cash balance Invoice draft → open → paid / void PaymentIntent · Charge The attempt and the settled payment Customer Cash Balance Bank-transfer funds awaiting reconciliation Balance → Payout Settled funds paid to Adventive bank

Credit notes reduce an open invoice’s amount due

CUSTOMER PAYS BY Card ACH bank transfer Domestic / international wire funds in ADVENTIVE BANK Connected payout account Receives payouts on schedule payout DOWNSTREAM Acodei Stripe event connector QuickBooks Accounting system of record events

Stripe models the account as a small set of related objects. Knowing which is which prevents most reconciliation confusion.

ObjectWhat it representsWhere it appears
CustomerOne invoiced Adventive account. Holds saved payment methods and the customer’s cash balance.Customers page; linked from every invoice.
InvoiceA bill for a customer. Moves through a defined lifecycle (see 02). Accepts credit notes while open or paid.Invoices page.
PaymentIntentA single attempt to collect money for an invoice or checkout. Tracks the lifecycle of that attempt.Payments page; linked from the invoice.
ChargeA settled payment. The money actually captured from a card or bank transfer.Payments page; linked from the PaymentIntent.
Customer Cash BalanceFunds Stripe received by bank transfer for a customer that are not yet applied to an invoice. Central to 03.Customer detail → Cash balance.
Credit NoteA reduction against an invoice. On an open invoice it lowers the amount due; on a paid invoice it refunds or credits the customer.Invoice detail → More → Issue a credit note.
PayoutA transfer of settled funds from the Stripe balance to Adventive’s connected bank account.Balance → Payouts.
  1. Invoice created and finalized. Adventive assembles the invoice and finalizes it in Stripe. It becomes open and is delivered to the customer.
  2. Customer pays. Payment arrives by card, ACH, or wire. Card and ACH-debit payments attach directly to the invoice. Bank transfers (ACH credit and wires) land in the customer’s cash balance first, then Stripe attempts to reconcile them to an open invoice.
  3. Reconciliation. For a bank transfer, Stripe matches the incoming funds to an invoice by memo reference or exact amount. On a match, it applies the funds and marks the invoice paid. If it cannot match, the funds stay in the cash balance as unapplied: this is the exception section 03 exists to resolve.
  4. Settlement and payout. Captured funds accrue in the Stripe balance and pay out to Adventive’s connected bank account on the account’s payout schedule.
  5. Downstream sync. Stripe events flow to Acodei, which posts the corresponding entries to QuickBooks. Actions taken in Stripe: payments, credit notes, refunds, propagate along this path, so reconciliation done correctly in Stripe keeps the books correct downstream.

Stripe’s platform behavior changes over time. For anything Stripe owns, treat these as the source of truth over memory: