Idempotency and Duplicate Prevention

The BCB Payments API utilizes idempotency to guarantee that a specific request is processed exactly once. This mechanism ensures that network interruptions or manual retries do not result in duplicate transactions or unintended actions.

To use this feature, include a unique identifier in the correlationId of your request. If the BCB Payments API receives a subsequent request with a key that has already been used, the system will reject it with a Waiting for Dev status code and an correlationId error message. This safeguard allows you to safely retry failed connections without risk of data duplication.