SFTP Batch Upload and Processing

This page is about understanding the v3 Batch file upload process via sFTP. Each template field provides specs and explanations for better understanding. The document has downloadable CSV templates for ordering, registering, and loading cards. Users can also find a look-up table for the error messages here: Error Messages. If you have any issues or questions, refer to our FAQs page.

Processing a File

A batch file uploaded via SFTP goes through Pre-processing and Post-processing stages. These stages ensure the file is validated, processed, and managed with appropriate error handling and status updates. Completed and failed files are placed within the processed folder with suffixes _completed or _failed , depending on the result.

Stages of Batch File Processing

1. Client Creates a Batch File

   • Generate a Batch File: Create a batch file to place orders of type Instant Issue/Personalized/Register/Load using the Unified V3 template.

2. Upload to Configured SFTP Folder

   • Use an SFTP Client: Use an SFTP client like FileZilla to upload the batch file to a configured folder outside the processed folder. Refer to the prerequisites section for more details.

3. Pre-processing

   Pre-processing tasks are handled by Dash to prepare and validate the file before further processing.

• File Pickup and Validation:
  • Dash automatically picks up the file every 15 minutes for processing and validation.
  • If Validation is Successful:
  • The file is routed to the appropriate landing zone based on size and traffic:
    • Files with 4000 or more records are dropped in Landing Zone 3.
    • Smaller files are dropped in Landing Zone 1 or 2.
  • The status updates to “File Uploaded”.
  • If Validation Fails:
  • The file is placed in the processed folder with one of the following suffixes:
    • _failed: Indicates overall file failure.
    • _duplicate: Indicates duplicate records.
    • _invalid: Indicates an invalid template or record.
    • _partialprocessed: Indicates partial validation success.
  • An error message is updated in the file, and the Account Manager (AM) and user are notified about the failure. Users must resolve the issue and re-upload the corrected file. Refer to the error guide for common issues.

4. Post-processing

Post-processing tasks are managed by the processing platform to complete order processing and deliver results back to Dash.

• File Processing at Processing Platform:
  • Once a file is successfully routed to the processing platform, further validation and order processing begin.
  • Successful Processing:
  • If all records are processed successfully:
    • A return file is generated with the suffix _completed and placed in the processed folder (if configured by the customer).
    • Additional columns such as DDA number, proxy card number, etc., are included in the return file.
    • Fetch PersonID, Exp Date, DDA, and TRN from the processing platform and store them in Dash.
    • Results are updated on the Dash portal, and the status changes to “Completed”.
  • If some records fail:
    • Those records are marked as failed, and a file with the suffix _partialprocessed is placed in the processed folder.
  • If all records fail:
    • A return file is generated with the suffix _failed_ddmmyyyy_hhmmss and placed in the processed folder.
  • Entire File Failed:
  • A return file is generated with the suffix _failed and placed in the failed folder (if configured by the customer).
  • The status updates to “Failed”.

Note: Post-processing results may take some time to reflect on the Dash portal.

Dash SFTP Process Flow