Market finder

Find PSPs by market

Select a country, industry, and entity status to build a practical shortlist of PSPs, aggregators, acquirers, wallet routes, and gateways to verify.

Selected market: TurkeyPublic contact leads: 16

Regional planning

Planning more than one country?

Use a regional hub to narrow the provider categories first, then verify each country route before implementation.

Curated market guide

Turkey PSP routes to verify first

Which PSPs, wallets, and domestic card/bank routes should a merchant ask first for Turkey?

3
local_psp_or_aggregator · curated

Turkish PSP / gateway shortlist

iyzicoPayTRCraftgateParam POS

Use when you need cards, installments, wallet options, or payment links through a local PSP evaluation.

Treat local-entity access as a verification item. Ask each provider whether your current merchant entity can onboard, whether a local company or local bank account is required, and which settlement currencies are supported.

  • Confirm whether your merchant entity can onboard directly or whether a local entity, local bank account, licensed partner, or sponsor merchant is required.
  • Confirm KYB documents, beneficial-owner checks, website/app review requirements, prohibited categories, reserve policy, and production support path.
  • Confirm supported payment methods, refund/dispute handling, reconciliation fields, FX treatment, payout currency, and settlement timing before integration.
acquirer_or_bank · curated

Domestic card and acquiring route

TroyParam POSMoka UnitedÖdeal

Use when domestic card acceptance, installment logic, or bank/acquirer underwriting is the primary decision point.

Treat local-entity access as a verification item. Ask each provider whether your current merchant entity can onboard, whether a local company or local bank account is required, and which settlement currencies are supported.

  • Confirm whether your merchant entity can onboard directly or whether a local entity, local bank account, licensed partner, or sponsor merchant is required.
  • Confirm KYB documents, beneficial-owner checks, website/app review requirements, prohibited categories, reserve policy, and production support path.
  • Confirm supported payment methods, refund/dispute handling, reconciliation fields, FX treatment, payout currency, and settlement timing before integration.
direct_scheme_or_wallet · curated

Wallet and instant-transfer route

PaparaPaycellParamFAST

Use when wallet reach, domestic account transfer, or app-based checkout is central to the user journey.

Treat local-entity access as a verification item. Ask each provider whether your current merchant entity can onboard, whether a local company or local bank account is required, and which settlement currencies are supported.

  • Confirm whether your merchant entity can onboard directly or whether a local entity, local bank account, licensed partner, or sponsor merchant is required.
  • Confirm KYB documents, beneficial-owner checks, website/app review requirements, prohibited categories, reserve policy, and production support path.
  • Confirm supported payment methods, refund/dispute handling, reconciliation fields, FX treatment, payout currency, and settlement timing before integration.
KYB prep

Documents to prepare

  • Company registration certificate and operating entity details.
  • Beneficial-owner, director, and signatory identity documents.
  • Business website/app URLs, product description, refund policy, terms of service, and restricted-category explanation where relevant.
  • Bank account, settlement currency, tax/VAT/GST information, and expected processing volume.
Due diligence

Questions to ask

  • Can my current merchant entity onboard, or is a local company or bank account required?
  • Which local payment methods are live for my business category and customer flow?
  • What documents are required for KYB, technical review, and production approval?
  • How are refunds, chargebacks, reconciliation files, reserves, FX, and payout currencies handled?
  • Which public email, form, dashboard, or partner manager should be used for merchant onboarding?

Local PSP / aggregator

Start here when you need a provider route for local wallets, bank transfer, cards, or aggregated checkout.

12
Turkey · Payment gateway · Public email

Param POS

Param POSCardsMarketplace paymentsiFrame

Turkey payment gateway and marketplace payment API route for merchants using Param POS and related online collection products.

The official FAQ points applications to the Param Sanal POS page; actual acceptance is subject to Param review.

Turkey · Payment gateway · Official page only

Craftgate

Payment orchestrationPayment gatewayAlternative payment methodsTokenization

Turkey merchants and platforms evaluating payment orchestration, gateway routing, alternative payment methods, and tokenization.

Craftgate official pages indicate a merchant-facing request/demo and developer route; final commercial onboarding must be confirmed with Craftgate.

No public sales email or explicit form found yet. Open the official page or ask LocalPayMap to help verify.

Turkey · PSP / aggregator · Official form only

iyzico

cardswallet checkoutonline payments

iyzico official merchant contact route for Turkey; verify merchant fit, eligibility, and local requirements directly with the provider.

The official application page describes a merchant application flow and documentation fields, but LocalPayMap should not infer final eligibility without merchant-specific review.

No public sales email found yet. Open official form or ask LocalPayMap to help verify.

Turkey · PSP / aggregator · Official form only

Lidio

Lidio is a Turkish payment institution focused on online businesses, positioning itself as a digital payment platform for merchants that need virtual POS, subscriptions and marketplace collection. It serves the domestic market and settles in lira, so a foreign merchant needs a Turkish entity or a local partner arrangement. It is not a cross-border payout provider.

