RevGlanceConnecting sources
How sources, keys, webhooks and syncs work, whichever provider you use.
A source is one account at a payment provider, connected to one business. A business can have several sources, also of the same provider: a Stripe account and an App Store app, or two Stripe accounts. Owners and admins connect sources; viewers see them.
Supported providers
Providers marked beta were built and tested against the provider's documentation but have not yet been run against a live account. Tell us if a number differs from the provider's own reports.
Keys
Every source connects with a key you create in the provider. RevGlance stores credentials encrypted, never shows them again, and only reads. Prefer a restricted or read-only key wherever the provider offers one.
Two features can write, and only when you allow it on the key:
- Recovery emails can create an update-card link (a Stripe portal session, a Polar customer session, a Paddle update-payment transaction).
- In privacy mode, sending recovery or survey emails asks the provider for the customer's address at send time.
Syncing
- The first sync reads everything the provider keeps, except where the provider limits it (the App Store keeps a year of daily reports).
- Later syncs read from three days before the last one, so late changes are caught. Current state, like subscriptions, is read in full.
- Sources sync every hour while someone uses the business. When nobody has signed in for 30 days, they sync once a day; coming back syncs anything older than an hour.
- Sync now in the top bar's sync status syncs every source of the business at once.
When a provider refuses a request, the source shows the error under its name in Settings › Sources. A partial sync keeps its place, so the next run reads the same window again.
Webhooks
A webhook lets the provider tell RevGlance that something changed, and RevGlance queues a sync of that source right away. Find a source's webhook URL in Settings › Sources under its menu, Webhook. Providers verify webhooks in one of three ways:
| How | Providers | What you do |
|---|---|---|
| Signing secret | Stripe, Polar, Lemon Squeezy, Paddle, Recurly | Paste the provider's signing secret into RevGlance |
| Secret in the URL | Gumroad, App Store, Google Play, Chargebee | Save a random secret in RevGlance, then add ?token= and the secret to the URL you give the provider |
| The source's own keys | Braintree, Shopify | Nothing: the provider signs with the keys the source already has |
Counting
Each provider reports money a little differently: refunds with or without tax, fees or none, cancel dates or not. RevGlance evens these out the same way everywhere and says where it cannot. Every integration guide lists its provider's rules, and How we count has all of them on one page.
Removing a source
Choose Remove source in its menu and hold the button. Its payments and subscriptions are removed with it; connecting it again brings them back.