Transaction Details Field Reference
The Transaction Details view displays every stage and data component involved in processing a transaction. This glossary outlines each section of the transaction lifecycle and each data category shown on the Transaction Detail page.
Transaction Lifecycle Stages
The Transaction Lifecycle shows each step a transaction goes through as it is processed. These stages appear in the Transaction Details timeline and include timestamps, duration, and activity counts to help merchants understand how the transaction progressed.
Lifecycle Stage Summary
| Stage | Description |
|---|---|
| Validation | Confirms that the transaction request includes the required information and is properly formatted before processing continues. |
| Enrichment | Adds supplemental data used for screening and authorization, such as card metadata or additional transaction details. |
| Screening | Applies fraud and risk checks, including rules configured for the merchant, to determine whether the transaction should proceed. |
| Authorization | Sends the transaction to the issuing bank or processor for approval. Returns results such as approval/decline status, AVS/CVV responses, and authorization codes. |
| Finalization | Completes the transaction flow after authorization and prepares the transaction for settlement or follow-up actions. |
| Capture | For two-step processing, this stage represents the capture of previously authorized funds. Some merchants or processors may always auto-capture immediately, while others perform capture later. |
Data Section Descriptions
Below are descriptions of each data section shown in the Transaction Details page.
Card Data
The Card Data section contains detailed information about the payment card used in the transaction, including card attributes, issuer details, and billing contact information.
Card Information Fields
| Field | Description |
|---|---|
| Card Number | The card account number. |
| Expiration Date | The expiration date of the card. |
| Name On Card | The name on the card. |
| Entry Mode | The entry mode of the card. |
| Cv Presence | The CV (Card Verification) presence status. |
| IIN | The IIN (Issuer Identification Number) of the card. |
| ARQC | The ARQC (Authorization Request Cryptogram) of the card. |
| Last4Card Number | The last 4 digits of the card number. |
| Expiration Month | The expiration month of the card. |
| Expiration Year | The expiration year of the card. |
| Bin Data | The BIN (Bank Identification Number) data associated with the card. |
| Cvv | The CVV (Card Verification Value) of the card. |
| Pin | The PIN (Personal Identification Number) of the card. |
| Key Serial Number | The Key Serial Number associated with the card. |
| Emv Data | The EMV (Europay, Mastercard, and Visa) data associated with the card. |
| Track Data | The track data of the card. |
| Encrypted Track1Data | The encrypted track 1 data of the card. |
| Encrypted Track2Data | The encrypted track 2 data of the card. |
| Encrypted Track3Data | The encrypted track 3 data of the card. |
| Billing Address | The billing address associated with the card. Optional by default (no nested validation enforced). |
| Phone | The phone number associated with the card. |
| The email address associated with the card. |
BIN / Issuer Details Fields
| Field | Description |
|---|---|
| Bin | The Bank Identification Number (BIN). |
| Brand | The brand associated with the BIN. |
| Type | The type of the card associated with the BIN. |
| Category | The category of the card associated with the BIN. |
| Pan Length | The length of the Primary Account Number (PAN) associated with the BIN. |
| Issued Entity | The entity type to which the card is issued. |
| Organization | The organization associated with the BIN. |
| Country Number | The ISO 3166-1 numeric country code associated with the BIN. |
| Issuer Phone | The phone number of the issuer associated with the BIN. |
| Issuer Website | The website of the issuer associated with the BIN. |
| Regulated | Value indicating whether the BIN is regulated. |
| Commercial | Value indicating whether the BIN is commercial. |
| Healthcare | Value indicating whether the BIN is healthcare-related. |
| Country | The country associated with the BIN. |
| Country Code A2 | The ISO 3166-1 alpha-2 country code associated with the BIN. |
Billing Contact Fields
| Field | Description |
|---|---|
| Address1 | The first line of the billing contact’s street address. |
| Address2 | The second line of the billing contact’s street address, if applicable. |
| City | The billing contact’s city. |
| State | The billing contact’s state or province. |
| Zip | The billing contact’s postal or ZIP code. |
| Country | The billing contact’s country. |
| Phone | The billing contact’s phone number. |
| The billing contact’s email address. |
Device Data
The Device Data section shows details about the payment device used for the transaction. This includes the SDK version, device identifier, battery status, and whether any device data is encrypted.
Device Data Fields
| Field | Description |
|---|---|
| Sdk Version | The version of the SDK used by the device. |
| Serial Number | The serial number of the device. |
| Battery Level | The battery level of the device. The value is nullable to accommodate devices that may not report battery level. |
| Is Encrypted | Value indicating whether the device data is encrypted. |
| Encryption Type | The type of encryption used for the device data, if applicable. |
FSA
The FSA (Flexible Spending Account) section displays healthcare-related spending categories associated with the transaction. These fields break down amounts eligible under specific FSA categories such as medical, dental, vision, prescription, and transit benefits. It also indicates whether partial authorization is supported for FSA transactions.
FSA Fields
| Field | Description |
|---|---|
| QHP Amount | The Qualified Health Plan (QHP) amount for the FSA. |
| Rx Amount | The prescription (Rx) amount for the FSA. |
| Vision Amount | The vision care amount for the FSA. |
| Dental Amount | The dental care amount for the FSA. |
| Clinical Amount | The clinical care amount for the FSA. |
| Copay Amount | The copay amount for the FSA. |
| Transit Amount | The transit amount for the FSA. |
| Partial Auth Support | Indicates whether partial authorization is supported for this FSA. |
Soft Descriptors
The Soft Descriptors section contains optional alternate merchant information that can appear on the cardholder’s statement or be used by the issuer for additional context. This includes an alternate merchant name and an alternate merchant contact address.
Alternate Merchant Name Fields
The Alternate Merchant Name is an optional, more customer-friendly label for the merchant that may appear on the cardholder statement instead of (or in addition to) the primary merchant name.
Alternate Merchant Contact
The Alternate Merchant Contact subsection captures an alternate address and contact details for the merchant. This information can be used by issuers or cardholders to identify or contact the merchant.
| Field | Description |
|---|---|
| Address1 | First line of the alternate merchant address (for example, street address). |
| Address2 | Second line of the alternate merchant address (for example, apartment, suite, unit, or building). |
| City | City for the alternate merchant address. |
| State | State or region for the alternate merchant address. |
| Zip | ZIP code for the alternate merchant address. |
| Country | Country for the alternate merchant address (defaults to “USA” if not otherwise specified). |
| Province | Province for the alternate merchant address, if applicable. |
| Postal Code | Postal code for the alternate merchant address (used where postal code differs from ZIP code). |
| Id | Unique identifier for this alternate merchant address record. |
| Is Mailing | Indicates whether this address is used as a mailing address. |
| Is Default | Indicates whether this address is the default alternate merchant address. |
Register
The Register section identifies the specific source that submitted the transaction. Registers allow merchants to differentiate transactions originating from different systems—such as POS terminals, integrations, or internal applications—when multiple sources operate under the same merchant account. This information is useful for reporting, troubleshooting, and understanding transaction flow across various entry points.
Register Fields
| Field | Description |
|---|---|
| Id | The unique system-generated identifier of the register associated with the transaction. |
| Name | The display name of the register. |
Invoice Data
The Invoice Data section captures the financial breakdown of the transaction along with the shipping address, when applicable. This information is used for authorization, settlement, and reporting, and helps clearly separate the base purchase amount from fees, taxes, and other charges.
Request Amounts Fields
| Field | Description |
|---|---|
| Base | The base amount of the transaction (for example, the cost of goods or services before tax, tips, and fees). This value is required and cannot be negative. |
| Tip | The tip or gratuity amount for the transaction. This value cannot be negative. |
| Tax | The tax amount applied to the transaction. This value cannot be negative. |
| Shipping | The shipping amount for the transaction (for example, delivery or freight charges). This value cannot be negative. |
| Convenience | The convenience fee amount added to the transaction, if applicable. This value cannot be negative. |
| Convenience Percentage | The convenience fee expressed as a percentage of the transaction amount, if applicable. This value cannot be negative. |
| Surcharge | The surcharge amount applied to the transaction (for example, a card surcharge, where legally permitted). This value cannot be negative. |
| Cashback | The cashback amount requested as part of the transaction (typically for debit transactions with cashback). This value cannot be negative. |
| Total | The total amount of the transaction. This is calculated based on the sum of the base amount, tip, tax, shipping, and convenience (and may include other configured components). The value must be positive and is required. |
Shipping Address Fields
| Field | Description |
|---|---|
| Address1 | First line of the shipping address (for example, street address). |
| Address2 | Second line of the shipping address (for example, apartment, suite, unit, building, or floor). |
| City | City for the shipping address. |
| State | State or region for the shipping address. |
| Zip | ZIP code for the shipping address. |
| Country | Country for the shipping address. Defaults to “USA” if not otherwise specified. |
| Province | Province for the shipping address, if applicable (often used outside the U.S. or in certain regional formats). |
| Postal Code | Postal code for the shipping address (used where postal code differs from or supplements the ZIP code). |
| Id | Unique identifier for this shipping address record. |
| Is Mailing | Indicates whether this address is used as a mailing address (for example, for statements or correspondence). |
| Is Default | Indicates whether this address is the default shipping address for this context or entity. |
Original Transaction
The Original Transaction section is displayed when the current transaction is related to, or derived from, a prior transaction. This typically appears for actions such as refunds, voids, reversals, or captures against a previously authorized transaction. The field provides a reference link to the original transaction so that reporting, reconciliation, and downstream payment processor flows remain consistent.
Original Transaction Fields
| Field | Description |
|---|---|
| Original Transaction | A reference identifier that links this transaction to the original one. This may be the original transaction ID, authorization ID, or another gateway-specific reference used when the operation is a refund, void, reversal, or capture. |
Signature Data
The Signature Data section contains information captured when a cardholder provides a signature as part of the transaction process. This may include signatures collected on supported payment devices, touchscreen-based POS interfaces, or other customer-facing input hardware. The fields in this section indicate the type of signature captured and the raw signature data, when available.
Signature Data Fields
| Field | Description |
|---|---|
| Signature Type | The type or identifier of the signature data captured. |
| Data | The signature image or encoded signature content. |
Level2 Data
The Level2 Data section contains enhanced transaction information used primarily for corporate, purchasing, and B2B card transactions. Providing Level 2 data can help merchants qualify for better interchange rates on eligible card types. These fields represent supplemental commercial details such as purchase order information, merchant location identifiers, and transaction timestamps.
Level2 Data Fields
| Field | Description |
|---|---|
| Po Number | The purchase order (PO) number associated with the transaction. Used for commercial and purchasing card flows. |
| Transaction Date | The date and time the transaction was processed. |
| Merchant Zip | The merchant’s ZIP code as submitted for Level 2 qualification. |
Level3 Data
The Level3 Data section provides enhanced commercial transaction details used for line-item and freight-related interchange qualification. Level 3 data is typically submitted for purchasing cards, corporate cards, and B2B transactions where additional shipping and document-level fields help improve issuer transparency and can lower interchange costs for eligible merchants.
Level3 Data Fields
| Field | Description |
|---|---|
| Ship From Zip | The ZIP code of the location from which goods were shipped. Used for freight, delivery, and Level 3 qualification. |
| Destination Zip | The ZIP code of the customer’s destination address for shipped goods. |
| Invoice Number | The invoice identifier associated with the transaction, typically included on B2B billing or procurement documents. |
| Order Number | The merchant’s internal order identifier for the transaction, often used to reconcile purchases with line-item detail. |
Response Data
The Response Data section displays information returned from the gateway or processor after the transaction is sent for authorization. It includes the monetary amounts used by the issuer (such as balances and approved amounts) as well as detailed processor and network response metadata (result codes, network identifiers, and other authorization details).
Response Amounts Fields
| Field | Description |
|---|---|
| Beginning Balance | The beginning balance of the account at the time the transaction was processed. |
| Available Balance | The available balance on the account after considering holds and pending authorizations. |
| Cashback | The cashback amount for the transaction. |
| Requested | The requested amount for the transaction. |
| Preauthorized | The preauthorized amount for the transaction. |
| Open To Buy | The open to buy amount (the amount remaining spending capacity on the account after this transaction, as reported by the issuer). |
| Ewic Discount | The EWIC (Electronic Women, Infants, and Children) discount amount applied to the transaction. |
| Transaction Fee | The fee amount associated with processing the transaction. |
| Approved | The amount that was actually approved by the issuer or processor. |
| Balance Due | The remaining balance due after the transaction is applied. |
Processor Response Detail Fields
| Field | Description |
|---|---|
| Card Validation Data | The card validation associated with the transaction. |
| Result Code | The result code of the transaction. |
| Result Message | The result message of the transaction. |
| Debit Trace Number | The debit trace or reference number associated with a debit transaction. |
| Result Detail | Additional text or structured details about the transaction result. |
| Authorization Code | The authorization code returned by the issuer or network for an approved transaction. |
| Response Date | The date and time when the processor response was received. |
| Authorizing Network Id | The identifier of the authorizing network that processed the transaction. |
| Authorizing Network Name | The name of the authorizing network. |
| Routing Indicator | The routing indicator for a transaction. |
| Customer Signature Recommended | Indicates whether the processor recommends capturing a customer signature for this transaction. |
| Processor Response Detail | Any additional detailed response details returned from the processor. |
| Association Response Code | The card association–specific response code (ISO or network code indicating approval/decline reason). |
| Response Category Code | A higher-level category or grouping for the response (for example, approved, soft decline, hard decline). |
| Card Indicator | The card indicator for a transaction. |
| Detailed Product Id | The detailed product id associated with the transaction. |
| Client Ip Address | The client or terminal IP address associated with the transaction at the time of processing. |
| Amounts | The response amounts associated with the transaction. |
Settle Data
The Settle Data section contains information produced once a transaction has been successfully settled (captured and submitted for funding). Settlement is the final stage of the payment lifecycle when the transaction is included in a batch and sent to the acquirer for deposit. If the transaction has not yet settled—or if it is an authorization-only, void, or declined transaction—this section may appear empty.
Settle Data Fields
| Field | Description |
|---|---|
| Settle Data | Settlement information associated with the transaction. This may include settlement date/time, settled amount, batch or deposit identifiers, acquirer settlement references, or other funding-related metadata. This section will be populated only for transactions that have reached the settlement stage. |
Updated 4 months ago
