Skip to main content
Transactions submitted to Retain, undergo an asynchronous post-submission system review to detect errors. This process can take up to an hour to process and may contain errors concerning:
  • Transaction submission duplicates
  • Transaction hashing and encryption
  • Payment method tokenization
Access the Submission History screen an hour after API batch submission or file upload to check the submitted Transactions’ status. If errors were detected, download the CSV file for the details and resolution recommendations. Transactions that were marked as errors were not accepted by Retain and need to be re-submitted for additional processing, if needed. Note: API submitted Transactions are grouped by day and include all the API batches you submitted in that day (by UTC time zone). The Retain error file updates after each batch, wait an hour after the last batch to get the most updated error file. Before you begin
  • Ensure that at least one Transaction batch has been submitted.
To verify if any post-submission errors were detected by Retain, do the following:
  1. Log in to the Vindicia Retain Hub at https://portal.vindicia.com/portal/login
  2. From the top menu, select Transactions > Submission History. The Retain Submission History page appears. Retain Submission History Page listing API error files)
  3. Filter the dates to see the list of error files for the submitted Transactions in your merchant account. You can use the pre-defined options such as Past 7 days and Past 30 days. Otherwise, select custom dates and enter your required display period. The list of files in the table is updated according to the defined dates with Status Errors Found (# of Transactions with detected errors).
  1. Click the Download icon . The Retain error CSV file is downloaded locally to your device.
  2. Open the CSV file with a spreadsheet application to see the Transactions that were not accepted by Retain as well as the relevant error code and description. The following details appear per Transaction (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. For resolution steps and more details, continue to Retain Transaction Submission Errors.
Parent topic:Retain Transactions Related information Retain Transaction Submission Errors