Paymentech Auth Retail Transaction UML

Paymentech specific low-level representation of Retail Transaction produced by Forward Transformation Process within Authorization Process.
During Generation Process, Paymentech specific interchange message is generated from this object for authorization. Consequently, all fields of the object are mapped into message segments/elements.

The amount element defines the amount of the transaction. Supply the value in cents without a decimal point.

Approval Status:
0 – Decline
1 – Approved
2 – Message/System Error

Issuer approval Code: Unique transactional level code issuer uses to show each request was approved

Cardholder billing address line 1 (street).

Cardholder billing city.

Cardholder name.

Address verification request response

Cardholder billing state code.

Cardholder billing address ZIP (or postal) code.

Transaction Routing Definition.

Credit card brand.

Card Presence Identifier:

Y – Card Present/Swiped
N – Manually Entry

Credit card (or bank account) number of the customer.

Credit card verification number.

Card Security Presence Indicator
If a Card Verification Number for a manual entry transaction is attempted to be collected, this value needs to be passed for a Visa or Discover [and only those cards] transaction:
9 - Cardholder states data not available

Expiration date of the customer's credit card.

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

Any additional comments on the transaction.

Name of the customer.

Card verification number request response

An error message from a SOAP message can be carried inside a Fault element. If a Fault element is present, it will appear as a
child element of the Body element. A Fault element can only appear once in a SOAP message.
The Orbital Gateway SOAP Fault element has the following sub elements:
-faultcode
-faultstring

Fault Code - For errors generated by the Orbital Gateway, this value will be ‘SOAP-ENV:Server’.

Actual host address verification response code:
Exact address verification response sent by host authorization system [nonnormalized by the gateway].

Actual host card verification response code:
Exact card verification response sent by host authorization system [non-normalized by the gateway]

Actual host response code:
Exact response sent by host authorization system [non-normalized by the gateway].

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

Defines the Industry type of the transaction:
RE – Retail

The Date / time in which the PREVIOUS transaction using the same retryTrace value was processed by gateway:
Format – ‘YYYYMMDDhh[24]miss’

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.

Gateway merchant account number assigned by Chase Paymentech

Password used for Chase Paymentech Orbital payment gateway connection.

Username used for Chase Paymentech Orbital payment gateway connection.

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

Indicates whether partial authorization occured.

Process Status:
The first data set that should be checked to determine the result of a request. It is the only element that is returned in all response scenarios. It identifies whether transactions have successfully passed all of the Gateway edit checks.
0 – Success
All other values constitute an error condition and will be returned in a SOAPFault.

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

Remaining balance of the credit card of the customer.

Response Code:
Normalized authorization response code issued by the PNS host system, which identifies an approval (‘00’) or the reason for a decline or error.
Value conditionally returned when procStatus = 0

Response Text message

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

Reference to the entity that represents a group of real-time transactions which must be settled together.

Defines the number of times a Transaction Result has been returned:
0 - First Response [unique retryTrace]
1 or Greater means the Orbital Gateway has processed this request previously and is echoing back the response. The number represents the number of requests processed by the Gateway with the same retryTrace number.

Defines the Trace Number used for Retry Logic.

The Orbital Gateway offers functionality, referred to as “Retry Logic”, which allows a customer to retry a transaction without
duplicating the original request.
The result is any Client properly utilizing Retry Logic can reprocess transactions with an unknown result without:
• Risk of double authorizing a transaction against a cardholder’s available balance.
• Prevent duplicate [or more] settlement items.

Allowed number of reversal retries.

Order shipping reference.

Amount of tax.

Tax indicator.

Merchant Terminal ID assigned by Chase Paymentech

Defines the transaction New Order Transaction Type:

AC – Authorization and Capture
R – Refund request

Gateway transaction index:
Will always return a ‘0’ value on original transaction and a ‘1’ on void responses.

Gateway transaction reference number:
A unique value for each transaction, which is required to Void any transaction