Errors and recovery
Plan for validation failures, rejected requests, and uncertain outcomes.
Error reference status
KPPAY-specific error codes and response schemas are pending publication. Use the verified endpoint contract when implementing response parsing and retry rules.
Recovery decisions
| Failure | Integration behavior to plan |
|---|---|
| Invalid input | Identify the field and allow correction |
| Authentication failure | Check credentials and environment configuration |
| Insufficient permission | Confirm the required access before trying again |
| Timeout | Establish the operation's outcome before repeating it |
| Rate limit | Follow the documented delay and retry policy |
| Service failure | Retry only when the contract establishes it is safe |
Unknown outcomes
A network timeout does not establish that an operation failed. Before repeating an operation that can move money or create a record, use the documented lookup or reconciliation mechanism. Do not assume an idempotency header is supported.
Useful diagnostics
Record the time, environment, operation, status, and request identifier when available. Redact credentials and sensitive payload fields. Present a clear recovery action to the user rather than raw provider errors.