Lidio Ödeme Hizmetleri A.Ş. is listed by TÖDEB as a licensed payment institution, supervised by the Central Bank of the Republic of Turkey. Its contact process runs through a Turkish-language web form, which reflects its domestic-merchant focus.

No public sales email found yet. Open official form or ask LocalPayMap to help verify.

Turkey · PSP / aggregator · Official form only

Moka United

Moka United was formed by merging Moka, a Türkiye İş Bankası subsidiary, with United Payment, part of the OYAK group, which makes it the bank-backed independent payment infrastructure provider in the market. It operates in six countries and supports cross-border collection, so it is one of the more internationally capable Turkish providers. Its UK arm is being used to launch digital banking services for the Turkish corridor, which may matter for merchants with UK exposure.

The company describes itself as a licensed e-money and payment institution regulated in Turkey by the Central Bank of the Republic of Turkey and MASAK, and it provides payment infrastructure independently of any single bank. Turkish tax registration is the basic requirement for a merchant application.

No public sales email found yet. Open official form or ask LocalPayMap to help verify.

Turkey · Payment gateway · Official form only

PayTR

Virtual POSCardsiFrame APIDirect API

Turkey virtual POS and payment gateway provider with merchant application flow and public developer documentation.

PayTR's official pages present merchant application and support routes; final onboarding requirements must be confirmed in PayTR's merchant flow.

No public sales email found yet. Open official form or ask LocalPayMap to help verify.

Turkey · PSP / aggregator · Official page only

PayU Turkey

global payment solutionsonline payments

PayU Turkey official merchant contact route for Turkey; verify merchant fit, eligibility, and local requirements directly with the provider.

Turkey-specific legal entity and onboarding route must be confirmed with PayU; reviewed sources are global corporate PayU pages.

No public sales email or explicit form found yet. Open the official page or ask LocalPayMap to help verify.

Turkey · PSP / aggregator · Official page only

Ininal

Ininal is one of Turkey's earliest prepaid card and e-wallet platforms, licensed as an electronic money institution, and its cards are sold at retail chains so customers can start without a bank account. For foreign merchants it is not an acquiring route; it is an acceptance method to enable for Turkish buyers, particularly younger and unbanked ones. It is widely used for game credits and digital codes.

İninal Ödeme ve Elektronik Para Hizmetleri A.Ş. is registered as an electronic money institution supervised by the Central Bank of the Republic of Turkey. Physical cards are distributed through major retail chains, which is what makes the product accessible without a bank relationship.

No public sales email or explicit form found yet. Open the official page or ask LocalPayMap to help verify.

Local acquirer / bank merchant services

Use this route when a local entity, merchant account, or acquiring relationship may be required.

0

No public candidates in this group yet. Check other groups or submit requirements.

Wallet / mobile-money route

Use this route when local customers rely on wallet or mobile-money checkout, then confirm the provider route.

3
Turkey · Wallet operator · Public email

Papara

Papara walletmerchant payments

Papara official merchant contact route for Turkey; verify merchant fit, eligibility, and local requirements directly with the provider.

The official merchant page is a Turkey Papara Ticari route; merchant-specific eligibility and documentation still require Papara confirmation.

Turkey · Wallet operator · Public email

Paycell (Turkcell Ödeme ve Elektronik Para Hizmetleri)

CardsPayment linksWallet paymentsOnline payments

Turkey merchants evaluating Paycell for wallet, link-based, and online card collection flows.

Official Linkle Ödeme flow asks businesses to submit company-title information and application documents before use.

Turkey · Wallet operator · Official form only

Hepsipay

Hepsipay walletmerchant payments

Hepsipay official merchant contact route for Turkey; verify merchant fit, eligibility, and local requirements directly with the provider.

Official sources identify Hepsipay merchant panel onboarding fields; final account opening and credentials require Hepsipay review.

No public sales email found yet. Open official form or ask LocalPayMap to help verify.

Global PSP with local methods

Useful for cross-border teams, but each market, method, entity, and payout route still needs confirmation.

0

No public candidates in this group yet. Check other groups or submit requirements.

Contact-first / needs manual verification

Use these leads to ask official questions before treating the option as an onboarding path.

1
Turkey · Payment provider · Public email

TROY

TROY card scheme

TROY official merchant contact route for Turkey; verify merchant fit, eligibility, and local requirements directly with the provider.

TROY is a payment scheme rather than a direct PSP sales route; merchants should verify acceptance through acquirers, banks, or PSPs.

Questions to ask before integration

  • Does this provider support my merchant entity location, industry, and transaction model?
  • Is a local company, local bank account, tax registration, licence, or local contact required?
  • Which local wallets, bank transfers, card acquiring, refunds, and dispute flows are actually supported?
  • What settlement currency, timing, reserves, chargeback fees, and contract fees apply in writing?
  • Are API, plugins, webhooks, sandbox, reconciliation exports, and go-live support available?

Pricing and settlement caveat

Published pricing is suitable for initial screening only. Actual pricing can vary by country, industry, volume, settlement currency, integration model, and contract terms. Confirm the official pricing page or a provider quote before going live.