Read the response body
API errors use an error object with code and message. HTTP 400 generally means malformed input; 401 means credentials are missing or invalid; 403 means the operation is disallowed; 404 means the resource is not available to this account. Show a helpful message without exposing credentials or another merchant’s records.
Conflicts and throttling
HTTP 409 can mean an existing registration, an idempotency conflict or an invalid test state transition. Correct the request instead of automatically looping. HTTP 429 means the registration or login attempt limit was reached. Back off and let a person retry later.
Network errors
A dropped connection or a server error may leave the outcome uncertain. For sandbox intent creation, retry with the same idempotency key. For live payment flows, reconcile the purchase and receipt records before provisioning again. Preserve diagnostic references without including secrets.
Support evidence
Share the endpoint, time in UTC, HTTP status, safe request reference and a short description of the expected result. Remove passwords, bearer keys, signing secrets, full raw receipts and unrelated personal information. Support is available at contact@ispbillingpay.com.
KEEP EXPLORING