PROVIDER_NOT_SUPPORTED

Payment provider '‹value›' not supported


HTTP status	`422` Unprocessable Content
Retry	After fixing the cause

When it happens

The provider is not one BeeL. connects. Today only stripe is supported.

Retry

Not as is: the same request fails the same way. Fix the cause described above, then send the request again, under a new Idempotency-Key if the body changed.

Example response

When this error occurs, the API answers 422 Unprocessable Content with a JSON body of this shape:

{
  "type": "https://docs.beel.es/errors/PROVIDER_NOT_SUPPORTED",
  "title": "PROVIDER_NOT_SUPPORTED",
  "detail": "Payment provider '‹value›' not supported",
  "instance": "/v1/<resource>",
  "errors": [],
  "success": false,
  "error": {
    "code": "PROVIDER_NOT_SUPPORTED",
    "message": "Payment provider '‹value›' not supported",
    "details": {}
  },
  "meta": {
    "timestamp": "2026-05-21T10:00:00Z",
    "request_id": "4bf92f3577b34da6a3ce929d0e0e4736"
  }
}

The type URI is stable and always resolves to this page.

Message

Payment provider '‹value›' not supported

Proveedor de pago '‹value›' no soportado

Proveïdor de pagament '‹value›' no suportat

Send the request with Accept-Language: <es|en|ca> to receive the message in your preferred language.

Placeholders like ‹value› are filled in at runtime with the actual values of your request.

Other errors in this category

COMPANY_NOT_ACTIVATED_IN_ENVIRONMENT

This company is not activated in ‹value› mode. Activate it in that mode before connecting the payment provider: activation is what creates the invoice series and tax configuration that charges need