SFTP (alternate option)

❗️

REST API integration is highly recommended over less preferred SFTP integration

Abstract

This document outlines the standardized requirements and procedures for partners to download Redemption Feed files via alternate SFTP option.

The SFTP method shares the same CSV schema as the REST API method for the result file content.

Error Codes

The Redemption Feed delivered via SFTP itself is a data file, so it does not have real-time API error codes in the traditional sense for individual record failures. However, potential issues in the file delivery or data quality can manifest in different ways.

SFTP Delivery Errors:

• Connection/Authentication Errors: Issues with your SFTP client connecting to the Cardlytics SFTP server, or incorrect credentials. These would be client-side errors reported by your SFTP software.
  • Resolution: Verify SFTP hostname, port, username, password/key. Check network connectivity.
• File Not Found/Permissions: If expected files are not present or you lack permissions to download them.
  • Resolution: Confirm file naming conventions and paths. Contact Cardlytics support to verify your SFTP user permissions.
• Incomplete File Transfer: The file download might be interrupted, resulting in a partially transferred or corrupted file.
  • Resolution: Implement robust SFTP client logic for retries and checksum verification if supported. Cardlytics aims for atomic file delivery.

Data Quality / Content Errors within the Feed (Post-Download):

While Cardlytics aims to provide clean data, partners should implement robust parsing and validation within their own systems to handle unexpected data. These are not "error codes" from Cardlytics but rather potential issues your system might encounter:

• Malformed Data: A row might not conform to the expected CSV/JSON structure (though CSV is typical for SFTP feeds).
  • Impact: Row parsing failure.
  • Resolution: Log the problematic row, skip it, and investigate the file for corruption.
• Missing Required Fields: A field marked "No" under "Nullable" in the table above is empty or missing.
  • Impact: Data integrity issue, potential processing failure.
  • Resolution: This should ideally not happen. If it does, log the record as an error and alert Cardlytics support with the specific transaction_id and field.
• Invalid Data Format: A field's content does not match its expected format (e.g., transaction_amount is not a number, transaction_timestamp is not ISO 8601).
  • Impact: Data type conversion errors, incorrect calculations.
  • Resolution: Implement strict data type validation. Records with invalid formats should be flagged for review and potentially quarantined.
• Unexpected Values: For card_type, receiving a value not in the common list (e.g., "Unknown Card").
  • Impact: May require flexible parsing or additional mapping logic.
  • Resolution: Treat as an acceptable but uncommon value or map to a generic "other" category.

Contacting Cardlytics Support:

For any persistent SFTP delivery issues or if you encounter widespread data quality problems within the Redemption Feed, contact your dedicated Cardlytics Partner Success Manager or the Cardlytics Support team with detailed information (file names, timestamps of issues, specific error messages from your systems).