Why collections are usually the slowest part of a launch
Operators expect payouts to be the hard part. In practice it is often collections — taking money from the sender in the first place — that holds up a launch. The reason is underwriting. Money remittance is treated as a higher-risk category by most general-purpose payment providers, so applications go to a manual review that a typical online retailer never sees.
Plan for this. Start gateway conversations before you choose software, not after, and expect to be asked for your authorisation status, your AML policy, your expected volumes and your corridor list in the first conversation.
What makes remittance different to a gateway
Understanding why you are treated differently makes the conversation easier.
- Funds leave the country. An acquirer's usual recourse — clawing back from a merchant — is harder when the value has already been delivered abroad.
- Chargeback exposure is asymmetric. A card-funded transfer can be disputed after the payout is irreversible. The operator carries that gap.
- Fraud patterns are distinctive. Stolen-card funding of remittance is a known attack, so acquirers scrutinise it heavily.
- Regulatory overlay. You are a regulated firm, and the acquirer inherits some reputational exposure from how well you run your compliance.
None of this makes you unbankable. It means you should approach providers who already understand the sector rather than the cheapest general-purpose option.
The main collection methods
Card payments
Familiar to customers and good for conversion, particularly on mobile. The trade-offs are cost and chargeback exposure. Debit is generally viewed more favourably than credit for remittance funding, and some operators restrict credit funding for that reason.
Open banking and bank transfer
Compare account-to-account and card collection using actual provider fees, customer coverage, refund arrangements and fraud controls. Different payment methods have different dispute and reimbursement risks; bank payments are not risk-free.
Direct debit
Useful for recurring senders, less so for one-off transfers, and it carries its own reversal rules that need to be understood before you rely on it.
Cash and in-branch
Still relevant for agent-based operators. It moves the collection problem from underwriting to physical handling, reconciliation and agent float management.
What to ask a payment gateway
- Do you underwrite money remittance, and have you onboarded firms like mine? Ask this first. It saves weeks.
- What is your settlement timing? The gap between collection and settlement is working capital you have to fund, particularly if you pay out before you are settled.
- Will you hold a rolling reserve, and on what terms? Reserves are common for this sector and materially affect cash flow. Get the percentage and the release schedule in writing.
- How are chargebacks handled and what evidence do you expect? Your platform needs to be able to produce that evidence.
- Which payment methods and currencies are in scope? Confirm the ones your customer base actually uses.
- What are your fraud controls and can I tune them? Rules too tight will reject good senders; too loose and you carry the losses.
Matching collection timing to payout timing
This is the operational detail most new operators miss. If you release a payout on receipt of a card payment but the acquirer settles to you three days later, you are funding the gap. Multiply that by daily volume and it becomes the largest working-capital item in the business.
There are three ways to manage it: hold payouts until settlement, which harms the customer experience; fund the gap from your own capital; or negotiate faster settlement. Most operators use a combination, and the balance shifts as volumes grow. Model it before launch rather than discovering it in month two.
Reserves, and why they surprise people
A rolling reserve means the acquirer retains a percentage of your collections for a defined period as security against chargebacks. It is normal for this sector, it is negotiable, and it has a direct effect on how much cash you have available. Ask about it explicitly — it is rarely volunteered early.
How this connects to your platform
Validate the payment methods and countries needed, then test collection confirmation, failed payments, reversals and reconciliation records. Existing compatible connectors may reduce development but still need configuration and testing.
If Trust Payments is on your shortlist, the Trust Payments integration overview helps frame the scoping discussion; it does not confirm merchant acceptance or service availability. Prepare the documentation and operational requirements in the integration readiness checklist before agreeing implementation.
Frequently Asked Questions
Where Remitz fits
Remitz is software. We do not provide banking, payout, KYC, payment gateway or licensing services — you hold each of those relationships directly. Remitz provides the software and assesses your chosen providers against supported connectors. A compatible connection may reduce development work; API versions, services, configuration, testing and any additional work are agreed in your quotation. Provider fees remain separate.
