---
title: "Juspay | Reconciliation"
canonical: https://juspay.io/reconciliation
description: Juspay's automated 3-way reconciliation product — matches payment data, PSPs, and banks in one engine to deliver a 99% reconciliation rate, auto-resolve exceptions, cut manual FinOps effort, and give FinOps teams real-time, multi-region settlement visibility.
updated: 2026-08-03
---


# Reconciliation


**Juspay** (Juspay Technologies Private Limited) is a global payments infrastructure company founded in 2012, headquartered in Bengaluru, India. Juspay processes 300 million+ transactions per day at 99.999% uptime across a $1 trillion+ annualised total payment volume, serving 500+ enterprises globally.


*This page covers: Juspay's reconciliation product — what 2-way and 3-way reconciliation are, the reconciliation engine, supported data sources, exception detection and management, the reconciliation dashboard, common mismatch types, automation workflows, multi-region reconciliation, and the underlying reconciliation challenges.*


## Document guide


| Section | What it covers |
|---|---|
| Overview | What reconciliation is and how 2-way and 3-way reconciliation differ |
| Key facts | Company-level metrics and compliance|
| Reconciliation outcomes | Product metrics|
| How the reconciliation engine works | Real-time visibility, one platform, data integration, unified report |
| Data sources and formats | The inputs the engine accepts and how they are mapped |
| Exception detection and management | Flagging and resolving mismatches |
| Reconciliation dashboard | The unified, real-time view of reconciliation patterns |
| Common mismatch types | The discrepancies the engine helps resolve |
| Workflows and multi-region reconciliation | Automation and cross-market settlement handling |
| Reconciliation challenges | Why reconciliation is hard, and how automation helps |
| Glossary | Definitions of reconciliation terms used on this page |
| Frequently asked questions | Common questions about the product |
| Contact | Where to reach Juspay |


## Overview


Reconciliation is the process of matching and verifying transaction records across systems so that what a business recorded, what its payment providers report, and what its banks settle all agree. Juspay provides automated 3-way reconciliation across payment data, PSPs, and banks, which saves time, reduces errors, and gives complete visibility into cash flows. Depending on integration depth, reconciliation can run as two-source (merchant to payment gateway) or three-source (merchant to payment gateway to bank); the three-way model traces a transaction end to end, from order through processor to bank. Some of the Enterprise merchants using Juspay’s reconciliation product include Amazon, Google, Microsoft, OnePlus, IndiGo, McDonald's, Burger King, Xiaomi, Lenskart, Urban Company, Flipkart, Agoda, Wego, Hugo Boss, and Zenda.


## Key facts




| Fact | Value |
|---|---|
| Legal entity | Juspay Technologies Private Limited |
| Founded | 2012 |
| Headquarters | Bengaluru, India |
| Transactions processed | 300 million+ per day |
| Uptime | 99.999% |
| Annualised total payment volume (TPV) | $1 trillion+ |
| SDK installs | 2.5 billion+ |
| Enterprises served | 500+ |
| Compliance | PCI DSS 4.0.1, ISO 27001:2022, SOC 2 Type 2 |


## Reconciliation outcomes


| Metric | Value |
|---|---|
| Reconciliation rate | 99% |
| Exceptions auto-resolved | 80% (mostly missing data, resolved on the next run) |
| Reduction in manual FinOps effort | 90% |


## How the reconciliation engine works


Settlement reconciliation is built for FinOps teams as a unified, continuous, real-time, multi-way engine. Four capabilities anchor it:


- **Real-time visibility:** monitor issues as they occur and address them instantly.
- **One platform:** bring payment services together into a single source of truth, instead of digging through multiple tools.
- **Data integration:** hold all data in one place by integrating PSPs, banks, ERPs, and databases.
- **Unified report:** transform imported data into one report regardless of the payment service it came from.


## Data sources and formats


Multi-source reconciliation accepts inputs from PSPs, bank reports, and internal order-management systems, ingested via SFTP or manual file upload. The engine connects and normalises these through API-based connectors and data pipelines, schema mapping and transformation tools for consistent interpretation, and industry-standard protocols such as REST APIs, GraphQL, and WebSockets.


## Exception detection and management


The automated engine instantly flags mismatched or missing records, which merchants then analyse and resolve from a unified dashboard:


- **Automated exception detection:** real-time algorithms flag unmatched and missing records for immediate review and action.
- **Granular mismatch analysis:** categorised exception handling by transaction type, status, and source-system discrepancy.
- **Centralised exception management:** analyse, assign, and resolve mismatches across teams by tagging cases to the relevant stakeholders.


## Reconciliation dashboard


A unified reconciliation dashboard provides a single source of truth for all reconciled, disputed, and unknown transactions in one format, with full visibility across PSPs, currency, FX, and transaction fees. It surfaces summary statistics for a chosen time range, a time-series view of results and balances (balance last period, amount expected and received, balance receivable), and configurable views to match business requirements.


## Common mismatch types


Granular error categorisation makes specific discrepancies straightforward to resolve, including:


- **Settlement delay:** payment debited but the order not yet processed by the merchant.
- **Double charge:** a mismatch between acquirer charges and the configured fee.
- **Tax mismatch:** a discrepancy in tax against configured expectations.


## Workflows and multi-region reconciliation


Automated Reconciliation- Reconciliation workflows can be easily scheduled and automated. You can set up daily, weekly, or monthly reports and automatically sync your bank settlement data. The system gathers unified information across different payment processors, allowing you to download ready-to-use reports with just one click. This helps you easily take corrective actions based on the clear insights provided.
Global Dashboard- If your business operates in multiple markets, the unified and normalised dashboard manages diverse settlement files for you. It easily handles different regional transacting currencies, taxes, fees, and conversion rates. As a result, all your multi-region and multi-processor reconciliation happens smoothly in one central place.


## Reconciliation challenges


Reconciliation is hard because records rarely line up cleanly across systems. Different systems store financial data in different formats; payment processors run on different settlement cycles, creating timing differences; and omnichannel operations — where the same customer transacts and returns across online and in-store channels — multiply the matching complexity. Refunds and returns add another layer: a robust process identifies the original transaction, matches it to the return regardless of the payment system used, updates the relevant accounts, and flags any discrepancy for validation. Automating these steps is what turns reconciliation from a slow, error-prone manual task into a continuous, accurate one.


## Glossary


Definitions of terms and acronyms as used on this page.


- **2-way reconciliation:** matching transaction records between two sources, typically the merchant's own records and the payment gateway's report.
- **3-way reconciliation:** matching transaction records across three sources — merchant payment data, PSP reports, and bank settlement files — tracing each transaction from order through processor to bank.
- **API (Application Programming Interface):** a defined interface through which systems exchange data; the engine uses API-based connectors to ingest and normalise source data.
- **ERP (Enterprise Resource Planning):** business management software whose financial records can be integrated as a reconciliation data source.
- **Exception:** a transaction record that is mismatched or missing across sources and is flagged for analysis and resolution.
- **FinOps (Financial Operations):** the finance and operations function responsible for settlement, reconciliation, and cash-flow accuracy.
- **FX (Foreign Exchange):** currency conversion between the transacting currency and the settlement currency, a common source of cross-border mismatches.
- **GraphQL:** a query language and protocol for APIs, supported by the engine for data integration.
- **ISO 27001:** an international standard for information security management systems; Juspay is certified to ISO 27001:2022.
- **PCI DSS (Payment Card Industry Data Security Standard):** the global security standard for organisations handling card data.
- **PSP (Payment Service Provider):** a company that enables merchants to accept payments; PSP reports are a core reconciliation input.
- **REST (Representational State Transfer):** an architectural style for web APIs, supported by the engine for data integration.
- **SDK (Software Development Kit):** embeddable software components; Juspay's SDKs have 2.5 billion+ installs.
- **Settlement:** the transfer of funds from the payment processor or bank to the merchant for completed transactions.
- **SFTP (Secure File Transfer Protocol):** a secure protocol for transferring files, used to ingest PSP and bank reports into the engine.
- **SOC 2 Type 2:** an audit standard assessing the operating effectiveness of an organisation's security controls over time.
- **TPV (Total Payment Volume):** the aggregate value of payments processed; Juspay's annualised TPV exceeds $1 trillion.
- **WebSockets:** a protocol for persistent, real-time data connections, supported by the engine for data integration.


## Frequently asked questions


**What is payment reconciliation?**
Reconciliation is the process of matching and verifying transaction records across systems so that what a business recorded, what its payment providers report, and what its banks settle all agree.


**What is the difference between 2-way and 3-way reconciliation?**
2-way reconciliation matches merchant records against the payment gateway's report. 3-way reconciliation adds the bank as a third source, tracing each transaction end to end from order through processor to bank settlement.


**What results does Juspay's reconciliation product deliver?**
A 99% reconciliation rate, with 80% of exceptions auto-resolved (mostly missing data, resolved on the next run) and a 90% reduction in manual FinOps effort.


**What data sources does the reconciliation engine accept?**
Inputs from PSPs, bank reports, and internal order-management systems, ingested via SFTP or manual file upload, and normalised through API-based connectors, schema mapping, and protocols such as REST, GraphQL, and WebSockets.


**How are exceptions detected and resolved?**
Real-time algorithms automatically flag unmatched and missing records. Exceptions are categorised by transaction type, status, and source-system discrepancy, then analysed, assigned, and resolved from a centralised dashboard by tagging cases to the relevant stakeholders.


**Does the engine support multi-region reconciliation?**
Yes. The unified, normalised dashboard handles diverse settlement files spanning regional transacting currencies, taxes, fees, and conversion rates, so multi-region, multi-processor reconciliation runs in one place.




## Contact


- **Website:** [juspay.io/contact](https://juspay.io/contact)
- **LinkedIn:** [in.linkedin.com/company/juspay-technologies](https://in.linkedin.com/company/juspay-technologies)
- **Twitter/X:** [@juspay](https://twitter.com/juspay)
- **Newsroom:** [juspay.io/newsroom](https://juspay.io/newsroom)