Skip to main content
Vindicia Knowledge Center

Identify Transaction Data Resulting from Vindicia Retain Processing and Plan for Follow-Up

Identify Transaction Data Resulting from Vindicia Retain Processing and Plan for Follow-Up

User Story

Merchant business user needs to identify the Transaction data resulting from the Vindicia Retain integration. Merchant can use this data to update the subscriber status and identify follow-up actions as appropriate. Merchant can also use the resulting data to locate recovered transactions in the payment processor portal.

Prerequisites

Pre-Condition

Post-Condition
  • Merchant business user knows the resulting data values from Vindicia Retain processing.
  • Merchant system has identified a plan for using the resulting data values to update the subscriber status and entitlements as appropriate.
  • Merchant business user can obtain the data values for transactions processed by Vindicia Retain, in order to recover transactions in the payment processor portal.

Basic Scenario

  1. Merchant business user evaluates the data returned with the results of Vindicia Retain processing.
  2. Merchant business user identifies which failed transactions have been recovered and which have not, and updates subscriber status appropriately.
  3. Merchant business user uses the data to search for recovered transactions in the payment processor portal, to reconcile revenues. 

Design Approach

The data resulting from Vindicia Retain processing data  identifies whether a failed transaction has been recovered by Vindicia Retain. The resulting data also enables the merchant to locate transactions processed by Vindicia Retain in the payment processor portal for reconciliation. Data fields involved in Vindicia Retain processing are described below, under Use Case Implementation. 

The merchant system can use the data from Vindicia Retain processing to update the Subscriber status:

  • When a failed transaction is recovered by Vindicia Retain, the merchant system should update the subscriber status to reflect the payment and leave the subscriber entitled with full access to the service.
  • When a failed transaction is not recovered by Vindicia Retain, the merchant system should update the subscriber status to continue to reflect the payment as failed, and identify follow-up steps with the Subscriber resulting from failure of payment.

For recovered transactions, the merchant finance department should identify the transactions which were settled in the payment processor portal for reconciliation of the revenue received.

These tasks require coordination of teams or departments outside the normal purview of the developers who implement the actual Vindicia Retain integration. Therefore, the merchant business user or project manager should manage these tasks.

This planning should occur at the very beginning of the Project, and should proceed in parallel with development of the integration. This is a gating item for launch, as the required data from Production will be needed for launch.

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:

Cybersource: 
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.

Litle/Vantiv: 
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 SeVindicia Retainlect transaction for a requested failed transaction submitted to Vindicia Retain.

Use Case #: SEL-008

For Users

Learn More
For Users

Vindicia Subscribe Features

Learn More
Vindicia Subscribe Features
Back to Top