Sandbox self-serve
Set up your Stablecoin Cards program in the sandbox — unlock, register, connect page, and binding admission — all without a Facto approval step.
Everything in the sandbox is self-serve. From the moment you sign in you can register a Card Program, point Facto at your hosted connect page, and open binding admission yourself. Facto operations only provisions the account and reviews production graduation — nothing in this walkthrough waits on a ticket.
The workspace re-authorizes ownership and environment on every call, so these steps grant no standing power: a sandbox program moves no real funds, and production admission always stays with Facto.
Prerequisites
| Facto configures | You do, self-serve |
|---|---|
| Your Partner account and Stablecoin Cards membership | Register a sandbox program |
| Production graduation (a separate, reviewed request) | Set the hosted connect page URL |
| Open sandbox binding admission |
Walkthrough
Open Stablecoin Cards
Sign in and open Stablecoin Cards from the sidebar. The workspace is unlocked for your membership already — there is no access request to file.

Register a sandbox program
Enter a program code and a display name, then register. The program is
created immediately with status: active and both admissions closed — no Facto
approval step in sandbox.

Set your hosted connect page URL
Register the page Facto's cardholder popup may open. Facto navigates only to
this exact URL. Use https://, or a loopback http://127.0.0.1 / http://localhost
address while testing locally. Clearing the field removes it.

Open sandbox binding admission
New programs start with admission closed. Opening it is an explicit switch: acknowledge that no real funds move in sandbox, then confirm with your password (a recent re-entry is required). Authorization admission is never opened from this surface, and production admission stays with Facto.

Watch your sandbox from Home
Home is your sandbox at a glance — programs, open admissions, connect pages set, and team members. It reflects real server state, and it surfaces the single next step whenever one is outstanding.

What stays with Facto
Self-serve stops exactly where money and third parties begin:
- Production — every production capability, including production admission, is a separate reviewed request. Sandbox self-serve never touches it.
- The binding runtime — opening admission makes a program bindable; the program-scoped binding runtime is enabled separately per environment.
- Reconciliation — settlement profiles and reconciliation cases live with the finance collaborator persona. Invite one from Team to review them.
Next
- Connection flow — how the cardholder selects and approves cards on your connect page.
- Cardholder binding — the program-scoped, opaque binding outcomes you can read back.