Revenue: how FoxPlug reads Authorize.net, Braintree, Gumroad, Helcim, Mollie, Patreon, PayPal, Razorpay, RevenueCat, Square

Authorize.net

Authorize.net is a payment gateway used by merchants in North America, with an Automated Recurring Billing feature for subscriptions.

What it reads

• Your active and inactive subscription lists: up to 5 pages of 1000 for each list: id, status, created time, amount and currency.
• The billing interval of up to 25 subscriptions: one extra read per active or suspended subscription, only for the interval length and unit and the amount; the first 25 are priced.
• Active subscriptions: subscriptions with status active are counted.
• Monthly revenue: the amount of the priced active subscriptions, turned into a monthly number using the interval, then added up.
• Past due: subscriptions with status suspended are counted, with the monthly amount they carry.
• New in 30 days: subscriptions whose created time is within the last 30 days.
• Currency: the currency code on the entries when it is three letters, lowercased; usd if none.

Moments

• The first active subscription appears. A maker connects Authorize.net 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 Authorize.net).'
• Active subscriptions reach 10, 50 or 100. The read shows 12 active subscriptions, so 'Passed 10 paying subscribers' is written once, described as '10 people now pay for it every month (counted from Authorize.net).'
• Monthly revenue crosses a milestone number between two reads. The stored read showed $480 a month and a read at least a day later shows $520. The brief offers a Say line for crossing $500.

Set up

1. Sign in to the live Authorize.net Merchant Interface and open Account, then Settings, then API Credentials and Keys.
2. Press New Transaction Key and leave the box about disabling the old key empty, so your other tools keep working for 24 hours.
3. Copy the new transaction key now: Authorize.net shows it only once. Update your other tools within 24 hours.
4. Paste the API login id, a colon and the transaction key as one line into the Authorize.net box in FoxPlug.

What it never reads

• Customer names, addresses, emails and cards. The reply carries some of them, but the reader only picks id, status, amount, interval, created time and currency.
• Individual transactions and settled batches: only the recurring billing lists and per-subscription schedule are read.
• Anything written back: the requests are named get and list requests; they are sent as POST because Authorize.net takes every request that way.
• Cancel dates: Authorize.net's subscription replies carry none, so cancelled in 30 days stays 0.

How it differs

Authorize.net lists subscriptions without a billing interval, so FoxPlug makes one extra read per subscription for the first 25, which no other revenue tool here needs. Like Razorpay it has no read-only key, and unlike Mollie it gives no cancel date. Every call is a POST, though the calls are read-style.

Braintree

Braintree is a card and PayPal payment processor from PayPal that software makers use to take payments and run recurring billing plans.

What it reads

• Subscriptions that are active or late: status, price and plan of each, up to 5 pages of 50. The search is a POST because GraphQL has no GET, but it only reads.
• Plan billing length and currency: each plan's billing frequency in months and its currency, so a yearly price is turned into a monthly one.
• Cancelled subscriptions: the status history is read; a subscription counts as cancelled in the last 30 days when its cancel event is that recent.
• New subscriptions: subscriptions created in the last 30 days, counted from a search filtered by creation time.
• Late subscriptions: subscriptions in the past due status are counted with their monthly value as money at risk.
• Settled payments of the last 30 days (fallback only): if the key's role cannot search subscriptions, the amount of settled transactions is added up and the result is marked partial.

Moments

• The count of active subscriptions reaches at least one. A maker connects Braintree. The read shows 1 active subscription, so the moment reads 'Got the first paying customer' with the line 'Someone is paying for the thing I'm building (counted from Braintree).'
• Active subscriptions reach 10, 50 or 100. The read shows 12 active subscriptions, so 'Passed 10 paying subscribers' is written once, described as '10 people now pay for it every month (counted from Braintree).'

Set up

1. In the Braintree Control Panel make a role with only Download Transactions with Masked Payment Data and Download Subscription Records ticked, and a user with that role.
2. Sign in as that user, click the gear icon, then API, and generate an API key if none is shown.
3. Copy the public key and the private key (View in the Private Key column) and paste them into the Braintree box in FoxPlug with a colon between them. Use production keys, not sandbox.

