Skip to main content

Retryable

Yes

Typical status

502

What it means

We normalise every provider failure into this code rather than surfacing provider specific errors, because provider identity is never part of your integration.

Common causes

  • A provider returned an unexpected response or timed out.
  • A provider rejected a leg after accepting the quote.

How to resolve

Retry. The router records the failure against that provider’s health for the affected corridor and will prefer a different provider on the next attempt. If funds were already received, the intent moves to refund automatically.
The provider is never named in the error body. If you need to know which provider was involved for a support conversation, quote the request_id.

Example response