Plain HTTP
Verb-based REST, predictable URLs, JSON in / JSON out. If you can curl, you can integrate.
Don't invest unless you're prepared to lose all the money you invest. This is a high-risk investment and you should not expect to be protected if something goes wrong. Take 2 mins to learn more.
Verb-based REST, predictable URLs, JSON in / JSON out. If you can curl, you can integrate.
Events such as deposit.received reach your endpoint signed with HMAC-SHA256. Failed deliveries are retried with exponential backoff.
Create keys in your dashboard under Settings, then API. Each key carries scopes and an IP allowlist, and goes in the X-Api-Key header.
Build and test against the sandbox before any real money moves. Our team issues sandbox keys, normally the same business day.
Pass an Idempotency-Key header. Retry safely; we return the original response.
Versioned and machine-readable. Generate a client in the language you use.
Paths are relative to https://api.kwiikpay.io/api/v1/partner. {customerId} is your own ID, which GET /me returns. The API reference lists every endpoint.
Every endpoint, every parameter, every error — with request and response examples.
Open reference →Introduction, authentication and your first request — start here.
Read the intro →The full machine-readable spec — generate a client in your stack of choice.
View openapi.json →Request sandbox keys; our team issues them, normally the same business day. Production access is reviewed with your onboarding.
Get keys →Integration questions answered by the people who built the API — within one business day.
Contact us →How we protect data and client money: screening, encryption and how client money is held.
See security →