> ## Documentation Index
> Fetch the complete documentation index at: https://docs.m1amdocs.com/llms.txt
> Use this file to discover all available pages before exploring further.

# View Transaction Info

* Transactions can't be created in the Commerce Engine Portal rather only viewed. They hold all the relevant data of the request for funds sent to a payment processor. A full or partial refund can be issued for Captured Transactions.

1. To locate a specific Transaction, go to **Billing** > **Transactions**.

   The Transaction Query Filter appears.

2. Search according to relevant data in the key search fields, displayed with a light blue background. At least one key search field (with a blue background) must be used in order to search. Click **Apply**. For more details, see [Filtering Transactions in Commerce Engine](filterTransactions).

   A list of relevant Transactions appears.

   **Note:** If the search returns only one result, the details page opens immediately.

3. To view the relevant Transaction page, click the Transaction **ID** field.

   The specific Transaction page appears.

   <img src="https://mintcdn.com/amdocs-spbu/itXsdbmkLJUvOY0b/marketONE/Commerce_Engine_User_Guide/images/transactionExample.gif?s=e496bd833664f44cb16473974cd108a1" alt="Commerce Engine Transaction Page Example" width="979" height="892" data-path="marketONE/Commerce_Engine_User_Guide/images/transactionExample.gif" />

4. View and understand the Transaction data. Refer to the tables below for guidance regarding the fields.

5. For a transaction, you can issue a refund by clicking the [**Issue Refund**](transactionIssueRefund) button that appears on the **Actions** panel.

