Your money goes to your account, not ours

Turtini is not a payment processor and never holds your money. Your customer pays a merchant account that belongs to you, in your name, underwritten on your own merits. We hold a narrow key so a checkout page can create a charge on your behalf — nothing more.

**Why it works this way**

Most software in this category creates a payment account for each organization underneath its own platform account. That arrangement has a property nobody notices until the day it matters: the account belongs to the platform. It has no separate dashboard of its own, it cannot be moved to another provider, and it stops working when the platform does — for reasons that have nothing to do with the organization using it.

An account in your own name, underwritten on your own merits, has none of those properties. You hold the relationship with the processor, you can move it, and nobody else can switch it off. That is why it is the only kind we support.

**What this means for you, concretely**

- **Turtini takes nothing from a sale.** Not a percentage, not a per-transaction fee. Your processor charges you their rate, you pay us for the software monthly, and those are separate things.
- **Payouts are between you and your processor.** We do not schedule them, hold them, or take a share. If you want your money faster, that is a conversation with your processor, not with us.
- **You can revoke us in about ten seconds**, from your own processor's dashboard, without asking and without warning us. Everything you have built here keeps working; it simply stops being able to charge until you connect something again.
- **If Turtini disappeared tomorrow**, your merchant account, your customers' saved payment methods and your payout history would all still be there. You would need different software. You would not need a different payment account.

**Connecting yours**

Settings → Payment Processor, which only the organization's owner can open — connecting a processor decides where every dollar you take will land.

You paste two things: a **publishable key**, which is public by design and ships in the source of every checkout page on the internet, and a **restricted key**, which is stored encrypted and never shown again, not even to you.

We ask for a *restricted* key specifically, and we refuse a full secret key even though one would work. A restricted key can be scoped to exactly what a checkout needs — create a payment, issue a refund, register a webhook — and nothing else. A full secret key would additionally let anyone holding it read your customer list and move your money. Asking for a credential far broader than the job is how a break-in at a software company becomes a catastrophe at an organization that merely sold tickets.

**Changing processors later**

Paste new keys over the old ones. Charges switch immediately; nothing in your history moves or breaks. Revoke the old key in the old processor's dashboard when you are ready.

**What we still do**

We meter what you process so we can bill the software, and we watch refund and dispute rates so we can warn you early if something looks wrong — the kind of warning nobody gave us. That monitoring exists to protect you from an outcome we have actually had, and it never involves touching your money.