High Wire Ledger

Products / Ledger

High Wire LedgerReconciliation across the full payment lifecycle

Every event in the payment lifecycle is written to a ledger, then proved every day against settlement files from processors and deposits from the bank. When the numbers disagree, you hear it from us first.

A day is not closed until all three agree.

Our ledger, the processor settlement file, and the money that actually landed in the bank are matched every day. What does not reconcile becomes an exception with a reason and an owner, rather than a quiet shortfall in a payout.

High Wire ledger

Captures$128.4M
Refunds$2.1M
Fees$3.42M

Processor settlement

Gross$128.4M
Adjustments$2.3M
Interchange$2.18M

Bank deposit

ACH credits$120.8M
In transit$2.1M
Reserve held$1.24M
  • 4,219 batches matched
  • Fees agree with expected interchange
  • Deposits tie to settlement
  • 1 batch short funded, $12,480.00exception

99.94%matched · day closed 06:14 UTC

Sample figures

Balanced against an outside source, not against ourselves.

A three-way match runs daily. Our ledger, the processor's settlement file, and the money that actually landed in the bank all have to agree before a day is closed.

source 1

High Wire ledger

  • Captures$128.4M
  • Refunds$2.1M
  • Chargebacks$184.2k
  • Fees$3.42M
source 2

Processor settlement

  • Gross$128.4M
  • Adjustments$2.3M
  • Interchange$2.18M
  • Net funding$122.9M
source 3

Bank deposit

  • ACH credits$120.8M
  • In transit$2.1M
  • Reserve held$1.24M
  • Returns$38.4k
result

Matched

99.94%

4,231 batches, 12 exceptions open, day closed at 06:14 UTC

Sample figures

Every state, on one payment ID.

The ledger records the whole lifecycle, not just the sale. Each entry carries the payment ID, the merchant, the processor, and the fee breakdown, so any number on a statement can be traced back to the event that caused it.

Lifecycle eventWhat the ledger records
AuthorizationAmount, processor, MID, approval or decline reasonNo money moves yet, but the intent is recorded
CaptureCaptured amount, currency, timestamp, batch
RefundFull or partial, original payment ID, fee treatment
Chargeback and reversalCase ID, reason code, amount held, representment outcome
FeesInterchange, scheme fees, processor markup, High Wire feeExpected versus actual, per transaction
ReserveRolling or fixed, amount held, scheduled release
PayoutNet amount, rail, bank reference, arrival date
AdjustmentCorrections, recoveries, write-offs, with a reason and an owner

Exceptions come to you, with the reason attached.

Anything that doesn't match becomes a worked item with an owner, an age, and a resolution. Nothing is silently written off.

ExceptionTypeAmount
Deposit short of settlement filePSP B, batch 2026-04-22, investigating with partnerShort funded$12,480.00
Fee charged above expected interchange14 transactions, MCC 5499, recovery requestedFee variance$318.44
Refund issued twice for one orderDuplicate detected before payout, second refund reversedResolved$89.50
Chargeback reversed after representmentFunds returned, ledger corrected, statement updatedResolved$1,207.40
Payout returned by bankAccount details changed, merchant notified, retry scheduledReturned$4,212.00

Sample exception queue

What it does

  • Every lifecycle event recorded against one payment ID
  • Daily three-way match: our ledger, processor settlement, bank depositPreview
  • Expected interchange compared against what was actually billedPreview
  • Reserves, holds, and release dates tracked per merchant
  • Exceptions raised with an owner, an age, and a resolutionPreview
  • Month-end close with journal exports to your accounting systemPreview

What you get

  • Statements that tie out across merchants, agents, and platforms
  • Money you would have lost surfaced as exceptions rather than quiet shortfalls
  • A faster close, because the books are already balanced against the bank
  • An audit trail that satisfies assessors, partners, and sponsor banks
  • Fewer support tickets, since merchants can see where their money is

What you get out of it.

01Statements that tie out

Merchant statements, agent residual statements, and platform fee reports all come from the same ledger, so they agree with each other and with the bank.

02Month-end close Preview

A close checklist per entity and per processor, with journal entries exported to your accounting system as CSV or through the API.

03Money you would have lost Preview

Fee variances, short-funded batches, duplicate refunds, and missed recoveries surface as exceptions instead of quietly reducing a payout.

04One view across processors

Multiple MIDs and processors settle on different schedules and formats. The ledger normalizes them into one set of books.

05Audit trail

Every entry is immutable and traceable to a source document, which is what auditors, partners, and sponsor banks ask for.

06Reserves you can see

Rolling reserves, holds, and scheduled releases are visible to the merchant and the agent, which removes most support tickets about missing money.

Stop closing the books by hand.

Tell us what month-end looks like today, and we will show you what it looks like when every day is proved against the bank.