Introduction

The following sections outline the different callback notifications that are used throughout the APIs.

Prior to being able to receive callbacks to your notifyURL you will need to have the relative product configured with your URL(s).

Direct Debit Notification

This notification is triggered every hour and sends a ZIP compressed CSV file that contains a list of all cleared direct debit from bank account transactions at the present time.

Transactions that are created via the processDDebit function will initially be marked as having a status of pending. As the status of the transaction(s) update (approved or declined) over the following (2) days, they will be listed in the compressed CSV that you receive from this callback.

A sample compressed Direct Debit Notify CSV can be found here

Headers

Header Description
MWFILEHASH

An md5 hash of your API Passphrase (see DDNotify File Hash and the compressed csv file that your notifyURL receives. This can be used as a method to verify that the file you receive from us has not been tampered with or become corrupt during transit.

CSV Columns

Column Description
Transaction ID

The direct debit transaction ID.
Example: 52-1031d519-a67e-11ec-abd4-005056b209e0

MW Response

The Merchant Warrior transaction status response.
Example: approved

Amount

The original transaction amount formatted to two decimal places.
Example: 10.00

Currency

The original transaction currency.
Example: AUD

Created

The date/time that the transaction was initially created.
Example: 18/03/2022 16:41:30

Processed

The date/time the transaction was processed.
Example: 18/03/2022 16:50:13

Account Name

The customer's bank account name.
Example: Bob Smith

Account BSB

The customer's bank account BSB.
Example: 111-111

Account Number

The customer's bank account number.
Example: 12341234

Custom 1

Freeform field for you use. If it is set it will be returned.
Example: 3516843

Custom 2

Freeform field for you use. If it is set it will be returned.
Example: 3516843

Custom 3

Freeform field for you use. If it is set it will be returned.
Example: 3516843

Store ID

The store identifier. If your account is enabled for this feature and it has been set, it will be returned.
Example: 90

Type

Defines the type of transaction.
Example: ddebit

Provider Response

The response code and message returned by the Bank.
Example: 0 - Approved

EFT Notification

This notification is triggered every hour and sends a ZIP compressed CSV file that contains a list of all cleared EFT bank account transactions at the present time.

A sample compressed EFT Notify CSV can be found here

Headers

Header Description
Mw-Filehash

A sha256 hash of the compressed csv file that your notifyURL receives. This can be used as a method to verify that the file you receive from us has not been tampered with or become corrupt during transit.

Mw-Signature

A unique 25 character string prefixed with MW that is used to verify the Mw-Signaturehash.
Example: MW6253bdf46e05e9.33850753

Mw-Signaturehash

A sha256 hash of your API Passphrase, merchantUUID and Signature (from above) (see Signature Hash. This can be used to verify the authenticity of the request you receive to ensure that it is from our platform and has not been tampered with during transit.

CSV Columns

Column Description
Merchant ID

The Merchant ID associated with the transaction.
Example: 4f90ea634abd6

Processed Date

The date (dd/mm/yyyy) the transaction was processed.
Example: 11/04/2096

Processed Time

The time (hh:mm:ss) the transaction was processed.
Example: 15:03:32

Settled Date

The date (dd/mm/yyyy) the transaction will be settled to your settlement account. Example: 12/04/2096

Transaction ID

The EFT/PayID transaction ID.
Example: 52-1031d519-a67e-11ec-abd4-005056b209e0

Payment Source

The source or channel of the transaction.
Example: EFT

Amount

The transaction amount formatted to two decimal places.
Example: 10.00

Currency

The transaction currency.
Example: AUD

Status

The status of the transaction.
Example: approved

Fee

The fee associated with the transaction formatted to two decimal places.
Example 0.65

Incoming BSB

Your BSB that the customer paid to.
Example: 801457

Incoming Account Number

Your account number that the customer paid to.
Example: 1234567

Customer Account Name

The account name of the payment initiator.
Example: Will Smith

Customer BSB

The BSB of the payment initiator.
Example: 325647

Customer Account Number

The account number of the payment initiator.
Example: 5467898

Customer Account Reference

The reference the payment initiator used when submitting the transaction.
Example: ABCD1234

Customer Bank

The bank name of the payment initiator.
Example: CBA

PayID

The PayID associated with the Incoming BSB and Incoming Account Number from above. This will only be present if your account has been enabled for PayID.
Example: [email protected]

Customer Description

The description the payment initiator used when submitting the transaction. Data for this field will only be present if the transaction was sent to a PayID.
Example: This can potentially be a very long string 280 characters to be exact

BPAY Notification

This notification is triggered every hour and sends a ZIP compressed CSV file that contains a list of all cleared BPAY transactions at the present time.

A sample compressed BPAY Notify CSV can be found here

Headers

Header Description
Mw-Filehash

A sha256 hash of the compressed csv file that your notifyURL receives. This can be used as a method to verify that the file you receive from us has not been tampered with or become corrupt during transit.

Mw-Signature

A unique 25 character string prefixed with MW that is used to verify the Mw-Signaturehash.
Example: MW6253bdf46e05e9.33850753

Mw-Signaturehash

A sha256 hash of your API Passphrase, merchantUUID and Signature (from above) (see Signature Hash. This can be used to verify the authenticity of the request you receive to ensure that it is from our platform and has not been tampered with during transit.

CSV Columns

Column Description
Merchant ID

The Merchant ID associated with the transaction.
Example: 4f90ea634abd6

Processed Date

The date (dd/mm/yyyy) the transaction was processed.
Example: 11/04/2096

Processed Time

The time (hh:mm:ss) the transaction was processed.
Example: 15:03:32

Settled Date

The date (dd/mm/yyyy) the transaction will be settled to your settlement account. Example: 12/04/2096

Transaction ID

The BPAY transaction ID.
Example: 52-1031d519-a67e-11ec-abd4-005056b209e0

Payment Source

The source or channel of the transaction.
Example: BPAY

Amount

The transaction amount formatted to two decimal places.
Example: 10.00

Currency

The transaction currency.
Example: AUD

Status

The status of the transaction.
Example: approved

Fee

The fee associated with the transaction formatted to two decimal places.
Example 0.65

Biller Code

The 6 digit Biller Code associated with your account.
Example: 548789

CRN

The unique customer reference number input by the payment initiator when submitting the transaction. This should match the unique CRN that you generated for the customer when issuing them their bill.
Example: 55142467

Customer Bank

The bank name of the payment initiator.
Example: CBA

Chargeback Notification

This notification is triggered every day and sends a ZIP compressed CSV file that contains a list of all Chargeback transactions at the present time.

A sample compressed Chargeback Notify CSV can be found here

Headers

Header Description
Mw-Filehash

A sha256 hash of the compressed csv file that your notifyURL receives. This can be used as a method to verify that the file you receive from us has not been tampered with or become corrupt during transit.

Mw-Signature

A unique 25 character string prefixed with MW that is used to verify the Mw-Signaturehash.
Example: MW6253bdf46e05e9.33850753

Mw-Signaturehash

A sha256 hash of your API Passphrase, merchantUUID and Signature (from above) (see Signature Hash. This can be used to verify the authenticity of the request you receive to ensure that it is from our platform and has not been tampered with during transit.

CSV Columns

Column Description
Transaction ID

The transaction ID associated with the Chargeback.
Example: 52-1031d519-a67e-11ec-abd4-005056b209e0

Purchase Date

The date (mm/dd/yy) of the original purchase or captured transaction.
Example: 041996

Card Number

The masked card number represented by first 6 (BIN) xxx last 4 digits of the card number.
Example: 512345xxx1245

Microfilm Reference

Reference data for use by the Acquirer.
Example: microfilm625e27cab61d1

Customer Name

The name of the customer associated with the chargeback transaction.
Example: Will Rock

Customer Addresss

The address of the customer associated with the chargeback transaction.
Example: 45 Venture Street

Amount

The chargeback amount formatted to two decimal places.
Example: 10.00

Reason

The chargeback reason code and description. You can find a list of chargeback reason codes and their descriptions here.
Example: 11.3 - No Authorisation

Merchant ID

The Merchant ID associated with the transaction.
Example: 4f90ea634abd6