Skip to main content
Every account has a set of enabled services according to its commercial agreement with CBPay. Before showing a product in your UI (or trying to use it), query the effective map:

Service catalog

What happens when a service is off

The product’s actions respond 403 service_disabled:
Important rules:
  • Reads are never blocked: you can always list and query your historical operations, balances and movements.
  • In-flight money finishes its cycle: a processing payout completes (or refunds) even if the service is disabled afterwards.
  • With cards off, card purchases stop authorizing instantly and no monthly fees are generated.
  1. Query GET /v1/services when your app loads (and cache for a few minutes).
  2. Show only the products set to true.
  3. Still handle 403 service_disabled on any action: configuration can change between your cache and the operation.
Services are enabled by your organization according to the commercial agreement. If you need a product activated (for example banking or cards), contact your CBPay administrator — the change is immediate, no redeploy needed.

EUR banking service flags

The platform exposes eur_funding for EUR-to-USDT funding and virtual_iban for optional EUR banking balances and SEPA Instant. Both are separate from the general banking capability and must be enabled explicitly when the organization uses them.
Last modified on September 17, 2026