Skip to main content

Fiatsend Console

Fiatsend Console is the business workspace for teams that collect payments and send payouts with Fiatsend. Use it to manage your organization, connect a Stellar wallet, collect payments (payment links, invoices and website checkout), fund and hold balances, run single or batch payouts, and track settlement status.

What this guide covers

This page is the operator guide for Console. API credentials, request formats, and webhooks live in the Developer Documentation.

Typical Uses​

  • Set up and manage your business account (sandbox → production).
  • Connect a Stellar wallet and collect payments: payment links and QR codes, branded invoices with automatic receipts, and checkout on your own website.
  • Accept Fiatsend checkout, mobile money and bank transfer, and choose who pays the fee.
  • Fund your balance with USDC or USDT and see deposits credited automatically.
  • Create single and bulk Stellar payouts (including mobile-money recipients).
  • Review payout activity, on-chain references, and local settlement status.
  • Manage team access, API keys, webhooks and notification preferences.

Exact features depend on your organization status, role, and corridor. If something expected is missing, contact Support.


Get Started​

1. Create Your Business Account​

  1. Open console.fiatsend.com.
  2. Register with a company-managed email, company name, and contact details.
  3. After signup, your account starts in pending status while Fiatsend reviews the registration.
  4. When sandbox access is granted, status becomes verified (sandbox). You can sign in and use testnet Stellar flows.

Use one account per teammate. Do not share passwords. Invite colleagues from Team once you can sign in.

2. Account Statuses​

StatusMeaningWhat you can do
PendingRegistration received, not yet unlockedWait for activation; see pending screen
Verified / sandboxSandbox unlockedStellar testnet wallet, payment links, Stellar payouts, API sandbox keys
ActiveProduction approved (after KYB / Go live)Live corridors, production keys, production payouts
SuspendedAccess revokedContact Support

3. Sandbox vs Production​

SandboxProduction
Console statusverified / sandboxactive
Stellar networkTestnet (default)Mainnet (only when enabled for your org)
API keysfs_test_…fs_live_…
Local MoMo settlementSimulated refs (sim_momo_*) unless a live rail is configuredLive provider refs after go-live
Payment links, invoices, website checkoutTest mode: buttons and checkouts are marked Test mode and use the Stellar test networkReal payments
BalancesSeparate sandbox balancesYour live balances
How to upgradeComplete Go live / KYB in Settings when readyFiatsend activates after KYB approval

Sandbox and Live are kept apart: payment buttons, invoices and balances you create in one don't appear in the other. Switch between them with the toggle at the top of the sidebar (available once your account is active).

Sandbox Setup in Console walks through API health, rates, and webhook smoke tests. For Stellar operator flows, stay on this page.


Find Your Way Around​

The sidebar groups Console into four sections. Which items you see depends on your account status and your role.

SectionPagesWhat they're for
MainDashboard, Account balances, Linked accounts, SwapYour overview, balances and deposits, your connected Stellar wallet, and converting stablecoins to cedi.
PaymentsReceive payments, Invoices, Website checkout, Payouts, Payment settingsEverything about collecting and sending money. See Accepting Payments.
DevelopersSandbox Setup, API Keys, WebhooksCredentials and notifications for integrating by code.
AccountTeam, SettingsPeople, sign-in email and notification preferences.

Stellar Wallet on Testnet​

Connect a Stellar wallet so your business can receive USDC and fund / operate Stellar payouts on testnet.

Prerequisites​

  • Console account in verified, sandbox, or active status.
  • Freighter (or another supported wallet such as xBull) installed in your browser.
  • Freighter network set to Testnet (not Public / mainnet).

Steps​

  1. In Console, open Linked accounts.
  2. Choose Connect Stellar wallet and approve the connection in Freighter / xBull.
  3. Sign the bind challenge when prompted. Console stores your Stellar G-address for your organization.
  4. Add a USDC trustline for the Circle testnet issuer (the wallet panel shows the issuer and a Stellar Lab link).
  5. Claim testnet USDC from the Circle Stellar faucet using your G-address.
  6. Click Refresh in the wallet panel until the USDC balance appears.

Checklist​

StepDone when
Freighter installedExtension available in browser
Network = TestnetFreighter Settings → Network → Testnet
Wallet bound in ConsoleLinked accounts shows your G-address
USDC trustlineBalance panel can show USDC (even if 0)
Faucet fundedNon-zero testnet USDC balance
Balance refreshedPanel matches Horizon / Freighter
Troubleshooting wallet bind
  • Wrong network — Freighter must be on Testnet while Console is in sandbox.
  • Signature failed — Re-run connect; challenges expire quickly.
  • Balance still zero — Confirm trustline + faucet address match the bound G-address, then refresh.

Collect Payments​

Everything for getting paid lives under Payments. See Accepting Payments for how to choose, or go straight to:

PageUse it to
Receive paymentsCreate a payment link or QR code for a customer, or an in-person terminal QR.
InvoicesCreate branded invoices, manage customers, and track payment and receipts.
Website checkoutAccept payments on your own site with a payment button, embedded checkout or the API.
Payment settingsSet your default payment methods, who pays the fee and the payment deadline.

Fiatsend checkout needs a bound Stellar wallet (see above). On testnet, payers should use Stellar testnet wallets and USDC. Mobile money and bank transfer don't need a wallet; you save your account details in Payment settings and confirm each payment yourself.


Recipients​

