Skip to main content


QuickBatch allows you to process card, bank account and PayTo payments by uploading a payment file.

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.

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.

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.

Westpac Privacy Statement

Privacy Statement (for individuals whose personal information may be collected - in this clause referred to as "you"). All personal information we collect about you is collected, used and disclosed by us in accordance with our Privacy Statement which is available at Privacy Statement or by calling us through your relationship manager or Westpac representative. Our Privacy Statement also provides information about how you can access and correct your personal information and make a complaint. You do not have to provide us with any personal information but, if you don't, we may not be able to process an application or a request for a product or service.