* **[Transaction Details Pane](transactionWorking#transaction-details-pane)**\
  The current Transaction status is displayed in the title bar of this pane.
* **[Transaction Refunds Pane](transactionWorking#transaction-refunds-pane)**\
  Refunds provide a way to reverse a charge, returning money to the customer. A refund can only be executed against an existing, successfully captured transaction. The pane lists all of the refunds issued for the Transaction up to the total Transaction amount.
* **[Transaction Account Pane](transactionWorking#transaction-account-pane)**\
  Customer Account information relevant for this transaction.
* **[Transaction Subscription Pane](transactionWorking#transaction-subscription-pane)**\
  The recurring subscription responsible for generating this Transaction. If a One-time purchase generated the transaction, this pane will not appear.
* **[Transaction Payment Methods Pane](transactionWorking#transaction-payment-methods-pane)**\
  Payment Method(s) for this Transaction. The payment method type is displayed in the bar at the top of the section.
* **[Transaction Items Pane](transactionWorking#transaction-items-pane)**\
  Transaction Items are the line items associated with the transaction. For a Purchase these are the products and billing plans.
* **[Transaction History Pane](transactionWorking#transaction-history-pane)**\
  This pane lists the transaction history, that is, the status of payments activity on the transaction.
* **[Transaction Activity History Pane](transactionWorking#transaction-activity-history-pane)**\
  This pane lists Commerce Engine or customer activity, such as email notifications or payments, related to the Transaction.
* **[Custom Data](transactionWorking#custom-data)**\
  Custom data lets you store Reseller (Service Provider)-specific data to Products, Rate Plans, Billing Plans, Subscriptions, Accounts, and Payment Methods as a pair of matched text strings, called name-value pairs. These name-value pairs can help you categorize and sort aspects of your objects. Use **Name** to define a category, and **Value** to define a specific item in that category. For example, you could use name-value pairs to track your sales teams. Define a name-value pair with Office as the **Name** and the city in which the office is located as the **Value**.

**Parent topic:**[Transactions](transactionAbout)

## Transaction Details Pane

The current Transaction status is displayed in the title bar of this pane.

| Field | Guidance |
| - | - |
| **Transaction ID** | Reseller-specified identifier for this Transaction object. |
| **Status** | The current Transaction status appears in the title bar of this pane. Possible statuses are: - **New**: The Transaction has been created, but not yet submitted for payment. - **Authorized**: Transaction was successfully authorized and is awaiting a capture call. - **Authorized for Validation**: Transaction was successfully validated (for example, by a \$1.00 authorization). - **Authorization Pending**: The transaction was created, but the customer has not completed the payment process. The customer has three hours to complete the transaction before it times out. If the transaction times out, Status remains Authorization Pending indefinitely. - **Authorized Pending**: The Transaction passed authorization with the payment processor and the capture of funds is pending. - **Auth Expired**: Transaction was Authorized, but no Capture was made within the payment processor’s authorization time frame and the authorization has expired. - **Captured**: The payment processor successfully captured the Transaction. - **Cancelled**: The Transaction was cancelled because of a hard or soft failure, or because the Reseller (Service Provider) chose not to capture the transaction, for example, based on a fraud screen result. - **Refunded**: The Transaction was successfully refunded, either fully or partially. - **Pending**: The transaction status is pending. - **Void**: Transaction previously classified as **Auth Expired** has been reversed. Voiding a transaction avoids Visa fees for Authorizations that are not captured. |
| **Last Status** | A transaction may go through multiple statuses and it gets updated as statuses change. This date will reflect the last time the status was changed. |
| **Amount** | Amount and currency symbol for this Transaction. |
| **Submitted** | Date and time at which the Transaction was initially submitted for processing. |
| **Account ID** | Email address of the subscriber associated with this Transaction. |
| **Subscription ID** | Your unique identifier for the subscription associated with this Transaction. |
| **Started** | Date on which the subscription started. |
| **Email** | Email address of the subscriber associated with this Transaction. |
| **Credit Card** | |
| **Billing Descriptor** | |
| **Division Number** | |
| **Processor Transaction ID** | The identifier assigned to the Transaction by the Payment Processor. In most cases, this is identical to the ID. In some cases due to format requirements of some payment processors, the ID is altered. |
| **AVS Code** | |
| **Billing Address** | |
| **Prev Bill Count** | |
| **Received Auth Code** | Response Code from the Payment processor for this transaction. |
| **CVN Code** | Response Code from the Payment processor for this transaction. |
| **Retry attempts for Transaction** | |
| **ID** | |
| **Amount** | |
| **Timestamp (UTC)** | |
| **Auth Code** | |
| **Description** | |
| **Type** | The response from the payment provider and the applicable action to take. Common responses are:- **Successful Approved**: The Payment Provider has accepted the transaction. - **Soft Fail**: A payment capture attempt has failed but may indicate that an additional attempt may succeed, such as when the customer has insufficient funds. The classification of the type of fail is performed according to the error code returned by the payment provider and follows industry standards and recommendations. - **Hard Fail**: A payment capture attempt has failed and indicates that additional attempts will subsequently fail, such as when the account has been terminated. The classification of the type of fail is performed according to the error code returned by the payment provider. Hard fails are not resubmitted for capture. |
| **Status** | The type of transaction whether **One time** or **Subscription** (recurring) Transaction. |
| **Force Deposit** | The Amount and currency type successfully refunded by this transaction. |
| **Parent topic:**[View Transaction Info](transactionWorking) | |

## Transaction Refunds Pane

Refunds provide a way to reverse a charge, returning money to the customer. A refund can only be executed against an existing, successfully captured transaction. The pane lists all of the refunds issued for the Transaction up to the total Transaction amount.

| Field | Guidance | Relevancy |
| - | - | - |
| **Created Date** | Date the refund was created. | Automatic |
| **Amount** | The refunded amount and currency as represented by the national flag. | Required |
| **Includes Tax** | An indication whether the refund includes Tax or not. | Required |
| **Status** | Status of the Refund. When the batch refund job completes, the status will show Complete. | Automatic |
| **Distribution** | What kind of communication was sent. | Optional |
| **Note** | Notes made by the Customer Service Rep when issuing the refund. This is the reason for issuing the refund. | Optional |

**Parent topic:**[View Transaction Info](transactionWorking)

## Transaction Account Pane

Customer Account information relevant for this transaction.

| Field | Guidance | Relevancy |
| - | - | - |
| **ID** | The customer's unique account ID. Click the ID to access the associated account page. | Required |
| **Name** | The Customer's full name on the account. | Required |
| **Parent** | The Parent account linked to the displayed child account. Appears only when relevant. | Optional |
| **Email** | The email address associated with the customer account. | Optional |
| **Shipping Address** | Shipping address for the account. |   |

**Parent topic:**[View Transaction Info](transactionWorking)

## Transaction Subscription Pane

The recurring subscription responsible for generating this Transaction. If a One-time purchase generated the transaction, this pane will not appear.

| Field | Guidance | Relevancy |
| - | - | - |
| **ID** | The unique identifier for the Subscription. Click the **Subscription ID** to access the relevant Subscription page. | Required |
| **Subscription Cycle** | Current Billing Cycle in the Subscription. | Optional |
| **Billing Attempts** | The number of attempts to bill this transaction in this cycle. | Automatic |
| **Billing Plan Cycle** | Billing Plans may have several cycles. This field indicated the current billing cycle in the Billing Plan. | Automatic |

**Parent topic:**[View Transaction Info](transactionWorking)

## Transaction Payment Methods Pane

Payment Method(s) for this Transaction. The payment method type is displayed in the bar at the top of the section.

| Field | Guidance | Relevancy |
| - | - | - |
| **Payment Method ID** | The Reseller's (Service Provider's) customer ID associated with the billing profile. |   |
| **Type** | Payment method type. |   |
| **Account** | Name of the account holder. |   |
| **Created** | The date the Payment Method was created. | Automatic |
| For Credit Card Payment Method | | |
| Expand | Use the arrow to expand the Payment Method details. The payment Method attributes are displayed. Numbers are masked where required. |   |
| **Card Number** | The (hashed) credit card number used for this Transaction. |   |
| **Card Expiration** | Expiration date of the credit card. |   |
| **Billing Address** | Billing address associated with the payment method. |   |
| **Phone Number** | The customer Account provided Telephone number. |   |
| **Card Attributes** | If provided by the customer, card attributes include such things as whether the card is credit, a commercial or consumer card, or a prepaid card. |   |
| Other Supported Payment Methods are displayed in the [Account Payment Method Pane](accountViewing). | | |

**Parent topic:**[View Transaction Info](transactionWorking)

## Transaction Items Pane

Transaction Items are the line items associated with the transaction. For a Purchase these are the products and billing plans.

| Field | Guidance | Relevancy |
| - | - | - |
| **Type** | The supported Transaction Types are: - Purchase - Modification Refund - Discount before Tax Click the arrow to expand the line Item for more details. | N/A |
| **SKU** | The Billing Plan or Product ID (also known as Stock Keeping Unit) associated with the Transaction. | N/A |
| **Description** | The description of the Product or Billing Plan. | N/A |
| **Price** | The price of the line Item along with the national flag icon representing currency. | N/A |
| **QTY** | Quantity of the line item in this Transaction. | N/A |
| **Subtotal** | Amount for this item after discounts have been applied exclusive of tax. | N/A |
| **Taxes** | The Tax amount billed for the purchase. | N/A |
| **Tax Classification** | Commerce Engine uses the Tax Classification field, in conjunction with Reseller (Service Provider) nexus and tax rules provided during implementation, to calculate appropriate taxes, if any. This field contains the text string that corresponds to the classification in your tax engine for this product. | N/A |
| **Available Refund** | The amount still available for a refund for the associated line Item. This is displayed along with the national flag icon representing currency. | N/A |
| **Discount** | The discounted amount subtracted from the Total. The discount is applied when a campaign code was provided for the purchased item. | N/A |
| **Service Period** | The service period covered by this Transaction. | N/A |
| **Tax Type** | Available tax type values:- Inclusive Sales Tax - Exclusive Sales Tax - Inclusive Use Tax - Exclusive Use Tax | N/A |
| **Parent topic:**[View Transaction Info](transactionWorking) | | |

## Transaction History Pane

This pane lists the transaction history, that is, the status of payments activity on the transaction.

| Field | Guidance | Relevancy |
| - | - | - |
| **Time Stamp** | Date and time of the activity based on system time. | Automatic |
| **Payment** | Payment type used for this Transaction. | |
| **Disposition** | Status of the Transaction on a particular Date and Time. The disposition values are available Transaction status.For the list of statuses, see [Transaction Details Pane](transactionWorking#transaction-details-pane). | |
| **Note** | The notes entered regarding an activity that was logged. | Optional |
| **Parent topic:**[View Transaction Info](transactionWorking) | | |

## Transaction Activity History Pane

This pane lists Commerce Engine or customer activity, such as email notifications or payments, related to the Transaction.

| Field | Guidance | Relevancy |
| - | - | - |
| **Time Stamp** | Date and time of the activity based on system time. | Automatic |
| **Type** | Type is either a predefined type, or a custom Reseller (Service Provider)-defined activity added or created through the Commerce Engine API. Predefined activity types include the following:- Login - Logout - Email - Call - URL access - Product Delivery/Fulfillment - Service Usage - Cancellation Event - Note Click the Type entry to view more details. | By API Call |
| **IP Address** | IP address from which the customer initiated activity, if applicable. | Read Only |
| **Notes** | The notes entered regarding an activity that was logged. | Optional |
| **Add Note Button** | Click the **Add Note** button to record a new activity relevant to the Transaction. | Optional |
| **Parent topic:**[View Transaction Info](transactionWorking) | | |

## Custom Data

Custom data lets you store Reseller (Service Provider)-specific data to Products, Rate Plans, Billing Plans, Subscriptions, Accounts, and Payment Methods as a pair of matched text strings, called name-value pairs. These name-value pairs can help you categorize and sort aspects of your objects. Use **Name** to define a category, and **Value** to define a specific item in that category. For example, you could use name-value pairs to track your sales teams. Define a name-value pair with Office as the **Name** and the city in which the office is located as the **Value**.

| Field | Guidance | Relevancy |
| - | - | - |
| **Name** | Name is the field for defining metadata. It is unique and once submitted can't be changed. 1. Place your cursor in the selection box and either select from existing Names or enter a new Name. 2. For a new entry, click **Create New:** 3. Enter a Value for the Name. 4. Click **Add** to save this pair. **Note:** - Name field is limited to 255 characters. - System generated parameters use the prefix **vin** in the name field. | Required if adding custom data |
| **Value** | 1. Once you've selected/created a Name. 2. Enter the category's Value in the corresponding field. 3. Click **Add** to save this pair. **Note:** Value field is limited to 255 characters. | Required if adding custom data |
| **Parent topic:**[View Transaction Info](transactionWorking) | | |


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.