ChargeflowDocs
Log in
For MerchantsFor PlatformsAPIResources
Resources

Error codes reference

Lookup table of HTTP status codes and EaaS-specific error codes returned by the Chargeflow API, with causes and resolutions.

A quick lookup of the codes the Chargeflow API returns. For how to handle and retry each status - which are retry-safe, how to back off, and how to diagnose a 403 - see Error handling.

HTTP status codes

StatusNameMeaning
400Bad RequestMalformed syntax or incorrect parameters.
401UnauthorizedMissing or invalid API key (or bad HMAC signature, if enabled).
403ForbiddenValid key without permission for the resource, or an invalid key. Diagnose which →
404Not FoundThe resource or URL does not exist.
429Too Many RequestsRate limit exceeded.
500Internal Server ErrorUnexpected server error.
502Bad GatewayUpstream/gateway error.

For which of these are safe to retry and how, see Error handling → retry safety.

EaaS-specific error codes

Error CodeDescriptionResolution
422_dispute_invalid_stateDispute must have status needs_responseCheck dispute status before generating evidence
409_generation_in_progressEvidence generation already in progressUse idempotency-key header to avoid duplicates
404_*_not_foundResource not foundVerify the ID in your request
403_eaas_not_enabledAPI key not entitled to EaaSContact your account manager
504_generation_timeoutGeneration timed outRetry the request

Next steps

Error HandlingHow to handle and recover from each status codeRate LimitsWhat to do when you hit a 429AuthenticationFix 401 and 403 responsesSupportWhat to include when you contact the team
Was this page helpful?
ToolsPreviousChangelogNext

On this page

HTTP status codesEaaS-specific error codesNext steps