Retain Transaction Submission Errors

Failed Transactions submitted to Retain are validated as part of the submission process. Additionally, the failed Transactions then undergo an asynchronous post-submission system review to detect additional errors. Transactions that incur an error, either when first submitted or as part of the post-submission system validation are not accepted by Retain and do NOT undergo additional processing.

Viewing Post-Submission Validation Errors

As a Retain merchant submitting failed transactions, you can view the post-submission validation errors in one of the following:

Push notifications: Retain’s push notifications send your listener (endpoint URL) event-driven messages as they occur. The Validation Failed notification, notifies of a Transaction’s failure as part of the post-submission validation. For more details, see Push Notifications.
Submission History page in the Retain Hub: The Submission History page serves as a central location in the Retain Hub (portal) to download a CSV file of daily submission errors. For more details, see Submission History and System Validation Error Files.

Understanding the Submission History Error CSV File

The Retain Hub’s Submission History page, displays the submission error files on a daily basis. Once you download the file, each row displays the error details for a specific Transaction. The following details will be available for each row:

api_request_id: The API batch identifier that is included in your POST request for the specific Transaction in question. This same identifier may be relevant for several rows, if several Transactions from the same batch had errors detected.
id: The unique Transaction ID you submitted, allowing you to identify the specific Transaction.
error: The error code and description, identifying the problem that was encountered for the specific Transaction.
recommendations: Additional info explaining the problem and suggesting resolution steps.
RET001
RET002
RET003
RET004
RET005
RET006
RET007
RET008
RET009
RET010
RET011
RET012
RET400
RET900

Parent topic:Error Resolution And Troubleshooting Related information View Submission History and System Validation Error Files

RET001

Error Code	Error Description	Additional Info and recommended resolution action
RET001	Duplicate transaction within submission	The same Transaction ID was provided more than once in the same batch submission. In Retain, Transaction IDs must be unique. Review the submitted list and correct the duplication. If the same transaction was included twice in error, no other action is needed.
Parent topic:Retain Transaction Submission Errors

RET002

Error Code	Error Description	Additional Info and recommended resolution action
RET002	Duplicate transaction from prior submission	The same Transaction ID was provided more than once in different file or batch submissions. In Retain, Transaction IDs must be unique. If you do need to submit the same Transaction again (with additional data or corrections), change the Transaction ID to a unique one and re-submit it.

Parent topic:Retain Transaction Submission Errors

RET003

Error Code	Error Description	Additional Info and recommended resolution action
RET003	A Transaction for the same Subscription is still processing	Another Transaction, part of the same subscription,is being processed and therefore this one can’t be accepted. If you do need to submit the Transaction, change the Subscription ID to a unique one and re-submit it or wait for a later time.

Parent topic:Retain Transaction Submission Errors

RET004

Error Code	Error Description	Additional Info and recommended resolution action
RET004	Transaction was previously submitted and processed	The same Transaction ID was previously submitted and reached its final status. Transaction IDs must be unique. If you do need to submit the same Transaction (with additional data or corrections), change the Transaction ID to a unique one and re-submit it.
Parent topic:Retain Transaction Submission Errors

RET005

Error Code	Error Description	Additional Info and recommended resolution action
RET005	System cannot read Transaction	Review the submitted transaction for formating errors, correct them, and then resubmit. If problem persists, contact Vindicia Customer Technical Support.

Parent topic:Retain Transaction Submission Errors

RET006

Error Code	Error Description	Additional Info and recommended resolution action
RET006	Missing Transaction element	When submitting a Transaction, you must provide a valid Transaction object. Something was missing or unreadable in this specific Transaction object.To resolve, do the following: 1. Review the Transaction object and ensure all required fields are available and readable. 2. Resubmit the Transaction. Note: You do not need to change the Transaction ID, this Transaction was not accepted and can be resubmitted.
Parent topic:Retain Transaction Submission Errors

RET007

Error Code	Error Description	Additional Info and recommended resolution action
RET007	Trial mode without capture. Incompatible configuration	There is an issue with your merchant configuration settings.Contact your Vindicia representative to review configuration settings.

Parent topic:Retain Transaction Submission Errors

RET008

Error Code	Error Description	Additional Info and recommended resolution action
RET008	Processing error	To resolve, do the following: 1. Review the Transaction object and ensure all required fields are available and readable. 2. Resubmit the Transaction. Note: You do not need to change the Transaction ID, this Transaction was not accepted and can be resubmitted. 3. If problem persists, contact Vindicia Customer Technical Support
Parent topic:Retain Transaction Submission Errors

RET009

Error Code	Error Description	Additional Info and recommended resolution action
RET009	Schema validation error	Check the API call and object submitted for errors. When corrected, resubmit the Transaction.
Parent topic:Retain Transaction Submission Errors

RET010

Error Code	Error Description	Additional Info and recommended resolution action
RET010	Credit Card number is not valid or incorrectly encrypted	To resolve do the following: 1. Review the provided Transaction. 2. Ensure you provided the correct Credit Card number and verify that the correct PGP encryption key was used. 3. Resubmit the Transaction with the corrected details.
Parent topic:Retain Transaction Submission Errors

RET011

Error Code	Error Description	Additional Info and recommended resolution action
RET011	Unable to process provided tokenized payment method	Unable to process provided tokenized payment method.Ensure you provided the correct combination of payment provider ID, and paymentMethod ID
Parent topic:Retain Transaction Submission Errors

RET012

Error Code	Error Description	Additional Info and recommended resolution action
RET012	did not pass validation check:<field>	The error lists the problematic field or area that did not pass validation.Check the problematic field and resubmit the Transaction with the amended data.
Parent topic:Retain Transaction Submission Errors

RET400

Error Code	Error Description	Additional Info and recommended resolution action
RET400	Invalid parameter <faulty Parameter>	An API parameter error. Review your submitted call and correct the faulty parameter.

Parent topic:Retain Transaction Submission Errors

RET900

Error Code	Error Description	Additional Info and recommended resolution action
RET900	Unable to submit, please try again	Try to resubmit at a later time. If issue persists, contact Vindica Customer Technical Support
Parent topic:Retain Transaction Submission Errors

Home

Guides

Viewing Post-Submission Validation Errors

Understanding the Submission History Error CSV File

RET001

RET002

RET003

RET004

RET005

RET006

RET007

RET008

RET009

RET010

RET011

RET012

RET400

RET900

​Viewing Post-Submission Validation Errors

​Understanding the Submission History Error CSV File

​RET001

​RET002

​RET003

​RET004

​RET005

​RET006

​RET007

​RET008

​RET009

​RET010

​RET011

​RET012

​RET400

​RET900

Viewing Post-Submission Validation Errors

Understanding the Submission History Error CSV File

RET001

RET002

RET003

RET004

RET005

RET006

RET007

RET008

RET009

RET010

RET011

RET012

RET400

RET900