Cross-Border Remittance & International Money Transfer App
Build a consumer or B2B remittance product that moves money across borders with competitive FX rates, local payout rails, and AML compliance.
The Stack
CurrencyCloud
— FX conversion and multi-currency settlementCurrencycloud (now part of Visa) provides API-based FX at interbank-adjacent rates, virtual multi-currency accounts per customer, and settlement in 35+ currencies. The Collections and Payments API covers the full corridor in a single integration.
Alternatives: airwallex, wise, nium
Airwallex
— Alternative multi-currency infrastructure with built-in SWIFT and local rails optionalAirwallex offers global accounts, local collection in AU/UK/EU/US/HK/SG, FX conversion, and payouts to 150+ countries. Strong option if you need to collect in APAC (Australia, Singapore, HK) and pay out in LatAm or Africa.
Nium
— Real-time cross-border payments network (B2B) optionalNium's licensed network reaches 190+ countries with real-time bank transfers to 100+ markets. Particularly strong for B2B corridors (SMB payroll, supplier payments) with a single API connection to local rails globally.
Thunes
— Last-mile payout to mobile money and cash networks in Africa, LatAm, APAC optionalThunes connects to 700+ mobile money wallets and cash agent networks across Africa (M-Pesa, MTN MoMo), LatAm, and Southeast Asia — corridors where bank account penetration is low. Essential for true financial inclusion remittance.
Alternatives: chipper-cash, flutterwave, dlocal
dLocal
— Card collection and local payment methods in LatAm, Africa, APAC optionaldLocal provides a single API to accept payments via local methods in 40+ emerging markets (Boleto in Brazil, OXXO in Mexico, M-Pesa in Kenya). Critical for the 'sender side' when your users are in emerging markets.
Stripe
— Card and bank debit collection in developed markets (US, EU, UK, AU)For the sender-side in North America and Europe, Stripe handles card, ACH Debit, SEPA Direct Debit, and BACS. Low integration friction and 3DS2 compliance out of the box.
Sumsub
— Global KYC/AML onboarding and ongoing monitoringRemittance products need KYC at onboarding (ID + selfie), sanctions screening at transaction time, and ongoing monitoring for high-risk customers. Sumsub's 220-country coverage makes it the default choice for multi-corridor products.
Alternatives: jumio, onfido, trulioo
ComplyAdvantage
— Real-time sanctions, PEP, and adverse media screeningEvery transfer must screen both sender and recipient against OFAC SDN, EU sanctions, and PEP lists in real time. ComplyAdvantage updates within 15 minutes of new designations and exposes a REST API for transaction screening.
Alternatives: chainalysis, elliptic
Unit21
— AML transaction monitoring and SAR managementAs a Money Services Business, you must file SARs within 30 days of suspicious activity. Unit21 provides rule-based transaction monitoring (structuring detection, velocity rules, corridor-specific thresholds) and a case management dashboard for SAR filing.
Alternatives: sardine, feedzai
Hummingbird
— SAR/CTR filing workflow and BSA officer tooling optionalHummingbird streamlines the FinCEN SAR filing process with auto-populated forms, workflow approvals, and audit trails. Designed for the BSA officer role that every US MSB must maintain.
Gotchas
- ⚠️ Money Transmitter Licences (MTLs): remittance is the most heavily licensed fintech vertical. In the US you need an MTL in each state you operate in (or use a licensed partner/sponsor bank). In EU you need an EMI or PI licence. Budget 12–18 months and $500K+ in legal fees for direct licensing.
- ⚠️ Corridor-specific compliance: FATF travel rule requires you to share sender/beneficiary data for transfers >$3,000 (US) or €1,000 (EU). Implement travel rule compliance from day one — retrofitting is painful.
- ⚠️ FX margin vs spread: remittance companies make money on FX spread. CurrencyCloud and Airwallex charge a markup over interbank. Negotiate rates early — at low volume expect 0.5–1.5% spread; at >$10M/month you can negotiate down to 0.1–0.3%.
- ⚠️ Bank account verification before payout: always verify recipient bank accounts (micro-deposit or instant verification) before sending. Failed payouts in APAC and Africa are expensive to reverse or re-route.
- ⚠️ Sanction screening latency: your compliance provider must return results in <500ms so you can block the transaction inline. Test your p99 latency under load — slowdowns cause transaction failures, not just delays.
- ⚠️ Stale rate locks: FX quotes are typically locked for 30–60 seconds. If the user takes longer to confirm, re-quote. Stale rates at high volume create FX exposure that compounds quickly.
Related Stacks
KYC / KYB Compliance API Stack for Fintech
Verify individual and business customers at onboarding, screen against sanctions and PEP lists, and monitor ongoing AML risk — all via API.
Two-Sided Marketplace Payments (Airbnb / Uber Style)
Accept payments from buyers, split funds, and pay out providers — with chargebacks, compliance, and tax forms handled.
Fiat-to-Crypto On-Ramp Integration for Your App
Let users buy crypto with card or bank transfer directly inside your app, without building a money transmitter from scratch.