409

API problem detail

Idempotency Key In Flight

Description

This problem happens when a request arrives with an X-Idempotency-Key whose original request is still being processed. DirecFunds first waits up to about 30 seconds for the original to finish and, if it does, returns that outcome. Only when the original is still running after the wait does the response become this 409. Nothing was duplicated: the duplicate never runs the operation itself.

Bank-account POST /BankAccount/{id}/$Verify reports the same situation differently: a 409 with an empty type, the title Request Still Processing, and errorCode STATE_CONFLICT. Treat it the same way.

Response title: Original Request In Progress. Response errorCode: REQUEST_IN_PROGRESS.

Experience API error bodies also carry errorCode, resolution, and traceId. Branch on errorCode, not on title or detail; see fields on every error.

How to resolve

Wait a second or two, then retry the request unchanged, with the same key and the same body, to collect the original outcome. Do not switch to a new key: that would start a second, independent operation.
Back to all problem details