WorldPay Secure Net Auth Retail Transaction UML

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

Account number of the customer.

Type of customer's account.

Remaining balance on a stored value account.

Indicates whether it is permissible to authorize less than the total balance available on a prepaid card.

Amount of the transaction.

Authorization approval code.

The total authorized amount for the authorization request. If the Partial authorization flag is enabled, this amount may be less than the requested amount.

Address verification code. Refer to the specification of the provider for additional information.

Address verification result.

Possible values:

• MATCH
• NOT_MATCHED
• NOT CHECKED

Base64-encoded image of the back of the check in BMP/JPG/PNG format; optional.

Card security code result.

Possible values:

• 0 - CVV/CID not provided
• M - Match
• N - No match
• P - Not processed
• S - Data not present
• U - Issuer unable to process request
• Y - Card code matches (Amex only)

Card security code result.

Possible values:

• MATCH
• NOT_MATCH
• NOT_CHECKED

Last 4 digits of the credit card number.
Format: XXXXXXXXXXXX 3456.

Typically used as an optional field for PIN Debit processing. The value of cashBackAmount indicates the amount in cash to be given back to the customer during card processing.

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

Check number.

Type of check payment being made.

City where address is located.

Company name.

Country code. US is set by default.

Identifies the credit card type.

Possible values:

• VISA
• VISAFLEET
• MASTERCARD
• MASTERCARDFLEET
• AMEX
• DISCOVER

Current installment number. Required if transactionCategory is set as installment.

Unique customer identifier.

Card security code.

Developer ID of integrator assigned by SecureNet.

Duty amount included in the transaction.

Email address used to send notifications.

Expiration date of the credit card.

First name of the account holder.

Freight amount included in the transaction.

Base64-encoded image of the front of the check in BMP/JPG/PNG format; optional.

Amount of the tip.

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

Industry-specific data for ecommerce and moto transactions.

For eCommerce transactions:

• P - Physical goods
• D - Digital goods

For Moto transactions:

• 1 - Single purchase transaction (AVS is required)
• 2 - Recurring billing transaction (do not submit AVS)
• 3 - Installment transaction

Unaltered KSN Number from PIN pad. (Debit only.)

Last name of the account holder.

Indicates whether the credit card is level 2 eligible.

Indicates whether the credit card is level 3 eligible.

Street address of the account holder.

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.

Text description of the response.

Transaction method.

Possible values:

• CC - Credit Card
• DB - Debit
• ECHECK - Electronic Check
• PD - Pinless Debit
• SV - Stored Value

Identifier for the network that returned the transaction response.

Notes (any additional information) about the record.

Credit card account number.

Date of the transaction.

Client-generated unique ID for each transaction, used as a way to prevent the processing of duplicate transactions. The orderId must be unique to the merchant's SecureNet ID, but uniqueness is only evaluated for approved transactions and only for the last 30 days. If a transaction is declined, the corresponding orderId may be used again.

The orderId is limited to 25 characters; e.g., “CUSTOMERID MMddyyyyHHmmss”.

Credit card or check type. Valid values can be found in the specification of the provider.

Transaction method.

Possible values:

• CHECK
• CREDIT_CARD
• DEBIT_CARD
• FLEET_CARD
• UNKNOWN

Phone number used to discuss any processing issues.

PINblock obtained from the PIN pad. (Debit only.)

Purchase order number associated with the transaction.

Date and time of the sent request.

Type of the sent request.

Response code for the method call. A value of 1 indicates the customer was created.

Date and time of the transaction response.

Transaction approval status.

Result of the method call.

Lane number at which the transaction was completed in a retail environment.

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

Routing number (expiration date) of the customer's bank account.

Secure key used in conjunction with Secure Net ID to access the processor's gateway.

SecureNet ID assigned by WorldPay.

Server number (used in restaurant transactions).

Amount of the transaction.

Identifier for the batch that the transaction belongs to.

Date and time when the transaction was settled.

State where address is located. Valid values are 2-character state abbreviations.

Tax status of the transaction.

Customer result.

Surcharge amount to be added to the transaction.

Tax amount for the transaction.

Total number of installments. Required if transactionCategory is set as installment.

Data that has been read from the card's magnetic stripe.

Indicates how checks for duplicate transactions should behave. Duplicates are evaluated on the basis of amount, card number, and order ID; these evaluation criteria can be extended to also include customer ID, invoice number, or a user-defined field.

Possible values:
0 - No duplicate check
1 - Exception code is returned in case of duplicate
2 - Previously existing transaction is returned in case of duplicate
3 - Check is performed as above but without using order ID, and exception code is returned in case of duplicate

The transactionDuplicateCheckIndicator parameter must be enabled in the Virtual Terminal under Tools->Duplicate Transactions. Duplicates are checked only for approved transactions.

Transaction ID of the completed payment.

Transaction ID in the response to the transaction.

Type of the transaction.

Type of transaction.

Possible values:

• SINGLE_PURCHASE
• RECURRING
• INSTALLMENT

Type of goods that are being purchased.

Possible values:

• DIGITAL
• PHYSICAL

Type of check verification that was used for the transaction.

Version number of the integrator's application.

5- or 9-digit ZIP (or postal) code of the address.