What it never reads

• Customer names, emails, addresses and card details: the queries name only status, price, plan, dates and amounts.
• Anything written back: no mutation is sent, only searches.
• Sandbox data: sandbox keys are refused and only the production address is used.

Gumroad

Gumroad is a storefront where creators and software makers sell digital products, memberships and subscriptions directly to buyers.

What it reads

• Sales of the last 30 days: up to 5 pages of sales with after set to 30 days ago, following next page key.
• Order count: each sale that is neither refunded nor charged back counts as an order; the sale's currency is kept.
• Refunds: sales flagged refunded are counted as refunds. Charged-back sales are skipped altogether.
• Subscription charges: for sales with a subscription id: the distinct subscription ids and each sale's price, added up as the 'monthly revenue' figure (the subscription charges taken in the last 30 days).
• New subscribers: subscription ids whose sale has no recurring charge flag (the first charge) count as new in the last 30 days.

Moments

• The first subscription charge shows up in the last 30 days. A maker sells a membership on Gumroad. One subscription has been charged in the last 30 days, so the moment reads 'Got the first paying customer' with the line 'Someone is paying for the thing I'm building (counted from Gumroad).'
• Subscriptions charged in the last 30 days reach 10, 50 or 100. Ten different subscription ids were charged in the last 30 days. The moment 'Passed 10 paying subscribers' is written once, described as '10 people now pay for it every month (counted from Gumroad).'
• New subscribers started in the last 30 days. Three subscription ids have a first charge inside 30 days, so the brief carries that count and says the monthly figure is the last 30 days of subscription charges.

Set up

1. In Gumroad, open Settings and then Advanced (the in-app link goes there).
2. Under Applications, make an application named FoxPlug.
3. Press Generate access token, copy it now and paste it into the Gumroad box in FoxPlug. Gumroad may show it only once.

What it never reads

• Customer emails. The panel says it reads no customer email.
• Charged-back sales are skipped and not counted.
• Anything written back: only sales are read.

How it differs

Gumroad has no subscriber or price list in the API FoxPlug reads, only sales. So FoxPlug reads 30 days of sales (Lemon Squeezy and Paddle read real subscriptions), counts orders and refunds, and adds up subscription charges as an approximate 'monthly revenue' marked partial. It has no past-due number and no cancelled number. Charged-back sales are dropped.

Helcim

Helcim is a payment processor for small businesses in Canada and the United States, with recurring billing for subscriptions.

What it reads

• Your payment plans: up to 5 pages of 100: each plan's billing period, how many periods between charges, and currency.
• Your subscriptions: up to 5 pages of 100: status, recurring amount, plan, created date and last-changed date.
• Active subscriptions: subscriptions with status active, or ending at the end of their term (Helcim counts that as active), are counted.
• Monthly revenue: each active subscription's recurring amount in cents, turned into a monthly number using its plan's billing period, then added up.
• New in 30 days: subscriptions whose created date is within the last 30 days.
• Cancelled in 30 days: subscriptions with status cancelled (or term ended) whose last-changed date is within the last 30 days.
• Currency: the currency of the plan on the last subscription read, lowercased; usd if none.
• Whether anything is being paid: if there are no active subscriptions the read is stored as empty and the brief says so instead of inventing a number.

Moments

• The first active subscription appears. A maker connects Helcim 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 Helcim).'
• Active subscriptions reach 10, 50 or 100. The read shows 12 active subscriptions, so 'Passed 10 paying subscribers' is written once, described as '10 people now pay for it every month (counted from Helcim).'
• Monthly revenue crosses a milestone number between two reads. The stored read showed $480 a month and a read at least a day later shows $520. The brief offers a Say line for crossing $500.

Set up

1. In Helcim, press All Tools, then Integrations under Merchant Tools, then open API Access Configurations.
2. Press New API Access, name it FoxPlug and leave the checkout box empty.
3. Pick General: Read, Settings: No access and Transaction Processing: None, then press Create.
4. Copy the API token Helcim makes and paste it into the Helcim box in FoxPlug.

