Integrations › Revenue › Dodo Payments

Turn your Dodo Payments into build-in-public posts

Dodo Payments is a payments service that acts as the merchant of record for software makers, handling checkout, subscriptions and sales tax on their behalf. FoxPlug reads what you did there, scores it, and tells you what to fix, what to say and what to skip. Nothing posts until you approve it.

Read onlyBuilt, not yet read live

1What FoxPlug reads from Dodo Payments

These are the exact things it reads, and nothing else.

WhatThe details it takes
Subscriptionsup to 5 pages of 100 subscriptions from the live Dodo Payments address, stopping early when a page comes back short. Per subscription: status, price, quantity, currency, billing interval and count, created time and cancelled time.
Monthly amount per subscriptionthe price before tax, times the quantity, turned into a monthly figure from the billing interval (year, week, day or month) and its count. Discounts are not applied.
Active subscribers and monthly revenuesubscriptions with status active are counted, and each adds its monthly amount.
Past-due subscriptionsstatus past due or on hold: how many, and the monthly amount at risk. The count is stored only when it is above zero.
New and cancelled in 30 daysnew = created in the last 30 days, leaving out pending, failed and expired; cancelled = status cancelled with a cancelled time in the last 30 days.
Currencythe currency on the subscriptions as read (the last one seen wins), in lower case; usd when none is given.

2Moments it finds, and what each becomes

A moment is one thing that happened in Dodo Payments worth a second look. Each one is scored, then it becomes a post, a changelog entry, a thing to fix or an idea to email, or it is skipped.

Post

The first active subscription is read

The moment is titled like this: 💸 Got the first paying customer

A maker connects Dodo Payments and presses Check for what's new. One subscription is active, so the moment reads 'Got the first paying customer' with the line 'Someone is paying for the thing I'm building (counted from Dodo Payments).' A post is drafted for review.

Post

Active subscriptions reach 10, 50 or 100

The moment is titled like this: Passed 10 paying subscribers

The 10th active subscription is read. The moment 'Passed 10 paying subscribers' is written once, described as '10 people now pay for it every month (counted from Dodo Payments).'

Fix first

One or more subscriptions are past due

The moment is titled like this: No milestone. Brief line like '2 subscriptions are past due, $48 a month at risk.'

Two subscriptions show past due. The monthly amount at risk is added up from their prices and the brief puts a Fix line ahead of any post.

Post

Monthly revenue crosses a milestone number between two reads

The moment is titled like this: Brief line: 'You passed $500 a month. Tell people.'

A first read shows $480 a month and a later read at least a day on shows $520. The brief offers a Say line for crossing $500.

3How the brain uses it

The rules below are the ones that apply to Dodo Payments. The same rules, with worked examples, are on the brain page.

4Set up Dodo Payments in a few steps

Access: Live API key pasted into FoxPlug. What to give it: Live API key. Dodo Payments lets each key be set to None, Read or Write per area, so the guide says to give Subscriptions Read and everything else None. Test keys (starting dodo test) are refused.

  1. In Dodo Payments, switch to Live mode, open Developer, then API Keys, and choose Create New Key named FoxPlug.
  2. Set Subscriptions to Read and leave every other row on None.
  3. Copy the key right away, because Dodo Payments shows it only once, and paste it into the Dodo Payments box in FoxPlug.

5Limits worth knowing

Where it stops, so nothing surprises you.

6What it never reads

Read only means read only, and the list below is what the code leaves alone.

  • Customer names, emails, addresses and cards. The customer and billing parts of each subscription are never touched.
  • Discounts, tax, add-ons and usage meters: only the pre-tax list price is used.
  • Anything written back: only plain GET reads of the subscription list.
  • Test mode data: a test key is refused and only the live address is called.

7How Dodo Payments differs from the tools next to it

Dodo Payments lists subscriptions page by page with the price and billing interval on each one, so no second price lookup is needed, unlike Lemon Squeezy. Its key can be limited to Read on Subscriptions, which Polar's documentation does not list. Past due and on hold both count as at risk.

8Questions

Does FoxPlug see my customers' names or emails from Dodo Payments?

No. It reads subscription status, price, currency, billing interval and dates. No customer detail is read or stored.

Which key does it need?

A live API key with Read on Subscriptions and nothing else. Dodo Payments lets you set each area to None, Read or Write when you make the key.

Can I use a test key?

No. A test key holds test data, so FoxPlug refuses it and asks for a live key.

When does it read Dodo Payments?

When you press Check for what's new or Build the brief.

FoxPlug reads this tool only when you press Check for what's new, and only to read. Plans and limits are on the pricing page. Questions: support.