Skip to main content
Vindicia Knowledge Center

Reconcile Recovered Transactions

Reconcile Recovered Transactions

User Story

Merchant user wants to reconcile transactions recovered by Vindicia Retain with transactions available via the merchants payment processor portal.



  • Merchant business user knows the resulting data values from Vindicia Retain processing.
  • Merchant business user can obtain the data values for transactions processed by Vindicia Retain, in order to reconcile transactions in the payment processor portal.

Basic Scenario

  1. Merchant business user uses the data to search for recovered transactions in the payment processor portal, to reconcile transactions. 

Design Approach

The data resulting from Vindicia Retain processing data  identifies whether a failed transaction has been recovered by Vindicia Retain. This data can is used by the merchant user to locate transactions processed by Vindicia Retain in the payment processor portal for reconciliation. Data fields used in Vindicia Retain processing are described in the Use Case Implementation section of the this Use Case. 

Sequence Diagram

Not Applicable

Use Case Implementation

The following fields are always returned with the results of Vindicia Retain processing:

1. The authorization response code received from the most recent Failed authorization (i.e. decline code such as 302, 530, or other). 

2. The time of the final status determined by Vindicia Retain.

3. The amount of the transaction recovered or attempted by Vindicia Retain (equal to the failed transaction amount).

4. The final status of the transaction determined by Vindicia Retain.  When the failed transaction is recovered, the status will be Captured.

5. The unique identifier for the failed transaction, as provided to Vindicia Retain when processing was requested.

6. A unique identifier assigned by Vindicia Retain to the final transaction attempt made by Vindicia Retain, which resulted in the status returned.

This identifier is sent by Vindicia Retain to the payment processor in the Order ID/Number field when the Vindicia Retain Transaction is processed. The merchant can use this identifier as a search value to search for the recovered transaction in the payment processor portal.

7. If a refund was performed, a unique identifier assigned by Vindicia Retain to the refund.

8. The AVS (Address Verification) result for the Billing Address received by Vindicia Retain for the final attempt.


The following data may also be returned from the respective payment processors:

Request ID, corresponding to the Credit Card Settlement Status displayed in the Cybersource Business Center. The Request ID may be used to look up the Transaction in the Cybersource Business Center to locate a recovered Vindicia Retain Transaction.

By default, the Merchant Reference Number field in the Cybersource Business Center displays the unique identifier assigned by Vindicia Retain to the final transaction attempt made by Vindicia Retain. The merchant can use the Merchant Reference Number to look up the transaction in the Cybersource Business Center, by entering the unique identifier assigned by Vindicia Retain. It is possible to change this behavior, so that the Merchant Reference Number field displays the unique identifier for the failed transaction, as provided to Vindicia Retain when processing was requested. Contact Vindicia to request this configuration change.

Capture Request ID assigned by Litle/Vantiv to the final transaction attempt by Vindicia Retain for the Capture/Settlement request. This value may be used to look up the Transaction in the Litle/Vantiv portal, to locate a recovered Vindicia Retain transaction for a requested failed transaction submitted to Vindicia Retain.

Sample Code

Sample code not available

Scenario Extensions



No Certification required.

Use Case #: SEL-009

For Users

Learn More
For Users

Vindicia Subscribe Features

Learn More
Vindicia Subscribe Features
Back to Top