Book a demo
The product The platform tour

Every API a finance team would have asked for.

Reparpay is six modules wired into a single double-entry ledger — payments, refunds, disputes, ledger, fraud and developer surface — designed so revenue stops leaking on its way to your bank account.

01 Payments core

A charge API that already knows the rest of the story.

One call authorises, scores fraud, indexes evidence, opens the ledger journal entry, and pre-positions the dispute response template — all under a single round-trip. The dispute desk doesn't start from zero a year later; it inherits everything.

  • Cards — Visa, Mastercard, Amex, JCB, UnionPay, Discover, Cartes Bancaires, Bancontact, Maestro.
  • Wallets — Apple Pay, Google Pay, Klarna, PayPal, Bizum, Twint, MB Way, GrabPay.
  • Bank rails — SEPA Instant, SEPA, BACS, ACH, FedNow, Pix, UPI, Faster Payments, Interac.
  • Network tokens — saved cards travel as tokens, not PANs, with automatic credentials-on-file lifecycle.
POST /v1/charges// idempotent · live key
{
  "amount": 4290,
  "currency": "eur",
  "customer": "cu_3F2A",
  "source": "tok_visa",
  "evidence": {
    "receipt_url": "https://...",
    "shipping_proof": "shp_91"
  },
  "on_dispute": "auto_respond"
}
02 Dispute desk

A response queue that runs without you.

Reparpay's dispute desk treats a chargeback as a queue event, not a panic email. The original charge arrives at the queue with its evidence pre-indexed; an underwriter-grade response is composed, formatted to network spec, and filed before the deadline counter is even visible to your team.

  • 74% average win rate — measured across 12,400 customers, vs a 36% industry baseline.
  • Per-network awareness — Visa CE 3.0, Mastercard Collaboration, Amex Inquiry — each rebuttal speaks the right format.
  • Plain-language rules — "auto-respond if delivery proof exists and refund window closed" — written in English, not regex.
  • Outcome ledger — every dispute, won or lost, becomes a journal entry your CFO can audit.
WON ch_91a · product not received + € 4,820 2h
FILED ch_91b · duplicate processing € 1,290 3h
WON ch_91c · credit not processed + € 312 5h
WON ch_91d · service not as described + € 1,140 8h
03 Refund engine

Refunds that cannot overrun.

The refund engine binds every credit to a hold account. The policy rails prevent the duplicate refund, the over-refund, the not-allowed-yet refund and the partial refund on a fully captured charge. Customer service stops being the place that loses you money.

  • Hold accounts — ring-fenced balances by SKU, region or campaign.
  • Schedule & revoke — refunds can be queued for 14 days and cancelled if the dispute window closes safely.
  • Partial & credit — line-item refunds, account credits, gift-card conversions, with full audit trail.
  • Cross-rail — refund a card charge as bank credit or wallet balance when the original card is gone.
refund.request hold.balance refund.settled € 142.40 € 8,420.10
04 Ledger

Double-entry, and proud of it.

The ledger is the product, not a side effect. Every charge, fee, dispute, refund and transfer writes its own journal entry, in real time, against accounts your finance team can configure. The reconciliation file is generated nightly and is the file your auditor opens first.

  • Per-entity ledgers — subsidiaries, brands and marketplaces, each with their own chart of accounts.
  • Multi-currency at the entry — FX rates locked at booking time, with revaluation runs at month-end.
  • Exports — NetSuite, Sage, QuickBooks, Pennylane, Datev, BC365 — pre-formatted, signed and immutable.
  • Closing — daily close in 8 minutes median, with full audit log down to the keystroke.
Journal · entry je_8a4c12
Dr 4012 — Card receivable € 4,290.00
Cr 7020 — Sales revenue € 4,005.84
Cr 4452 — VAT collected € 284.16
Dr 6175 — Network fees € 8.20
Cr 4012 — Card receivable € 8.20
Booked 2026-05-14 08:14:01 UTC · idempotent
05 Risk & fraud

Score every move, tune in English.

Network-of-networks

A risk model trained on €240bn of pseudonymised flow from 12,400 merchants. A new fraud pattern at one customer becomes a signal across the whole network within 8 minutes.

Plain-language rules

"Block if IP region differs from billing country AND email domain is < 30 days old AND amount > €400" — written exactly like that, with version history and per-rule outcome graphs.

3DS only when it helps

Reparpay routes 3DS dynamically — applied where it lifts authorisation and waived where it tanks conversion. The before/after lives in the dashboard.

Six modules. One platform.

Book a 30-minute walkthrough with an engineer who's wired the platform into production. We'll model your last quarter against ours, and send the numbers within a working day.

Book a walkthrough Read the docs