FYNIX Beta
Corridors

Six representative flows. Ten launch jurisdictions. One coverage story.

The operations pack ships with six worked corridor diagrams, not one per country pair. It's how we tell the money-movement story — from origination to payout — with enough depth for regulators, partners and investors, without drowning in permutations.

Wave 1 launch corridors

The six flows we've worked end-to-end

Each corridor documents entities, KYC, funding, FX, payout, reconciliation, and exception handling. Together they cover student, worker and family flows on both directions of our launch footprint.

Student · West

India → United Kingdom

Parent or student funds an INR/USD sponsor wallet. FYNIX orchestrates KYC on both wallets, initiates GBP tuition payment via a named GBP virtual account, and settles with reconciliation across three ledgers.

Rails: GBP virtual account + licensed payout partner
Student · West

India → United States

USD tuition flow using a named US virtual account. Uses ACH funding paths that are exempt from the 1% US cash-funded remittance tax — a structural tailwind versus cash-heavy incumbents.

Rails: USD virtual account + licensed payout partner
Student · APAC

India → Australia

AUD tuition and living-expense funding routed via our APAC last-mile partner, with named-account funding-reference issuance at origin.

Rails: APAC last-mile partner + named funding accounts
Student · EU

India → EU (SEPA)

EUR tuition to Continental European universities via SEPA payout, on named EUR virtual accounts. A secondary SEPA relationship sits ready as backup if volume or primary-partner capacity requires it.

Rails: EUR virtual account + SEPA payout partner
Worker · MENA

UAE → India worker remittance

Salary collected in AED at destination, KYC'd worker wallet, and licensed INR payout to family in India. Corridor-tailored pricing and full audit trail across all three ledgers.

Rails: AED virtual account + licensed INR payout partner
Worker · APAC

Singapore → Bangladesh worker remittance

SGD salary collection, licensed BDT payout through our APAC last-mile partner and destination partner. Includes local instant-payment ingress for worker top-ups.

Rails: SGD collection partner + BDT payout partner
Strategic corridor

US → Mongolia

A partnership-led corridor with a US-based Mongolian exchanger and licensed Mongolia-side bank/NBFI partners. Historical informal activity does not migrate. The formal corridor begins only with new customers who pass KYC and banking-channel controls.

  • ✓ Structured B2B2C: partner brings customers, FYNIX brings platform, ledger, compliance
  • ✓ Persistent introducer attribution + 24–36 month tail
  • ✓ Pilot caps, manual review of large transfers, daily tri-party reconciliation
Three-rail contingency

Pricing bands by rail

SWIFT fallback Day-one

Proves viability. Priced closer to Remitly.

PSP direct 2.50–2.75%

Independent base case. Protects viability without a direct bank relationship.

Destination bank direct 2.00–2.25%

Direct relationship with a Mongolia-side bank. Structural best case — corridor moat.

Coverage narrative

Where we hold named accounts — and where we collect

Named-account footprint reads as global coverage. Wave 1 keeps the launch focused on markets our rail partners are already ready to underwrite.

vIBAN coverage · Target

Named USD, EUR, GBP, AED and SGD accounts issued through our banking partners

🇺🇸USA
🇬🇧UK
🇪🇺EU
🇸🇬Singapore
🇦🇪UAE
🇲🇾Malaysia
🇭🇰Hong Kong
🇦🇺Australia
🇨🇦Canada
🇯🇵Japan

Source markets · Collections

Where FYNIX or partner rails support in-market collection for students and workers

🇮🇳India
🇱🇰Sri Lanka
🇳🇵Nepal
🇲🇾Malaysia
🇸🇬Singapore
🇮🇩Indonesia
🇲🇳Mongolia
🇹🇱Timor-Leste

Mongolia is included as a migrant-worker remittance source, not a student-source market.

Benchmark · illustrative

On a USD 210 transfer to Mongolia…

Incumbent

Remitly · card-funded

USD 8.34

USD 1.99 transfer fee + USD 6.35 card fee. Total sender cost on the same USD 210.

FYNIX target

2.00–2.50% all-in

USD 4.20–5.25

Same USD 210 transfer, priced through our target rail bands. Illustrative, before rail-specific caveats.