Accepting payments in Australia and New Zealand. 6 chapters and a final quiz.

Chapter 1. Scoping the launch: two markets with nothing in common.

“Australia and New Zealand” is sold as a region, but it isn’t one. There are two currencies, two central banks, and two authorities that set the cost of acceptance by public decision. You can’t derive a New Zealand rate schedule from an Australian one, and the two countries’ regulatory timelines don’t share a single date. Your first launch task, then, is to split what your team has been treating as one project: two contracts, two sets of pricing parameters, two compliance plans.

The tax line deserves a closer look, because it changes the amount you authorize. Both countries collect their tax at checkout on low-value imported goods rather than at the border, up to A$1,000 per item in Australia and NZ$1,000 in New Zealand. A foreign seller whose local sales exceed the threshold must register, charge the tax, and remit it. Your pricing engine therefore needs to know the delivery country before it builds the amount to authorize. An error here hits every transaction, not just a few.

• Pick your entry country: launching Australia first gives you the NPP, and with it refunds in seconds; launching New Zealand first means handling deferred settlement from day one
• Choose the settlement currency for each country, then check where conversion happens: at the acquirer, at your bank, or in your accounting
• Check the pricing model on offer: without interchange plus plus, regulatory cuts to the caps will never reach you
• Map the recurring-payment rails before you promise subscriptions: BECS, PayTo, and BPAY in Australia; New Zealand BECS and API-initiated payments in New Zealand
• Put the four regulatory dates in your project plan: December 1, 2025, and May 1, 2026, for New Zealand; October 1, 2026, and April 1, 2027, for Australia
• Treat tax as payment data: the authorized amount includes GST, and the registration threshold needs continuous monitoring

Chapter 2. NPP, Osko, and PayID: naming what you need.

The New Payments Platform (NPP), run by NPP Australia, a subsidiary of Australian Payments Plus (AP+), clears and settles individual payments in seconds, around the clock, natively in ISO 20022. One practical point determines how productive your conversations with an Australian bank will be: the NPP is not for sale. What you order are the services built on top of it: Osko for transfers, PayID for addressing, PayTo for mandates. A spec that asks for “an NPP connection” comes back without a quote, while one that asks for “outbound Osko payments addressed by PayID, with the payee’s name returned” gets priced.

Think of PayID as a security control as much as a convenience. The service resolves an alias to an account, then shows the payer the account holder’s name before confirmation, which puts the check at the moment of sending. For a merchant paying out funds to third parties, this is the only step where a wrong account detail can still be caught. An Osko payment is final within seconds. Wire the returned name into your payout interface, and require human confirmation above an amount threshold you set.

{
  "rail": "npp_osko",
  "amount": 24500,
  "currency": "aud",
  "payee": {
    "payid_type": "MOBILE",
    "payid": "+61400000000"
  },
  "remittance_information": "Refund for order CMD-2026-1042 - 2 items",
  "idempotency_key": "payout_CMD-2026-1042_v1"
}

// Response: the resolved name must be shown BEFORE confirmation.
// {
//   "status": "requires_confirmation",
//   "payee_name_resolved": "JANE JOHNSON",
//   "payid": "+61400000000"
// }

Chapter 3. PayTo: wiring the mandate, rewriting the dunning logic.

PayTo is the NPP’s digital mandate. The creditor creates a payment agreement, the payer’s bank presents it, and the payer authorizes it in their banking app. The consent is held and displayed by the bank, not by the merchant. The reversal looks cosmetic, but it hands control of the billing cycle to the payer and removes the delays that direct debit logic quietly relied on.

Mandate statuses are the most underestimated part of the integration. A PayTo agreement has a life of its own, independent of your invoices: the payer can suspend it on a Tuesday and reactivate it on Thursday. Your billing system must read these events, not infer them from a failed collection. A creditor that collects on a revoked mandate does two kinds of damage at once: a customer complaint and an accounting entry that has to be reversed.

type MandateStatus =
  | "pending_authorisation" // created, waiting for the payer in their banking app
  | "active"                // authorized: collection is allowed
  | "suspended"             // suspended by the payer or their bank
  | "cancelled"             // revoked: no further collection is legitimate
  | "expired"               // reached its end date under the agreement's attributes
  | "error";                // bank-side error: neither active nor closed

// An agreement is NOT an invoice. It governs the right to collect, nothing else.
function onMandateEvent(sub: Subscription, status: MandateStatus): void {
  switch (status) {
    case "active":
      sub.collectable = true;
      scheduleNextCollection(sub); // can resume after a suspension
      break;
    case "pending_authorisation":
      sub.collectable = false;
      remindCustomerToAuthoriseInBankingApp(sub); // otherwise the flow dies silently
      break;
    case "suspended":
      sub.collectable = false;
      pauseDunning(sub); // never retry the payment: the right is suspended
      break;
    case "cancelled":
    case "expired":
      sub.collectable = false;
      stopDunning(sub);
      openWinBackFlow(sub); // this is where churn shows up, in real time
      break;
  }
}

• One agreement, one subscriber, one source of truth: store the agreement reference next to the subscription, with its authorization date and attributes
• A readable description in the agreement: it is what the payer will see at their bank, and it heads off “I don’t recognize this payment” disputes
• Attributes broad enough to absorb a price increase, but not so broad that they worry the payer at authorization
• An “awaiting authorization” status handled like an abandoned cart, with a reminder: an agreement that is never authorized throws no error, just silence
• An end-to-end revocation test, triggered from the banking app, all the way to your dunning actually stopping

Chapter 4. BECS: producing a batch that goes through.

