About TerraPay
TerraPay operates a cross-border payment network used by money transfer operators, banks and wallet providers to move funds into destination markets. Its focus is interoperability: connecting a sending institution to bank accounts and mobile money wallets in receiving countries through a single integration rather than a separate agreement per market.
For an MTO, that means one commercial relationship can open several payout markets at once. It is typically used by operators who want breadth across multiple corridors without negotiating individually with banks and wallet operators in each destination.
Provider services to discuss
This provider overview is not a connector availability register. Confirm the current API, services, markets and Remitz implementation scope before relying on any option below.
- Cross-border payouts
- Mobile wallet delivery
- Bank account deposits
Delivery methods to validate
- Bank deposit
- Mobile wallet
Which of these are available to you is set by your own agreement with TerraPay, not by Remitz.
Typical use cases
- Operators launching several corridors at once who want breadth from a single payout agreement.
- Diaspora corridors where mobile wallet delivery matters as much as bank transfer.
- Operators adding destination markets without renegotiating local partnerships each time.
How Remitz integrates TerraPay
Confirm supported services and connector status during scoping. Existing compatible connections can reduce development work; your quotation identifies included configuration, testing and any additional development. Provider fees are separate.
For an agreed implementation, you supply your provider credentials through the agreed secure process. Remitz configures supported connections and tests the launch scope with you, including rejected requests, status updates and reconciliation records. New API services may require additional development.
Remitz does not resell, introduce or provide TerraPay services. You hold the commercial relationship with TerraPay directly, complete their onboarding and due diligence, and supply your own API credentials.
Remitz connects those credentials to a connector that is already built and already running in production for other operators — which is why this step is configuration rather than development. See step six of the launch process for where it sits in the timeline.
Frequently Asked Questions
Talk through your provider set
Bring your provider shortlist, target services and launch requirements. We will discuss compatibility and identify what needs technical validation or a separate quotation. Provider onboarding and approval remain outside Remitz’s control.
