SpicePay

Refunds & disputes

Returning money and fighting chargebacks across every processor from one queue.

Refunds

Refund any succeeded payment — fully or partially — from the Control Center or API. SpicePay forwards the refund to the connector that processed the original payment and tracks it to completion.

curl https://api.spicepay.net/refunds \
  -H "api-key: prd_****************" \
  -H "Content-Type: application/json" \
  -d @body.json

{
  "payment_id": "pay_V4t1RJgSy4hoBQzoqqRz",
  "amount": 500,
  "reason": "Customer returned item"
}
  • Omit amount to refund the full payment amount; multiple partial refunds are allowed up to it.
  • Pass your own refund_id for idempotency across retries of the same partial refund.
  • Refund status flows pending → succeeded (or failed, e.g. when the customer's card was closed — the connector's failure reason is surfaced on the refund detail page).
  • refund_succeeded and refund_failed webhooks keep your systems in sync.

Disputes

Chargebacks from all connected processors land in one queue under Disputes in the Control Center — no more checking three processor dashboards.

Each dispute shows:

  • Stage and status (opened, evidence_required, under_review, won, lost)
  • The respond-by deadline, sorted so the most urgent is on top
  • The full payment context: connector, authentication result, customer history

A dispute moves through these stages:

Dispute lifecycle A dispute is opened, evidence is required and submitted, it goes under review, and is resolved as won or lost. opened evidence_required under_review won lost

Responding to a dispute

  1. Open the dispute and review the reason code (e.g. fraudulent, product_not_received).
  2. Attach evidence: invoices, delivery confirmation, customer communication, 3DS authentication proof (SpicePay attaches the cryptogram/liability-shift data automatically when available).
  3. Submit — SpicePay formats the evidence for the specific processor's requirements.

Liability shift: card payments authenticated with 3-D Secure at checkout usually shift fraud liability to the issuer. SpicePay stores the authentication result on every transaction so it's available as evidence.

Preventing disputes

  • Use the Blocklist to block cards, emails, and IPs with prior fraudulent activity.
  • Enable network alerts (Verifi/Ethoca) on connectors that support them; alerts appear as pre-dispute cases you can refund before they become chargebacks.