CSV Integration

Documentation: https://docs.liberis.com/reference/sharing-data-via-csv-file

We also provide a file-based integration where partner client and revenue claim data can be shared via CSV templates we have designed.

As part of this integration, as a partner, you will need to generate your partner clients and revenue claims data into the CSV templates we provide and uploaded them to an SFTP folder structure which will be setup as part of this integration.

We have an automated file ingestion process which will pick files you place on an SFTP server.

Although we always recommend and prefer daily revenue claim delta, with the CSV approach it depends on the technical capabilities of each partner as there is sometimes some manual intervention needed to generate the data in the CSV templates.

The file-based approach does not support near-real time data validation. If our CSV file ingestion pipeline detects invalid data in files, the data is not saved to our data stores as valid and is therefore not used for the relevant merchant(s) when our eligibility process runs to decided what offer each merchant can be presented with.

Getting the data right in our CSV templates is key to ensuring the most efficient integration possible.

CSV Data Validation & Testing

We conduct a data validation step as part of the onboarding, whereby you can share example understandings of the partner client and revenue claim CSV templates which we will validate for you to confirm its accuracy.

Pre-Production Validation

For pre-production validation, our sandbox provides a tool where you can validate the format and data integrity of the partner client and revenue claims files.

CSV validation - https://sandbox.liberis.com/#/data-sharing

Production Validation & Testing

Once you are happy with the sandbox validation, we then ask for a small snapshot of some real merchants and their historical revenue – this can a small cohort, we recommend no more than 100.

We then validate the data in our production pipelines. This ensures that the values within the files are valid. Ensuring the data quality is as expected and the data integrity is high.

When we are all satisfied the data looks good - we can then test the production workflow via the SFTP servers, whereby a file lands in a folder and is automatically picked up and processed by our services, where the expected result is the data lands in our data stores, ready for eligibility to run.