{ "corpus": "orca-product", "format_version": "1", "built": "2026-09-26", "snapshot": "2026-09-20", "commit": "019924ac64ee0aa0742b8f02a04488a83633385d", "license": { "name": "Creative Commons Attribution 4.0 International (CC BY 4.0)", "spdx": "CC-BY-4.0", "url": "https://creativecommons.org/licenses/by/4.0/", "attribution": "Data from Orca (https://qstve.com/orca/), CC BY 4.0. Snapshot 2026-09-20.", "notice": "Reference material about published payment rules. Not legal, compliance or financial advice. Orca cites rulebooks by section and edition and does not reproduce them; rights in the cited documents stay with their authors." }, "uid": "au-npp:txn.mandate-payment", "rail": "au-npp", "page": "../../../au-npp/mandate-payment.html", "product": { "uid": "au-npp:txn.mandate-payment", "id": "txn.mandate-payment", "slug": "mandate-payment", "rail": "au-npp", "rail_name": "New Payments Platform (Australia)", "governing_authority": "NPP Australia Limited", "snapshot": "2026-09-20", "page": "au-npp/mandate-payment.html", "file": "data/products/au-npp/mandate-payment.json", "name": "Mandate Payment (PayTo)", "anchor": "3 authorisations of its own, a lifecycle of its own (5 states)", "transaction_type": { "uid": "au-npp:txn.mandate-payment", "name": "Mandate Payment (PayTo)", "status": "corroborated", "stored_status": "corroborated", "source_class": "authoritative_primary", "confidence": "medium", "tier": { "k": "cor", "label": "Corroborated (authoritative primary)", "say": "A validator compared this with 1 named source, the strongest being a publication of NPP Australia Limited itself. It is not verified: no person has checked it against the current rulebook edition." }, "summary": "A payment the payer's own institution makes on the strength of an active mandate held in the Mandate Management Service, after an initiating participant sends it a mandate payment initiation request. Nothing is pulled: this is an ordinary credit push that a stored authorisation set going, which is why the rulebook calls it a persistently authorised debit-like credit transfer.", "effective_since": "Unknown: the Regulations date individual amendments, not the provision as a whole", "effective_note": "Drafted 2026-09-21 from the NPP Regulations v21.0 of 24 September 2024, the newest edition of the governing rulebook an agent can read. NPPA publishes the current edition, NPP Product Rules v.31 of September 2026, as 102 scanned page images carrying no text layer, so what moved between the two editions is not held [Unverified].", "source_edition": "NPP Regulations v21.0, 24 September 2024, public redacted version, read 2026-09-21. The current edition, NPP Product Rules v.31 of September 2026, was downloaded on 2026-09-21 and could not be read: 102 pages, no font resource on any page, and no character extractable. Regulation 6.9 and Annexure C are redacted in the edition that was read.", "directions": [ "credit" ], "account_types": [ "any" ], "sources": [ { "uid": "au-npp:src.npp-regulations-v21", "name": "Regulations for the New Payments Platform, v21.0, public version", "url": "https://www.auspayplus.com.au/wp-content/uploads/2024/10/NPP-Regulations-v21.0_Public_version.pdf", "source_class": "authoritative_primary", "edition": "v21.0, 24 September 2024; the Regulations commenced 1 July 2017", "section": "the Part 17 preamble and Regulations 17.1(b) and (c), and 17.8(b)" } ] }, "counts": { "rules": 18, "mandates": 3, "states": 5, "code_sets": 0, "reason_codes": 6, "roles": 9, "members": 33 }, "trust": { "members": 33, "by_status": { "draft": 1, "corroborated": 32, "verified": 0, "superseded": 0 }, "strongest_source_class": "authoritative_primary" }, "roles": [ { "uid": "au-npp:role.connected-institution", "name": "Connected Institution", "kind": "institution", "via": [ "binds" ] }, { "uid": "au-npp:role.initiating-participant", "name": "Initiating Participant", "kind": "institution", "via": [ "binds" ] }, { "uid": "au-npp:role.mps-user", "name": "MPS User", "kind": "party", "via": [ "given_to", "binds" ] }, { "uid": "au-npp:role.nppa", "name": "NPP Australia Limited (NPPA)", "kind": "operator", "via": [ "binds" ] }, { "uid": "au-npp:role.overlay-service-provider", "name": "Overlay Service Provider", "kind": "service_provider", "via": [ "binds" ] }, { "uid": "au-npp:role.payer-customer", "name": "Payer Customer", "kind": "party", "via": [ "given_by", "binds" ] }, { "uid": "au-npp:role.payer-participant", "name": "Payer Participant", "kind": "institution", "via": [ "given_to", "binds" ] }, { "uid": "au-npp:role.payment-initiator", "name": "Payment Initiator", "kind": "service_provider", "via": [ "binds" ] }, { "uid": "au-npp:role.sponsor", "name": "Sponsor", "kind": "institution", "via": [ "binds" ] } ], "mandates": [ { "uid": "au-npp:mandate.authorised-payment-mandate", "name": "Authorised Payment Mandate (a PayTo agreement)", "status": "corroborated", "stored_status": "corroborated", "source_class": "authoritative_primary", "confidence": "medium", "tier": { "k": "cor", "label": "Corroborated (authoritative primary)", "say": "A validator compared this with 2 named sources, the strongest being a publication of NPP Australia Limited itself. It is not verified: no person has checked it against the current rulebook edition." }, "summary": "The ordinary PayTo mandate. It is a record of a payment authorisation the payer gives in favour of a business or a payment initiator, and the record does not live with either of them: it lives in the Mandate Management Service, a central access controlled database the scheme operator runs, under a unique identifier the database itself generates. It gives the holder the right to send requests instructing the payer's own institution to make payments inside the mandate's terms, and it is only active once the payer's institution has recorded in the database that the payer authorised it. Three parties act and an operator holds the record, which is the thing that makes it unlike every other mandate in the corpus.", "form": "A record in the Mandate Management Service, the scheme operator's own central database, identified by a mandate identifier the database generates. It is not a document either party keeps. The payer authorises it in their own institution's channel after that institution delivers the authorisation request to them in near real time, and the institution then records the confirmation in the database. Lookup rights belong to the parties to the mandate and the information in the record is confidential to them.", "scope": [ "a stated amount, purpose and frequency the payer authorised, which the record itself is the evidence of. No amount is typed as a constraint because no source gives a figure: what the sources give is the shape of the range, and three of the reason codes the authority publishes sit at its edges, one for an amount below the minimum the agreement allows, one for an amount that is not the amount agreed or expected, and one for an amount above a limit the payer and their own bank agreed", "one off, ad hoc or recurring payments to the business or provider named in it", "payments the payer's own institution makes as ordinary credit pushes; nothing is pulled", "active only while the payer's institution has recorded the payer's authorisation in the operator's database" ], "constraints": { "recurrence": { "max_occurrences": null, "text": "The mandate states the frequency the payer authorised, and the record in the operator's database is the evidence of it. The rulebook sets no ceiling of its own on the number of payments and no public document gives one." }, "counterparties": { "text": "The mandate names the business or payment initiator it is given to, and where a beneficiary is recorded the record is the evidence of that too. A payment initiator's mandate may be moved to a different participant or connected institution on the initiator's instruction without the authorisation changing." } }, "governed_by": [ { "uid": "au-npp:rule.mandate-a-mandate-is-a-record-in-the-scheme-operators-database", "name": "A PayTo mandate is a record in a database the scheme operator runs, not a document a party keeps" }, { "uid": "au-npp:rule.mandate-participation-is-mandatory-for-a-payer-participant", "name": "Offering PayTo is optional for a creditor's bank and compulsory for the payer's bank" }, { "uid": "au-npp:rule.mandate-authorisation-is-delivered-in-near-real-time", "name": "The payer's institution must deliver the authorisation request to the payer in near real time" }, { "uid": "au-npp:rule.mandate-a-request-may-not-be-sent-unless-the-mandate-is-active", "name": "No payment request may be sent unless the mandate is active" }, { "uid": "au-npp:rule.mandate-an-amount-or-frequency-change-comes-from-the-business", "name": "A change to the amount or the frequency has to come from the business as a fresh agreement" }, { "uid": "au-npp:rule.mandate-a-mandate-may-be-ported-to-another-participant", "name": "A mandate may be moved to another institution without the authorisation changing" }, { "uid": "au-npp:rule.mandate-data-is-confidential-to-the-parties", "name": "A mandate record is confidential to its parties and may be looked up only by them" }, { "uid": "au-npp:rule.mandate-an-authorised-mandate-claim-is-deemed-substantiated-by-the-record", "name": "A claim about an ordinary mandate is tested against the record, or against evidence the initiator must produce" } ], "revoked_via": [ { "uid": "au-npp:rule.mandate-the-payer-customer-can-view-suspend-cancel-and-amend", "name": "The payer's institution must give the payer a way to view, suspend, cancel and amend their mandates" } ], "evidenced_by": [ { "uid": "au-npp:rule.mandate-the-record-is-evidence-of-quantum-frequency-and-beneficiary", "name": "The mandate record is the evidence of the amount, the frequency and the beneficiary" } ], "disputed_via": [ { "uid": "au-npp:exc.mandate-claim", "name": "Mandate claim", "shared": true } ], "given_by": [ { "uid": "au-npp:role.payer-customer", "name": "Payer Customer", "note": null } ], "given_to": [ { "uid": "au-npp:role.mps-user", "name": "MPS User", "note": "The authorisation runs to the business or payment initiator, but the record is held by the scheme operator and the authorisation is validated and recorded by the payer's own institution. One target uid cannot carry all three positions; the operator's custody is in form and in the rules this mandate is governed by." } ], "sources": [ { "uid": "au-npp:src.npp-regulations-v21", "name": "Regulations for the New Payments Platform, v21.0, public version", "url": "https://www.auspayplus.com.au/wp-content/uploads/2024/10/NPP-Regulations-v21.0_Public_version.pdf", "source_class": "authoritative_primary", "edition": "v21.0, 24 September 2024; the Regulations commenced 1 July 2017", "section": "Regulations 17.1(b) and (c), 17.2(e), 17.6(c), 17.7(a), 17.8(b), 17.10(d) and (f), and the definition of Active" }, { "uid": "au-npp:src.auspayplus-payto-faqs", "name": "Australian Payments Plus, PayTo FAQs", "url": "https://www.auspayplus.com.au/solutions/payto-faqs", "source_class": "public_primary", "edition": "live page, read 2026-09-21", "section": "what a PayTo agreement is, how PayTo works, and managing agreements" } ] }, { "uid": "au-npp:mandate.debtor-payment-arrangement", "name": "Debtor Payment Arrangement", "status": "draft", "stored_status": "draft", "source_class": null, "confidence": "low", "tier": { "k": "draft", "label": "Draft, unchecked", "say": "An agent wrote this from published material and nobody has checked it. NPP Australia Limited's own text was not the source for this record. Treat it as a lead to confirm, not an answer, before acting on any retry, deadline or rate." }, "summary": "The third thing the Mandate Management Service can hold, and the thinnest. A payer's own institution may choose to store records of these arrangements in the database, and it is answerable for payments made in connection with them. What one is, who gives it and to whom, and how it is authorised, amended or ended are all defined in the procedures rather than in the published rulebook, so Orca can say that the record type exists and almost nothing else.", "form": "Not held. The published rulebook defines this term only by pointing at the NPP Procedures Volume 6, which is available to members and direct affiliates only and was not consulted. What is known is that storing these in the operator's database is optional for the payer's institution and that the institution is responsible for payments made in connection with them.", "scope": [ "not held: the arrangement's scope is defined in a document Orca cannot read" ], "constraints": null, "governed_by": [ { "uid": "au-npp:rule.mandate-a-mandate-is-a-record-in-the-scheme-operators-database", "name": "A PayTo mandate is a record in a database the scheme operator runs, not a document a party keeps" } ], "revoked_via": [], "evidenced_by": [], "disputed_via": [], "given_by": [ { "uid": "au-npp:role.payer-customer", "name": "Payer Customer", "note": "[Inference] from the term itself and from the payer participant being the party that stores the record. No read source says who gives one." } ], "given_to": [ { "uid": "au-npp:role.payer-participant", "name": "Payer Participant", "note": "[Inference] the payer's own institution is the party that opts to store the record and is responsible for the payments. No read source names a holder." } ], "sources": [ { "uid": "au-npp:src.npp-regulations-v21", "name": "Regulations for the New Payments Platform, v21.0, public version", "url": "https://www.auspayplus.com.au/wp-content/uploads/2024/10/NPP-Regulations-v21.0_Public_version.pdf", "source_class": "authoritative_primary", "edition": "v21.0, 24 September 2024; the Regulations commenced 1 July 2017", "section": "Regulation 17.1(b) final paragraph, Regulation 17.8(f), and the definition of Debtor Payment Arrangement, which points at the NPP Procedures" } ] }, { "uid": "au-npp:mandate.migrated-ddr-mandate", "name": "Migrated DDR Mandate", "status": "corroborated", "stored_status": "corroborated", "source_class": "authoritative_primary", "confidence": "medium", "tier": { "k": "cor", "label": "Corroborated (authoritative primary)", "say": "A validator compared this with 2 named sources, the strongest being a publication of NPP Australia Limited itself. It is not verified: no person has checked it against the current rulebook edition." }, "summary": "A PayTo mandate created out of an existing direct debit arrangement, and the one mandate in the corpus that nobody consented to. The business and its sponsoring participant create it in the operator's database unilaterally, and it is deemed active the moment it is created, with no authorisation step and no message to the payer's institution asking for one. Its safeguards are notice and delay rather than consent, and its risk shows up in the claim rules, where the burden of proof falls on the sponsor rather than on the payer.", "form": "A record the business's sponsoring participant creates in the Mandate Management Service from an existing direct debit request, mapped across as the procedures prescribe, and deemed active on creation. The payer never authorises it. The payer's own institution may choose to satisfy itself that the record matches its customer's existing direct debit and may ask the customer to confirm, but it is not obliged to, and pending any word from the customer it must keep processing requests against the record.", "scope": [ "an existing direct debit arrangement and nothing else; one of these cannot be created from scratch", "deemed active on creation, with no payer authorisation step", "unusable for a payment initiation request until 5 days after it was created", "conditional on the business having given the payer written notice, as its direct debit service agreement requires or at least 14 days beforehand", "conditional on direct debit processing of the same arrangement stopping from the migration date, except in a genuine outage" ], "constraints": { "execution_window": { "from": "2023-05-05", "to": null, "text": "No public document gives a date on which this kind of mandate stops being creatable. The date recorded here is not an execution window of the mandate but the earliest date the whole of the part that governs it was in force; the industry target for retiring the direct debit system these mandates come from is 2030, which would end them, and that target rests on a source not read here [Unverified]." }, "recurrence": { "max_occurrences": null, "text": "The terms are the terms of the direct debit arrangement the record was mapped from, not terms the payer gave the operator's database. That is why a claim about one is tested against the original direct debit authorisation." }, "counterparties": { "text": "The business is the direct debit user the participant already sponsored, deemed approved as a user of the service by the act of creating the record, and its BECS user identifier must be carried in the record so the payer's institution can check the arrangement against its own customer's history." } }, "governed_by": [ { "uid": "au-npp:rule.mandate-a-migrated-mandate-is-created-without-a-consent-step", "name": "A migrated direct debit mandate is created unilaterally and is active the moment it exists" }, { "uid": "au-npp:rule.mandate-fourteen-days-notice-before-a-migrated-mandate-is-created", "name": "A migrated mandate needs written notice to the payer first, at least 14 days ahead" }, { "uid": "au-npp:rule.mandate-five-days-before-a-migrated-mandate-may-be-used", "name": "A migrated mandate may not be used for a payment request until 5 days after it was created" }, { "uid": "au-npp:rule.mandate-the-payer-participant-keeps-processing-pending-word", "name": "Until the payer says something, their institution must keep processing a migrated mandate" }, { "uid": "au-npp:rule.mandate-a-migrated-mandate-claim-is-deemed-substantiated", "name": "A claim about a migrated mandate is deemed substantiated unless the sponsor produces the evidence" }, { "uid": "au-npp:rule.mandate-a-request-may-not-be-sent-unless-the-mandate-is-active", "name": "No payment request may be sent unless the mandate is active" }, { "uid": "au-npp:rule.mandate-data-is-confidential-to-the-parties", "name": "A mandate record is confidential to its parties and may be looked up only by them" } ], "revoked_via": [ { "uid": "au-npp:rule.mandate-the-payer-customer-can-view-suspend-cancel-and-amend", "name": "The payer's institution must give the payer a way to view, suspend, cancel and amend their mandates" } ], "evidenced_by": [ { "uid": "au-npp:rule.mandate-the-record-is-evidence-of-quantum-frequency-and-beneficiary", "name": "The mandate record is the evidence of the amount, the frequency and the beneficiary" } ], "disputed_via": [ { "uid": "au-npp:exc.mandate-claim", "name": "Mandate claim", "shared": true } ], "given_by": [ { "uid": "au-npp:role.payer-customer", "name": "Payer Customer", "note": "Only in the sense that the payer once authorised the direct debit this record was mapped from. No authorisation was given for this record, and the rulebook does not pretend otherwise." } ], "given_to": [ { "uid": "au-npp:role.mps-user", "name": "MPS User", "note": null } ], "sources": [ { "uid": "au-npp:src.npp-regulations-v21", "name": "Regulations for the New Payments Platform, v21.0, public version", "url": "https://www.auspayplus.com.au/wp-content/uploads/2024/10/NPP-Regulations-v21.0_Public_version.pdf", "source_class": "authoritative_primary", "edition": "v21.0, 24 September 2024; the Regulations commenced 1 July 2017", "section": "Regulations 17.4(a) to (f), 17.6(c)(viii) and 17.10(c)(ii) and (e)" }, { "uid": "au-npp:src.auspayplus-payto-faqs", "name": "Australian Payments Plus, PayTo FAQs", "url": "https://www.auspayplus.com.au/solutions/payto-faqs", "source_class": "public_primary", "edition": "live page, read 2026-09-21", "section": "moving direct debits to PayTo agreements" } ] } ], "states": [ { "uid": "au-npp:state.mandate-awaiting-authorisation", "name": "PayTo agreement: created, awaiting the payer's authorisation", "status": "corroborated", "stored_status": "corroborated", "source_class": "authoritative_primary", "confidence": "medium", "tier": { "k": "cor", "label": "Corroborated (authoritative primary)", "say": "A validator compared this with 2 named sources, the strongest being a publication of NPP Australia Limited itself. It is not verified: no person has checked it against the current rulebook edition." }, "summary": "The business's sponsor has created the agreement record in the Mandate Management Service, and the payer has not yet said yes or no. The operator's database has sent an authorisation request to the payer's institution, which must match it to the payer by account number and put it in front of them in near real time; no payment may be requested under it yet. A migrated direct debit mandate never passes through this state, because it is active from the moment it is created.", "terminal": false, "money_moved": "no", "visible_as": null, "precedes": [ { "uid": "au-npp:state.mandate-active", "name": "PayTo agreement: active" }, { "uid": "au-npp:state.mandate-declined", "name": "PayTo agreement: declined by the payer" } ], "sources": [ { "uid": "au-npp:src.npp-regulations-v21", "name": "Regulations for the New Payments Platform, v21.0, public version", "url": "https://www.auspayplus.com.au/wp-content/uploads/2024/10/NPP-Regulations-v21.0_Public_version.pdf", "source_class": "authoritative_primary", "edition": "v21.0, 24 September 2024; the Regulations commenced 1 July 2017", "section": "Regulations 17.6(c)(i) to (v), 17.6(c)(viii) and 17.8(b), and the definition of Active in 1.1" }, { "uid": "au-npp:src.npp-payto-service-overview-v2", "name": "NPP Australia, PayTo Service Overview v2.0, November 2021", "url": "https://www.auspayplus.com.au/wp-content/uploads/2025/07/PayTo-Service-Overview-Nov-2021-2.0.pdf", "source_class": "public_primary", "edition": "v2.0, November 2021 (PDF created 2021-11-23), re-uploaded July 2025", "section": "page 7 and the worked examples on pages 18 to 21" } ] }, { "uid": "au-npp:state.mandate-declined", "name": "PayTo agreement: declined by the payer", "status": "corroborated", "stored_status": "corroborated", "source_class": "authoritative_primary", "confidence": "low", "tier": { "k": "cor", "label": "Corroborated (authoritative primary)", "say": "A validator compared this with 2 named sources, the strongest being a publication of NPP Australia Limited itself. It is not verified: no person has checked it against the current rulebook edition." }, "summary": "The payer was shown the agreement and refused it, and their institution recorded the refusal in the Mandate Management Service. The agreement never became active and no payment may be requested under it. If the terms were wrong, the business has to create a fresh agreement for the payer to authorise.", "terminal": true, "money_moved": "no", "visible_as": null, "precedes": [], "sources": [ { "uid": "au-npp:src.npp-regulations-v21", "name": "Regulations for the New Payments Platform, v21.0, public version", "url": "https://www.auspayplus.com.au/wp-content/uploads/2024/10/NPP-Regulations-v21.0_Public_version.pdf", "source_class": "authoritative_primary", "edition": "v21.0, 24 September 2024; the Regulations commenced 1 July 2017", "section": "Regulations 17.6(c)(v) and 17.8(b)" }, { "uid": "au-npp:src.auspayplus-payto-faqs", "name": "Australian Payments Plus, PayTo FAQs", "url": "https://www.auspayplus.com.au/solutions/payto-faqs", "source_class": "public_primary", "edition": "live page, read 2026-09-21", "section": "what if the details of the PayTo agreement are wrong" } ] }, { "uid": "au-npp:state.mandate-active", "name": "PayTo agreement: active", "status": "corroborated", "stored_status": "corroborated", "source_class": "authoritative_primary", "confidence": "medium", "tier": { "k": "cor", "label": "Corroborated (authoritative primary)", "say": "A validator compared this with 2 named sources, the strongest being a publication of NPP Australia Limited itself. It is not verified: no person has checked it against the current rulebook edition." }, "summary": "The payer's institution has recorded in the Mandate Management Service that the payer authorised the agreement, or the agreement is a migrated direct debit mandate, which the rulebook treats as active from creation. Only now may the business's side send payment initiation requests, and each must fit the agreement's terms. A change of amount or frequency comes from the business as an updated agreement for the payer to authorise again; the payer may pause or cancel it from their online banking.", "terminal": false, "money_moved": "no", "visible_as": "MMS mandate status Active, the name the NPP Regulations give it", "precedes": [ { "uid": "au-npp:state.mandate-suspended", "name": "PayTo agreement: suspended (paused)" }, { "uid": "au-npp:state.mandate-cancelled", "name": "PayTo agreement: cancelled" } ], "sources": [ { "uid": "au-npp:src.npp-regulations-v21", "name": "Regulations for the New Payments Platform, v21.0, public version", "url": "https://www.auspayplus.com.au/wp-content/uploads/2024/10/NPP-Regulations-v21.0_Public_version.pdf", "source_class": "authoritative_primary", "edition": "v21.0, 24 September 2024; the Regulations commenced 1 July 2017", "section": "definition of Active in 1.1; Regulations 17.4(b), 17.6(c)(v) and (vii), and 17.8(b)" }, { "uid": "au-npp:src.npp-payto-service-overview-v2", "name": "NPP Australia, PayTo Service Overview v2.0, November 2021", "url": "https://www.auspayplus.com.au/wp-content/uploads/2025/07/PayTo-Service-Overview-Nov-2021-2.0.pdf", "source_class": "public_primary", "edition": "v2.0, November 2021 (PDF created 2021-11-23), re-uploaded July 2025", "section": "pages 7 and 8" }, { "uid": "au-npp:src.auspayplus-payto-faqs", "name": "Australian Payments Plus, PayTo FAQs", "url": "https://www.auspayplus.com.au/solutions/payto-faqs", "source_class": "public_primary", "edition": "live page, read 2026-09-21", "section": "can I change, pause, resume or cancel my PayTo agreement" } ] }, { "uid": "au-npp:state.mandate-suspended", "name": "PayTo agreement: suspended (paused)", "status": "corroborated", "stored_status": "corroborated", "source_class": "authoritative_primary", "confidence": "medium", "tier": { "k": "cor", "label": "Corroborated (authoritative primary)", "say": "A validator compared this with 2 named sources, the strongest being a publication of NPP Australia Limited itself. It is not verified: no person has checked it against the current rulebook edition." }, "summary": "The agreement has been put on hold, most often by the payer through their institution's online banking, where it is called pausing. While it is suspended no payment may be requested under it, and a payment procured anyway counts as unauthorised for a Mandate Claim. It can be made active again, and the operator's overview says only the party that paused it can do that. Pausing leaves the payer's contract with the business untouched.", "terminal": false, "money_moved": "no", "visible_as": "shown to the payer as paused in their online banking (AP+ FAQs and the PayTo Service Overview); the Regulations' word is Suspend", "precedes": [ { "uid": "au-npp:state.mandate-active", "name": "PayTo agreement: active" }, { "uid": "au-npp:state.mandate-cancelled", "name": "PayTo agreement: cancelled" } ], "sources": [ { "uid": "au-npp:src.npp-regulations-v21", "name": "Regulations for the New Payments Platform, v21.0, public version", "url": "https://www.auspayplus.com.au/wp-content/uploads/2024/10/NPP-Regulations-v21.0_Public_version.pdf", "source_class": "authoritative_primary", "edition": "v21.0, 24 September 2024; the Regulations commenced 1 July 2017", "section": "Regulations 17.4(d)(iii), 17.6(c)(vii) and (d), and 17.10(c)(i)(B)" }, { "uid": "au-npp:src.npp-payto-service-overview-v2", "name": "NPP Australia, PayTo Service Overview v2.0, November 2021", "url": "https://www.auspayplus.com.au/wp-content/uploads/2025/07/PayTo-Service-Overview-Nov-2021-2.0.pdf", "source_class": "public_primary", "edition": "v2.0, November 2021 (PDF created 2021-11-23), re-uploaded July 2025", "section": "pages 5, 8 and 10" }, { "uid": "au-npp:src.auspayplus-payto-faqs", "name": "Australian Payments Plus, PayTo FAQs", "url": "https://www.auspayplus.com.au/solutions/payto-faqs", "source_class": "public_primary", "edition": "live page, read 2026-09-21", "section": "can I change, pause, resume or cancel my PayTo agreement" } ] }, { "uid": "au-npp:state.mandate-cancelled", "name": "PayTo agreement: cancelled", "status": "corroborated", "stored_status": "corroborated", "source_class": "authoritative_primary", "confidence": "medium", "tier": { "k": "cor", "label": "Corroborated (authoritative primary)", "say": "A validator compared this with 2 named sources, the strongest being a publication of NPP Australia Limited itself. It is not verified: no person has checked it against the current rulebook edition." }, "summary": "The agreement has been ended, by the payer through their institution or by the side that is permitted to under its terms. It can never again carry a payment request, and a payment procured under it after cancellation counts as unauthorised for a Mandate Claim. The record stays in the operator's database for investigations. Cancelling ends the authorisation, not the payer's contract with the business.", "terminal": true, "money_moved": "no", "visible_as": null, "precedes": [], "sources": [ { "uid": "au-npp:src.npp-regulations-v21", "name": "Regulations for the New Payments Platform, v21.0, public version", "url": "https://www.auspayplus.com.au/wp-content/uploads/2024/10/NPP-Regulations-v21.0_Public_version.pdf", "source_class": "authoritative_primary", "edition": "v21.0, 24 September 2024; the Regulations commenced 1 July 2017", "section": "Regulations 17.6(c)(vii) and (d), 17.7(b)(iv) and 17.10(c)(i)(B)" }, { "uid": "au-npp:src.npp-payto-service-overview-v2", "name": "NPP Australia, PayTo Service Overview v2.0, November 2021", "url": "https://www.auspayplus.com.au/wp-content/uploads/2025/07/PayTo-Service-Overview-Nov-2021-2.0.pdf", "source_class": "public_primary", "edition": "v2.0, November 2021 (PDF created 2021-11-23), re-uploaded July 2025", "section": "page 8" }, { "uid": "au-npp:src.auspayplus-payto-faqs", "name": "Australian Payments Plus, PayTo FAQs", "url": "https://www.auspayplus.com.au/solutions/payto-faqs", "source_class": "public_primary", "edition": "live page, read 2026-09-21", "section": "can I change, pause, resume or cancel my PayTo agreement" } ] } ], "code_sets": [], "reason_codes": [ { "uid": "au-npp-reject:AG01", "name": "Transaction forbidden", "status": "corroborated", "stored_status": "corroborated", "source_class": "authoritative_primary", "confidence": "medium", "tier": { "k": "cor", "label": "Corroborated (authoritative primary)", "say": "A validator compared this with 1 named source, the strongest being a publication of NPP Australia Limited itself. It is not verified: no person has checked it against the current rulebook edition." }, "id": "AG01", "summary": "The debit or credit account is not enabled for PayTo. The authority gives this value a PayTo specific meaning that the ISO definition does not carry, which is one reason a value on this list must never be read across from another rail.", "sources": [] }, { "uid": "au-npp-reject:AM06", "name": "Too low amount", "status": "corroborated", "stored_status": "corroborated", "source_class": "authoritative_primary", "confidence": "medium", "tier": { "k": "cor", "label": "Corroborated (authoritative primary)", "say": "A validator compared this with 1 named source, the strongest being a publication of NPP Australia Limited itself. It is not verified: no person has checked it against the current rulebook edition." }, "id": "AM06", "summary": "The amount asked for is below the minimum the PayTo agreement allows. A PayTo specific meaning that the ISO definition does not carry.", "sources": [] }, { "uid": "au-npp-reject:AM09", "name": "Wrong amount", "status": "corroborated", "stored_status": "corroborated", "source_class": "authoritative_primary", "confidence": "medium", "tier": { "k": "cor", "label": "Corroborated (authoritative primary)", "say": "A validator compared this with 1 named source, the strongest being a publication of NPP Australia Limited itself. It is not verified: no person has checked it against the current rulebook edition." }, "id": "AM09", "summary": "The amount in a PayTo payment request is not the amount the agreement agreed or expected. Another PayTo specific meaning.", "sources": [] }, { "uid": "au-npp-reject:AM21", "name": "Limit exceeded", "status": "corroborated", "stored_status": "corroborated", "source_class": "authoritative_primary", "confidence": "medium", "tier": { "k": "cor", "label": "Corroborated (authoritative primary)", "say": "A validator compared this with 1 named source, the strongest being a publication of NPP Australia Limited itself. It is not verified: no person has checked it against the current rulebook edition." }, "id": "AM21", "summary": "The amount asked for exceeds the limit the payer and their own institution agreed. This is a third kind of PayTo amount failure and the limit behind it is a private one between a customer and their bank.", "sources": [] }, { "uid": "au-npp-reject:MD01", "name": "No mandate", "status": "corroborated", "stored_status": "corroborated", "source_class": "authoritative_primary", "confidence": "medium", "tier": { "k": "cor", "label": "Corroborated (authoritative primary)", "say": "A validator compared this with 1 named source, the strongest being a publication of NPP Australia Limited itself. It is not verified: no person has checked it against the current rulebook edition." }, "id": "MD01", "summary": "The PayTo agreement identifier is missing from the payment instruction. A payment request under an agreement has to name the agreement.", "sources": [] }, { "uid": "au-npp-reject:NAUT", "name": "Not authorised", "status": "corroborated", "stored_status": "corroborated", "source_class": "authoritative_primary", "confidence": "medium", "tier": { "k": "cor", "label": "Corroborated (authoritative primary)", "say": "A validator compared this with 1 named source, the strongest being a publication of NPP Australia Limited itself. It is not verified: no person has checked it against the current rulebook edition." }, "id": "NAUT", "summary": "The contents of a PayTo payment request do not line up with the terms of the agreement. Another PayTo specific meaning, and the broadest of them: where AM06, AM09 and AM21 are about the amount, this one is about the request not matching the agreement in any respect.", "sources": [] } ], "rules": [ { "uid": "au-npp:rule.finality-no-cancel-or-recall-once-the-message-is-in-the-gateway", "name": "The paying institution cannot cancel or recall a payment once the message is in its own gateway", "status": "corroborated", "stored_status": "corroborated", "source_class": "authoritative_primary", "confidence": "medium", "tier": { "k": "cor", "label": "Corroborated (authoritative primary)", "say": "A validator compared this with 1 named source, the strongest being a publication of NPP Australia Limited itself. It is not verified: no person has checked it against the current rulebook edition." }, "statement": "The point of no return on this rail is early and it is inside the sending institution. Once the clearing request has been input into the payer participant's own gateway, that participant may neither cancel it nor recall it. Nothing later moves that point, and there is no message in the scheme for taking a payment back.", "facet": "finality", "rests_on": "rule", "via": "applies_to", "also_applies_to": [ { "uid": "au-npp:txn.bsct", "name": "Basic Single Credit Transfer (BSCT)" }, { "uid": "au-npp:txn.os-payment", "name": "Overlay Service Payment (OS Payment)" } ], "parameters": [], "part_of": [ "au-npp:exc.settlement-rejection" ], "sources": [ { "uid": "au-npp:src.npp-regulations-v21", "name": "Regulations for the New Payments Platform, v21.0, public version", "url": "https://www.auspayplus.com.au/wp-content/uploads/2024/10/NPP-Regulations-v21.0_Public_version.pdf", "source_class": "authoritative_primary", "edition": "v21.0, 24 September 2024; the Regulations commenced 1 July 2017", "section": "Regulation 6.2(a)" } ] }, { "uid": "au-npp:rule.messages-a-rejected-mandate-payment-request-carries-a-reason-code", "name": "A rejected mandate payment initiation request must also carry a valid and applicable reason code", "status": "corroborated", "stored_status": "corroborated", "source_class": "authoritative_primary", "confidence": "medium", "tier": { "k": "cor", "label": "Corroborated (authoritative primary)", "say": "A validator compared this with 1 named source, the strongest being a publication of NPP Australia Limited itself. It is not verified: no person has checked it against the current rulebook edition." }, "statement": "The same shape on the PayTo leg. A payer participant must respond to each mandate payment initiation request inside the timeframes the procedures prescribe with a status report indicating receipt and either acceptance or rejection, and where it rejects it must provide a valid and applicable reason code. Where it accepts and funds are available it then sends a clearing request for the amount claimed. Again no value is listed.", "facet": "messages", "rests_on": "rule", "via": "applies_to", "also_applies_to": [], "parameters": [], "part_of": [], "sources": [ { "uid": "au-npp:src.npp-regulations-v21", "name": "Regulations for the New Payments Platform, v21.0, public version", "url": "https://www.auspayplus.com.au/wp-content/uploads/2024/10/NPP-Regulations-v21.0_Public_version.pdf", "source_class": "authoritative_primary", "edition": "v21.0, 24 September 2024; the Regulations commenced 1 July 2017", "section": "Regulation 17.8(b)(i) and (ii)" } ] }, { "uid": "au-npp:rule.messages-iso-20022-from-launch", "name": "The platform has used ISO 20022 natively since launch", "status": "corroborated", "stored_status": "corroborated", "source_class": "authoritative_primary", "confidence": "medium", "tier": { "k": "cor", "label": "Corroborated (authoritative primary)", "say": "A validator compared this with 2 named sources, the strongest being a publication of NPP Australia Limited itself. It is not verified: no person has checked it against the current rulebook edition." }, "statement": "Every message on this rail is an ISO 20022 message and always has been. A clearing request that starts a payment is a pacs.008, the clearing notification that answers it and the settlement notification the settlement service sends are both pacs.002, the settlement request is a pacs.009, a return is a pacs.004 and a request for one is a camt.056. On the customer to institution leg a payment instruction is a pain.001, a creditor payment initiation request under PayTo is a pain.013, and the status report back to a corporate customer is a pain.002.", "facet": "messages", "rests_on": "rule", "via": "applies_to", "also_applies_to": [ { "uid": "au-npp:txn.bsct", "name": "Basic Single Credit Transfer (BSCT)" } ], "parameters": [], "part_of": [], "sources": [ { "uid": "au-npp:src.npp-regulations-v21", "name": "Regulations for the New Payments Platform, v21.0, public version", "url": "https://www.auspayplus.com.au/wp-content/uploads/2024/10/NPP-Regulations-v21.0_Public_version.pdf", "source_class": "authoritative_primary", "edition": "v21.0, 24 September 2024; the Regulations commenced 1 July 2017", "section": "the definitions of Clearing Request, Clearing Notification, Settlement Request, Settlement Notification, NPP Payment Return and Request for Payment Return, and Regulation 17.1(c)" }, { "uid": "au-npp:src.npp-payment-initiation-messages-v4", "name": "NPP Payment Initiation Messages, technical guidance for corporates, government and third parties, v4.0", "url": "https://www.auspayplus.com.au/wp-content/uploads/2026/03/NPP-payment-initiation-V4.0.pdf", "source_class": "authoritative_primary", "edition": "v4.0, 20 November 2025, uploaded March 2026", "section": "Background" } ] }, { "uid": "au-npp:rule.mandate-a-mandate-is-a-record-in-the-scheme-operators-database", "name": "A PayTo mandate is a record in a database the scheme operator runs, not a document a party keeps", "status": "corroborated", "stored_status": "corroborated", "source_class": "authoritative_primary", "confidence": "medium", "tier": { "k": "cor", "label": "Corroborated (authoritative primary)", "say": "A validator compared this with 1 named source, the strongest being a publication of NPP Australia Limited itself. It is not verified: no person has checked it against the current rulebook edition." }, "statement": "The Mandate Management Service is a centralised, secure, access controlled database of mandates that the scheme operator established and runs. A mandate is a record in it of a payment authorisation the payer gave in favour of a business or a payment initiator, identified by a unique mandate identifier the database itself generates, which gives the holder the right to send requests instructing the payer's own institution to make payments within the mandate's terms. The database may also hold, at the payer institution's option, records of another kind of arrangement defined only in the procedures.", "facet": null, "rests_on": "rule", "via": "both", "also_applies_to": [], "parameters": [], "part_of": [], "sources": [ { "uid": "au-npp:src.npp-regulations-v21", "name": "Regulations for the New Payments Platform, v21.0, public version", "url": "https://www.auspayplus.com.au/wp-content/uploads/2024/10/NPP-Regulations-v21.0_Public_version.pdf", "source_class": "authoritative_primary", "edition": "v21.0, 24 September 2024; the Regulations commenced 1 July 2017", "section": "Regulation 17.1(a) and (b), and Regulation 17.1(g)" } ] }, { "uid": "au-npp:rule.mandate-a-mandate-may-be-ported-to-another-participant", "name": "A mandate may be moved to another institution without the authorisation changing", "status": "corroborated", "stored_status": "corroborated", "source_class": "authoritative_primary", "confidence": "medium", "tier": { "k": "cor", "label": "Corroborated (authoritative primary)", "say": "A validator compared this with 1 named source, the strongest being a publication of NPP Australia Limited itself. It is not verified: no person has checked it against the current rulebook edition." }, "statement": "A mandate can change custodian. The payer's institution must facilitate porting a mandate where necessary at the payer's request, and a mandate established for a payment initiator may be moved to another participant or connected institution on the initiator's instruction. An institution's right to read a mandate record is expressly subject to the other parties' right to port it away. All the porting provisions took effect on 5 May 2023.", "facet": null, "rests_on": "rule", "via": "mandate", "also_applies_to": [], "parameters": [], "part_of": [], "sources": [ { "uid": "au-npp:src.npp-regulations-v21", "name": "Regulations for the New Payments Platform, v21.0, public version", "url": "https://www.auspayplus.com.au/wp-content/uploads/2024/10/NPP-Regulations-v21.0_Public_version.pdf", "source_class": "authoritative_primary", "edition": "v21.0, 24 September 2024; the Regulations commenced 1 July 2017", "section": "Regulations 17.6(c)(vi), 17.5(f) and 17.7(b)(iv), and the Part 17 drafting note on porting" } ] }, { "uid": "au-npp:rule.mandate-a-migrated-mandate-claim-is-deemed-substantiated", "name": "A claim about a migrated mandate is deemed substantiated unless the sponsor produces the evidence", "status": "corroborated", "stored_status": "corroborated", "source_class": "authoritative_primary", "confidence": "medium", "tier": { "k": "cor", "label": "Corroborated (authoritative primary)", "say": "A validator compared this with 1 named source, the strongest being a publication of NPP Australia Limited itself. It is not verified: no person has checked it against the current rulebook edition." }, "statement": "This is where the missing consent shows up. Where a mandate claim relates to a migrated mandate, the claim is deemed to be substantiated unless the sponsoring participant produces written evidence both of the payer's authorisation of the direct debit request the mandate was based on and that the payment in question was authorised by the mandate's terms. The burden runs against the side that created the record without asking.", "facet": null, "rests_on": "rule", "via": "mandate", "also_applies_to": [], "parameters": [], "part_of": [ "au-npp:exc.mandate-claim" ], "sources": [ { "uid": "au-npp:src.npp-regulations-v21", "name": "Regulations for the New Payments Platform, v21.0, public version", "url": "https://www.auspayplus.com.au/wp-content/uploads/2024/10/NPP-Regulations-v21.0_Public_version.pdf", "source_class": "authoritative_primary", "edition": "v21.0, 24 September 2024; the Regulations commenced 1 July 2017", "section": "Regulations 17.10(c)(ii) and 17.10(e)" } ] }, { "uid": "au-npp:rule.mandate-a-migrated-mandate-is-created-without-a-consent-step", "name": "A migrated direct debit mandate is created unilaterally and is active the moment it exists", "status": "corroborated", "stored_status": "corroborated", "source_class": "authoritative_primary", "confidence": "medium", "tier": { "k": "cor", "label": "Corroborated (authoritative primary)", "say": "A validator compared this with 1 named source, the strongest being a publication of NPP Australia Limited itself. It is not verified: no person has checked it against the current rulebook edition." }, "statement": "The one mandate in the corpus nobody consented to. A participant that is a framework participant in the direct debit system may create mandate records for direct debit arrangements it already processes for the businesses it sponsors. Those records are designated migrated mandates, they are established unilaterally by the business and its sponsor, and they are deemed active in the operator's database immediately on creation. The business is deemed approved as a user of the service by the same act. The obligations to deliver an authorisation request to the payer and to facilitate porting are expressly switched off for them.", "facet": null, "rests_on": "rule", "via": "both", "also_applies_to": [], "parameters": [], "part_of": [], "sources": [ { "uid": "au-npp:src.npp-regulations-v21", "name": "Regulations for the New Payments Platform, v21.0, public version", "url": "https://www.auspayplus.com.au/wp-content/uploads/2024/10/NPP-Regulations-v21.0_Public_version.pdf", "source_class": "authoritative_primary", "edition": "v21.0, 24 September 2024; the Regulations commenced 1 July 2017", "section": "Regulations 17.4(a), (b) and (d), and 17.6(c)(viii)" } ] }, { "uid": "au-npp:rule.mandate-a-request-may-not-be-sent-unless-the-mandate-is-active", "name": "No payment request may be sent unless the mandate is active", "status": "corroborated", "stored_status": "corroborated", "source_class": "authoritative_primary", "confidence": "medium", "tier": { "k": "cor", "label": "Corroborated (authoritative primary)", "say": "A validator compared this with 1 named source, the strongest being a publication of NPP Australia Limited itself. It is not verified: no person has checked it against the current rulebook edition." }, "statement": "A participant or connected institution acting as the initiating participant must not send a mandate payment initiation request unless the associated mandate is active, and is responsible for each request it sends being properly built and consistent with the mandate's terms. Sending one against a suspended or cancelled mandate is one of the things the rulebook lists as not authorised, which is what turns the resulting payment into a claim. The payer's institution may look the mandate up before processing but is not obliged to.", "facet": null, "rests_on": "rule", "via": "both", "also_applies_to": [], "parameters": [], "part_of": [ "au-npp:exc.mandate-claim" ], "sources": [ { "uid": "au-npp:src.npp-regulations-v21", "name": "Regulations for the New Payments Platform, v21.0, public version", "url": "https://www.auspayplus.com.au/wp-content/uploads/2024/10/NPP-Regulations-v21.0_Public_version.pdf", "source_class": "authoritative_primary", "edition": "v21.0, 24 September 2024; the Regulations commenced 1 July 2017", "section": "Regulations 17.8(a), (b) and (c), and 17.10(c)(i)(B)" } ] }, { "uid": "au-npp:rule.mandate-an-amount-or-frequency-change-comes-from-the-business", "name": "A change to the amount or the frequency has to come from the business as a fresh agreement", "status": "corroborated", "stored_status": "corroborated", "source_class": "public_primary", "confidence": "medium", "tier": { "k": "cor", "label": "Corroborated (public primary)", "say": "A validator compared this with 1 named source, the strongest being an operator or regulator publication. It is not verified: no person has checked it against the current rulebook edition." }, "statement": "A payer can pause, resume and cancel, and can make the amendments the mandate's terms permit, but cannot simply raise or lower what they agreed to. The operator's parent says that for a change of amount or frequency the business has to make the change and send the payer an updated agreement to authorise. That keeps every change to the substance of the authorisation on the same footing as the original one.", "facet": null, "rests_on": "guidance", "via": "mandate", "also_applies_to": [], "parameters": [], "part_of": [], "sources": [ { "uid": "au-npp:src.auspayplus-payto-faqs", "name": "Australian Payments Plus, PayTo FAQs", "url": "https://www.auspayplus.com.au/solutions/payto-faqs", "source_class": "public_primary", "edition": "live page, read 2026-09-21", "section": "can I change, pause, resume or cancel my PayTo agreement" }, { "uid": "au-npp:src.npp-regulations-v21", "name": "Regulations for the New Payments Platform, v21.0, public version", "url": "https://www.auspayplus.com.au/wp-content/uploads/2024/10/NPP-Regulations-v21.0_Public_version.pdf", "source_class": "authoritative_primary", "edition": "v21.0, 24 September 2024; the Regulations commenced 1 July 2017", "section": "Regulation 17.6(d), on a maintenance function being permitted by the mandate's terms" } ] }, { "uid": "au-npp:rule.mandate-an-authorised-mandate-claim-is-deemed-substantiated-by-the-record", "name": "A claim about an ordinary mandate is tested against the record, or against evidence the initiator must produce", "status": "corroborated", "stored_status": "corroborated", "source_class": "authoritative_primary", "confidence": "medium", "tier": { "k": "cor", "label": "Corroborated (authoritative primary)", "say": "A validator compared this with 1 named source, the strongest being a publication of NPP Australia Limited itself. It is not verified: no person has checked it against the current rulebook edition." }, "statement": "For an ordinary PayTo mandate the rulebook splits the claim in two. Where the payer's institution says the payment was not permitted by the mandate in amount, frequency or beneficiary, the claim is deemed substantiated by reference to the record in the operator's database itself, which is what makes that record the evidence. Where it says the payer did not authorise that particular payment at the time the request was sent, the claim is deemed substantiated unless the initiating side produces evidence that they did, and if the two of them disagree about the reliability of that evidence they may use the rulebook's own dispute resolution process.", "facet": null, "rests_on": "rule", "via": "mandate", "also_applies_to": [], "parameters": [], "part_of": [ "au-npp:exc.mandate-claim" ], "sources": [ { "uid": "au-npp:src.npp-regulations-v21", "name": "Regulations for the New Payments Platform, v21.0, public version", "url": "https://www.auspayplus.com.au/wp-content/uploads/2024/10/NPP-Regulations-v21.0_Public_version.pdf", "source_class": "authoritative_primary", "edition": "v21.0, 24 September 2024; the Regulations commenced 1 July 2017", "section": "Regulation 17.10(f)(i) and (ii), and Regulation 17.10(c)(i)" } ] }, { "uid": "au-npp:rule.mandate-authorisation-is-delivered-in-near-real-time", "name": "The payer's institution must deliver the authorisation request to the payer in near real time", "status": "corroborated", "stored_status": "corroborated", "source_class": "authoritative_primary", "confidence": "medium", "tier": { "k": "cor", "label": "Corroborated (authoritative primary)", "say": "A validator compared this with 1 named source, the strongest being a publication of NPP Australia Limited itself. It is not verified: no person has checked it against the current rulebook edition." }, "statement": "Creating a mandate record is not the same as authorising it. The payer's institution must be able to receive authorisation requests from the operator's database, must associate each one with a payer by the account number in the record, must deliver it to that customer in near real time for authorisation to the standards the procedures set, must take any consents privacy law needs, and must record the confirmation in the database promptly after the customer authorises or rejects it. The mandate is active only once that confirmation is recorded.", "facet": null, "rests_on": "rule", "via": "mandate", "also_applies_to": [], "parameters": [], "part_of": [], "sources": [ { "uid": "au-npp:src.npp-regulations-v21", "name": "Regulations for the New Payments Platform, v21.0, public version", "url": "https://www.auspayplus.com.au/wp-content/uploads/2024/10/NPP-Regulations-v21.0_Public_version.pdf", "source_class": "authoritative_primary", "edition": "v21.0, 24 September 2024; the Regulations commenced 1 July 2017", "section": "Regulation 17.6(c)(i) to (v), and the definition of Active" } ] }, { "uid": "au-npp:rule.mandate-data-is-confidential-to-the-parties", "name": "A mandate record is confidential to its parties and may be looked up only by them", "status": "corroborated", "stored_status": "corroborated", "source_class": "authoritative_primary", "confidence": "medium", "tier": { "k": "cor", "label": "Corroborated (authoritative primary)", "say": "A validator compared this with 1 named source, the strongest being a publication of NPP Australia Limited itself. It is not verified: no person has checked it against the current rulebook edition." }, "statement": "Lookup rights are restricted to the parties to the mandate, and information in a mandate record must be treated as confidential to them and not disclosed to anybody else except as law requires. A lookup may be performed only for validating and processing requests and payments, resolving investigations and claims, fraud investigation and analytics, or giving effect to the parties' own instructions. Institutions must have systems to prevent unauthorised disclosure, to spot it promptly when it happens, and must tell the operator in writing when it does.", "facet": null, "rests_on": "rule", "via": "mandate", "also_applies_to": [], "parameters": [], "part_of": [], "sources": [ { "uid": "au-npp:src.npp-regulations-v21", "name": "Regulations for the New Payments Platform, v21.0, public version", "url": "https://www.auspayplus.com.au/wp-content/uploads/2024/10/NPP-Regulations-v21.0_Public_version.pdf", "source_class": "authoritative_primary", "edition": "v21.0, 24 September 2024; the Regulations commenced 1 July 2017", "section": "Regulations 17.2(e) and 17.7(a) and (b)" } ] }, { "uid": "au-npp:rule.mandate-five-days-before-a-migrated-mandate-may-be-used", "name": "A migrated mandate may not be used for a payment request until 5 days after it was created", "status": "corroborated", "stored_status": "corroborated", "source_class": "authoritative_primary", "confidence": "medium", "tier": { "k": "cor", "label": "Corroborated (authoritative primary)", "say": "A validator compared this with 1 named source, the strongest being a publication of NPP Australia Limited itself. It is not verified: no person has checked it against the current rulebook edition." }, "statement": "The second safeguard is delay. A migrated mandate may be used to issue a mandate payment initiation request no earlier than five days after the time and date it was created. To let the payer's institution check the arrangement against its own customer's account status and transaction history, the record must carry the business's direct debit user identifier.", "facet": null, "rests_on": "rule", "via": "both", "also_applies_to": [], "parameters": [ { "kind": "time_window", "text": "5 days from the time and date the migrated mandate record was created, before it may be used for a payment request. The rulebook says five days without saying calendar or business days, and calendar days is Orca's reading [Inference]." } ], "part_of": [], "sources": [ { "uid": "au-npp:src.npp-regulations-v21", "name": "Regulations for the New Payments Platform, v21.0, public version", "url": "https://www.auspayplus.com.au/wp-content/uploads/2024/10/NPP-Regulations-v21.0_Public_version.pdf", "source_class": "authoritative_primary", "edition": "v21.0, 24 September 2024; the Regulations commenced 1 July 2017", "section": "Regulation 17.4(e)" } ] }, { "uid": "au-npp:rule.mandate-fourteen-days-notice-before-a-migrated-mandate-is-created", "name": "A migrated mandate needs written notice to the payer first, at least 14 days ahead", "status": "corroborated", "stored_status": "corroborated", "source_class": "authoritative_primary", "confidence": "medium", "tier": { "k": "cor", "label": "Corroborated (authoritative primary)", "say": "A validator compared this with 2 named sources, the strongest being a publication of NPP Australia Limited itself. It is not verified: no person has checked it against the current rulebook edition." }, "statement": "The consent step is replaced by a notice step. Before the record is created, the business must have told each of its payers in writing that future debits will generally go through the platform rather than the direct debit system where their account can take them, and must have given whatever notice its direct debit service agreement requires or at least fourteen days. It must hold and be able to produce evidence of the original direct debit authorisation and of the notice. Direct debit processing of the same arrangement must stop from the migration date, except in a genuine outage. The operator's parent tells customers they may opt out during the notice period and stay on direct debit.", "facet": null, "rests_on": "rule", "via": "mandate", "also_applies_to": [], "parameters": [ { "kind": "time_window", "text": "At least 14 days before the migrated mandate record is created, or whatever longer notice the direct debit service agreement requires. The rulebook says fourteen days; it does not say whether they are calendar or business days, and calendar days is Orca's reading [Inference]." } ], "part_of": [], "sources": [ { "uid": "au-npp:src.npp-regulations-v21", "name": "Regulations for the New Payments Platform, v21.0, public version", "url": "https://www.auspayplus.com.au/wp-content/uploads/2024/10/NPP-Regulations-v21.0_Public_version.pdf", "source_class": "authoritative_primary", "edition": "v21.0, 24 September 2024; the Regulations commenced 1 July 2017", "section": "Regulation 17.4(c)(i) to (iii)" }, { "uid": "au-npp:src.auspayplus-payto-faqs", "name": "Australian Payments Plus, PayTo FAQs", "url": "https://www.auspayplus.com.au/solutions/payto-faqs", "source_class": "public_primary", "edition": "live page, read 2026-09-21", "section": "what should I do if my direct debit is moving to PayTo, and do I have to agree" } ] }, { "uid": "au-npp:rule.mandate-participation-is-mandatory-for-a-payer-participant", "name": "Offering PayTo is optional for a creditor's bank and compulsory for the payer's bank", "status": "corroborated", "stored_status": "corroborated", "source_class": "authoritative_primary", "confidence": "medium", "tier": { "k": "cor", "label": "Corroborated (authoritative primary)", "say": "A validator compared this with 1 named source, the strongest being a publication of NPP Australia Limited itself. It is not verified: no person has checked it against the current rulebook edition." }, "statement": "The service is asymmetric by design. Taking part is optional for a participant acting as a provider of the service to businesses, optional for a connected institution, and optional for an overlay service provider, but it is mandatory for every participant and sponsored institution in its capacity as a payer participant and account servicer. A payer's institution must also provide the service for every account type that is enabled and eligible to make payments on the platform.", "facet": null, "rests_on": "rule", "via": "mandate", "also_applies_to": [], "parameters": [], "part_of": [], "sources": [ { "uid": "au-npp:src.npp-regulations-v21", "name": "Regulations for the New Payments Platform, v21.0, public version", "url": "https://www.auspayplus.com.au/wp-content/uploads/2024/10/NPP-Regulations-v21.0_Public_version.pdf", "source_class": "authoritative_primary", "edition": "v21.0, 24 September 2024; the Regulations commenced 1 July 2017", "section": "Regulation 17.1(f)(i) to (iv) and Regulation 17.1(n)" } ] }, { "uid": "au-npp:rule.mandate-the-payer-customer-can-view-suspend-cancel-and-amend", "name": "The payer's institution must give the payer a way to view, suspend, cancel and amend their mandates", "status": "corroborated", "stored_status": "corroborated", "source_class": "authoritative_primary", "confidence": "medium", "tier": { "k": "cor", "label": "Corroborated (authoritative primary)", "say": "A validator compared this with 2 named sources, the strongest being a publication of NPP Australia Limited itself. It is not verified: no person has checked it against the current rulebook edition." }, "statement": "A payer participant must provide a facility that lets payers see the mandates they are a party to and give instructions to suspend or cancel them or make permitted amendments to them, and must promptly give effect to those instructions. Whoever performs any mandate maintenance function is responsible for making sure the particular mandate's terms allow it. The operator's parent describes the same thing to customers as pausing, resuming or cancelling in online banking, and says that doing so does not change the customer's contract with the business.", "facet": null, "rests_on": "rule", "via": "mandate", "also_applies_to": [], "parameters": [], "part_of": [], "sources": [ { "uid": "au-npp:src.npp-regulations-v21", "name": "Regulations for the New Payments Platform, v21.0, public version", "url": "https://www.auspayplus.com.au/wp-content/uploads/2024/10/NPP-Regulations-v21.0_Public_version.pdf", "source_class": "authoritative_primary", "edition": "v21.0, 24 September 2024; the Regulations commenced 1 July 2017", "section": "Regulation 17.6(c)(vii) and 17.6(d)" }, { "uid": "au-npp:src.auspayplus-payto-faqs", "name": "Australian Payments Plus, PayTo FAQs", "url": "https://www.auspayplus.com.au/solutions/payto-faqs", "source_class": "public_primary", "edition": "live page, read 2026-09-21", "section": "can I change, pause, resume or cancel my PayTo agreement" } ] }, { "uid": "au-npp:rule.mandate-the-payer-participant-keeps-processing-pending-word", "name": "Until the payer says something, their institution must keep processing a migrated mandate", "status": "corroborated", "stored_status": "corroborated", "source_class": "authoritative_primary", "confidence": "medium", "tier": { "k": "cor", "label": "Corroborated (authoritative primary)", "say": "A validator compared this with 1 named source, the strongest being a publication of NPP Australia Limited itself. It is not verified: no person has checked it against the current rulebook edition." }, "statement": "The payer's institution could optionally satisfy itself that a migrated mandate really matches its customer's existing direct debit and may ask the customer to confirm it, and must keep a record if the customer does. If the customer says authorisation was never given, or tells it to suspend or cancel, it must act promptly. But pending confirmation or any other instruction from the customer, it must continue to process payment requests against the mandate. Treating one of these as unauthorised by default would misstate the rule as badly as treating it as authorised.", "facet": null, "rests_on": "rule", "via": "mandate", "also_applies_to": [], "parameters": [], "part_of": [], "sources": [ { "uid": "au-npp:src.npp-regulations-v21", "name": "Regulations for the New Payments Platform, v21.0, public version", "url": "https://www.auspayplus.com.au/wp-content/uploads/2024/10/NPP-Regulations-v21.0_Public_version.pdf", "source_class": "authoritative_primary", "edition": "v21.0, 24 September 2024; the Regulations commenced 1 July 2017", "section": "Regulation 17.4(d)(i) to (iv)" } ] }, { "uid": "au-npp:rule.mandate-the-record-is-evidence-of-quantum-frequency-and-beneficiary", "name": "The mandate record is the evidence of the amount, the frequency and the beneficiary", "status": "corroborated", "stored_status": "corroborated", "source_class": "authoritative_primary", "confidence": "medium", "tier": { "k": "cor", "label": "Corroborated (authoritative primary)", "say": "A validator compared this with 1 named source, the strongest being a publication of NPP Australia Limited itself. It is not verified: no person has checked it against the current rulebook edition." }, "statement": "The rulebook says out loud what most rails leave implicit: the mandate record is evidence of the quantum, the frequency and, where it is recorded, the beneficiary of the payments the payer authorised. That single sentence is why a claim that a payment fell outside the amount, frequency or beneficiary of an ordinary PayTo mandate is deemed substantiated simply by reference to the record.", "facet": null, "rests_on": "rule", "via": "mandate", "also_applies_to": [], "parameters": [], "part_of": [ "au-npp:exc.mandate-claim" ], "sources": [ { "uid": "au-npp:src.npp-regulations-v21", "name": "Regulations for the New Payments Platform, v21.0, public version", "url": "https://www.auspayplus.com.au/wp-content/uploads/2024/10/NPP-Regulations-v21.0_Public_version.pdf", "source_class": "authoritative_primary", "edition": "v21.0, 24 September 2024; the Regulations commenced 1 July 2017", "section": "Regulation 17.10(d)" } ] } ], "inherited": [ { "facet": "settlement", "label": "Settlement", "question": "How and when does the money settle between institutions?", "fact_uid": "au-npp:settlement", "fact_name": "How and when does an NPP payment settle?" }, { "facet": "hours", "label": "Hours", "question": "When does the rail run, and what are its cut-offs?", "fact_uid": "au-npp:hours", "fact_name": "When is the NPP open?" }, { "facet": "limits", "label": "Limits", "question": "What limits apply to a payment, and who sets them?", "fact_uid": "au-npp:limits", "fact_name": "Is there a limit on an NPP payment?" }, { "facet": "return", "label": "Return", "question": "How does a payment come back, and on what deadline?", "fact_uid": "au-npp:return", "fact_name": "How does money come back on the NPP?" }, { "facet": "recall", "label": "Recall", "question": "Can the sender ask for a payment back, and who decides?", "fact_uid": "au-npp:recall", "fact_name": "Can an NPP payment be recalled?" }, { "facet": "refund", "label": "Refund", "question": "Can the payer get the money back, and on what right?", "fact_uid": "au-npp:refund", "fact_name": "Can a customer get an NPP payment refunded?" }, { "facet": "liability", "label": "Liability", "question": "Who bears a loss when something goes wrong?", "fact_uid": "au-npp:liability", "fact_name": "Who bears the loss on an NPP payment?" }, { "facet": "consumer-law", "label": "Consumer law", "question": "What does the law give a consumer here, beyond the rulebook?", "fact_uid": "au-npp:consumer-law", "fact_name": "What consumer law sits above the NPP?" }, { "facet": "participants", "label": "Participants", "question": "Who may take part, and in what role?", "fact_uid": "au-npp:participants", "fact_name": "Who takes part in the NPP?" }, { "facet": "decision-points", "label": "Human decision points", "question": "Where does a rule leave the decision to a bank or a person?", "fact_uid": "au-npp:decision-points", "fact_name": "Where does somebody decide something on the NPP?" } ], "differs": [ { "facet": "finality", "label": "Finality", "fact_uid": "au-npp:finality", "fact_name": "When is an NPP payment final, and can it be undone?", "rules": [ { "uid": "au-npp:rule.finality-no-cancel-or-recall-once-the-message-is-in-the-gateway", "name": "The paying institution cannot cancel or recall a payment once the message is in its own gateway" } ] }, { "facet": "liability", "label": "Liability", "fact_uid": "au-npp:liability", "fact_name": "Who bears the loss on an NPP payment?", "rules": [ { "uid": "au-npp:rule.mandate-a-migrated-mandate-claim-is-deemed-substantiated", "name": "A claim about a migrated mandate is deemed substantiated unless the sponsor produces the evidence" }, { "uid": "au-npp:rule.mandate-an-authorised-mandate-claim-is-deemed-substantiated-by-the-record", "name": "A claim about an ordinary mandate is tested against the record, or against evidence the initiator must produce" } ] }, { "facet": "messages", "label": "Messages", "fact_uid": "au-npp:messages", "fact_name": "What messages does the NPP use, and what codes do they carry?", "rules": [ { "uid": "au-npp:rule.messages-iso-20022-from-launch", "name": "The platform has used ISO 20022 natively since launch" }, { "uid": "au-npp:rule.messages-a-rejected-mandate-payment-request-carries-a-reason-code", "name": "A rejected mandate payment initiation request must also carry a valid and applicable reason code" } ] }, { "facet": "decision-points", "label": "Human decision points", "fact_uid": "au-npp:decision-points", "fact_name": "Where does somebody decide something on the NPP?", "rules": [ { "uid": "au-npp:rule.mandate-a-mandate-is-a-record-in-the-scheme-operators-database", "name": "A PayTo mandate is a record in a database the scheme operator runs, not a document a party keeps" }, { "uid": "au-npp:rule.mandate-participation-is-mandatory-for-a-payer-participant", "name": "Offering PayTo is optional for a creditor's bank and compulsory for the payer's bank" }, { "uid": "au-npp:rule.mandate-authorisation-is-delivered-in-near-real-time", "name": "The payer's institution must deliver the authorisation request to the payer in near real time" }, { "uid": "au-npp:rule.mandate-a-request-may-not-be-sent-unless-the-mandate-is-active", "name": "No payment request may be sent unless the mandate is active" }, { "uid": "au-npp:rule.mandate-the-payer-customer-can-view-suspend-cancel-and-amend", "name": "The payer's institution must give the payer a way to view, suspend, cancel and amend their mandates" }, { "uid": "au-npp:rule.mandate-an-amount-or-frequency-change-comes-from-the-business", "name": "A change to the amount or the frequency has to come from the business as a fresh agreement" }, { "uid": "au-npp:rule.mandate-a-mandate-may-be-ported-to-another-participant", "name": "A mandate may be moved to another institution without the authorisation changing" }, { "uid": "au-npp:rule.mandate-data-is-confidential-to-the-parties", "name": "A mandate record is confidential to its parties and may be looked up only by them" }, { "uid": "au-npp:rule.mandate-the-record-is-evidence-of-quantum-frequency-and-beneficiary", "name": "The mandate record is the evidence of the amount, the frequency and the beneficiary" }, { "uid": "au-npp:rule.mandate-a-migrated-mandate-is-created-without-a-consent-step", "name": "A migrated direct debit mandate is created unilaterally and is active the moment it exists" }, { "uid": "au-npp:rule.mandate-fourteen-days-notice-before-a-migrated-mandate-is-created", "name": "A migrated mandate needs written notice to the payer first, at least 14 days ahead" }, { "uid": "au-npp:rule.mandate-five-days-before-a-migrated-mandate-may-be-used", "name": "A migrated mandate may not be used for a payment request until 5 days after it was created" }, { "uid": "au-npp:rule.mandate-the-payer-participant-keeps-processing-pending-word", "name": "Until the payer says something, their institution must keep processing a migrated mandate" } ] } ], "exceptions": [ { "uid": "au-npp:exc.mandate-claim", "name": "Mandate claim", "shared": true, "via": [ { "from": "au-npp:mandate.authorised-payment-mandate", "type": "disputed_via" }, { "from": "au-npp:mandate.migrated-ddr-mandate", "type": "disputed_via" }, { "from": "au-npp:rule.mandate-a-request-may-not-be-sent-unless-the-mandate-is-active", "type": "part_of" }, { "from": "au-npp:rule.mandate-an-authorised-mandate-claim-is-deemed-substantiated-by-the-record", "type": "part_of" }, { "from": "au-npp:rule.mandate-the-record-is-evidence-of-quantum-frequency-and-beneficiary", "type": "part_of" }, { "from": "au-npp:rule.mandate-a-migrated-mandate-claim-is-deemed-substantiated", "type": "part_of" } ] }, { "uid": "au-npp:exc.settlement-rejection", "name": "Settlement rejection, which voids a cleared payment", "shared": true, "via": [ { "from": "au-npp:rule.finality-no-cancel-or-recall-once-the-message-is-in-the-gateway", "type": "part_of" } ] } ] } }