Reference stack
Launch cross-border remittance and payouts
A remittance and payout stack spanning collection, FX, recipient verification, local payout networks, treasury, AML and reconciliation.
Remittance companiesPayroll platformsMarketplaces
Intended audience and markets
Audience
Remittance companiesPayroll platformsMarketplaces
Markets
Global
Infrastructure layers
01
Collection accounts and funding
RequiredReceive sender or business funds in origin markets.
Selection criteria
- Funding methods
- Account and safeguarding model
- Returns and chargebacks
02
FX and treasury
RequiredConvert and prefund required currencies.
Selection criteria
- Spread and fee model
- Cut-offs and liquidity
- Hedging and prefunding
03
Payout networks
RequiredReach bank accounts, cards or wallets in destination markets.
Selection criteria
- Country and rail coverage
- Delivery time and traceability
- Returns and recipient fees
04
Recipient verification and compliance
RequiredVerify recipients and screen payment parties.
Selection criteria
- Name matching
- Sanctions and PEP coverage
- Corridor risk
05
Reconciliation and customer support
RequiredTrack end-to-end status, returns and investigations.
Selection criteria
- Unique end-to-end reference
- Status transparency
- Exception and complaint workflow
Implementation sequence
- Collection accounts and funding
- FX and treasury
- Payout networks
- Recipient verification and compliance
- Reconciliation and customer support
Regulatory considerations
- Remittance and payout services commonly require licences in origin and destination markets.
- Corridor restrictions, sanctions and consumer disclosures must be assessed individually.
Technical considerations
- Maintain traceability across every intermediary and currency conversion.
- Design for failed, delayed, returned and misdirected payouts.
Questions to ask providers
- Which legal entity contracts for each service and in which jurisdictions?
- Which responsibilities remain with the product operator rather than the provider?
- What are the implementation, approval, testing and migration timelines?
- How are incidents, exits, data portability and business continuity handled?
- Who has the sender and recipient relationship in each corridor?
What this stack does not cover
- Cash agent networks and local licensing counsel are not fully covered.
Related stacks
Reviewed on 2026-07-07.
Provider options are examples of infrastructure roles, not endorsements or a guarantee of suitability, availability or regulatory compliance. Confirm requirements for your product with each provider and qualified advisers.