Check that each accepted deposit reached the customer ledger.
A deposit can be confirmed on the network while your internal ledger shows no credit. PipsClarity checks whether each eligible, attributed deposit has the matching customer credit.
PipsClarity checks outcomes. It never moves funds or creates trading accounts.
Crypto exchange assessments
Deposit awaiting acceptance
25.000000 units of a synthetic token
Waiting within SLAAccepted deposit to ledger credit
25.000000 units credited
Matched
Confirmed on the network, missing from the ledger
Custody or the network can accept a deposit while the customer ledger is still uncredited. Public chain data cannot show your internal ledger, so a block explorer cannot settle the question.
- Custody status and customer credit are separate records.
- A deposit must be tied to a customer before a credit is expected.
- The acceptance rule depends on the asset and what you agreed.
From accepted deposit to ledger credit
The check starts from a supported deposit, waits for the agreed acceptance rule and customer attribution, then looks for the ledger credit.
Supported deposit
An asset and network in scope
Required acceptance
The agreed finality condition
Customer attribution
The deposit is tied to a customer
Internal ledger credit
The customer ledger shows the credit
PipsClarity checks these outcomes. It does not perform them.
25.000000 units of one synthetic token
A deposit of 25.000000 units arrives on its stated network. The result changes only when the evidence changes.
Recorded facts
- Deposit
- 25.000000 units
- Asset
- Synthetic token on its stated network
- Acceptance rule
- As agreed for this asset
- Customer attribution
- From the exchange’s own records
- Expected ledger credit
- 25.000000 units
What PipsClarity reports
While the acceptance rule is not met
Waiting within SLAThe deposit is seen. The agreed acceptance rule is not met yet.
Accepted and attributed, no ledger credit
DiscrepancyA missing credit counts as a discrepancy only when the ledger export covers the period.
After a 25.000000-unit ledger credit
MatchedThe customer ledger shows the matching credit.
If a later reorg changes the evidence
OpenA separate review case opens. The earlier resolution stays on record.
Keep these separate
Amounts are never added up across networks or assets.
A ticker alone is not enough
The same ticker can exist on more than one network. Each asset is registered with its exact identity and scale, and amounts are never added up across networks or assets.
Registered asset, synthetic
- Network
- Synthetic test network
- Identity
- Contract address or native asset, as registered
- Scale
- 6 decimal places, for example 25.000000
- Source reference
- Transaction reference from the custody or network export
What PipsClarity can flag for exchanges
Every finding keeps the records, the rule version, the time of the check and the coverage behind it.
Accepted deposit, no credit
Custody or network data shows acceptance, and the customer ledger shows no matching credit.
Unclear customer
The deposit cannot be tied to one customer with the records supplied.
Not enough acceptance evidence
Confirmation or finality records do not support a conclusion yet.
Reorg exposure
Later evidence changes a deposit that was already credited. It gets its own review case.
What it takes to check this workflow
Agreed exports from custody or network sources and from your internal ledger, with the period each one covers. Public chain data alone cannot prove a customer credit.
- Custody or network deposit data
- Internal customer ledger
- Customer attribution records
- Asset register with network, contract or native identity and scale
- Acceptance or finality rule for each asset
- Coverage details for each export
Pilot scope is one agreed workflow and a set evidence window. Other routes stay out of scope unless agreed and tested.
Questions from crypto exchanges
How does an exchange check that every accepted deposit was credited?
Compare custody or network deposit records with customer attribution and the internal ledger for the same period. PipsClarity does this from agreed exports and flags accepted, attributed deposits with no matching ledger credit.
Is a confirmed transaction treated as credited?
No, network confirmation alone doesn’t prove a customer credit. The check is whether the internal customer ledger shows the matching credit.
How is an asset identified?
By its registered identity. That means the network, the contract address or native asset, and its scale, for example 6 decimal places. A ticker alone is not enough, because the same ticker can exist on more than one network.
What happens after a reorg?
If later evidence changes a deposit that was already credited, a separate review case opens. The earlier resolution stays on record.
Does PipsClarity hold keys or move assets?
No, PipsClarity doesn’t hold private keys, move assets or credit customer ledgers. It checks the records you authorize, and your team makes every fix in your own systems.
See the crypto workflow with synthetic data
Request a demo. The form fills in your sector from this page.