Configuration Guide

Transaction file configuration is used to process Merchants file of transactions. It tells the system how to handle, validate, and transform the data before saving it to the database.

Configuring on Juspay Dashboard

Configuration Breakdown:

1. Global Configuration

Used to add or override columns such as Transaction status and Merchant ID. If all transactions belong to the same merchant, this configuration ensures consistency across all records.

What it does:

2. Local Configuration

This configuration section defines how to process different types of transactions such as ORDER , REFUND , CHARGEBACK , DISPUTE, etc based on specific filter conditions. 

2.1 Filters:

Each block starts with a filter condition that determines which rows the configuration applies to.

• Configuration for ORDER Transactions:

This configuration applies to rows where transaction_type equals "ORDER".

• Configuration for REFUND Transactions:

This configuration applies to all rows that are NOT "ORDER" essentially REFUND or others.

2.2 Mappings:

Each configuration maps CSV column names to corresponding internal database field names.

• Eg: card_network: payment_methods

  This means the card_network column in the CSV will be saved into the payment_methods column in the database.

3. Validation

The validation section defines a set of rules that your uploaded transaction data must pass before it's accepted for processing Ensuring Data Integrity. These checks help ensure that the data is clean, complete, and correctly formatted.

When a file is uploaded, the system will automatically run the defined validations on the mapped columns from your transaction file.

Validation Logic Breakdown