Verified BursaPay workflow: Interpret validation, authentication, permission, rate-limit and business errors returned by the gateway.
1. Overview & Purpose
Gateway responses use structured error identifiers so client applications can distinguish malformed requests from authorization, resource and business-state failures.
2. Requirements & Setup
Clients should inspect HTTP status and the returned error code/message rather than parsing human prose only.
3. Step-by-Step Workflow
- Read the HTTP response status.
- Extract the machine-readable error code.
- Map expected errors to application behavior.
- Log a safe correlation/reference value for unexpected errors.
4. Rules & Troubleshooting
Do not retry validation or permission errors blindly. Retry only errors that are explicitly transient.
5. Verification & Next Steps
Keep a small error-mapping layer in the integration so response handling remains consistent.