Check that each payment became the right credit or account.
PipsClarity is an operational reconciliation service for forex brokers, prop firms and crypto exchanges. It compares records from the systems you already use, applies your rules and keeps the evidence behind every result.
PipsClarity checks outcomes. It never moves funds or creates trading accounts.
Assessments
Instructed transfer to trading account A
Forex broker, wallet to trading account
DiscrepancyUSD 600 remaining
Paid order awaiting account
Prop firm, paid order to account
Waiting within SLADeposit credited to customer ledger
Crypto exchange, 25.000000 units
MatchedDeposit outside the covered interval
Crypto exchange, gap in the ledger export
Insufficient evidence
Reconciliation for forex brokers, prop firms and crypto exchanges
PipsClarity is built for the operations team at the broker, prop firm or exchange, not for its traders. Pick a sector to see the steps it checks.
Forex brokers
Payment, wallet credit, transfer instruction and trading account credit.
Payment received
The provider confirms the payment
Wallet credit
The wallet journal shows the funds
Explicit transfer instruction
The client instructs an amount to trading
Trading credit
The trading record shows that amount
PipsClarity checks these outcomes. It does not perform them.
Prop firms
Paid order, purchased entitlement and the account that should match it.
Paid order
Order and payment records
Purchased entitlement
Product, size, stage and platform
Account provisioning evidence
An observed account record
Verified account match
The account matches the entitlement
PipsClarity checks these outcomes. It does not perform them.
Crypto exchanges
Attributed deposit, acceptance rule and the credit on the customer ledger.
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.
Paid is not the same as delivered
A payment can land in one system while the outcome it paid for is still missing in another. Often the first sign is a customer asking support where their money or account went.
- A payment reaches the broker’s wallet before the client asks to move part of it to a trading account.
- A prop firm order is paid while the right challenge account is still missing.
- A crypto deposit is confirmed on the network while the customer ledger shows no credit.
Paid prop order awaiting account access
Order and payment records
Order paid.
USD 100
Purchased entitlement
Evaluation account, USD 10,000 simulated notional.
Account provisioning records
No matching account record in the covered interval.
OutcomeDiscrepancy
The expected outcome is the right account, not a cash amount.
Five steps from agreed workflow to checked outcome
1
Agree the workflow
Name the legal entity, the sources, the account mappings, the timing rules and the outcome to check.
2
Send records
Share agreed CSV or JSON exports from authorized systems. We validate each file before it is used.
3
Review outcomes
Each expected outcome gets an assessment. It matched, it is still waiting, it differs or it lacks evidence.
4
Investigate cases
When a rule calls for it, a case holds the evidence, the owner and the notes.
5
Check later records
You fix the issue in your own systems. New records show whether the outcome is now supported.
What your operations team sees
A list of assessments, a case with its evidence trail, and what each source covers.
Current assessments
Wallet funding
Policy: payment to wallet credit
MatchedInstructed transfer to trading account A
Policy: instruction to trading credit
DiscrepancyUSD 600 remaining
Paid order to matching account
Policy: order to provisioned account
Waiting within SLADeposit with two candidate customers
Policy: deposit to ledger credit
Ambiguous matchDeposit outside the covered interval
Policy: deposit to ledger credit
Insufficient evidence
Case detail
Instructed transfer to trading account A
AssignedUSD 600 instructed. No matching trading credit in the covered interval.
Transfer instruction
To trading account A
USD 600
Trading credit
No matching record yet
Wallet journal
Registered export source
- Covered interval
- 1 Nov 2026 00:00 to 7 Nov 2026 23:59 UTC
- Exported
- 8 Nov 2026 06:10 UTC
- Known gaps
- 4 Nov 2026 02:00 to 05:00 UTC. A missing export does not prove a missing credit.
Six outcomes, in plain words
An assessment can match, still be inside its allowed time, need a closer look or lack enough evidence. Nothing is forced into pass or fail.
The evidence meets the rule.
The rule still allows time, or the record is waiting to become eligible.
A difference or a missing outcome needs review.
More than one record could fit, so there is no firm match.
The records or their coverage cannot support a conclusion.
The workflow or asset is outside the rules in scope.
You stay in control of your systems
Authorized records only
PipsClarity works from the records you approve for one workflow. The public form never asks for passwords, trading logins, private keys or customer lists.
Access by workspace
Each client sees only its own workspace and legal entity records. Your traders and depositors appear in the records. They never become PipsClarity users.
You make the changes
PipsClarity checks and reports. It does not send money, place trades, create trading accounts or hold private keys. Your team makes every fix in your own systems.
Start with one workflow and a set evidence window
A scoped review starts with one agreed workflow and a set period of records. A standard pilot is a fixed USD 2,500. Our team guides the first reviews, so you don’t need a hosted account to start.
PipsClarity is at pilot stage. Every example on this site uses synthetic records.
A scoped pilot, step by step
Demo request
Tell us your sector and the workflow you want to check.
Fit review
A person on our team reads your request.
Written scope
One workflow, a set evidence window and an approved way to send data.
First data review
We validate the agreed exports and check them against your rules.
Findings meeting
We walk you through each finding and the records behind it.
Follow-up check
Later records show whether each outcome is now supported.
Questions teams ask first
What is PipsClarity?
PipsClarity is an operational reconciliation service for forex brokers, prop firms and crypto exchanges. It checks whether each payment or deposit led to the outcome it should. That might be a trading credit, a matching account or a ledger credit. It keeps the records behind every result, and it is at pilot stage.
How is this different from payment reconciliation?
Payment reconciliation checks that the payments in your records match what your providers report. PipsClarity checks the step after that. It asks whether each payment became the trading credit, the account or the ledger credit it should have, using records from every system involved.
What data is needed?
Agreed CSV or JSON exports from the systems in one workflow, plus the account mappings and the time period each export covers. The exact list depends on the sector and goes into the written scope.
Does PipsClarity replace our payment, CRM or trading systems?
No, it works next to them. It compares their authorized records and keeps the evidence behind each finding. Your systems stay the source of truth and the place where fixes are made.
Do you connect live to our providers?
Not at the start. The starting method is agreed CSV or JSON exports from authorized systems. A live connection is shown as verified only after that vendor and version pass acceptance tests.
Who gets access?
Only approved people at your firm, inside your own workspace and by role. Your traders and depositors appear in the records. They never become PipsClarity users.
What counts as resolved?
A case counts as resolved only when later records support the outcome. A case closed by hand is recorded as a team decision. It is not proof that money or account access arrived.
See it on a workflow like yours
Request a demo and tell us which workflow you want to check. The demo uses synthetic data, so you don’t share anything to see it.