PayID

PayID is not a payment product but an addressing layer: an identifier — mobile number, email, ABN or Organisation Identifier — registered against an Australian bank account so a payer needs no BSB and account number, and sees the registered name before sending. It is a brand of Australian Payments Plus (payid.com.au redirects to the AP+ brand page), which sits alongside NPP, Osko and PayTo and says PayID is offered by over 100 financial institutions. Integrators should separate two things called "PayID". (1) Inbound collection: an AU platform gets PayIDs from an NPP-connected provider and issues one per customer or invoice so real-time credits reconcile automatically. Zai documents this as POST /virtual_accounts/{id}/pay_ids, with EMAIL the only accepted type and statuses pending_activation/active/activation_failed/deregistered; Monoova sells the same pattern, priced per PayID created plus per transaction, for invoices, checkout and account funding. In this mode there is no authorisation, capture or chargeback — the customer pushes a credit from their banking app, so a missing payment is an ops problem, not a decline. (2) PayID as an identifier inside PayTo: Stripe and Adyen both accept "PayID or BSB + account number" to authorise a PayTo mandate, and the published AU / AUD / recurring / refunds / partial-refunds data is PayTo's, not PayID's. Adyen's own feature table and Disputes section contradict each other on chargebacks, so that is left unrecorded. No cross-border gateway catalogue checked (Adyen, Airwallex, Antom, Stripe, Checkout.com, Rapyd) lists PayID as a selectable checkout method. Nobody publishes PayID limits — those sit with each bank — and Stripe warns a refund to a PayID fails on a payer-name mismatch. Note also the unrelated Ripple-backed PayID identifier standard; payid.org refused connection on 2026-10-20.

Checked against PayID’s own documentation on 21 October 2026. Coverage changes; confirm anything you are about to build on.