Remittance API Integrations | Payout & KYC

Provider options to validate

Payout & mobile money

Fincra TerraPay Tranglo Nsano Zeepay Kora Fliqpay MFS Africa e-pocket CashMinute Payceler SmallWorld

KYC, AML & identity

Onfido Yoti Trulioo SignX Rapid ID

Payments & collections

Trust Payments Monoova Volume Payments Open Banking

FX provider connections

USI Money Currency Cloud Verto GeoSwift

Communications

Twilio Clickatell SendGrid Mailchimp

Address verification

GetAddress AddressFinder

Available on request

DT One — airtime top-up connector scope and availability confirmed during onboarding

These names are options for discussion, not a current availability register or an endorsement. Confirm the provider, connector version and services before committing. Additional APIs require technical assessment and an agreed quotation. Product names belong to their owners.

What needs to connect

Payout Networks

Confirm your payout provider’s supported destinations, delivery methods and status updates. A connector does not automatically enable every service on the provider’s network.

KYC & AML Providers

Agree identity checks separately from sanctions and PEP screening. Your contracted services determine coverage; your compliance team sets policy and reviews results.

FX & Rate Sources

Connect your rate source and agree the required FX workflows. Your banking and FX providers supply accounts and liquidity; Remitz does not.

Payment Gateways

Connect contracted payment services for customer funding. Available payment methods, onboarding, settlement and fees are determined with your provider.

SMS & Communications

Scope verification messages and transaction notifications with your messaging provider. Delivery depends on its service, destination rules and your configuration.

Email Services

Agree receipt and notification templates, sender setup and email-provider access. Marketing consent and communication policies remain your responsibility.

Airtime & VAS

Discuss DT One airtime top-up requirements separately from remittance payouts. Confirm current products, destinations, commercial access and connector scope before including them in your offer.

Address Verification

Review supported address-lookup services for your onboarding markets. Address lookup alone does not establish identity or replace your required customer checks.

Custom API Integration

Bring API documentation and required workflows. We assess feasibility and quote development, testing and support scope. Arrange credential access through an agreed secure channel, not the public enquiry form.

Integration detail

How each connector actually works

Use these provider pages to prepare a scoping discussion. They do not replace current provider documentation, contracts or confirmation of the services available to your business.

TerraPay

Cross-border payouts to bank accounts and mobile wallets.

Tranglo

Cross-border payouts with depth across Asian corridors.

Fincra

Collections and local payouts across African markets.

Onfido

Document and biometric identity verification at onboarding.

Trulioo

Database-backed identity verification across many markets.

Trust Payments

Card and alternative payment collection from senders.

Your provider strategy should lead

Your remittance software should fit your provider strategy. An existing connector can reduce development work, but it does not grant a provider account or automatically enable every service and market.

What to prepare for an integration discussion

Your provider relationship. Name the provider and whether you are evaluating, applying or already contracted. Remitz does not supply the account or guarantee onboarding.
The services you need. List sending and payout markets, currencies, delivery methods and required identity or screening checks. Confirm these with the provider.
Technical documentation and access. Share API documentation and version details. Arrange test access and credentials through an agreed secure channel; do not send API keys, passwords or customer records through the public enquiry form.
Operational test cases. Describe successful, pending, failed and reversed transactions, review decisions and reconciliation evidence you need to validate.
An agreed implementation scope. Confirm compatible services, configuration, any new development, testing, support and costs. Remitz fees and third-party provider fees are separate.

If provider onboarding is unfinished, we can discuss requirements, but implementation timing remains conditional on provider readiness, credentials, configuration and testing. If you are replacing a provider, include historic records and cutover requirements in the assessment.

Review software pricing, then book a demo with your provider list and required workflows.

Frequently Asked Questions

What APIs does Remitz integrate with?

Remitz connects software with the operator's chosen payout, KYC, payment, FX and communication providers. The provider options listed here are a starting point for scoping, not a promise of every service or corridor. Confirm the supported connector, provider contract, credentials and any development needed for your implementation.

Can I bring my own payout partner to Remitz?

Bring the provider API documentation and your requirements to scoping. Remitz assesses technical feasibility, supported services and testing needs before quoting any new integration work. You arrange the provider account and commercial agreement.

How long does it take to integrate a new API with Remitz?

Integration timing depends on the connector, provider onboarding, documentation, credentials and testing. Existing compatible connections may reduce development work; new APIs need an agreed implementation schedule.

Remittance API Integrations — Payout, KYC and FX Partners