See what’s happening. Find what’s wrong. Understand what it costs.
Merchant 1 is software designed to work in the background, bringing your payment data together and doing the heavy lifting of comparison, reconciliation, and reporting—so your team can focus on the exceptions and decisions that need attention.
See how the software is designed to connect your data, handle the heavy lifting, and help your team focus on what matters.
Illustrates the intended software workflow. No live accounts are connected.
Merchant 1 is designed to keep payment operations moving in the background: organizing connected data, comparing settlements, and surfacing what needs your attention.
Less manual checking. Clearer answers. More time to run your business.
Turn scattered payment records into one consistent operating view.
Compare activity, settlements, and deductions to find the differences.
Review clear reports and flagged exceptions with the supporting context.
Designed for connected data sources. Your team stays in control of reviews and decisions.
Merchant 1 is designed around operational clarity: what happened, why it happened, what it cost, and what needs attention next.
Bring transaction, merchant, processor, settlement, and reconciliation data into one consistent operating view.
Surface settlement variances, declines, refund patterns, chargeback pressure, and performance changes that deserve investigation.
Analyze fees, deductions, refunds, chargebacks, reserves, and effective processing costs so margins are easier to understand.
Compare what was processed, what was expected, what was deposited, and what remains unexplained.
Track merchant-level performance, MIDs, connected processors, settlements, and risk signals.
Give operations and finance teams the context they need to investigate, document, and resolve payment issues.
Merchant 1 is being designed to make changes, anomalies, and performance shifts easier to see and investigate.
Expected settlement does not match the amount received.
In this example, $513,900 was expected and $511,400 was received, leaving a $2,500 shortfall.
Compare the settlement report with the deposit record, then check timing, fees, reserves, and adjustments before documenting the cause.
Processing costs should not be buried across statements and disconnected reports. Merchant 1 is designed to bring the economics of payments into view.
Merchant 1 is built to help teams compare expected settlement activity with what was actually received, investigate a variance, and document how it was resolved.
$742,118 expected − $742,118 received = $0 variance. This example shows matching totals; supporting settlement and deposit records would be needed to confirm a real reconciliation.
$513,900 expected − $511,400 received = $2,500 shortfall. Review deposit timing, processor fees, reserves, and adjustments against supporting records before deciding the cause.
$286,730 expected − $286,730 received = $0 variance. This example shows matching totals; supporting settlement and deposit records would be needed to confirm a real reconciliation.
Merchant 1 is being designed around role-based access, protected credentials, auditability, encrypted infrastructure, and limited exposure of sensitive payment data.
Designed to give each team member access to the information and actions their role requires.
Designed to record key actions so teams can review what changed, when it changed, and who made the change.
Designed to restrict access to processor credentials and keep them out of everyday reporting views.
Designed to hide sensitive payment details in routine views while keeping operational information useful.
One dashboard for payment analytics, costs, reconciliation, and operational clarity.
Demo music: “Inspired” by Kevin MacLeod (incompetech.com). Licensed under Creative Commons Attribution 4.0. Edited excerpt, mixed beneath narration. Map outlines: Natural Earth, public domain.