Facto Developer Docs
Integrate Facto as a merchant, a card provider, or a card program.
Facto Developers
Choose your integration
Merchant and Card Program integration guides are shown here. Card provider documentation is temporarily hidden because new provider onboarding is closed. Each role uses separate credentials and APIs. If you are unsure, start with First steps.
I'm a merchant
Accept Facto payments
Link a customer with Facto Connect, check payment readiness, and submit idempotent payments from your backend.
I'm a card program
Connect a branded program
Connect cardholders through the Engine with a Program Connection and credentials for the environment you are using.
Getting access
To read the guides, use an independent Docs account. There is no signup page. Ask your Facto contact for a Test Docs login, then sign in at test-docs.facto.to. The initial password reminder can be skipped so you can start reading. Your Partner password and permissions are separate.
For the Test Partner registration, organization, invitation, and first-app flows, start with Partner Workspace. For external Sandbox access, follow the instructions confirmed by your Facto contact.
One organization can hold several roles, but credentials, environments, acceptance and settlement never flow from one to another.
Merchants
- Enable mandated payments. In the Partner Workspace, this completes the Sandbox setup needed to create a merchant app.
- Create a Sandbox app and rotate its first credential. Facto does not hand merchants credentials. You create the app in the Partner Workspace and rotate in the secret yourself, and it is shown once.
- Pass integration acceptance for production. Production is a separate approval, not a promotion, and nothing carries over from sandbox.
Card programs
The Card Program Connect routes are implemented in the Engine. Before you call them, ask your Facto contact to configure an active Program Connection and server credential in the target environment, then enable the APIs your program will use.
Start with Stablecoin cards. Sandbox and Production use separate credentials and configuration. Production requires its own approval.
Access and credentials covers the three access levels, common setup errors, and how every secret is shown once, rotated and revoked.