Photo by EmilyStock
Choosing a payment service provider (PSP) is one of the highest-stakes decisions you will make as a remittance operator — and the pool of PSPs willing to work with money transfer businesses is far smaller than the market suggests. Most mainstream Australian PSPs classify remittance as high-risk and decline onboarding outright, so your real task is identifying which providers actively serve MTOs, then comparing them on collection rails, settlement speed, fee structure, and compliance alignment.
The wrong PSP costs you more than money. A provider that suddenly offboards you mid-quarter can freeze inbound customer funds, break your safeguarding obligations, and leave beneficiaries unpaid. This guide walks you through the PSP landscape for Australian remittance, the integration options available, the fee components that erode your margin, and the specific compliance questions to ask before you sign anything.
Key Takeaways
- Most mainstream PSPs decline remittance operators — you need providers with explicit high-risk or MTO appetite, not generic merchant acquirers.
- Collection rails matter more than headline pricing — PayTo, PayID/NPP, and card acquiring each carry different settlement speeds, chargeback exposure, and cost.
- Compare total cost of acceptance, not advertised rates: transaction fees, settlement fees, chargeback fees, FX margins, and minimum monthlies all compound.
- Ask compliance questions upfront — how the PSP handles safeguarding, offboarding notice periods, and their own AUSTRAC or ASIC obligations under the 2026 reforms.
- Redundancy is a survival strategy — running two PSPs protects you when one reviews or exits the remittance sector.
What a PSP Actually Does for a Remittance Business
A payment service provider sits at the collection end of your money transfer flow — the point where you take Australian dollars from your sending customer. This is distinct from your correspondent banking or payout partners on the beneficiary side.
When a customer funds a transfer, the PSP processes that inbound payment through one or more rails: card acquiring (Visa/Mastercard), account-to-account transfers via the New Payments Platform (NPP), PayID, PayTo, or direct debit through the Bulk Electronic Clearing System (BECS). The PSP authorises the payment, manages fraud and chargeback risk, and settles the funds into your operating or client account.
For remittance, the PSP's role is complicated by two facts. First, you are moving money on behalf of customers, which triggers safeguarding obligations under Treasury's incoming PSP licensing reforms. Second, your business is a reporting entity under the AML/CTF Act 2006, and your PSP needs to understand — and tolerate — the transaction patterns that come with cross-border money movement.
Why Most PSPs Won't Work With Remittance Operators
Remittance is a high-risk merchant category. According to card scheme classifications, money transfer sits alongside gambling, crypto, and adult services as a sector where acquirers apply the strictest underwriting.
The reasons are structural:
- Chargeback exposure — cross-border money movement is a prime target for payment fraud and friendly fraud, and once funds are paid to an overseas beneficiary they cannot be clawed back.
- De-banking spillover — the same de-risking pressure that closes MTO bank accounts (a documented crisis in the Australian market) extends to PSPs, whose own banking partners scrutinise the merchant portfolios they support.
- AML/CTF liability — PSPs worry about being drawn into your compliance failures, especially where scam-driven payment redirection losses reached AUD 2.18 billion in 2025 across the Australian economy.
The practical result: when you approach a generic acquirer or a Stripe-style aggregator, remittance is frequently on the prohibited or restricted list. You need providers who have deliberately built appetite for regulated money transfer businesses.
PSPs and Rails Currently Available to Australian MTOs
No single provider suits every MTO. Your choice depends on volume, corridor mix, customer payment preferences, and how much integration you can support. The categories below reflect the options Australian remittance operators use in 2025–2026.
Account-to-account rails (NPP, PayID, PayTo)
Account-to-account collection has become the preferred rail for many MTOs because it sidesteps card chargebacks entirely. PayTo, built on the NPP, lets you set up authorised payment agreements ('mandates') with customers, then initiate real-time pull payments — ideal for repeat senders. PayID enables instant push payments referenced to your business identifier.
The advantages are compelling for remittance: near-instant settlement, no interchange fees, and dramatically reduced fraud reversal risk because bank-initiated payments are authenticated at source. The trade-off is that A2A rails require the customer to bank in Australia and are less suited to first-time or one-off senders who default to cards.
PSPs offering PayTo/NPP access to MTOs include specialised Australian fintech providers such as Zepto, Monoova, and Azupay, all of which have positioned themselves toward regulated and high-volume merchants including money movement businesses.
Card acquiring
Card acquiring remains important for capturing first-time customers and international-card senders. The cost and risk are higher — you pay interchange plus scheme fees plus the acquirer margin, and you carry chargeback liability.
For remittance, look for acquirers with explicit high-risk underwriting and 3-D Secure enforcement. Some MTOs work with international high-risk acquirers where domestic appetite is thin, though this adds cross-border settlement complexity and often higher rolling reserves.
Direct debit (BECS)
Direct debit via BECS offers low per-transaction cost but slow settlement (typically same-day to three business days) and dishonour risk. It suits established, lower-risk repeat customers rather than new senders. Providers like Monoova and Ezidebit support BECS collection, though the multi-day clearing window creates a funding gap you must manage against your payout timing.
Aggregated / embedded solutions
Embedded finance platforms have expanded MTO options. Wise Platform's move into hosted KYC and funding APIs, and CDR-enabled open banking data for onboarding, mean some PSPs now bundle collection with verification and account data. These reduce build effort but tie you more tightly to one provider — weigh convenience against concentration risk.
Comparing PSP Rails: Speed, Cost, and Risk
| Rail | Settlement Speed | Typical Cost | Chargeback / Reversal Risk | Best For |
|---|---|---|---|---|
| PayTo / NPP | Real-time | Low fixed fee per transaction | Very low | Repeat senders, high volume |
| PayID push | Real-time | Low fixed fee | Very low | Tech-comfortable customers |
| Card acquiring | 1–2 business days | 1.5%–3.5%+ per transaction | High | First-time / one-off senders |
| Direct debit (BECS) | 1–3 business days | Very low fixed fee | Moderate (dishonours) | Established repeat customers |
The pattern is clear: A2A rails minimise both cost and reversal risk, while cards maximise customer reach at the highest cost and exposure. Most mature MTOs run a blend — cards to acquire, PayTo to retain.
Fee Structures: What to Compare Beyond the Headline Rate
PSP pricing is deliberately hard to compare. The advertised rate is rarely your true cost. Break every proposal down into these components:
- Transaction fee — per-payment charge, either a fixed amount (A2A) or a percentage plus fixed (cards).
- Settlement fee — some PSPs charge per payout to your account or per batch.
- Chargeback fee — a fixed penalty (often AUD 15–25) per dispute, on top of the reversed amount.
- Rolling reserve — the PSP holds a percentage of your turnover (commonly 5%–10%) for a set period as security. This directly affects your working capital.
- Minimum monthly fee — a floor you pay regardless of volume.
- FX margin — if the PSP converts currency, the spread they take, which can dwarf the transaction fee.
- Onboarding / setup fee and API integration cost.
Sample cost comparison
Consider two PSPs for a monthly card-collection volume of AUD 500,000 across 1,000 transactions:
| Component | PSP A (low rate, high fees) | PSP B (higher rate, clean fees) |
|---|---|---|
| Transaction rate | 1.6% + AUD 0.30 | 2.2% + AUD 0.20 |
| Volume cost | AUD 8,300 | AUD 11,200 |
| Monthly minimum | AUD 500 | AUD 0 |
| Rolling reserve | 10% (AUD 50,000 held) | 5% (AUD 25,000 held) |
| Chargeback fee | AUD 25 | AUD 15 |
| Effective cash impact | Higher — capital tied up | Lower — better cash flow |
PSP A looks cheaper on rate but ties up double the working capital in reserve and adds a monthly floor. For a cash-flow-sensitive MTO, PSP B may be the better commercial decision despite the higher headline rate. Always model total cost of acceptance against your actual volume and reserve tolerance.
The Compliance Questions to Ask Before Signing
A PSP contract is a compliance relationship, not just a commercial one. Ask these questions explicitly — and get the answers in writing — before you commit.
1. How do you handle safeguarding of customer funds?
Under Treasury's PSP licensing reforms and the incoming safeguarding regime, funds you hold on behalf of customers must be protected. Confirm whether the PSP segregates your collected funds, how quickly they settle to your safeguarding account, and whether they have any claim over held funds in an insolvency scenario. This intersects directly with your own safeguarding obligations as a remittance business.
2. What is your offboarding notice period?
The single most damaging PSP event is a sudden exit. Ask for the contractual notice period for offboarding, the circumstances that trigger immediate termination, and what happens to in-flight and reserved funds. A 30-day minimum notice is reasonable; anything allowing instant termination without cause is a serious risk. Negotiate this before you sign.
3. Do you support remittance as a permitted business category?
Get explicit written confirmation that your AUSTRAC-registered remittance activity is a permitted — not merely tolerated — merchant category. Verbal assurances from a salesperson do not survive an internal risk review.
4. How do you expect me to manage AML/CTF and transaction monitoring?
Understand what data the PSP shares with you (and with AUSTRAC), how they flag suspicious activity on their side, and whether their obligations overlap or duplicate yours. Clarify who files what — your suspicious matter reports and IFTI/IVTS reporting obligations remain yours regardless of the PSP.
5. What are your own regulatory obligations under the 2026 reforms?
The 2026 AML/CTF Reform and Treasury's payments licensing changes affect PSPs directly. A PSP that understands its own obligations is far less likely to abruptly de-risk your sector. Ask whether they hold or are pursuing the relevant licensing and how the reforms change their appetite for MTO clients.
6. What fraud and chargeback tools do you provide?
Given the scale of payment redirection scams, ask about 3-D Secure enforcement, real-time fraud scoring, velocity checks, and chargeback dispute support. These directly reduce your losses and your exposure to reversed transactions.
Integration Options: Build Effort vs Control
How you connect to your PSP determines your engineering burden and flexibility.
- Hosted payment page — the PSP hosts the collection flow; lowest build effort, least branding control, and the PSP carries more PCI-DSS scope. Good for smaller MTOs.
- API integration — you call the PSP's API directly from your platform for full control over customer experience and reconciliation. Requires developer resource and greater PCI-DSS responsibility for card data.
- SDK / embedded widgets — a middle path offering brand-consistent flows with reduced compliance scope.
- Bank feed / file-based — for BECS and some A2A flows, batch file exchange or bank feeds suit lower-frequency, higher-value collections.
Match the integration to your team's capability. A robust API is worthless if you cannot maintain it; a hosted page that limits reconciliation automation will cost you operationally at scale.
Build Redundancy: Never Rely on a Single PSP
The de-banking and de-risking history of Australian remittance makes single-PSP dependence a survival risk. If your only collection provider reviews and exits — as happens across the sector — you lose your ability to take customer funds overnight.
Run at least two PSPs where volume justifies it, ideally across different rails (for example, one card acquirer and one PayTo provider). This gives you failover capacity, negotiating leverage, and the ability to route transactions by cost and risk. The operational overhead of maintaining two integrations is small compared with the existential risk of a single point of failure.
Your PSP Selection Checklist
Before signing, confirm you can tick every box:
- The PSP explicitly permits AUSTRAC-registered remittance activity in writing.
- You have modelled total cost of acceptance against your real volume and reserve.
- The offboarding notice period is at least 30 days and documented.
- Safeguarding and fund-segregation arrangements are clear and align with your obligations.
- Fraud, chargeback, and 3-D Secure tooling is adequate for your corridors.
- The integration method matches your team's technical capacity.
- You have a second PSP or a credible plan for one.
Conclusion
Choosing a PSP for your remittance business is a decision about resilience as much as price. The providers willing to serve Australian MTOs are a specialised group — favour those with explicit remittance appetite, transparent total-cost pricing, generous offboarding terms, and a genuine understanding of their obligations under the 2026 reforms. Then build redundancy so no single provider can shut down your collection overnight.
Get the collection layer right and you protect your margin, your safeguarding compliance, and your ability to keep paying beneficiaries when the market shifts.
This information is general in nature and does not constitute legal advice. Consult AUSTRAC or a qualified legal professional for advice specific to your situation.
For help structuring the compliance side of your operation, use our AML/CTF Program builder, and explore corridor-specific funding considerations across our corridor guides. Stay current on payments and licensing changes with our newsletter.
Frequently Asked Questions
Why do most payment service providers reject remittance businesses?
Remittance is classified as a high-risk merchant category by card schemes and acquirers due to chargeback exposure, AML/CTF liability, and de-risking pressure from the PSPs' own banking partners. Once funds are paid to an overseas beneficiary they cannot be recovered, so acquirers apply strict underwriting or prohibit the category entirely. You need providers who have deliberately built appetite for regulated money transfer businesses.
What is the difference between a PSP and a correspondent bank for an MTO?
A PSP sits at the collection end of your flow — it takes Australian dollars from your sending customer through rails like cards, PayTo, or direct debit. A correspondent bank sits at the payout end, moving funds to beneficiary institutions overseas. You typically need both, and they solve entirely different problems in your money transfer chain.
Should I use PayTo or card acquiring for my remittance business?
Most mature MTOs use both. Card acquiring captures first-time and one-off senders but carries high cost and chargeback risk. PayTo and other NPP rails offer real-time settlement, low fixed fees, and minimal reversal risk, making them ideal for repeat customers. A blended approach — cards to acquire, PayTo to retain — optimises cost and reach.
What is a rolling reserve and how does it affect my cash flow?
A rolling reserve is a percentage of your turnover (commonly 5%–10%) that the PSP holds for a set period as security against chargebacks and fraud. It ties up working capital directly — a 10% reserve on AUD 500,000 monthly volume holds AUD 50,000 out of reach. Always factor reserve requirements into your total cost of acceptance comparison, not just the headline transaction rate.
How much notice should a PSP give before offboarding me?
Negotiate a minimum offboarding notice period of 30 days, documented in your contract, along with clarity on what happens to in-flight and reserved funds. Contracts allowing instant termination without cause are a serious risk, because a sudden PSP exit can freeze inbound customer funds and break your safeguarding obligations. Running a second PSP protects you regardless.
