Skip to content
E-commerce platforms

qualpay.com

Qualpay Payment Gateway sandbox and mock API

This document describes the Qualpay Payment Gateway API. Writes persist, data moves on a schedule and every change can fire a signed webhook.

Operations
14
Collections
-
Event types
-
Start this simulation
example request
curl https://your-qualpay.slurry.io/ \
  -H "Authorization: Bearer slurry_sim_..."

Your simulation gets its own hostname, key and IP allow-list. Built from API version 1.7.0.

What gets simulated

Collections, relationships and state machines are worked out from the spec when you start the simulation.

  • State. Creates, updates and deletes persist and show up in later reads.
  • Behaviour. Records move through their states on a schedule you control, and you can fast-forward up to 30 days.
  • Webhooks. Every change emits a signed, retried event.
  • Failure. Per-endpoint errors, latency and chaos rules, on demand.

Operations

First 12 of 14.

  • POST/ardef
  • POST/auth
  • POST/batchClose
  • POST/capture/{pgIdOrig}
  • POST/credit
  • POST/emailReceipt/{pgId}
  • POST/expireToken
  • POST/force
  • POST/recharge/{pgIdOrig}
  • POST/refund/{pgIdOrig}
  • POST/sale
  • POST/tokenize
Qualpay Payment Gateway sandbox and mock API | Slurry