For Stellar payouts you can:

  • Enter a recipient inline (Stellar G-address and/or mobile-money details).
  • Save recipients from the single-payout form for reuse.
  • Upload a CSV for bulk payouts (see below).

CSV columns follow the sample file in Console (Download sample CSV on the Stellar payouts tab). Typical fields include amount, destination type, Stellar address and/or phone + network for MoMo.


Send Payouts (Single and Batch)​

Stellar disbursements run through Fiatsend’s integration with the Stellar Disbursement Platform (SDP) on testnet.

Before You Send​

  • Wallet bound under Linked accounts.
  • Account status allows payouts (verified / sandbox or active).
  • KYB tier is not blocked (pending / rejected KYB cannot submit payouts).

Single Payout​

  1. Open Payouts → Stellar (USDC).
  2. Choose a saved recipient or enter a Stellar G-address and/or MoMo destination.
  3. Enter the USDC amount and submit.
  4. Watch the batch/item status until on-chain and local settlement states complete.

Bulk (Batch) Payout​

  1. On the Stellar payouts tab, download the sample CSV.
  2. Add at least one row per recipient (for volume testing, use 20+ rows).
  3. Upload the CSV and submit the batch.
  4. Repeat as needed. Batch list and item table poll automatically (~5–10s).

Status Meanings​

State (examples)Meaning
Queued / pendingAccepted; waiting for SDP / chain work
On-chain pending / completeStellar payment in flight or confirmed
Local settlement pendingOn-chain done; waiting for local MoMo / settlement step
Local settledTerminal success; includes a local settlement reference
FailedTerminal failure — inspect item error in Console

Dual tracking: each item can show an on-chain transaction hash (link to Stellar Expert when real) and a local settlement reference.

Simulated vs real settlement

In sandbox, mobile-money local settlement commonly uses simulated refs such as sim_momo_*. Mock SDP hashes are labeled (simulated) and are not explorer-verifiable. Real SDP testnet hashes open on Stellar Expert.


SEP-24 and Local Off-Ramp (Testnet)​

Tranche 2 testnet work includes SEP-24 interactive deposit/withdraw against a Stellar anchor.

PathStatus in Fiatsend
SEP-10 / SEP-24 protocol (MoneyGram testnet)Implemented and smoke-tested in the Fiatsend consumer stack
SeevCash mobile-money railScaffolded; live keys optional — sandbox accepts sim_momo_*
YellowcardNot the current Console off-ramp path

Businesses operating in Console primarily see payout item status + local settlement refs. Interactive SEP-24 hosted UI is part of the consumer / anchor integration, not a separate Console screen.


Track Activity and Reconcile​

  1. Payouts → Stellar — batch dashboard and per-item table.
  2. Open an item to copy the Stellar tx hash and local settlement reference.
  3. For real testnet hashes, verify on stellar.expert (testnet).
  4. Keep CSV upload files and batch IDs for your internal ops log.

Account Balances and Deposits​

Account balances shows your balances and how to add money.

  • Stablecoin balances hold USDC and USDT. Fund them on Stellar, Polygon or BNB Chain. Pick the network and asset, then send to the address shown.
  • USDC on Stellar uses a shared Fiatsend address plus a memo that is unique to your business. You must include the memo; without it Fiatsend can't tell the deposit is yours and it can't be credited automatically. Copy the memo from the page every time rather than typing it.
  • Deposits are credited automatically, usually within about a minute of the transaction landing. The page refreshes itself, and there's a button to check right now.
  • You're notified. When a real deposit is credited you get an email, and a WhatsApp message if you've saved a phone number. You can turn these off under Settings → Notifications. Test deposits in Sandbox don't send notifications.
  • Swap. Use Swap to convert stablecoins into your cedi (GHS) balance.

If a deposit hasn't appeared after a few minutes, check that you used the right network and included the memo, then contact Support with the transaction hash.


Settings and Notifications​

Under Settings you can:

  • Change your sign-in email. Enter your password and the new address. We send a one-time link to the new address, and your account switches only after you confirm it. Your old address is told both when you start the change and when it completes.
  • Choose which messages you get. Deposit emails, deposit WhatsApp messages and product tips are optional. Security and account notices (sign-in alerts, password and email changes, account status, invites) are always sent. Team members can see these preferences, but only the account owner can change them.
  • Go live. When you're ready for production, complete Go live / KYB.

Team, Security, and Support​

  • Invite teammates from Team with least-privilege roles.
  • Remove access when someone leaves.
  • Report unexpected access via Support.
  • Integrations and webhook signatures: the Website Checkout guide for checkout, and developer.fiatsend.com for the rest of the API.

Common Issues​

SymptomWhat to try
Cannot see Linked accounts / Stellar tabConfirm account is verified/sandbox/active, not pending
Wallet connect failsFreighter on Testnet; retry bind; clear expired challenge
CSV rejectedMatch sample headers; valid G-addresses; amounts > 0
Status stuck on local settlementWait for poll (~15s in mock MoMo); refresh batch detail
Explorer link missingHash may be simulated — labeled in UI
Production features lockedComplete Go live / KYB; wait for active status

Integrations​

Console supports your integration lifecycle. Technical implementation details live in the Developer Documentation: API credentials, request formats, webhooks, sandbox testing, and production requirements.

Access and Security​

Use a company-managed email address, give each teammate their own account, and remove access when a teammate changes roles. Report unexpected access or account activity through Support.