1What the document states

The ePayments Code is a voluntary code of practice. Banks, credit unions, building societies and other providers of electronic payment facilities to consumers subscribe to it. The version read took effect on 2 June 2022, and subscribers had to comply by 2 June 2023. The Code does not apply to business facilities, to facilities without a contractual relationship between holder and subscriber, or to biller accounts.1

Chapter E sets a process for a mistaken internet payment. The Code defines it as a payment made through a pay anyone banking facility where funds go to an unintended recipient because the user entered or selected a bank and account identifier that does not belong to the intended recipient, through the user’s error or because the user was advised of the wrong details. A note to the definition says it is meant to cover typographical or wrong-selection errors and excludes a case where the user transfers funds to a recipient as a result of a scam.1

For a mistaken internet payment, the user must be warned on screen before final confirmation to check the identifiers, and the warning must say the funds may go to the wrong account and may not be recoverable. The sending bank investigates a report and, if satisfied that an error occurred, sends a return request to the receiving bank within five business days. What the receiving bank must then do depends on how soon the report was made and whether the recipient’s account holds the funds.1

2Elements recorded

Element As stated in the document Where in the document
Status Voluntary code of practice About this Code
Subscribers Banks, credit unions, building societies and other providers to consumers About this Code
Effective date 2 June 2022, compliance by 2 June 2023 Document control
Excluded facilities Business facilities, facilities with no contract, biller accounts Clause 2.1
Mistaken internet payment Wrong identifier entered or advised, scams excluded by the note Clause 25.2
On-screen warning Before final confirmation, not required where a PayID is used Clauses 27.1 and 27.2
Return request By the sending bank within five business days of the report Clause 29.2
Report within 10 business days Funds returned within five business days of the request where practicable, at most 10 Clause 30
Report from 10 business days to 7 months Investigation in 10 business days, a 10 business day block, return 2 business days after Clause 31
Report after 7 months Return only if the recipient consents Clause 32
Insufficient funds The receiving bank uses discretion, from full return to none Clause 34
Outcome to the user In writing within 30 business days, with the right to complain Clause 35

The Code also sets rules for unauthorised transactions in Chapter C, where a transaction not authorised by the user is one the user did not perform or know of. Those rules deal with passcode security and reporting, and the Code excludes from them transactions performed by the user or with the user’s knowledge and consent.1

4Check

The Code’s recovery process is built for a typing error, so the check below is written for the payer who has sent funds on details supplied by a third party.

  1. Report the payment to your bank at once and say how you came to use the details, because the Code’s process turns on whether the payment was a mistake.
  2. Note the date and time of the report. The Code sets different steps for a report within 10 business days, up to 7 months, and later.
  3. Ask the bank in writing which process it is applying, and ask for the outcome in writing. The Code requires written notice within 30 business days.
  4. If you are not satisfied, use the bank’s complaint process. The Code names the external dispute body as the next step.
  5. If the payment was made from a business facility, ask the bank what applies, since the Code excludes business facilities.

The page Before you pay sets out the general checks.

5Notes

Voluntary.

The Code binds only the providers that subscribe to it.

Scope.

A payment that a fraudster induced is outside the mistaken internet payment definition as the note states it.

Business.

Business facilities are excluded by clause 2.1.

Version.

This entry records the version published on 2 June 2022. A later version may exist.

Outcomes.

The Code does not state how many recoveries succeed, and this entry records none.

Disclosure. Safe Payee is published and funded by Bulbea, which is named in this entry.
Sources
  1. Australian Securities and Investments Commission, ePayments Code, voluntary code, Published 2 June 2022, 2 June 2022. Read 16 November 2026.