Commerce
Money that settled, matched to the click.
Stripe knows what was charged, what was refunded, what was disputed and what reached the bank. Stripe does not know which ad preceded any of it, so the adapter carries a linking key set at checkout into payment metadata and matches it back on the payment itself. Fees, refunds and disputes arrive days after the charge, which is why early margin is marked provisional and restated as the ledger closes. Your finance system remains the authority on revenue recognition; Stripe supplies the movements, and Realvertising creates no charge, refund or payout of any kind.
In short: Stripe connects with a restricted API key or through Connect, and registers webhooks for payment, invoice, subscription, refund, dispute, balance transaction and payout events. Every event is stored against its event id and every settlement against its balance transaction id, so retries and replays converge on a single ledger row.
What it is
Stripe is the payment, subscription and payout rail behind a business's collected revenue. The integration is a read path for those movements plus one narrow write: metadata on customers, checkout sessions and payment intents linking each payment to its acquisition record.
What Realvertising receives
- Payment intents and charges with amount, currency, status and the metadata key linking the payment to a click and campaign.
- Invoices and subscription lifecycle events — created, upgraded, downgraded, paused, cancelled — with the amount billed in each period.
- Refunds, partial refunds, disputes and dispute outcomes, applied as adjustments against the original payment rather than as separate rows.
- Balance transactions and payouts: processing fees, dispute fees, currency conversion and the net amount settled to the account.
What it sends back
- Metadata on customers, checkout sessions and payment intents carrying the acquisition record, so a payment matches without a separate join table.
- Settlement-confirmed values onward to the channel adapters: the amount collected net of refunds is what returns to Google, Meta, Microsoft and TikTok as conversion value, not the amount booked at checkout.
- Nothing else. No charge, refund, payout, price or subscription is ever created or modified by Realvertising.
What this lets you ask
Questions this connection makes answerable.
- "What did we collect from customers whose first payment was recorded after a Meta click, net of refunds and dispute losses?"
- "Which campaigns are credited with subscriptions that churned inside two billing cycles?"
- "How much of last quarter's reported ROAS survives once Stripe fees and chargebacks are removed?"
How it connects
- 1Authorise with a restricted API key scoped to read payments, invoices, subscriptions, disputes and balance transactions, or connect the account through Stripe Connect if you run platform accounts.
- 2Confirm the webhook endpoint and the registered event types, then send a test event to verify deduplication on event id.
- 3Set the linking key at checkout — one metadata field or client_reference_id. Matched payments appear within the hour, and historical payments backfill across the window you choose.
Where it stops
- Stripe carries money, not journeys. Without a linking key written at checkout, a payment reconciles into financial truth but cannot be matched to a click, and no channel is credited with it.
- Fees, refunds and disputes settle late. A margin figure read on day one is provisional, and a chargeback can restate a month that was already reported.
- Currency conversion is Stripe's, at Stripe's rate and timing. Where your finance system books a different rate, the finance definition wins and the difference is shown rather than quietly absorbed.
Integrations
Everything the Growth Brain can read.
One goal. Every channel. Real business truth.
Connect your ad accounts, say what a good customer is worth, and let the Growth Brain work the objective inside limits you set.
No ad spend commitment · Connect one channel to start · [email protected]