Netherlands → Turkey
remittance corridor.
Diaspora profile in Netherlands: Turkish, Moroccan, Polish, Indonesian diaspora. Annual destination inflow to Turkey: ≈$1.0B (World Bank 2024). A 90-day Wave-1 typically targets 100k registered users and ≈$20M cumulative volume.
Why this corridor matters.
The Netherlands → Turkey corridor is anchored by the diaspora profile — Turkish, Moroccan, Polish, Indonesian diaspora. Average ticket size is ≈$350; the destination central bank (BDDK) reports ≈$1.0B (World Bank 2024) in annual diaspora inflow.
For an operator with a tier-1 mobile subscriber base in Netherlands, this corridor is the natural Wave-1 — narrow product, partner-bank EMI cover, billing-adjacent integration on the BSS event bus. Wave-2 (wallet + card) ships in months 4–12 once corridor reconciliation is clean.
- ORIGINNetherlands · DNBCurrency: EUR
- DESTINATIONTurkey · BDDKPartner: BDDK-licensed bank
From signed term-sheet to live transfers.
Legal & licensing
Confirm origin licence scope (typically existing DNB-supervised entity) and destination receiving partner (BDDK-licensed bank).
BSS integration scoping
Read-only consumer on operator event bus. Network change request filed in week 2. No write-path to OCS.
KYC & product build
SIM-as-anchor KYC pipeline. Target 85–92% auto-approve at sanctions screen. Travel Rule (IVMS101) wired to BDDK-aligned partner.
Soft launch & public
Closed-group test → invite-only soft launch → public. Target Day-90: 100k users, ≈$20M cumulative volume.
Sequence is from our published Wave-1 corridor field note — timeline varies by BSS vintage and origin-market licensing posture.
What is specific to Netherlands → Turkey.
Money leaves Netherlands in EUR and arrives in TRY. The settlement path that carries the cost and the delay is EUR → USD → TRY — each correspondent hop pre-funds a nostro balance and takes a cut. At the last mile the recipient is paid by credit to a Turkish bank account or domestic card, via a BDDK-licensed bank.
Remittance dependency in Turkey: Low — remittances are a small share of GDP. That is what makes the corridor a defensible Wave-1 — the demand is structural, not promotional.
A MiCA-compliant EMT can collapse the EUR → USD → TRY bridge into a single on-chain hop where a licensed last-mile partner exists — see when an EMT settles faster than correspondent banking.
| FX path | EUR → USD → TRY |
| Origin currency | EUR · DNB |
| Payout currency | TRY · BDDK |
| Last-mile payout | credit to a Turkish bank account or domestic card |
| Receiving partner | BDDK-licensed bank |
| Avg ticket | $350 |
| Annual inflow | $1.0B (World Bank 2024) |
What licence does the operator need in Netherlands?
A DNB-authorised PI or EMI in Netherlands can passport to any EU/EEA destination. Coreal partners typically use an EMI passport on the wallet layer plus a local remittance licence in the origin market.
Who provides the receiving leg in Turkey?
The receiving partner is typically a BDDK-licensed bank. BDDK supervises the destination side and requires Travel Rule (FATF Recommendation 16 / IVMS101) for transfers over the threshold.
What's the unit economics for Netherlands → Turkey?
Average ticket size in this corridor is ≈$350. Destination annual diaspora inflow is ≈$1.0B (World Bank 2024). A 90-day Wave-1 typically targets 100k registered users and $20M cumulative volume — see the field note in /insights for the exact sequence.
Bring the perimeter,
leave with a brief.
Read the Wave-1 runbook first.
The full 90-day launch sequence — phases, partner-bank gates, who signs off when. No form to read it.
Read the runbook →INDICATIVE DATA · Numbers and timelines reflect public regulator filings, vendor documentation and our own delivery experience. Per-engagement values vary with operator profile, BSS vintage and regulatory perimeter. Engage early for a fitted estimate under NDA.