Skip to content

Payments infrastructure · Türkiye

Your platform,
now in Türkiye.

Accept local payments. Issue compliant invoices. Handle tax. Pay local sellers. Move funds through Türkiye.

One integration into the stack you already have.

Global Platform

Your product
Your brand
Your customers

Finletry

The Türkiye layer

  • Local paymentsLocal acquiring · 3DS · TRY
  • Electronic invoicinge-Arşiv · e-Fatura
  • Tax operationsTransaction-linked records
  • Seller payoutsVerification · Local payouts
  • SettlementReconciled, then settled

The Türkiye gap

Your global payments stack stops one market too early.

Your existing stack may already cover the US, the UK and Europe. Türkiye adds a different operating layer underneath the payment.

Finletry brings those pieces together behind one integration.

  1. US

    Global provider

  2. EU

    Global provider

  3. UK

    Global provider

  4. TÜRKİYE

    The missing piece

  5. Global

    MoR

  6. Global payout

    infrastructure

How money moves

One payment. The full Türkiye flow.

A transaction does not end when the card is charged. It ends when the invoice exists, the tax is recorded, the seller is paid and the remaining funds are reconciled. This is that sequence.

  1. 01

    Customer pays locally

    Your customer checks out in TRY through the local payment experience available behind Finletry.

    CustomerLocal payment rails

  2. 02

    Finletry processes the Türkiye transaction

    The payment is routed through local infrastructure. Status, transaction data and reconciliation stay attached to a single Finletry transaction.

    PaymentFinletry

  3. 03

    Invoice and tax happen locally

    The required electronic invoice is issued and the transaction enters the Türkiye tax flow. Your product does not build a separate local invoicing stack.

    TransactionInvoice + tax

  4. 04

    Sellers are paid locally

    For platforms and marketplaces, local sellers are onboarded, verified and paid through the same operating layer.

    FinletrySeller payout

  5. 05

    Funds are reconciled and settled

    Payment, invoice, tax and payout records are reconciled, and the remaining funds are prepared for settlement according to the agreed commercial flow.

    TürkiyeYour platform

One transaction. One reconciliation trail. One integration.

The Türkiye layer

The infrastructure you don’t have to build.

Four operational outcomes rather than four feature names. Each one is work your platform would otherwise take on locally.

See the full product

Local collection

Accept TRY payments through local payment infrastructure and give customers a Türkiye-native checkout experience.

Local checkout

TRY 1,249.00
Card (3DS)Instalments
Pay in TRY

Local acquiring · TRY · 3DS

Invoice + tax

Connect each transaction to the local electronic invoicing and tax workflow it requires.

e-Fatura

T.C.
Invoice No
FTR2024001234
Issue Date
24 Jan 2024
Total
TRY 1,249.00

Issued and delivered

e-Arşiv · e-Fatura · Tax records

Sellers + payouts

Onboard local sellers, collect the business information regulation asks for and pay them into local bank accounts.

Payout to seller

TRY 48,250.00

TR local bank account
•••• 4587
Identity checkCompleted
Tax number (VKN)Verified
Bank accountVerified

Seller verification · Local payouts

Reconciliation + settlement

Hold payment, invoice, tax and payout records together as one transaction trail, and settle according to your operating model.

Transaction trail

or_0f3a91
PaymentSettled
InvoiceFTR2024001234
Tax recordRecorded
Seller payoutSent
SettlementPrepared

Reconciliation · Reporting · Settlement

One integration

Keep your stack.
Add Türkiye.

Your payment architecture does not need to be rebuilt. Route Türkiye transactions to Finletry. We operate the local layer behind them, so there is no local stack for you to build.

  1. 01Create a payment intentPOST /v1/payment_intents for a transaction that belongs to Türkiye.
  2. 02Customer completes local paymentThe Türkiye payment flow runs behind Finletry.
  3. 03Receive the resultA signed webhook returns the transaction state to your platform.

Behind that single call, the local work stays connected: payment, invoice, tax, seller, payout, settlement.

Same product. Same platform. A new local route.

cURLNodePython
Copy
curl https://api.finletry.com/v1/payment_intents
  -H "Authorization: Bearer fk_test_…"
  -H "Idempotency-Key: 8f14e45f-…"
  -d '{"amount_minor": 100000, "currency": "TRY", …}'

Payment intent created

  • PaymentProcessed
  • InvoiceIssued
  • TaxRecorded
  • SellerVerified
  • PayoutScheduled
  • SettlementPrepared

Local operations

Infrastructure is only half of the Türkiye problem.

Payments do not operate separately from invoicing, tax and local commercial requirements. The operating model behind each flow has to work as one system.

Built with Türkiye-based legal, tax and finance expertise.

  • Legal
  • Tax
  • Finance
  • Payments
  • Technology

Not just an API into Türkiye. An operating layer for Türkiye.

Operating foundation

Built for real transactions in Türkiye.

Finletry connects the local systems a payment flow needs behind it.

Explore the product
  • Local paymentsTürkiye-based payment infrastructure for TRY transactions
  • Electronic invoicinge-Arşiv and e-Fatura workflows connected to transaction data
  • Tax operationsLocal financial and tax workflows built into the operating model
  • Seller payoutsLocal seller verification and payouts where the model requires them
  • ReconciliationOne connected record across payment, invoice, tax, payout and settlement

Built for platforms

Different business models. The same Türkiye layer.

Event and community platforms are the vertical we run today; the same layer fits the models below.

Explore use cases

New market. Existing product.

Türkiye is open.

Tell us how money moves through your platform. Who pays. Who receives. Who needs an invoice. Who needs a payout.

We’ll map the Türkiye route.

Selling tickets for events in Türkiye? Create a seller account