Getting started

From zero to a running synthetic-disputes sandbox in five minutes.

  1. Sign up. Use any email address you control — the portal sends a six-digit verification code via Envoi, and every route stays locked behind a /verify-email gate until you enter it. Optional company name is captured on the form and surfaces in the sidebar / top bar.
  2. Generate a starter dataset. Open the Dev panel from the sidebar and run Generate. Pick a transaction count (up to 5,000), dispute rate (0–1), currency, and a time range in days. The generator emits transactions, disputes, evidence-required records, and the matching payment-event timeline in one batch.
  3. Walk a dispute end-to-end. Open the Disputes list and pick a row with status evidence_required. You have three options:
    • Challenge. Add evidence (upload a file, then finalise the record with a kind: receipt, shipping proof, communication, refund policy, service documentation, or other), then submit. Status moves to under_review.
    • Accept. Mark liability and move on. Status moves to accepted; the disputed amount is debited.
    • Ignore. Let the response window expire. The hourly background job flips the status to expiredonce respondBy is past.
  4. Advance the lifecycle.Don't want to wait for the hourly cron? The Dev panel's Advance lifecyclebutton runs the same job on demand, expiring overdue RFIs and evidence-required disputes and ruling on under_review disputes whose 55-day issuer window has elapsed (~60% won / ~40% lost).
  5. Export a report. The Reports page lets you queue a transactions or disputes CSV report. The portal downloads the file through a short-lived presigned URL.

What you should know upfront

  • Everything is synthetic.No real card networks, no real money movement. Reset state from the Dev panel any time — it wipes your tenant's synthetic data and leaves the account itself untouched.
  • Two surfaces, one product. The portal and the API (/v1/*) hit the same models. Your agents can click through the UI like a human or call the API directly — same data, same events, same audit trail.
  • RBAC included. Owner accounts have full access. Create synthetic accounts from the Team page with one of: full access, disputes-only, reports-only, or view-only.