Tranzact · Payments Hub
You already move money and want more corridors. One connection reaches every payer.
Cross-border payments infrastructure
Connect once. Reach every payer in the network — without a contract or an integration per payer.
Coverage
Send and receive. Click any country to see how it pays out.
No country matches that search. Tell us which corridor you need and we will look into it.
Solutions
Pick the one that matches what you already have. You do not need to rebuild what works.
You already move money and want more corridors. One connection reaches every payer.
No platform yet? Sending, compliance, settlement and reporting arrive assembled.
Your brand in front, our engine behind. App, portal and gateway under your name.
You have the license and the customers. We are the rails.
Why a hub
The contract is not per country: it is per payer. Every bank, cooperative and wallet inside every country is one more negotiation, one more integration and one more counterparty to audit.
48 relationships to negotiate and maintain
1 connection. The network handles the rest
Payout methods
Across the 23 countries that publish their methods today.
Integration
We review what you have and which corridors you need. You leave with a defined scope.
Your team works against a sandbox with real documentation until the flow passes.
Production with monitoring and a named contact. New countries need no new integration.
weeks to go live
From the first call to the first real transaction, sandbox and certification included.
Developers
A REST API with Bearer authentication. Your team finds the transaction, assigns it and confirms the payout. That is the whole loop.
# 1. find the transaction GET /api/transactions/referenceNumber={refNum} # 2. assign it to payout, keep the PayoutToken POST /api/transactions/{id}/payout-assignment # 3. pay through your channel, then confirm POST /api/transactions/{id}/payout-confirmation # if you cannot pay, reject with a reason code POST /api/transactions/{id}/payout-rejection
Bank deposit, office pickup, mobile wallet, home delivery and ATM. The method travels with the transaction, so adding one costs you no new code.
Client credentials grant against the environment token endpoint. Nothing custom to learn, nothing custom to audit.
Your team certifies against a sandbox with a published Swagger spec before a single real transaction moves.
Header-based versioning. New endpoints, fields and codes are added; what your client already reads keeps working.
The full documentation is online, in English and Spanish. One page with everything: environments, authentication, the two processing flows, the transaction lifecycle, every endpoint, every field and all rejection codes.
Compliance
No bank signs on coverage alone. Their risk committee reads this first.
Sanctions and PEP lists checked on every transaction, with an audit trail per operation.
Reports your regulator accepts, and settlement reconciled per corridor.
A team you can call, not a shared inbox: compliance@tranzmit.net
Tranzmit holds its MSB registration with FinCEN. The state money transmitter license is held by the MTO originating the operation in each state.
Every payer in the network operates under the license its own regulator requires, in its own country.
Partners
Sixteen operators send and pay out through Tranzmit today.
Contact
Someone from the commercial team answers within one business day.