Skip to main content
To allow Vindicia Retain to process failed transactions, you must first collect the required data about the failed transactions.

​
Basic Scenario

  1. Your software developer identifies the data in your transaction repository that maps to the data fields that are required by Vindicia Retain.
  2. You must work with your security, IT, development and finance teams as necessary to coordinate the collection of this necessary internal transaction data to submit to Vindicia Retain. Note: You must identify the transaction data at the beginning of the project, and in parallel with the Vindicia Retain integration. This data is required for launch.
  3. After identifying the failed transaction data, provide this data to the software developer to perform the mapping required for submission to Vindicia Retain.
  4. Your software developer uses this data to map the transaction requests to, and responses from, Vindicia Retain.

​
Design Approach

To collect the required data, you must coordinate with teams or departments outside the normal purview of the developers who implement the actual Vindicia Retain integration. Therefore, a business or project manager typically manages these tasks. This planning must occur at the very beginning of the project, and proceeds in parallel with development of the integration. This required data from production is a gating item for launch. For details about the transaction data that requires mapping, see: Parent topic:Getting Started with Vindicia Retain