Check that each paid challenge delivers the right account.
PipsClarity checks that a paid order leads to the right entitlement and an account that matches it, whether you call it a challenge or an evaluation.
PipsClarity checks outcomes. It never moves funds or creates trading accounts.
Prop firm assessments
Paid order to matching account
Fee USD 100 for a USD 10,000 simulated evaluation
DiscrepancyAccount not observed
Approved reward payout
Separate flow, USD 250
Waiting within SLA
Payment and account access are separate steps
A prop firm order can be paid while the right challenge account is still missing. The order, the entitlement and the account sit in different systems. The trader sees only that the login has not arrived.
- The fee paid and the simulated account size are different facts.
- The expected outcome is an account that matches what was bought.
- A reward is a separate matter from the purchase.
From paid order to the matching account
The check follows the purchase to the account. It asks what was paid for and what should exist, then looks for an account that matches.
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.
A USD 100 fee for a USD 10,000 simulated evaluation
A USD 100 fee buys an evaluation with USD 10,000 in simulated account size. These are separate facts. The expected outcome is the right account, not USD 10,000 in cash.
Recorded facts
- Order fee
- USD 100, paid
- Product
- Evaluation account
- Account size
- USD 10,000 simulated notional
- Stage and platform
- As purchased
- Account type and reference
- As the agreed source records give them
What PipsClarity reports
Paid order to matching account
DiscrepancyNo account was observed for this purchase. This opens an operational case.
After later account records
Verified resolvedThe observed account matches what was bought.
Keep these separate
A USD 100 fee for a USD 10,000 simulated account does not create a USD 9,900 cash gap.
What PipsClarity can flag for prop firms
Every finding keeps the records, the rule version, the time of the check and the coverage behind it.
Missing account
The order is paid, and no matching account is observed.
Wrong entitlement
An account exists, but its product, size, stage or platform differs from the purchase.
Possible duplicate account
More than one account could match the same order. It is flagged for review.
Late access
The account appears after the agreed window.
Rewards are checked as their own flow
An explicitly approved reward is checked against payout records. A reward is never assumed from the purchase of a challenge. If the reward flow is in scope, it has its own payout expectation and case trail.
Reward payout, a separate flow
Approved reward
Explicit approval record
USD 250
Payout record
Expected under the reward rule, not the purchase rule.
OutcomeWaiting within SLA
What it takes to check this workflow
Agreed exports from the order, payment and account systems, with the period each one covers.
- Order and payment records
- Purchased entitlement, with product, account size, stage and platform
- Account provisioning records
- Account type and reference mappings
- Approved rewards and payout records, if the reward flow is in scope
- Coverage details for each export
Pilot scope is one agreed workflow and a set evidence window, starting from exports. The reward flow is optional and agreed separately.
Questions from prop firms
How can a prop firm check that every paid challenge got an account?
Match each paid order with the entitlement it bought, then find the account your platform created for it. PipsClarity does this from agreed exports and flags paid orders with no matching account, or with an account that differs from what was bought.
Is the simulated account size treated as money owed?
No, the fee paid and the simulated account size are separate facts. The expected outcome is the right account, not a cash credit.
Does PipsClarity create the missing account?
No, PipsClarity doesn’t create trading accounts. Your team sets up the account in your own systems, and later account records show whether the entitlement is now matched.
Are rewards checked?
Only if the reward flow is in scope. An explicitly approved reward is checked against payout records as its own flow. A reward is never assumed from the purchase of a challenge.
What counts as resolved?
A case counts as resolved only when later records show an account that matches the agreed entitlement. A case closed by hand is recorded as a team decision, not as proof of account access.
See the prop workflow with synthetic data
Request a demo. The form fills in your sector from this page.