Paymentech Orbital Batch Transaction UML

Entity that represents a batch transaction as it is defined in Paymentech's batch processing specification.

Amex Purchasing Card Data – Transaction Advice
Addendum #1
The TAA Record is used to further identify the purchase that is associated with the charge to the cardholder. It is also used in Purchasing / Procurement card transactions to provide specific details about the transaction to the cardholder for tracking purposes. TAA’s should be as concise as possible. A TAA of “Merchandise” for example, would not be acceptable.

Amex Purchasing Card Data – Transaction Advice
Addendum #2

Amex Purchasing Card Data – Transaction Advice
Addendum #3

Amex Purchasing Card Data – Transaction Advice
Addendum #4

Defines the amount of the transaction

Current status of the approval.

Authorization code of the approved, original, authorized transaction.

Street address for AVS verification of the client.

City for AVS verification of the client.

Country code associated with the cardholder's billing address.

Name of the client for AVS verification.

Phone number associated with the cardholder's billing address.

Response code result of the client's AVS verification.

State code for AVS verification of the client.

ZIP (or postal) code for AVS verification of the client.

Batch request number

Biller Reference Number [PINLess Debit Only] Reference Number the Biller (merchant) uses on their system to identify this customer

Defines the Card Type / Brand for the Transaction

Account number.

Expiration Date of the credit card.

Reference to the entity that represents PaymenTech credit card batch information.

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

Free form comments:
Merchant can fill in this field and the info will be stored with the transaction details.

Email associated with the cardholder.

Reference number of the customer.

Authentication method assigned to electronic check processing.

Type of the bank account assigned to electronic check processing.

Direct debit check account assigned to electronic check processing.

Realtime account assigned to electronic check processing.

Delivery method assigned to electronic check processing.

AVS response code of the host.

Response code of the host.

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

Industry type - we use value MO or other, provided by provider

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.

Merchant Defined Order Number:
Field defined and supplied by the auth originator, and echoed back in response.

Amex Purchasing Card Data - Cardholder Ship To: Address
line 1

Amex Purchasing Card Data – Cardholder Ship TO: City

Amex Purchasing Card Data

Amex Purchasing Card Data – Cardholder Ship TO: State

Purchasing Card II Data - Shipping Destination Zip code for
the purchase:
- Required for Purchasing Card Level II Data
- For Zip Code + 4 please separate with ‘-‘.

Purchasing Card II Data - PO number from customer:
Required for Purchasing Card Level II Data

Current processing status.

Response Text message. If ProcStatus = 0, the ‘approvalStratus’ Message text is returned.

Response Code for transaction

Response Text message that describes the response code

Date / time the transaction was processed by gateway:
Format – ‘YYYYMMDDhh[24]miss’

Code used to determine how to process the transaction. Assigned by the gateway.

Soft descriptor assigned to merchant's city address in the provider profile.

Soft descriptor assigned to merchant's email address in the provider profile.

Soft descriptor assigned to merchant's name in the provider profile.

Soft descriptor assigned to merchant's phone number in the provider profile.

Soft descriptor assigned to merchant's URL in the provider profile.

Soft descriptor assigned to product description in the provider profile.

Shipping Tracking Reference Number.
Merchant can fill in this field and the info will be stored with the transaction details.

Purchasing Card II Data - Tax Amount for the purchase:
- Required for Purchasing Card Level II Data
- Implied decimal including those currencies that are a
zero exponent.

Type of the transaction.

Gateway transaction identifier assigned to unique components of the transactions adjusted more than one time.

Gateway transaction reference number which is required to adjust any transaction in the gateway, such as mark for capture or void.