Ezidebit Chargeback Transaction UML

Represents chargeback transaction as it is defined in Ezidebit's chargeback specification.

The full text description for the reason that the payment was unsuccessful (dishonoured)

Where a payment is successful or still pending an outcome, this value will be blank.

The original receipt number supplied by the banking system for real-time credit cards or BPAY payments

NB - ALL real time credit card payments are assigned a BankReceiptID when the transaction is attempted. The presence of a BankReceiptID does NOT identify the payment as being successful. You must check the PaymentStatus to determine the outcome of the transaction.

Return code of the bank that processed the transaction.

Referece to the entity that represents information about chargeback transaction.

Name of the customer.

The date that is wished for the payment to be deducted from customer's bank account or credit card.

Identification number of the customer, used for references. Provided by EziDebit.

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

The Ezidebit Tax Invoice number that the fees for this payment were charged on. The Invoice number is also used as a batch identifier for transactions that were settled to the client.

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.

Amount of the processed payment.

Identifier for the payment within Ezidebit's own payment systems.

Method used to make the payment.

The client side element name that is capturing a payment reference number. This may be a hidden field that server has already generated.

The source channel by which the payment was made.

Status indicating the state of the payment within the Ezidebit system.

Specific data included in the record.

The original amount that was scheduled to be deducted from the customers payment method.

NB - This figure may differ from the Payment Amount if Ezidebit has applied transaction, SMS or setup fees to the Customer.

The date that the payment was settled to the client (for successful transactions) or the date that Ezidebit was notified that the payment was unsuccessful (for dishonoured transactions).

This value will remain blank until such point as the payment is dishonoured in the Ezidebit system or is settled to the client's bank account.

The total amount of fees paid to Ezidebit by the client (business) for processing this transaction.

The total amount of fees paid to Ezidebit by the customer for processing this transaction.

Actual time of the transaction processing.

A secondary unique reference for the customer.

Where system based identifiers (YourSystemReference) can be complex numbers, this is designed to be a simpler, human-friendly number. You may use a GUID to create the system-to-system link with YourSystemReference, and choose to include a membership ID, or such in this field.

If no value is supplied for this field it will default to 'LastnameFirstnameYYYYmmDDhhMM'.

Unique system identifier for the customer (e.g. GUID or your primary key). You can use this value to identify your customer in the Ezidebit system.