- Do I need approval before using live keys?
- Test keys work as soon as you create the account and the owner creates one in Developer, API keys. Complete the verification the merchant panel asks for before you take live payments; a suspended merchant's keys are refused with 403.
- 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?
- Not with an API key yet. Merchants make refunds in the merchant panel, which supports partial refunds. There is no refund endpoint for API keys and no `refunded` payment status.
- 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.