API and Webhook Troubleshooting
QrX API and webhook support works best when requests include clear identifiers and sanitized technical details.
Common API Issues
Wrong merchant, customer, or channel identifier.
Missing customer email or phone for verification and support flows.
Invalid amount, currency, country, or payment method configuration.
Webhook endpoint unavailable or returning a non-success response.
Duplicate order references or idempotency problems.
Incorrect environment, such as sending production credentials to a test endpoint.
What to Send Support
Send the environment, merchant or channel, order reference, QrX transaction id, timestamp, endpoint, response status, webhook event id, and sanitized request or response body. Remove API keys, tokens, signatures, passwords, and personal data that is not needed for debugging.
Webhook Retry Checks
Check whether your endpoint is reachable, returns a success status quickly, validates signatures correctly, and handles duplicate webhook events safely. Webhook consumers should be idempotent because retries can happen.
When Fin Should Escalate
Fin should escalate API issues involving credentials, security, production incidents, payment inconsistencies, webhook signature failures, or repeated integration errors.