Skip to content

Connect Stripe

One Stripe key, and everything that pays you through it

Substack, Ghost, Memberful, Ko-fi, your own checkout: if the money lands in your Stripe, it lands here, with the fees split out.

A restricted key you mint yourself, read only on balance and balance transactions.

Connections · Stripe

The Stripe card and its drawer: what Orla reads, what it never does, and the restricted key it asks for. The credential is tried against Stripe before the connection exists, and encrypted once it is accepted, and never returned by the API again.

Why one key is enough

Most creator tools ask you to connect six platforms. Stripe already is the six

Subscriptions, memberships and tips have no money system. They have Stripe.

  • Everything money-shaped in Stripe passes through one place, the balance transactions, so one read-only key sees all of it.
  • Charges roll up into a day: gross in one figure, Stripe's fees in another, so your real income is not the number on the invoice.
  • Refunds subtract from the day they belong to rather than appearing as a mystery expense later.
  • Payouts come across one by one, so the transfer to your bank is a transfer, not more income.

The key you give us

A restricted key, with two permissions on it

You create it in your own Stripe dashboard and choose what it may read.

What to create
In your Stripe dashboard, a restricted key (rk_live_) with read access on Balance and Balance transactions; nothing else is needed or used.
What it cannot do
By construction, not by promise: a read key cannot charge a card, issue a refund or move a payout. Stripe enforces that, not us.
Checked before it is saved
Tried against Stripe first, so a wrong key never reaches the database.
Where it lives
Encrypted at rest once it is accepted, and never returned by our API again.
Your Orla billing
A different Stripe entirely: this is your Stripe as an earnings source, and it has nothing to do with how you pay for Orla.

The money still on Stripe

What has not reached your bank yet is an account, not a rounding error

What Stripe still holds becomes an account, counted once and in the right place.

  • Earned but not paid out is money you have, and it shows as money you have.
  • When the payout lands, it moves between two accounts you own instead of arriving from nowhere.
  • One account per currency, so a euro balance and a dollar balance stay themselves.

Questions

The questions people ask before they connect it

Which platforms does one Stripe key cover?

Anything that pays you through your own Stripe account: Substack, Ghost, Memberful, Ko-fi, Buy Me a Coffee and your own checkout. They mostly do not run their own money system, they run on Stripe, so one read-only key sees all of it.

Can the key charge anyone or move my payouts?

No. You create a restricted key with read access on balance and balance transactions, and Stripe itself refuses anything beyond that. The key is tried against Stripe before the connection is created, then encrypted at rest and never shown again.

Is this the same Stripe that bills me for Orla?

No, and they never touch. This is your Stripe as a source of earnings. How you pay for Orla is a separate arrangement on our side.

Other platforms

Connect Stripe, and see a month of income with the fees taken out

Platforms connect on the paid plans; the free plan keeps the book.

Shopify →
Sales, Shopify Payments fees and refunds apart, plus the balance still held.
PayPal →
Sales, refunds and payouts as earnings; what you spend from the same PayPal is left alone.
Gumroad →
Every sale with its price and Gumroad's cut as separate figures.
Lemon Squeezy →
A merchant of record: income from the subtotal, and the sales tax was never yours.
Bandcamp →
The partner sales report as rows, in the currency each sale happened in.

See it on your own books

Thirty minutes: we connect an account, drop a real bill in, and close a month together.