> ## Documentation Index > Fetch the complete documentation index at: https://docs.vindicia.com/llms.txt > Use this file to discover all available pages before exploring further. # View Retain Transactions and Retry Details View detailed information about the submitted Transaction and its associated retry attempts. The timeline shows important occurrences that happened to the Transaction as well as predicted retry attempts, if the transaction is still in retry. You can also view a specific retry attempt for a submitted [Transaction](glossRetainTransaction). 1. [Search for the relevant Retain Transaction](retainTransactionSearch). 2. In the search results list, click the relevant Transaction ID. The Submitted Transaction Details Page appears. 3. View and understand the Submitted Transaction Details data. Refer to the tables below for guidance regarding the fields. 4. To refund a captured Transaction and return funds to the customer, continue to [Refund Transactions in Retain](retainTransactionRefundMain#). 5. To stop attempting to capture a Transaction continue to [Stop Transaction Capture in Retain](retainTransactionStopMain#). 6. To view detailed information for a specific retry attempt, click the **ID** field in the Retry attempts pane. The Retry Details page appears. Retry Details Page Example 7. View and understand the Retry Details data. Refer to the tables below for guidance regarding the fields. * **[Submitted Transaction Details](../topics/retainTransactionView#)** * **[Retry Details](../topics/retainTransactionView#)**\ The Retry Details page contains detailed information for the retry attempt you selected in the Submitted Transaction Details page. Most of these fields represent data originally submitted for the Transaction by you the Merchant and are identical to the Submitted Transaction Details page. **Parent topic:**[Retain Transactions](../topics/retainTransactions) ## Submitted Transaction Details When Vindicia Retain attempts to capture the submitted Transaction, it generates retry attempts Transactions that are linked to the original submitted one. | Field | Guidance | | - | - | | **Transaction ID** | Unique identifier provided by the Merchant for this Transaction. | | **Status** | The current processing status for the Transaction. Possible statuses are: - **Captured**: Retain successfully captured the Transaction. The failed Transaction has been successfully recovered. - **Cancelled**: A submitted Transaction, for which Retain's defined retry period and attempts were exhausted. No further retry attempts for the submitted Transaction will be attempted. - **in Retry**:This status is applied to the Transaction while Retain attempts to capture it by utilizing Retain's many capture mechanisms. This status is temporary and a Transaction can move to several other statuses. - **Stopped**: A submitted Transaction that was In Retry status and merchant has asked to stop capture attempts. - **Refunded** - Retain successfully captured the submitted Transaction. By merchant request the Transaction was refunded and funds were returned to the customer. | | **Amount** | Billed Transaction amount and currency symbol for this Transaction. | | **Submitted** | Date and time (in UTC time zone) of the Transaction submission to Retain. | | **Account ID** | Unique identifier assigned by the Merchant to the customer Account for the Transaction. | | **Subscription ID** | Unique identifier for the subscription (recurring billing agreement) for this Transaction. | | **Started** | Start date for the Subscription as provided by the merchant. | | **Email** | The email address for the Customer associated with the Transaction. | | **Transaction Timeline** | Colored indicator that indicates when an action took place for the Transaction. Different points may appear based on the Transaction status such as Transaction submission to retain, retry attempts, capture , refund, stopped and others.When you hover over a node, a date and time stamp appears that denotes when the action took place. Transaction In Retry status will also show the estimated future retry attempts.**Note:** The Transaction timeline will appear correctly for Transactions submitted after the Retain January release. | | **Credit Card** | The masked or tokenized credit card account number. **Tokenized** indicates that this is a tokenized credit card number. Tokenization is a process that replaces the credit card number with an identifier, called a token. | | **Billing Address** | The billing address for the Transaction, including the street address, city, state or province, zip or postal code, and country indicator. | | **Billing Descriptor** | The description that appears on the Customer's credit card billing statement when they are charged for the Transaction. | | **Prev Bill Count** | The number of previous successful billings associated with the Subscription as provided by the merchant. | | **Division Number** | The division or group number your payment provider associates with this Transaction. For example, Chase Paymentech refers to this number as the Division ID; Litle calls it the Report Group; MeS calls it the Profile ID. | | **Received Auth Code** | The authorization response code provided for the submitted Transaction. | | **Processor Transaction ID** | Unique identifier assigned to the Transaction by the payment provider. In most cases, this is identical to the Transaction ID. In some cases, due to format requirements of some providers, the ID is altered. It is commonly used to reconcile Retain Transactions with Transactions recorded in the payment provider's system. | | **Payment Network Token** | CIT/MIT (card-on file) token provided by the Merchant for the submitted Transaction. | | **AVS Code** | Address Verification Service (AVS) response code returned by the payment provider for this Transaction. | | **CVN Code** | Card Verification Number (CVN) response code returned by the payment processor for this Transaction. | ### Retry Attempts For Transaction (Transaction ID) This section contains summarized information for each of the retry attempts that Retain has generated for the submitted Transaction. | Field | Guidance | | - | - | | **#** | The hash represents the retry attempt sequence going from 1 to as many attempts that were defined and required. | | **ID** | Unique identifier assigned by Vindicia Retain for this retry attempt. To access the Retry Details page to view detailed information for a specific retry attempt, click the **ID** field. | | **Amount** | Billed Transaction amount and currency symbol for this Transaction. | | **Timestamp (UTC)** | The date and time when Retain attempted to capture this retry, in Coordinated Universal Time (UTC). | | **Auth Code** | Authorization response code received from the payment provider for the retry attempt. Retain evaluates this code and determines whether the submitted Transaction is considered a Soft Fail (D) or a Hard Fail (R). | | **Type** | The Type of Auth code received for the retry attempt. classification for the Transaction that was submitted for recovery. Retain evaluates the Auth code and determines whether the submitted Transaction is considered a Soft Fail (D) or a Hard Fail (R). - **Soft Fail** (D): A payment capture attempt had failed but an additional retry attempt by Retain may succeed. for example insufficient funds, or a credit card declined, Retain will utilize its advanced algorithms to retry and capture the Transaction. - **Hard Fail** (R): A payment capture attempt has failed and has been rejected. Retain does not retry a Hard Fail transaction, unless the payment method on file for the customer has been updated since the last retry date. | | **Forced Deposit** | Indicates that the Transaction associated with this retry attempt was captured by Retain without a prior successful authorization response from the payment provider. | | **Parent topic:**[View Retain Transactions and Retry Details](../topics/retainTransactionView#) | | ## Retry Details The Retry Details page contains detailed information for the retry attempt you selected in the Submitted Transaction Details page. Most of these fields represent data originally submitted for the Transaction by you the Merchant and are identical to the Submitted Transaction Details page. The following fields are included in the Retry Details page: | Field | Guidance | | - | - | | **Retry ID** | A unique identifier generated by Retain for this retry attempt, followed by a description indicating which attempt it is and if it is final attempt. For example, **Retry 5 (Final)**. | | **Custom Data for Retry nnnnnnn** | Name value pair custom data, if any, associated with this Retry attempt. Name value pairs are custom data either the Merchant, payment provider, or Vindicia staff have set up and submitted for the submitted Transaction. They represent unique data that the Merchant or payment provider would like to track. If no custom data was submitted, no entries appear in the **Name** and **Value** fields. | | **Parent topic:**[View Retain Transactions and Retry Details](../topics/retainTransactionView#) | | **Related information** [Search Retain Transactions](retainTransactionSearch) [Refund Transactions in Retain](retainTransactionRefundMain#) [Stop Transaction Capture in Retain](retainTransactionStopMain#) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.