What it never reads

• Customer names, emails and card details. The reader only picks status, amount, plan, created and changed dates from each subscription.
• Which customer owns which subscription: the customer code Helcim returns is never used.
• Anything written back: only GET reads of the plan and subscription lists, with the token in a header.
• Past-due subscriptions: Helcim only says a subscription has had a failed payment at some time, not that it is overdue now, so this stays blank.

How it differs

Helcim is read with a plan list plus a subscription list, like Lemon Squeezy needs a second price lookup. Unlike Mollie or Razorpay it gives no overdue status and no cancel date, so past due is blank and cancelled in 30 days is approximate. Helcim lets you restrict the token to read access, which Razorpay and Authorize.net do not.

Mollie

Mollie is a European payment service that online shops and software makers use to take card, bank and wallet payments, including recurring subscriptions.

What it reads

• Your subscriptions: up to 5 pages of 250 across customers: status, amount, billing interval, created and cancelled dates.
• Active subscriptions: subscriptions with status active are counted.
• Monthly revenue: each active subscription's amount in cents, turned into a monthly number using its interval (days, weeks or months), then added up.
• Past due: subscriptions with status suspended are counted, with the monthly amount they carry.
• New in 30 days: subscriptions whose created date is within the last 30 days.
• Cancelled in 30 days: subscriptions with status canceled whose cancel date is within the last 30 days.
• Currency: the currency on the amounts, lowercased; usd if none.
• Whether anything is being paid: if there are no active subscriptions the read is stored as empty and the brief says so.

Moments

• The first active subscription appears. A maker connects Mollie 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 Mollie).'
• Active subscriptions reach 10, 50 or 100. The read shows 12 active subscriptions, so 'Passed 10 paying subscribers' is written once, described as '10 people now pay for it every month (counted from Mollie).'
• Monthly revenue crosses a milestone number between two reads. The stored read showed $480 a month and a read at least a day later shows $520. The brief offers a Say line for crossing $500.

Set up

1. In the Mollie dashboard open Developers, then API keys, and build an advanced access token (only Admin users can).
2. Name it FoxPlug and tick only the permission to read subscriptions.
3. Copy the token now: Mollie shows a secret only once.
4. Paste it into the Mollie box in FoxPlug. Test keys are refused.

What it never reads

• Customer names, emails and payment methods. The reader only picks status, amount, interval and the two dates from each subscription.
• Which customer owns which subscription: the customer id in each entry is never used.
• Test data: a Mollie test key is refused, and any entry marked test is skipped.
• Anything written back: only GET reads of the subscription list with a bearer header.

How it differs

Mollie lists subscriptions with their own amount and interval in one call, like Polar, so no second price lookup is needed (unlike Lemon Squeezy, Helcim or Razorpay). Together with Helcim it is one of two of these four where a read-only credential is documented (the access token). Past due is the suspended status.

Patreon

Patreon is a membership platform where creators earn monthly pledges from their patrons. FoxPlug reads the pledges from your patrons: who is an active patron and what each one pledges.

What it reads

• Your Patreon identity: the account's full name, used as the connection label 'Patreon (name)'.
• Your campaign: the id of the campaign linked to the account, which is the campaign whose members are read.
• Campaign members (patrons): up to 200 members, newest pledge first: full name, patron status, currently entitled amount cents, pledge relationship start.
• Active patron count: members whose patron status is active patron are counted and the count is saved as a snapshot with the date, shown on the Funding tab as 'Active patrons' with a last-read time.
• Newest active patron: the newest active patron's name, pledge amount and pledge start date, turned into one new-patron moment.

Moments

• You connect Patreon and the campaign has an active patron. A creator connects Patreon. The newest active patron is Ada Lovelace, so the moment reads 'New patron: Ada Lovelace' with the line 'Ada Lovelace became a patron on Patreon, real support for the work.' A post is drafted for review.
• You connect Patreon and the newest patron has no name. The newest active patron shows no full name, so the moment reads 'A new patron joined' with the line 'A new patron joined on Patreon, real support for the work.'
• You connect Patreon and the campaign has no active patrons. The member list has no active patron, so nothing is saved and no post is drafted. The Funding tile shows no patron count yet.

