Skip to content
Testnet only: a reference implementation, not a production service. Tokens and bank transfers here are simulated and have no value.
Stablecoin ReferenceSign up on Testnet
The business console

Everything a business does, on one console

The console is where a business moves money on Stellar Testnet: mint from a wire, pay, redeem, and manage counterparties, API keys and settings. Every screen comes from the same capabilities manifest as the capabilities page.

Open the console
What a business does

The console jobs, end to end

  1. Mint from a wire

    Match a bank wire to a mint and turn it into USDX in a wallet.

  2. Pay and move tokens

    Send USDX wallet to wallet, like any Stellar asset, and watch every state.

  3. Redeem to a bank account

    Send tokens to a one-time address; the burn pays out the dollars.

  4. Manage counterparties

    Add wallets and bank accounts, and prove control before money moves.

  5. Run the developer tools

    Issue API keys, register webhooks and force outcomes in the sandbox.

  6. Invite the team

    Bring teammates into the console and keep every action on record.

See it in action

Three films from the real console

Counterparties and wallet proof: add a wallet, then prove you hold its key.

Transcript

Counterparties are the wallets and bank accounts your money moves between, and every wallet is proved before use. To add a wallet, enter its Stellar address and a name. Details can't be changed after you add them. The wallet waits for proof of control. You get a challenge: a transaction that can't be submitted, so signing it moves nothing. Sign it with the wallet's key. Paste the signed challenge back. The console checks it's the same challenge, still valid, and signed by this wallet's key. It also checks the wallet on Stellar. Without a trustline for USDX, it warns that the wallet can't receive USDX yet.

Webhooks and the event log: signed events, retried and replayable.

Transcript

Webhooks send you signed events; the event log catches anything an endpoint missed. Add your endpoint's HTTPS URL, a description, and the events it should receive. Copy the signing secret now: it's shown once. Every delivery is signed with it, using HMAC-SHA256. A new endpoint starts disabled. Send a test event; when it succeeds, the endpoint is enabled. A failed delivery is retried up to ten times over 24 hours, and the event log keeps 30 days of events. Open an event to see its payload, then redeliver it to each enabled endpoint subscribed to its type.

Sandbox tools: force the outcomes you need to test, on Testnet only.

Transcript

The sandbox lets you force the outcomes you need to test: a mock wire, a failed transfer, a KYB decision. To simulate a wire, open the mock bank, pick a mint's reference and send it. The mint moves on. To test a failure, fail an open transfer. Only transfers that haven't moved tokens can be failed. Force the decision on your next KYB submission: approve, request information, or reject. And fund any Testnet address with Friendbot. These tools work on Testnet only.

Capabilities

Everything the console already does