Facto Developers

Choose your integration

Choose a Merchant or Stablecoin Card Provider (SCP) integration path below. If your cards are issued through Interlace, Rain, or Wasabi, start with Card Issuer Provider (CIP) integration: every CIP connects to the same normalized Card Connect standard through a dedicated adapter, and each CIP page states current adapter availability. Every partner role uses its own credentials and APIs. Not sure where to begin? Read First steps.

I'm a merchant

Accept Facto Pay

Offer Facto Pay, integrated with the Facto Connect SDK: link customer accounts, check payment readiness, and submit idempotent charges from your backend.

Merchant integration

I'm a Stablecoin Card Provider (SCP)

Connect a branded card product

Connect cardholders through Card Connect using a Program Connection and environment-scoped credentials.

SCP integration

Getting access

Sign in with your Partner identity through Partner Workspace single sign-on to read the guides available to your organization and assigned role permissions. Opening any protected guide prompts you to continue via Partner Workspace, where your active memberships determine which role tracks you can read.

For the Test Partner registration, organization, invitation, and first-app workflows, start with Partner Workspace. For external Sandbox access, follow the onboarding instructions provided by your Facto contact.

A single organization can hold multiple partner roles, but credentials, environments, acceptance status, and settlement configuration remain isolated per role.

Merchants

  1. Enable mandated payments. In Partner Workspace, complete the Sandbox opt-in required to create a mandate-capable merchant app.
  2. Create a Sandbox app and issue its first credential. Facto never sends merchant secrets out of band. Create the app in Partner Workspace and rotate its initial client secret yourself—the plaintext secret is shown only once.
  3. Complete integration acceptance for Production. Production requires a separate review and approval; Sandbox apps and credentials never carry over.

Stablecoin Card Providers (SCP)

Facto exposes the Card Connect API per environment. Before calling these endpoints, ask your Facto contact to provision an active Program Connection, issue server credentials for the target environment, and enable the operations your SCP needs.

Start with Stablecoin cards. Sandbox and Production use separate credentials and configuration, and Production requires dedicated approval.

See Access and credentials for environment access stages, common setup reason codes, and how show-once secrets are issued, rotated, and revoked.