Set up

1. Press Connect Patreon (or Authorise on Patreon) in the Patreon card.
2. Sign in at Patreon and allow the read-only access it asks for.
3. You come back to FoxPlug with Patreon marked Connected, and your newest patron is written up as a post.

What it never reads

• Patron emails, messages or payment details: the member fields asked for are only name, status, entitled amount and pledge start.
• Anything posted or changed on Patreon: it is a source only and FoxPlug never posts to it.

PayPal

PayPal is a payment service; its Subscriptions feature lets a seller charge customers on a plan every month or year.

What it reads

• Token exchange: the Client ID and secret are exchanged for a short-lived access token at PayPal's live address.
• Active and suspended subscriptions: plan, quantity, status and failed payment count of each, up to 5 pages of 20.
• Plan price and billing length: the regular billing cycle of each plan (up to 25 plans), turned into a monthly amount.
• Late subscriptions: a subscription with one or more failed payments is counted as late, with its monthly value as money at risk.
• Cancelled and new subscriptions: subscriptions cancelled with a status change in the last 30 days, and subscriptions created in the last 30 days.
• Payments and refunds of the last 30 days (only when there are no subscriptions): event code, status and amount of each transaction from Transaction Search; fields are limited to transaction details.

Moments

• The count of active subscriptions reaches at least one. A maker connects PayPal. The read shows 1 active subscription, so the moment reads 'Got the first paying customer' with the line 'Someone is paying for the thing I'm building (counted from PayPal).'
• Active subscriptions reach 10, 50 or 100. The read shows 12 active subscriptions, so 'Passed 10 paying subscribers' is written once, described as '10 people now pay for it every month (counted from PayPal).'

Set up

1. In the PayPal developer dashboard open Apps and Credentials, switch to Live and create an app named FoxPlug.
2. In the app's Features section tick Subscriptions and Transaction Search if listed, and save.
3. Copy the Client ID and the secret and paste them into the PayPal box in FoxPlug with a colon between them.

What it never reads

• Buyer or subscriber names, emails and addresses: the subscriber block is ignored and Transaction Search is asked for transaction details only.
• Anything written back: the only POST is the token exchange; every data call is a GET.
• Sandbox data: only the live address is used.

Razorpay

Razorpay is a payment service used by businesses in India and a few other countries to take online payments and run recurring subscriptions.

What it reads

• Your plans: up to 5 pages of 100: each plan's amount in the smallest unit, billing period, interval and currency.
• Your subscriptions: up to 5 pages of 100: status, plan, quantity, created date and ended date.
• Active subscriptions: subscriptions with status active are counted.
• Monthly revenue: the plan amount times the quantity, turned into a monthly number using the plan's period and interval, then added up for active subscriptions.
• Past due: subscriptions with status pending or halted are counted, with the monthly amount they carry.
• New in 30 days: subscriptions created in the last 30 days that were not left at the created stage.
• Cancelled in 30 days: subscriptions with status cancelled whose ended time is within the last 30 days.
• Currency: the currency on the plan amounts, lowercased; inr if none.

Moments

• The first active subscription appears. A maker connects Razorpay 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 Razorpay).'
• Active subscriptions reach 10, 50 or 100. The read shows 12 active subscriptions, so 'Passed 10 paying subscribers' is written once, described as '10 people now pay for it every month (counted from Razorpay).'
• Monthly revenue crosses a milestone number between two reads. The stored read showed $480 a month and a read at least a day later shows $520. The brief offers a Say line for crossing $500.

Set up

1. In the Razorpay Dashboard, switch to Live mode and open Account and Settings, then API Keys.
2. If you already have a key, use it; do not press Generate, because Razorpay allows one set of keys and a new one stops the old one.
3. If you have none, press Generate Key and save the secret now: Razorpay shows it only once.
4. Paste the key id, a colon and the key secret as one line into the Razorpay box in FoxPlug.

