NPP: Australia instant payments and PayID

The New Payments Platform, NPP, is Australia instant payment system, launched in February 2018 and operated by NPP Australia Limited, and it lets a payment move between accounts at different banks in seconds, 24 hours a day, 7 days a week, including weekends and public holidays. It settles in central bank money through the Reserve Bank of Australia Fast Settlement Service, and it carries ISO 20022 messages, so a payment can include rich remittance data, up to 280 characters, which lets a business reconcile automatically. The best known service on NPP is Osko, which most Australians use when they pay someone instantly from their banking app. Source: Reserve Bank of Australia, New Payments Platform; NPP Australia Limited. Why NPP exists is that Australia payments were batch-based, and a payment sent on Friday arrived on Monday, which was unacceptable once customers could order goods and pay for services instantly. Businesses needed to pay suppliers on the day the invoice was due, individuals needed to split a bill at dinner and have the money arrive before they left the table, and the old batch system could not do either. NPP answers by settling each payment individually, in real time, with immediate confirmation to the sender and the receiver, so the payment is final within seconds and both parties know it. The design choice was to build a new platform rather than speed up the old batch system, because real-time settlement needs a different architecture. The parties are the payer and the payee, their banks, which must both be NPP participants, NPP Australia Limited, which operates the platform, and the Reserve Bank of Australia, which settles the payments. A distinctive party is the PayID, which is an addressing service that lets a payer send money to a mobile number, an email address or an Australian Business Number instead of a BSB and account number. The payer bank looks up the PayID, finds the account it points to, and shows the payee name to the payer before the payment is sent, so the payer can confirm they are paying the right person, which is a control that batch payments never had. How it works is shown by a worked example. A café owner in Melbourne owes a supplier in Sydney AUD 12,400 for coffee beans, and pays on a Sunday at 09:00 using the supplier PayID, which is the supplier mobile number. The Melbourne bank looks up the PayID, shows the supplier business name, and the owner confirms. The payment travels as an ISO 20022 message through NPP, the Reserve Bank Fast Settlement Service moves AUD 12,400 between the two banks settlement accounts, and the supplier account is credited at 09:00:05, five seconds later, with remittance data naming the invoice INV-8841. The supplier sees the payment on Sunday, not Monday, and can dispatch the beans on Monday morning, a full day earlier than the old batch system allowed. On success the payment is final in seconds, the receiver can use the money immediately, and the sender has confirmation, so there is no uncertainty to manage. On failure the payment can be rejected, for example because the PayID is not registered, the account is closed, or the amount exceeds the sending bank limit, and the rejection is immediate, so the sender knows at once and can correct the details. The failure mode that matters most is a payment sent to the wrong PayID, because the payment is final and cannot be recalled by the sender alone, so the recovery is a request to the receiver to return the money, and if the receiver refuses, the bank must follow its mistaken payment process, which can take days and may not succeed. The data in an NPP payment is the payer and payee identification, the PayID or the BSB and account number, the amount in Australian dollars, the remittance information of up to 280 characters, and the ISO 20022 message that carries it. The remittance data is the feature that matters for business payments, because 280 characters is enough to list several invoice numbers, while the old batch system carried far less, and a business that receives an NPP payment can reconcile it automatically. A BA must specify the PayID lookup, the name confirmation step, the remittance field, the limits, and the mistaken payment handling, because each of those is a customer promise. Edge cases show the limits. NPP has no scheme-wide transaction limit, but each bank sets its own per-customer limits, so a AUD 250,000 payment that one bank allows may be blocked by another, and the customer must be told the limit before they try. A payment sent on a public holiday settles instantly, because NPP never closes, but the receiving bank back-office processes, such as reconciliation, may still run on business days, so the money is in the account but the ledger may not show it until the next business day. A PayID that is registered to an old account after a customer changes banks must be transferred, or payments will go to the wrong account, and the transfer process must be part of the requirement. The effect on the bank is a service that customers expect, and a reduction in the batch payment volume that used to clog the end of day. The effect on the customer is money that moves when the customer wants it to move, including weekends, and a name check that prevents most mistaken payments. The effect on operations is a 24/7 service that must be monitored 24/7, with fraud screening that runs in milliseconds, because an instant payment cannot wait for a morning fraud review, and a fraud that is detected after the payment has settled is a loss, not an exception. What a BA, PO or SME must understand is that NPP is a platform with services on top, and PayID, Osko and the ISO 20022 data are the services, not the platform itself. The requirement must name the addressing method, the confirmation step, the remittance data, the limits, the fraud screening and the mistaken payment process. The test is to send one payment by PayID on a Sunday, check that the name was shown before confirmation, that the credit arrived in seconds, and that the remittance data matched the invoice, because if any of those fails, the service is not delivering what it promises. Further reading: Reserve Bank of Australia, New Payments Platform; NPP Australia, PayID and Osko. Last reviewed 7 November 2026.