Product
One transaction. Every local system behind it.
The homepage shows the route a payment takes. This page shows the operating model underneath it: where every kuruş of a sale goes, the four systems that carry it, which transactions are in scope today, and what a local processor does not cover.
How the money moves
Every kuruş, accounted for.
This is the wide version of the flow on the homepage. One sale is not one payment — it is seven obligations settled in sequence. The example below is a ₺1.000,00 event ticket sold for a seller who is not registered for tax.
- Tax authority
- Other businesses
- Finletry
- Held, then released
Every rate resolves from a versioned rule set at the transaction’s own date, so a past calculation always reproduces exactly. Amounts are integers in kuruş — no floating-point arithmetic touches money.
The product
Four systems, operated as one.
Each one is a layer the transaction has to pass before it can settle legally. They are separated here because they fail separately — not because you integrate them separately.
Payments
Local acquiring with 3-D Secure on every transaction, which typically shifts fraud liability to the issuer where the authentication qualifies. Instalments — expected by Turkish buyers and rarely reachable through a global stack — are included.
- TRY checkout · hosted · PCI-DSS SAQ-A scope
- Single payment and instalments
- Full and partial refunds, prorated across every leg
Documents & tax
VAT is resolved per line item, not per order: a ticket and a service fee can sit at different rates. Income tax is withheld at source where the law requires it, and the statutory document is issued in our name.
- e-Arşiv and e-Fatura routed automatically
- Expense voucher where the seller isn’t registered
- Every rate from a versioned rule set, reproducible years later
Sellers
Sellers verify their identity and bank details with us, never with you — you never handle a national identity number. Onboarding collects the tax information the payable document depends on.
- Identity verification under KVKK
- Tax status read from the order, never recomputed
- Payout eligibility derived from document and settlement state
Money operations
Payouts are released only after the money has settled with the acquirer, and for events only once the event has taken place. Payment, invoice, tax and payout records stay attached to one transaction.
- Rolling reserve, held and then released
- No payout before settlement is known
- Daily reconciliation against the settlement report
Why a local processor isn’t enough
A local PSP solves collection. It doesn’t make your platform locally operational.
Turkish payment providers are good products and we use one. But acquiring is one of five layers a transaction has to pass through before it can settle legally — and the other four stay with you until someone else contracts as the local seller.
| Layer | A local PSP | Left with you |
|---|---|---|
| Card acquiring | Solved | Nothing to build |
| Statutory documents | Not covered | e-Arşiv / e-Fatura integration, expense vouchers |
| Tax at transaction level | Not covered | VAT per line, withholding, versioned rules |
| Seller verification | Partly | Identity under local data-protection law |
| Local commercial structure | Not covered | A Turkish counterparty for the buyer and the seller |
Finletry is not another Turkish payment provider. We are the local operating layer that keeps your platform from having to become a Turkish one — and the acquirer sits inside our stack, not inside your integration.
Scope
What we take, and what we don’t.
Event and community platforms are the vertical we run today. The same infrastructure fits marketplaces, creator platforms and local billing, and we are happy to look at those — but this table is what holds right now.
- Turkish organizer, Turkish buyer
- Supported
- Organizer not registered for tax
- Supported
- Sole trader, self-employed or company organizer
- Supported
- TRY checkout with instalments
- Supported
- Ticketed events, conferences, community meetups
- Supported
- Card issued outside Türkiye
- Ask us — depends on the acquirer
- Recurring subscriptions
- Not in the first release
- Physical goods
- Not in the first release
- Seller located outside Türkiye
- Out of scope — the model is a Turkish supplier
Built for your vendor review
Finletry is the merchant of record for transactions routed through it in Türkiye. The ticket invoice, the VAT and the seller relationship are ours.