What it never reads

• Customer names, emails, phone numbers and cards. The reader only picks status, plan, quantity and two dates from each subscription.
• Which customer owns which subscription: the customer id in each entry is never used.
• Test data: a test key (id starting with rzp test) is refused.
• Anything written back: only GET reads of plans and subscriptions with a Basic header.

How it differs

Razorpay keeps the price on the plan, not on the subscription, so FoxPlug reads the plan list as well, like Lemon Squeezy needs a price lookup. Unlike Mollie it has no read-only credential. Past due comes from two statuses, pending and halted.

RevenueCat

RevenueCat is a subscription management service that app makers use to handle in-app purchases and see subscription revenue across the app stores.

What it reads

• Your projects: the first 5 projects are listed (id only); the first 3 are used.
• Project overview: monthly recurring revenue: the overview metric with id mrr for each project, multiplied by 100 to cents and added across projects.
• Project overview: active subscriptions: the overview metric with id active subscriptions, added across projects.
• Whether anything is being paid: if the active subscription total is 0, the read is stored as empty and the brief says no active subscriptions yet instead of inventing a number.
• Currency: the overview's currency field, lowercased; usd if absent.

Moments

• The overview shows at least one active subscription. A maker connects RevenueCat for an iOS app. The overview shows 1 active subscription, so the moment reads 'Got the first paying customer' with the line 'Someone is paying for the thing I'm building (counted from RevenueCat).'
• Active subscriptions reach 10, 50 or 100. The overview reports 12 active subscriptions, so 'Passed 10 paying subscribers' is written once, described as '10 people now pay for it every month (counted from RevenueCat).'
• Monthly revenue crosses a milestone number between two reads. The overview's monthly revenue was $480 at the last stored read and is $520 now (at least a day later). The brief offers a Say line for crossing $500.

Set up

1. In RevenueCat, open your project and go to API keys, then make a new v2 secret key named FoxPlug.
2. Give it only read permissions: Projects read and Charts and metrics, Overview read.
3. Copy the key now and paste it into the RevenueCat box in FoxPlug. RevenueCat may show it only once.

What it never reads

• Individual subscribers or customers. Only project overview totals are read.
• New or cancelled subscribers: the overview gives no such split, so these stay blank.
• Anything written back: only GET reads of the project list and the overview.

Square

Square is a payment service for shops and online sellers; its Subscriptions feature bills customers on a repeating plan.

What it reads

• Subscriptions: status, plan variation, start, cancel and creation dates and any price override of each, up to 5 pages of 200. The search is a POST because Square's search has no GET, but it only reads.
• Plan price and billing cadence: the plan variation's last phase (price and cadence) for each active plan (up to 25), turned into a monthly amount.
• Active subscribers and monthly revenue: subscriptions in the active status, with a price override taking the place of the plan price.
• New subscriptions: subscriptions created in the last 30 days.
• Cancelled subscriptions: subscriptions cancelled or deactivated with a cancel date in the last 30 days.

Moments

• The count of active subscriptions reaches at least one. A maker connects Square. The read shows 1 active subscription, so the moment reads 'Got the first paying customer' with the line 'Someone is paying for the thing I'm building (counted from Square).'
• Active subscriptions reach 10, 50 or 100. The read shows 12 active subscriptions, so 'Passed 10 paying subscribers' is written once, described as '10 people now pay for it every month (counted from Square).'

Set up

1. In the Square developer console open your application and choose Credentials.
2. Choose Production at the top, then Show the Production Access token and copy it.
3. Paste it into the Square box in FoxPlug. Square's token has full access and no read-only version, and FoxPlug only reads.

What it never reads

• Customer ids, names, emails, cards and invoices: some of these come back in the subscription record but are never used or stored.
• Anything written back: the only POST is the read-style subscription search; the plan lookup is a GET.
• Sandbox data: sandbox tokens are refused and only the production address is used.