Westpac MTS Orders
The Westpac MTS Orders file is sent to process a batch of payments. The system responds with a Westpac MTS Rejects report.
File format
Fixed Width Legacy Format Card Payments Only Account Tokens Supported AUD Only Capture Pre-Auth Only
The Westpac MTS (Merchant Transmission Service) format is a legacy format. It may contain only card transactions. Use this format if your system already produces MTS files.
All files are plain text using UTF-8 character encoding. All records are separated by the CR LF end-of-line marker.
To upload a payment file in this format you must
- Send the parameter
format
withMTS
orMTS_TOKENS
. - Supports only transactions in AUD.
- Use only one supplier business code per batch header.
- In the card number field, use only all Card PANs for
MTS
or all account tokens forMTS_TOKENS
files.
The payment file has the following general structure:
- File header (one only per file)
- Batch header (per supplier business)
- Sale/Refund transaction (one or more in each batch)
- Batch trailer (one only per batch header)
- File trailer (one only per file)
Data types are listed as:
N
- numeric 0-9 only.A
- letters from the English alphabet including spaces.AN
- letters or numbers (alphanumeric) or spaces.S
- spaces only.
Unless otherwise noted, N
numeric fields are right-justified and padded with leading zeros and AN
alphanumeric fields are left-justified and padded with trailing spaces. Amounts are always expressed in cents, e.g. $125.94 is expressed as 00012594
(assuming the field has a length of 8).
File header
The file header must be the first record in the file.
No | Field Name | Position | Length | Data Type | Description |
---|---|---|---|---|---|
1 | Transaction Type | 1 | 1 | N |
Must be 1 to indicate file header. |
2 | Record Sequence | 2-7 | 6 | N |
Not used - set to any numeric value, e.g. 000000 . |
3 | Facility Link ID | 8-11 | 4 | N |
Not used - set to any numeric value, e.g. 000000 . |
4 | Originating PC ID | 12-14 | 3 | AN |
Transmitting PC ID (default is P01 ) |
5 | Creation Date | 15-22 | 8 | N |
Date the file was created in YYYYMMDD format. |
6 | Creation Sequence | 23-24 | 2 | N |
Creation Sequence beings at 01 and increments by 1 for each file created on Creation Date. |
7 | Posting Status | 25 | 1 | A |
O = Original Status |
8 | Filler | 26-80 | 55 | S |
Spaces |
Batch header
This record is used to group together data for a particular supplier business.
No | Field Name | Position | Length | Data Type | Description |
---|---|---|---|---|---|
1 | Transaction Type | 1 | 1 | N |
Must be 2 to indicate batch header. |
2 | Record Sequence | 2-7 | 6 | N |
Not used - set to any numeric value, e.g. 000000 . |
3 | Merchant Identifier | 8-15 | 8 | AN |
Supplier business code to process transactions in this batch. |
4 | Batch Value Date | 16-23 | 8 | N |
Must be the same as the date in the file header. |
5 | Batch Sequence Number | 24-25 | 2 | N |
Batch sequence beings at 01 and increments by 1 for each batch in the file. |
6 | Posting Status | 26 | 1 | A |
O = Original Status |
7 | Filler | 27-80 | 54 | S |
Spaces |
Sale/Refund transaction
Each batch contains one or more sale or refund transactions.
No | Field Name | Position | Length | Data Type | Description |
---|---|---|---|---|---|
1 | Transaction Type | 1 | 1 | N |
3 for sale, 4 for refund. |
2 | Record Sequence | 2-7 | 6 | N |
Not used - set to any numeric value, e.g. 000000 . |
3 | Merchant Identifier | 8-15 | 8 | AN |
Must be the same as the Merchant Identifier in the batch header. |
4 | Card Number or Account Token | 16-34 | 19 | N |
Card Number for MTS format. Do not include dashes or spaces between card number digits. Account Token for MTS_TOKENS format. |
5 | Transaction Date | 35-42 | 8 | N |
Must be the same as the Batch Value Date in the batch header. |
6 | Transaction Amount | 43-50 | 8 | N |
Transaction amount in cents, right justified with zero padding. For example, $125.94 is expressed as 00012594 . |
7 | Sale Type | 51 | 1 | A |
M - Mail Order T - Telephone order R - Recurring transaction. |
8 | POS Terminal Indicator | 52 | 1 | S |
Not used - set a single space. |
9 | Authorisation Code | 53-58 | 6 | AN |
If capturing a previous pre-auth transaction, this is the 6 character authorisation code from that pre-auth transaction. Otherwise, leave blank. |
10 | Merchant Reference Number | 59-64 | 6 | AN |
Your first reference number for this transaction. Populate this field with your system's identifier for this transaciton to allow tracing. |
11 | Card Expiry Date | 65-70 | 6 | N |
The card expiry date in MMYYYY format. |
12 | Merchant Secondary Reference Number | 71-78 | 8 | AN |
Your second reference number for this transaction. Leave blank if not required. |
13 | Filler | 79-80 | 2 | S |
Spaces |
Note:
- The Merchant Reference Number and Merchant Secondary Reference Number are shown as concatenated in QuickStream. For example, if the Merchant Reference Number field is
abc1
and the Merchant Secondary Reference Number is234xyz
, the Payment Reference Number field will showabc1234xyz
. - The Sale Type of
R
for Recurring transaction (i.e. Mastercard or Visa Recurring) should be set if a transaction is a recurring transaction for which you hold an agreement with the cardholder. In addition, for Visa Recurring, the first transaction has to be authorised with a valid card expiry date. If the transaction is a one-off transaction, you must set the Sale Type to one of the other values (i.e.M
orT
). Under no circumstances may you flag a one-off transaction as Recurring. - Refunds are a potential avenue for fraud. Check your merchant agreement for information about performing refunds.
Batch trailer
Each batch must have a trailer record following the last transaction in the batch.
No | Field Name | Position | Length | Data Type | Description |
---|---|---|---|---|---|
1 | Transaction Type | 1 | 1 | N |
Must be 5 to indicate batch trailer. |
2 | Record Sequence | 2-7 | 6 | N |
Not used - set to any numeric value, e.g. 000000 . |
3 | Merchant Identifier | 8-15 | 8 | AN |
Must be the same as the merchant ID in the batch header. |
4 | Batch Transaction Count | 16-21 | 6 | N |
Number of transactions in the batch. |
5 | Batch Transaction Total Amount | 22-31 | 10 | N |
Sum of batch sales transaction amounts minus sum of batch refund transaction amounts. |
6 | Batch Amount Sign Indicator | 32 | 1 | A |
C for credit if the above total is positive. D for debit if the above total is negative. |
7 | Sales Count | 33-37 | 5 | N |
Number of sale transactions in this batch. |
8 | Sales Total Amount | 38-47 | 10 | N |
Total amount for all sale transactions in this batch. |
9 | Refunds Count | 48-52 | 5 | N |
Number of refund transactions in this batch. |
10 | Refunds Total Amount | 53-62 | 10 | N |
Total amount for all refund transactions in this batch. |
11 | Filler | 63-80 | 18 | S |
Spaces |
File trailer
The file trailer record must be the last record in the file.
No | Field Name | Position | Length | Data Type | Description |
---|---|---|---|---|---|
1 | Transaction Type | 1 | 1 | N |
Must be 6 to indicate file trailer. |
2 | Record Sequence | 2-7 | 6 | N |
Not used - set to any numeric value, e.g. 000000 . |
3 | Facility Link ID | 8-11 | 4 | N |
Same as file header. |
4 | Batch Count | 12-15 | 4 | N |
Number of batches present in the file. |
5 | Transaction Count | 16-22 | 7 | N |
Total number of transactions in the file. |
6 | Transaction Total Amount | 23-33 | 11 | N |
Sum of all sales transaction amounts minus sum of all refund transaction amounts. |
7 | File Amount Sign Indicator | 34 | 1 | A |
C for credit if the above total is positive. D for debit if the above total is negative. |
8 | Sales Count | 35-40 | 6 | N |
Number of sale transactions in this file. |
9 | Sales Total Amount | 41-51 | 11 | N |
Total amount for all sale transactions in this file. |
10 | Refunds Count | 52-57 | 6 | N |
Number of refund transactions in this file. |
11 | Refunds Total Amount | 58-68 | 6 | N |
Total amount for all refund transactions in this file. |
12 | Filler | 69-80 | 12 | S |
Spaces |