QuataPay
Developer

Developer FAQ

The questions we see most often — bookmark this before opening a ticket.

Browse developer docs
Back to developer docs
Do I need approval before using live keys?
Yes — your merchant account has to complete KYC before live keys are issued. Sandbox keys work the moment you create the account.
Are there rate limits?
Yes: 60 requests per 60 seconds per API key and route. Beyond that you get a 429 with a Retry-After header.
How long is a payment intent valid?
60 minutes by default, or the expires_in_minutes you pass (1 to 1440). After expiry the intent is marked expired, a gateway.payment.expired webhook is sent, and the customer has to start over.
Can I issue refunds via API?
Yes — POST /api/v1/merchant/refunds. Partial refunds are supported. Refund state propagates back to the payment as `refunded` once it settles.
Is there a fixed fee or percentage?
Merchant transaction fees are configured according to the merchant's account and applicable service terms. See the public /pricing page for the fee schedule.
How are settlements paid out?
Daily, weekly, or monthly depending on your settlement preference (manage at /merchant/settlements). Withdrawals to a bank, credit union or MFI account are paid within 3 working days; payouts to MoMo and Orange Money are coming soon.
Do you support multi-currency?
XAF only at the moment.
Where do I report a security issue?
security@quatapay.com — encrypted via our PGP key on /legal/security. Don't open a public issue.

Still stuck?

Open a ticket at Developer support — include your X-Request-Id header and what you expected vs. what happened.