Credit Requests

This page documents the retry configurations implemented for credit requests to handle transient communication failures with external clients.

Retry Strategy & Backoff

The retry mechanism uses an exponential backoff strategy. This prevents overloading client servers when they are struggling.

• Max Attempts: 5 attempts.
• Backoff Strategy: Exponential
  • Initial Wait: 250ms before the first retry.
  • Multiplier: 2.0 (each delay is twice as long as the previous one).
  • Max Delay Cap: 4000ms (4 seconds is the maximum delay between any two attempts).

When Do We Retry?

Retries are only triggered for transient issues:

• Timeouts / Connection Drops: ResourceAccessException (client is unreachable or times out).
• Server-Side Errors: HttpServerErrorException (client returns a 5xx status code).

We do not retry on client-side errors (4xx codes like 400 Bad Request or 401 Unauthorized), as repeating the request will not change the outcome.

Feature Control

We may choose to enable or disable this feature if necessary.

Debit Requests

Look at reconciliations