Troubleshooting
Common errors, what causes them, and how to fix them.
Common errors
| Error | Likely cause | Fix |
|---|---|---|
402 Payment Required | The request did not include a valid payment. | Read the 402 response, create a payment, and retry the same URL. |
Unknown payment protocol | The URL segment does not match an available channel. | Use one of the protocol segments shown in the dashboard for the project. |
Payment channel is not configured | The project does not have that channel enabled. | Enable the channel in the dashboard, or switch to a configured protocol URL. |
Payment resource URL does not match | The client signed one URL but requested another. | Sign the exact URL, including path and query string, that will be retried. |
Usage limit exceeded | Your team reached its plan limit for the current period. | Review usage in the dashboard, then upgrade or wait for the next period. |
Getting help
Still stuck?
Capture the request URL, protocol, response status, and response body from the failed call. Those usually show whether the problem is channel setup, client signing, backend routing, or plan limits.