Idempotency Support

The API supports idempotency for safely retrying requests without accidentally performing the same operation twice. This is useful when an API call is disrupted in transit and you do not receive a response.

Enable Idempotency

To submit a request for idempotent processing, send a request with the Idempotency-Key:<value> in the Header.

The <key> is a unique identifier for the message with a maximum of 64 characters. We recommend using a UUID. If you don't receive a response (for example, in case of a timeout), you can safely retry the request with the same HTTP header. If the Fundiin payments platform already processed the request, the response to the first attempt will be returned without duplication.

If you submit a duplicate request before the first request has completed, the API returns an HTTP 422 – Unprocessable Entity status with the status code REQUEST_PROCESSING: "request already processed or in progress".

Key Scope and Validity Time

Idempotency-Key are valid for a minimum period of 7 days after first submission

When retrying transactions, it is essential to use an exponential backoff strategy to avoid overwhelming the API and encountering rate-limiting issues. For more information on exponential backoff, please refer to the Wikipedia article on Exponential Backoff.