Platform / Consolidated Reporting

Every processor, one set of numbers.

Running four providers means four portals, four file formats, and four versions of the truth. SoniqPay normalizes every transaction, fee, refund, chargeback, and settlement into a single ledger — queryable in the dashboard, exportable to your warehouse, and reconciled to what actually landed in the bank.

Request access See the API

Ledger scope: All connected processors
Reconciliation: Transaction to settlement
Access: Dashboard, API, scheduled export
Hierarchy: Merchant and sub-merchant

How it works

Consolidated Reporting, end to end.

Four stages, each observable in the dashboard and addressable over the API.

Step 1

Normalize

Every processor's file format and code set is mapped to one schema on ingest.

Step 2

Reconcile

Authorizations are matched to captures, settlements, fees, refunds, and disputes.

Step 3

Analyze

Approval rates, decline reasons, cost per transaction, and recovery — sliced by any dimension you route on.

Step 4

Distribute

Scheduled exports to your warehouse, or pull the same data through the reporting API.

For platforms

Your sub-merchants get their own view, not a spreadsheet you maintain.

Nested merchant structures are a first-class object, not a workaround. Set what a sub-merchant can see and do, brand the dashboard as yours, and let them self-serve the reporting your support team currently assembles by hand every month.

Nested hierarchyMerchants, sub-merchants, and groups with inherited settings and scoped visibility.

Granular permissionsRole-based access down to individual report types and data fields.

Branded as yoursYour brand, your domain — SoniqPay does not appear in front of your merchants.

Report	Contents
Transaction ledger	Every attempt with route, score, outcome, fees, and linked events
Settlement reconciliation	Batch-level match of expected versus received, with variance detail
Approval analytics	Approval and decline rates by BIN, issuer, route, geography, and amount
Dispute register	Chargebacks by reason code, stage, representment status, and coverage
Recovery attribution	Volume recovered by failure type and recovery method

Capabilities

What you get.

Everything below ships as part of consolidated reporting — no separate module, no separate contract.

Unified transaction ledger

One record per transaction with every event attached, regardless of which processor handled it.

Settlement reconciliation

Match what you were told you earned against what actually arrived, per batch.

Decline analytics

Approval rate by BIN, issuer, geography, route, and amount band — with the codes behind it.

Cost visibility

Effective cost per transaction and per route, so routing decisions can weigh economics.

Merchant hierarchy

Platforms see the portfolio; each sub-merchant sees only their own, with the access controls you define.

Warehouse-ready exports

Scheduled CSV and Parquet drops, or an API your data team can point a job at.

Rest of the stack

Works better with the pieces around it.

Each component is independently useful, but the value compounds when they share a decision path.

Bring your own MID. We will bring everything else.

Early access is opening to platforms running real volume. Tell us your stack and we will tell you plainly where the technology moves your numbers.

Request access Read the API docs