Error Handling

Map HTTP codes to playbooks

429 responses require respectful backoff; 5xx responses may be retried with jitter; malformed requests (4xx validation) should not be retried blindly.

Each code path should have an owner on-call and a customer-visible status if user journeys are impacted.

Never silent-fail screening

If a check cannot complete, route to manual review or halt the transaction according to your policy—document which path applies.

Silent continuation is the highest-risk engineering anti-pattern in compliance integrations.