📘

The Account Check Service is currently in 'early release' stage. The API and guides may change.

Purpose

This guide serves as a starting point to provide you with an overview of Azupay's Account Check service and Confirmation of Payee.

Introduction

Azupay's Account Check Service (ACS) enables real-time matching of customer-provided details, led by your workflow and powered by Confirmation of Payee, PayID Name Check, and ConnectID, so businesses can reduce mistakes, minimize rework, and make more confident payment decisions.

📘

Currently, CoP is available via the Account Check API endpoint. PayID Name Check will migrate from the PayID enquiry endpoint soon. For ConnectID enquiries, contact your Azupay Account Manager.

Confirmation of Payee (CoP)

Confirmation of Payee provides a layer of protection for payments to a BSB and account number by matching the account details provided with the account details held by the recipient's bank and displaying a match outcome. It's a new layer of protection for Australian businesses when they're making payments to a BSB and account number.

Confirmation of Payee can help safeguard businesses from fraud, scams, and mistaken payments, and help protect their money. It provides confidence that the details provided match the details held by the recipient's bank.

Importance

• Growing scam and fraud risk: Scams and fraudulent activity continue to rise, increasing the need for stronger protection when making payments to a BSB and account number.
• Payment redirection threats: False billing and payment-redirection scams can divert funds to the wrong account, often without being noticed until it's too late.
• First-time payments are higher risk: New or one-off payments are especially vulnerable because there is less confidence that the account details belong to the intended recipient.
• Increasing regulatory focus: Regulators are pushing for stronger "know your payee" standards, placing more emphasis on verifying account details before a payment is made.

API Implementation

See API Spec here - https://developer.azupay.com.au/v0/reference/post_accountcheck#/

📘

Contact your Account Manager to enable Account Check API permissions.

Required Parameters

• accountCheckId: Unique lookup identifier
• bsb: Target account BSB
• accountNumber: Target account number
• accountName: Expected account holder name
• purposeCode: Lookup purpose:
  • PYMT: Payment processing (existing customer verification)
  • PAYE: Customer onboarding or change in details
  • MAN: PayTo/direct debit setup
  • PIRQ: Pre-PayTo Payment Initiation lookup
• additionalDetails:
  • endUserId: Unique customer identifier
  • endUserSessionId: User session identifier

📘

endUserId and endUserSessionId enable enumeration controls to prevent service misuse. Account Managers will provide further information during implementation.

Response Format

Standard responses include:

• accountCheckResultCode
• accountCheckResult

Below is a list of possible of values for accountCheckResultCode

When the accountCheckResult is ERRR the API response will also include the following:

• accountCheckErrorReasonCode
• accountCheckErrorReasonDescription

Below is a list of possible of values for accountCheckErrorReasonCode

Test Data

To simulate different accountCheckResults and error scenarios use the test data below in the Staging environment.

Note: Individual accounts are personal accounts and Non-Individual account are business accounts

CX Guidelines

Customer Experience (CX) guidelines help ensure Azupay's Account Check service is presented consistently, clearly, and confidently to your end users. Well-designed journeys make it easy for customers and internal users to understand what's happening, what the result means, and what action to take next, so you get the full risk-reduction and operational benefits of Confirmation of Payee without adding friction or confusion.

📘

These guidelines are intentionally generic. You should adapt wording and layout to your brand, use cases, and workflows.

Icon and Messaging