Recurring revenue, traced back to where the customer came from.
Stripe knows what was charged. It does not know the customer arrived through a documentation page eleven weeks earlier, or which campaign paid for that visit. Reveliqo keeps Stripe's figure exactly as Stripe states it, and supplies the acquisition history that sits in front of it.
In short: Reveliqo treats Stripe as the record of what was actually charged — payments, subscriptions, upgrades, cancellations, refunds and recurring value — ingested idempotently so a retried webhook cannot inflate revenue.
What it is
Stripe processes payments and runs subscription billing: charges, invoices, plans, upgrades, downgrades, cancellations, disputes and refunds, emitting a webhook event for each. Those events are the closest thing most businesses have to an authoritative revenue log.
What this lets you ask
- “Which channels bring subscribers who are still paying six months later?”
- “What is a customer from paid search worth compared with one from organic?”
- “Which plan upgrades follow a visit to the pricing page, and which do not?”
What Reveliqo receives
- Successful payments with amount, currency and the customer they belong to
- Subscription lifecycle — started, upgraded, downgraded, paused, cancelled — with the plan on each side of the change
- Refunds, disputes and failed renewals, applied back to the period they belong in
- Recurring value per customer, so acquisition is measured against what a customer is worth over time rather than a first payment
How it is connected
- Connect the account through Stripe's own authorisation flow — read access only, and no card data is transferred
- Reveliqo registers the webhook endpoint and verifies the signature on every delivery
- Pass Reveliqo's pseudonymous customer key as Stripe metadata at checkout, so the payment joins the visit that produced it
- Set the reporting currency; Stripe's own exchange rate is used for conversion and stored with the event so a restated rate never silently rewrites history
How you verify it
- Net revenue for a closed day matches Stripe's balance report in the same currency
- Replaying a webhook delivery from the Stripe dashboard leaves the revenue figure unchanged — that is the idempotency key doing its job
- A test subscription shows its full path: landing page, channel, trial, first payment
Limits worth knowing
- Revenue joins to acquisition only when the customer key is passed at checkout. Without it the payment is still counted, accurately, but it sits outside channel attribution rather than being guessed into a channel.
- Reveliqo reports revenue as billed and collected. This is not accounting: recognition, deferral and tax treatment belong in your finance and accounting systems, and Reveliqo reads their outcome rather than restating it.
- Disputes and chargebacks settle weeks after the payment. They are applied back to the period of the original charge, so a closed month moves slightly when one resolves.
Other integrations
Connect the rest of the stack
Connect a site today. Read tomorrow's brief instead of building it.
Connect a site and the first brief arrives with the day's changes already explained — traffic separated from bots, conversions attached to revenue, and the evidence behind every sentence one click away.
Real people separated from bots Every answer shows its evidence Reveliqo runs on Reveliqo