BECS (Bulk Electronic Clearing System), also called Direct Entry, still carries most Australian recurring payments: wages, benefits, and direct debits. It dates from 1994 and runs on daily batches. Its retirement had been announced for June 2030, but AusPayNet withdrew that target date in December 2025 because the account-to-account roadmap was not mature enough. So don’t build your product plan around its demise. The rail is here to stay, and integrating it remains a must for any Australian biller.

• Get a Direct Debit Request signed, and give the customer a non-editable copy of the DDR and its Service Agreement
• Confirm in writing within 7 days any request taken over the phone, with the DDR and the Service Agreement (Stripe, BECS Direct Debit Request Service Agreement, 2026)
• Pre-notify every debit: debit date, last 4 digits of the account, amount, mandate ID, and creditor ID
• Follow AusPayNet’s BECS Procedures, which are published and binding, and which your PSP passes through in its own terms
• Accept the financial liability: a debit that is disputed, reversed, or failed is on you, even when the account details were wrong

// 1. The BSB (Bank-State-Branch) is SIX digits, often written XXX-XXX.
//    The hyphens come from user input, never from the file.
function normalizeBsb(input) {
  const digits = String(input).replace(/\D/g, "");
  if (digits.length !== 6) throw new Error("Invalid BSB: " + input);
  return digits;
}

// 2. A BECS reference holds EIGHTEEN characters.
//    The NPP accepts several thousand: a reference built for
//    Osko is silently truncated if you feed it into a BECS batch.
const BECS_REFERENCE_MAX = 18;

function becsReference(orderId) {
  const ref = "CMD" + orderId;
  if (ref.length > BECS_REFERENCE_MAX) {
    // Truncating here means losing reconciliation. Reject instead.
    throw new Error("Reference too long for BECS: " + ref);
  }
  return ref;
}

Disputes are the second thing to wire up. An account holder can file a claim with their bank, which forwards it to the creditor’s bank. The creditor must then produce proof of authorization, and response times depend on how old the transaction is. For a claim covering the last 12 months, the creditor’s bank must respond within five business days; beyond 12 months, the deadline becomes one month. A case still unresolved after 30 days can be escalated to the BECS management committee (GoCardless, Australian BECS documentation, 2026).

Chapter 5. Cards: least-cost routing, caps, and the end of surcharging.

Nearly every Australian debit card carries two networks: the domestic eftpos scheme and an international network, Visa Debit or Debit Mastercard. They are two separate applications on the chip, with two separate rate schedules. Least-cost routing (LCR), also called merchant choice routing, gives the choice to the acquirer, on the merchant’s instructions, not to the cardholder. That is the reverse of European co-badging, where the cardholder decides. For an Australian merchant, turning on LCR and verifying it comes before any fee renegotiation.

// Published order of magnitude: the cost of accepting debit is about
// 20% lower with least-cost routing turned on
// (Australian Payments Plus, 2025). The actual gain depends on YOUR mix.

const annualDebitVolumeAud = 12_000_000;  // domestic debit volume
const routingEligibleShare = 0.70;        // co-badged cards AND configured terminals
const currentDebitCost = 0.0090;          // 0.90% observed on your acquirer statements
const routingDiscount = 0.20;             // ~20% less on the routed share

const routedVolume = annualDebitVolumeAud * routingEligibleShare;
const savings = routedVolume * currentDebitCost * routingDiscount;

console.log(Math.round(savings)); // 15120 AUD per year

// How to read it: if your statements don't separate eftpos from Visa/Mastercard,
// you CANNOT calculate this line. That is the symptom of blended pricing.

Australia’s surcharging ban calls for a repricing project, not just a POS update. For 20 years, merchants could pass on their cost of acceptance, up to the actual cost. That right disappears on October 1, 2026, on designated networks. You need to rebuild your margin net of fees channel by channel, strip service fee lines from terminals and payment pages, and reprice products whose margin depended on surcharging. The 6 cents and 0.12% figures from the July 2025 consultation were not adopted. Configure from the March 2026 text.

Chapter 6. New Zealand: promising the right timeline.

New Zealand made card payments universal at the point of sale as early as the 1980s, with EFTPOS debiting the account directly and no merchant fee. That founding choice produced a very low cost of acceptance and no need for a faster rail. So the country never built a retail interbank instant payment system. It runs on several exchanges a day with prior settlement, under the SBI (Settlement Before Interchange) mechanism, in place since 2012. This architecture eliminates counterparty risk between participants, but it rules out any promise of immediate credit.

With no instant rail, API payment initiation serves as the stand-in for immediate payment, and that shapes how you should read the New Zealand market. The API Centre, set up within Payments NZ in 2019, publishes the API standards for payment initiation, account information, and event notification, along with operating rules and third-party accreditation. Six API providers are registered (ANZ, ASB, BNZ, Heartland, Kiwibank, Westpac), along with more than 20 accredited third parties (Payments NZ, API Centre, 2026). In 2025 the country moved from an industry-led model to a statutory regime under the Customer and Product Data Act 2025, with banking as the first designated sector and MBIE, the Ministry of Business, Innovation and Employment, in charge.

• Contract in NZD, and check where the conversion happens if your acquirer settles in AUD
• Ask for an eftpos vs. international scheme breakdown on your statements: you can’t see New Zealand’s caps in a single blended rate
• Don’t configure an end to surcharging on an assumed date: the bill announced for 2026 hasn’t passed, and online payments would stay out of scope
• Treat inbound tourism as a separate cost line: cards issued abroad have been capped since May 1, 2026, and your statements must show it
• Confirm your initiation provider’s accreditation with the API Centre before you build a flow on it