Interactive sample · synthetic records · no account needed
A payment succeeded.
Did the credits arrive?
Inspect the same purchase in four situations. This sample runs Ropely’s reconciliation engine in your browser. It cannot change a payment, grant credits or send alerts.
400 credits short
Expected 1,000 · recorded 600 IMAGE01 / Purchase evidence
Stripe Checkout · paid
- Purchase
cs_sample_purchase- Application account
account_sample_42- Paid at
- 1 Oct 2026, 10:00 UTC
- Quantity × credit rule
- 1 × 1,000 IMAGE
- Grant deadline
- 10:15 UTC
02 / Ledger evidence
Purchase-linked transactions
grant_sample_01- 600 IMAGE
- Purchase grant recorded
- 10:02 UTC
Same purchase reference and application account. Remaining balances are not used.
Verify a correction
In a real case, inspect the source application before issuing a correction. Here, add a synthetic correction transaction and rerun the same reconciliation engine.
Scope, coverage and limitations
Test account acct_sample · ledger_sample · one paid one-time credit pack · 15-minute fulfillment window. Purchase evidence is complete through 11:00 UTC; ledger evidence is declared complete through the same time. The price rule starts 1 January 2026. No rejected rows. Synthetic declarations are not independent verification of a real source.
Engine outcome: incorrect_amount. shortfall
Downloads contain the separate ten-case specification fixture, not the edits above. Sample changes reset when you leave or reload.