This section is for card providers that Facto has already activated. Facto acts as the settlement counterparty for your card platform. Your platform signs each request, uses the Issuer API for charges and refunds, sends card events to Facto, and reconciles settlement batches.

You never hand Facto card data, and on this path Facto never calls your APIs. Facto identifies your issuer from the authenticated Provider Connection. A request body cannot select another issuer.

New card providers cannot start this integration

Existing issuers in the active state can keep using these APIs. New issuer activation always returns 409, and the Issuer API rejects any issuer that is not active. The credential type Facto can still issue works only in Sandbox, where the published service is set to replicas: 0. The code constant enforcing the freeze is LEGACY_ISSUER_ONBOARDING_FROZEN. Use this section as a reference for the existing API. For a new branded card program, contact Facto and read Stablecoin cards.

How existing card providers connect

  • Issuer API, settlement, and certification requests carry four signed headers. Facto gets the issuer from the key binding, not the request body.
  • Provider webhooks use provider-specific verification. When the normalization feature is enabled, the mounted Rain and Immersve routes convert events to the common format. Response meaning depends on the route; an Immersve authorize 200 is an authorization decision, not a receipt.
  • Production approval requires a Certification Run tied to fixed inputs and a fixed scenario catalog. The run is evidence, not the approval itself.

If you operate the branded card product and want to associate your cardholders and cards with Facto, read Stablecoin cards instead. Card providers and merchants may share one organization, but the two API groups never share identity, credentials, certification state or production approval; merchants integrate through the merchant APIs.

The Provider Connection is the trust boundary: it binds one issuer, one environment, one mode, and purpose-specific credentials before traffic reaches either side.

If Facto already activated your issuer, start with Access and credentials, then follow the Legacy Issuer API walkthrough.