ResourcesSupport
Stuck on an integration issue? Reach the developer support team through the contact form or by email at developersupport@qrpay.com.
Before you contact us
Most integration problems are identified by the response envelope itself, so two minutes here often saves a round trip:
- Look up message.code in Response codes — e.g. 400 · The amount must be a string. or 403 · Requested with invalid token! both have documented fixes.
- Walk through Error handling and the FAQ — token expiry (600 seconds) and key mode (SANDBOX vs PRODUCTION) cover a large share of reports.
- Check your key’s mode and currencies in the merchant panel — a SANDBOX key never moves real money, and you can only charge currencies enabled on your account.
What to include in a report
The faster we can reproduce it, the faster we can fix it. Please send:
- The endpoint and method — e.g. POST /payment/create — and whether the key is in SANDBOX or PRODUCTION mode.
- The full response envelope — message.code, the success/error array and type, exactly as returned.
- Identifiers — the payment token and, if the payment completed, the trx_id from the return-URL payload.
- The timestamp of the request, including your timezone.
Never share your secret key
- Support will never ask for your secret_id, an access token or a password — redact them from any logs you send.
- If a secret key has been exposed, regenerate it in your merchant panel before contacting us.
Useful links
Developer