CC Westpac Batch Transaction UML

Represents a batch transaction as it is defined in batch processing specification of Westpac.

Account number of the user.

The amount in cents. For example, a refund for $3.00 will be included as “0000000300”.

If this transaction is completing a previous pre-authorisation, provide the authorisation ID here. Otherwise leave this field blank.

The transaction number provided with the original payment.

For credit cards this field will be populated with the card scheme.

For example:

• “DC” (Diners Club)
• “AX” (Amex)
• “VI” (Visa)
• “MC” (MasterCard)
• “JC” (Japan Credit Bureau)
• Blank – any unknown card scheme or invalid card

For bank accounts this field will be blank.

Reference to the entity that represents CC Wespac batch information.

Reference to the entity that represents real-time financial transaction.

Customer's account name.

Customer unique identifier.

The Electronic Commerce Indicator (ECI) is used by acquirers / issuers to determine the type of transaction being processed. The ECI value represents the source of the transaction request.

Accepted values include:

• CCT – Call Centre Transaction
• SSL – eCommerce Channel Encrypted Transaction

Note: Relevant to credit card refunds. It is an optional field and should only be populated if instructed by your implementation manager.

Expiration date of a credit card.

Identifier of the object used for references; auto-incremented integer value.

Code of Merchant Account to which instance of this object is attributed to. Depending on the context, Merchant Account Code field may contain either Merchant Code or Merchant Account Code.
The field is primarily used for data partitioning and data management, to make it easy to determine the ownership of a record within the database.

For credit cards, this field is blank.

For bank accounts:

• The DEEDS Response file will leave this field blank.
• The DERPS Response file will populate this field with “DH”.

For credit cards:

• If the transaction was rejected, this field will be blank.
• If the transaction was successful, this field will contain the Qvalent receipt number.

For bank accounts:

In the DEEDS Response file

o If the transaction was rejected, this field will be blank.
o If the transaction wasn’t rejected, this field will contain the Qvalent receipt number. * In the DERPS Response file, this field will contain the Qvalent receipt number.

The transaction response code.

Human readable response message explaining the response code.

The single digit summary code.

Unique identifier for the transaction. It must be unique across all transactions. It cannot be the same value as any other refund or payment from a previous file.