Troubleshooting
Fast diagnosis guide for the most common Cobru integration failures.
Use this page when the integration is failing and you need a concrete diagnosis path instead of general API guidance.
Fast triage order
- Confirm environment and base URL.
- Confirm all required credentials are present.
- Inspect the exact JSON body sent to Cobru.
- Inspect the raw Cobru response.
- Check whether the hosted payment URL was constructed from
url. - Check whether callbacks are arriving and being deduplicated.
Common failure map
| Symptom | First thing to check |
|---|---|
403 on payment creation | request validation, not only auth |
400 on payment creation | payment_method_enabled serialization |
| payment page does not open | hosted URL built from pk instead of url |
| callback arrives but order not updated | webhook persistence and async processing |
| duplicate business actions | missing idempotency in webhook handler |
| payout flow unclear | verify endpoint confidence level before implementation |
Payment creation triage
Webhook triage
What support should always have
- internal order ID
- Cobru
urlslug - payment creation timestamp
- raw Cobru error body when creation failed
- raw webhook payload when a callback was received
Escalate to Cobru when
- sandbox and production differ in undocumented ways
- a legacy-documented endpoint behaves differently from the published docs
- you see sustained provider-side failures without actionable error details
Related pages
/docs/testing/docs/webhooks/docs/errors/docs/api/reference