Every provider Paylytics reads
Polar, Stripe, Dodo Payments and Paddle. Connect any mix of them with read-only keys, and read them merged or one account at a time. Each page below is specific about what that provider issues, what it reports, and what Paylytics cannot promise about it.
One page per provider
A revenue dashboard for PolarRead-scoped organization access token. Polar publishes its own logo, so the account arrives already wearing it.Read about Polar
A revenue dashboard for StripeRestricted key only — a secret key is refused, because it could move money.Read about Stripe
A revenue dashboard for Dodo PaymentsRead-only is a checkbox when the key is made, and no API can prove it was ticked. The page says so.Read about Dodo Payments
A revenue dashboard for PaddleThe one provider that can genuinely prove a key cannot write, because read and write are separate grants.Read about Paddle
Why a merged total is harder than it looks
No two of these providers describe a sale the same way. One reports amounts as integers, another as integers inside a string. One treats a refund as a status on the order, another as a separate field beside it, another as an adjustment record entirely. One capitalises its billing intervals. One cannot tell you the product a payment was for without a second request per payment.
Adding those together in a spreadsheet is where the errors come from, because every one of those differences is invisible until it has already changed a total. Paylytics normalises each provider at the point it reads it — one money format, one status vocabulary, one way of identifying a repeat customer across accounts — so merging is not a step you perform, it is what the figures already are.
Every aggregate is also filtered to a single currency, resolved before the figures are calculated. Adding one yen to one cent produces a number, and that number is not a total.
Connect the first one in about a minute
Two accounts free, for as long as you like. Ten dollars a month for as many as you have.