BetterFans Link: the OnlyFans APIBetterFans Link

Money amounts: gross, net and fees

Every amount is an object with integer cents. Gross and net are different numbers; never add them together.

Product page: OnlyFans earnings API

Money is where reports go wrong. BetterFans Link returns it in one shape everywhere so that you never add floats or mix gross with net.

The Money object

{ "amount": 1250, "currency": "USD" }
FieldTypeDescription
amountintegerCents. 1250 is $12.50.
currencystringAlways USD.

Keep amounts in cents while you add and compare. Divide by 100 only when you display a number.

const format = (m: { amount: number; currency: string }) =>
  new Intl.NumberFormat("en-US", { style: "currency", currency: m.currency }).format(m.amount / 100);

format({ amount: 1250, currency: "USD" }); // "$12.50"

Gross, net and fee

Most money comes in pairs.

FieldWhat it is
grossWhat the fan paid.
netWhat the creator earns after the platform fee. It is about 80% of gross.
feeThe platform fee, on a single transaction.

Report gross or net and say which one. Never add a gross number to a net number, and never add gross and net together to get a total. When a report says "revenue" without qualification, use net for what the creator takes home and gross for what fans spent.

Where the numbers come from

Revenue and spend come from the account's transactions. The same sales feed every total. Only sales count: refunds and chargebacks are not in v1, so totals are gross sales, not what remains after refunds.

  • A fan's spend.total is lifetime gross with that creator, and spend.net is the net of the same sales. Get fan splits it by type: subscriptions, tips, paid messages, posts and other. On a Fansly account, message and post purchases count in other, since Fansly reports them together.
  • Revenue summary totals a period, splits it by transaction type and as a time series, and gives the previous period for comparison.
  • A mass message, post or tracking link reports the revenue it earned as a gross and net pair.

Totals you must not add

Some numbers already contain others. Adding them counts the same sale twice.

  • A mass message's revenue is the total for every copy sent. The copies also show up as single paid messages in each fan's chat. Report one or the other, never the sum.
  • A revenue summary's byType and series split the same total two ways. Add within one of them, never across both.
  • A fan's spend is part of the account's revenue. Do not add fan spend to account revenue.
  • previousPeriod is for comparison only.

Fansly amounts

Fansly counts money in tenths of a cent. BetterFans Link rounds each amount to the nearest cent, so a Fansly total can differ from the sum of its items by a few cents. Report the total the API gives rather than adding items yourself.

On Fansly, a sale of a message or a post is a transaction of type other, and a fan's spend.messages and spend.posts are always 0. See where Fansly data differs.

Fanvue amounts

Fanvue counts exact cents. Its revenue summary and a fan's spend are Fanvue's own totals. The revenue summary and revenue30d leave refunds and chargebacks out, as on OnlyFans, and a fan's spend leaves out what was refunded. List transactions shows each reversal as its own negative row. Fanvue gives totals by type, not how many payments made them, so each count in a Fanvue revenue summary is 0, and there is no stream revenue. See where Fanvue data differs.

A paid message (PPV) has a price. For messages the creator sent, purchased says whether the fan bought it. On Fansly it is always null, because Fansly does not say. A message with price set to null is not known to be paid. The sale itself is a transaction of type message, or other on Fansly. On OnlyFans and Fansly its messageId is not filled yet and is always null for now, so match a sale to a message by fan and time. On Fanvue, messageId names the message whenever Fanvue says which one it was.

On this page