Errors

SenteRail errors should guide your integration toward a safe next action. Avoid automatic retries unless the failure is retryable and your request uses a stable idempotency key.

Common Responses

Status	Meaning	Next action
400	The request is malformed or missing data	Fix the request before retrying
401	The credential is missing, expired, or wrong for the environment	Check the key, token, and environment
403	The account does not have access to the requested product or action	Confirm account enablement with SenteRail
404	The route or reference is unavailable in this environment	Check the path and account context
409	A duplicate or conflicting request exists	Reuse the idempotency key or inspect the original request
422	The request is syntactically valid but cannot be processed	Fix the business input
429	The integration is sending too many requests	Back off and retry later
5xx	SenteRail or an upstream dependency returned an unexpected error	Retry only with idempotency and alert your owner

Retry Rules

• Retry network timeouts with the same idempotency key.
• Do not retry validation failures until you change the request.
• Do not create a new payment reference just to bypass a conflict.
• Log the SenteRail reference and your own order or member reference together.

Customer Support Escalation

When you escalate an issue, include the environment, request reference, idempotency key, event ID if relevant, and the timestamp. Do not include full API keys, secrets, or unnecessary personal data.