Skip to main content


QuickBatch allows you to process card and bank account payments by uploading a payment file. The payment file contains full payment account details or Account Tokens, reference numbers and the payment amount.

How it works

  1. Your accounting system generates a payment file.
  2. Using QuickStream, you upload the file for processing.
  3. When processing is complete, you download the transaction report.
  4. You receive a bulk settlement for your account for approved transactions.

File formats

You can process payments by uploading a file in one of these formats:

Each format has a corresponding transaction report which you can download:

Uploading files

To fully automate payment file processing, use the QuickStream REST API or iLink.

You may also upload a payment file manually, via QuickStream Portal or iLink.

Viewing payment file status

To view the status of a payment file use the QuickStream REST API or find your payment file and view the details in QuickStream Portal.

Transaction settlement

See Transaction processing and settlement.


QuickStream will not apply surcharges to transactions in payment files. If you wish to surcharge, add the surcharge amount to the payment amount in your payment file. You may automate the calculation of surcharges based on your QuickStream facility:

  1. Using the cardType and cardScheme properties in the QuickStream REST API card response model once you tokenise or take a payment using a card account.
  2. Using the Query card surcharge API if you have the PAN.


To reduce your PCI-DSS compliance scope, you can instead store payment account details using QuickVault. Payments can be processed by uploading a payment file containing the account token, reference number and amount.

See Register account using the QuickStream REST API and QuickVault for more.

Suggested test plan

  • Sending payment files
  • Retrieving your transaction report
  • Uploading the transaction report into your system
  • Approved payments
  • Declined payments
  • Approved refunds
  • Declined refunds
  • Duplicate payments
  • Invalid payment details (e.g. invalid card number, invalid BSB, invalid Account Token)
  • Upper limit and lower limit transaction amount tests

To support the testing process a test environment is provided. This environment is also known as the Support Environment or Support. It simulates the banking system, allowing you to test payments without affecting any live bank accounts.

See Testing for more.

Test account numbers

See Test account numbers.

Test URL's and IP addresses

See URLs and IP addresses.

Response codes

See Response codes.

Production lodgement and go-live

See Production lodgement.

Soft descriptors

See Soft descriptors for Aggregators and Staged digtal wallet operators.


The information contained in this publication is provided for learning purposes only and is subject to change. Revisions may be issued from time to time that encompass changes or additions to this module.

This is a guide only and it is not comprehensive. It does not impinge on or overrule any formal arrangement you may enter into with the Bank. The Bank and its officers shall not have any liability for any losses of any kind incurred in connection with any action, inaction or decision taken in reliance on the information herein or for any inaccuracies, errors or omissions. In this publication references to the "Bank" are to Westpac Banking Corporation ABN 33 007 457 141 and to any of its operating Divisions, including BankSA and St.George.