Skip to main content
To submit Failed Transactions to Vindicia Retain, you must identify and map the source Transaction data from your merchant system to the required Vindicia Retain Request data members. A software developer typically performs this mapping.

Basic Scenario

Your organization wants to submit failed transactions to Vindicia Retain for recovery. To support this task, you must coordinate with your internal business manager to determine the availability of the required transaction data in your internal systems. You can then map these internal data fields to the Vindicia Retain Transaction data members and identify the Retain data members to populate in your requests.

Design Approach

The Required data fields for Vindicia Retain are a superset of the data fields that are required in the Web Services Description Language (WSDL) file. They include additional data fields that are marked as optional in the WSDL, but which provide additional detail about the Failed Transaction to assist in optimal processing decisions by Vindicia Retain with the least risk of Chargeback.

Retain Request Data Fields

For each failed transaction, include the Vindicia Retain data fields as specified in the following table, mapped to the corresponding merchant data values. Transactions can use a credit card or tokens as the payment method, with differing data values as specified. All values are required, except where designated as ‘if available’.

References

Parent topic:Getting Started with Vindicia Retain