Configuration Guide

This guide helps you set up a Payment Gateway Configuration for reconciling transaction data from those providers.

The configuration ensures that uploaded PG files are correctly transformed, validated, and mapped to your database, covering orders, refunds, and chargebacks (adjustments).

PSP Config on Juspay Dashboard

Setting Up PSP Configuration for Reconciliation

Configuration Breakdown:

1. Chargeback Configuration

In payment gateway reconciliation, chargebacks (typically represented as adjustment entries in the settlement reports) need to be explicitly handled. These are not traditional payment or refund entries they're disputes or transaction reversals triggered post-settlement.

To ensure these records are properly accounted for during reconciliation, we define a configuration that enables the system to accurately detect, transform, and tag chargeback entries.

1.1 Filters

This configuration applies to rows where the type field equals "adjustment", indicating a chargeback.

1.2 Field Mapping

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

    Eg: fee_amount": "fee"

    This means the fee_amount column in the CSV will be saved into the fee column in the database.

2. Global Configuration

global_configuration:Add or Override Columns

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

What it does:

  • Automatically adds or overrides two fields:

    • gateway is set to "RAZORPAY" for every row

    • merchant_id is set to "reconDemo"

3. Local Configuration

local_configuration:Allows Processing Logic

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

  • Filters:

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

    • Configuration for ORDER Transactions:

    • Configuration for Refund Transactions:

4. Validation

validation:Ensuring Data Integrity

The validation section defines a set of rules that your uploaded CSV data must pass before it's accepted for processing. 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 CSV. If any of the validation checks fail, the corresponding row or file can be rejected, flagged, or corrected as per implementation.

Validation Logic Breakdown

Scroll inside to view more
Validation Type
Purpose
date_format_check
Validates date string format
duplicate_records_check
Ensures unique values for critical identifiers
nan_value_check
Ensures required fields are not empty or null
numeric_dtype_check
Confirms numeric fields contain valid numbers
pkey_check
Verifies uniqueness and presence for primary key field
scientific_value_check
Rejects exponential notation for consistency
Last updated 9 months ago