Partner economics
- KYC charges
- Transaction charges
- FX spread
- Platform fees
- Revenue share
- Relevant partner cross-sell opportunities
Partner corridorsUS-side to destination-side operating model
Launch local payment corridors without rebuilding every rail from scratch.
Twynex helps regulated partners extend American payment relationships into local payment experiences abroad through corridor-specific routing, reporting, reconciliation, and partner coordination.
Discuss a partner corridorPartner outcomes
Keep customers active abroad while creating new corridor economics.
Keep customers active when they travel, trade, or support obligations abroad
Create new international transaction activity and corridor revenue opportunities
Participate in FX spread, platform fee, transaction fee, or revenue-share models where appropriate
Launch local payment corridors without asking every partner to build every rail integration from scratch
Improve routing visibility, reconciliation, settlement reporting, and auditability across corridors
Partner role matrix
Clear responsibilities across US-side, destination-side, and orchestration roles.
Twynex is positioned as the corridor operating layer while regulated partners retain ownership of applicable financial flows.
Operating model
Partner-owned flows, coordinated centrally
US-side partner
Customer relationship, distribution, and applicable US-side flows
Twynex orchestration
Routing, partner instructions, metadata, status, and reconciliation
Destination partner
Local rail access, regulated processing, merchant or payout reach
Control layer
Partner-led KYCAudit trailFX metadataSettlement reporting
US partner bank
Owns or supports US-side accounts and regulated flows, performs or coordinates KYC as applicable, and provides customer distribution or payment relationship access.
US issuer
Extends payment utility for travelers and business users while participating in transaction economics, reporting, and customer retention.
Destination-country bank or regulated partner
Provides local rail access, merchant reach, payout capabilities, and local operating support.
Reseller or market development partner
Supports corridor development, local distribution, collections, and partner acquisition.
Twynex
Orchestrates routing, FX metadata, compliance metadata, partner instructions, status, reconciliation, reporting, corridor setup, and product configuration.
How it works for partners
Start with one payment moment, then expand by rail, country, and service module.
- 1Define the payment moment, corridor, and service module
- 2Confirm US-side partner, destination partner, local rail, and customer journey
- 3Configure transaction orchestration, FX metadata, compliance metadata, and reporting needs
- 4Pilot with defined countries, partner accounts, and operating procedures
- 5Expand by corridor, service module, and local rail
Operating model
Designed around regulated partner ownership where applicable.
KYC is performed by partner banks or regulated partners. Payment flows move through partner-owned accounts where applicable, and sensitive data remains in partner systems where possible. Twynex coordinates the operating layer around those partner responsibilities.
Integration and reporting
API or embedded partner flows can support routing, local rail connectivity, transaction status, reconciliation, settlement reporting, audit trails, and proof of provenance.
Partner FAQ preview
The right corridor discussion starts with ownership, rails, and operations.
Read FAQWho owns the customer relationship?
Who performs KYC?
Which countries are supported first?
What rails can Twynex support?
How are disputes, refunds, and reconciliation handled?
Start a corridor discussion