About Trust Payments
Trust Payments provides payment gateway and acquiring services, handling the collection side of a remittance transaction: taking the sender's payment by card or an alternative method before the payout leg begins.
Confirm that the provider will accept your specific remittance business model before planning a card-funded launch. Approval, supported payment methods, settlement terms and fees are agreed with the provider, not supplied by Remitz.
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.
- Card acquiring
- Online payment collection
- Alternative payment methods
Delivery methods to validate
- Debit and credit card
- Alternative payment methods
Which of these are available to you is set by your own agreement with Trust Payments, not by Remitz.
Typical use cases
- Digital-first operators collecting from senders online or in-app.
- Businesses that need a gateway willing to underwrite remittance as a sector.
- Operators offering card funding alongside bank transfer or open banking.
How Remitz integrates Trust Payments
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 Trust Payments services. You hold the commercial relationship with Trust Payments 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.
