Skip to main content
Embed stablecoin-enabled cross-border payments, collections, and payouts into your financial products. StableStack provides financial institutions with infrastructure for connecting customers to fiat payment rails, stablecoin networks, and cross-border settlement.

What You Can Build

  • Customer stablecoin wallets
  • Fiat on-ramp and off-ramp
  • Cross-border payments
  • Customer collections
  • Local currency payouts
  • Stablecoin-funded payouts
  • Merchant and sub-merchant settlement
  • Treasury and liquidity operations
  • Embedded payment infrastructure

How the Flow Works

A financial institution can use StableStack as the underlying payment orchestration layer. Customer → your platform → StableStack → conversion / liquidity → payment rail or blockchain → beneficiary Your application remains the customer-facing layer while StableStack handles the underlying payment infrastructure.

Customer Collections

Collect funds in supported fiat currencies or stablecoins. For example: Customer NGN → StableStack → platform balance Or: Customer USDT → StableStack → platform balance Funds can then be converted, held, or routed for another transaction.

Customer Payouts

A financial institution can initiate payouts from fiat or stablecoin balances.

Stablecoin to Local Payout

USDT → StableStack → NGN → NIBSS → customer bank account

Stablecoin to International Payout

USDC → StableStack → USD → Fedwire → beneficiary

Fiat to International Payout

NGN → StableStack → USD → SWIFT → beneficiary

Merchant and Sub-Merchant Settlement

Platforms can use StableStack to manage settlement across merchants and sub-merchants. A typical flow can be: Customer payment → platform → merchant balance → StableStack → merchant payout The destination can be a local bank account, international payment rail, or supported stablecoin network.

Cross-Border Customer Payments

Financial institutions can expose cross-border payment capabilities without integrating each payment rail directly. For example: Customer NGN → StableStack → USDT/USDC → USD → international rail → beneficiary The institution controls the customer experience while StableStack orchestrates the underlying transaction.

Compliance and Transaction Management

StableStack supports the infrastructure required to operate payment flows, including:
  • Customer management
  • KYC/KYB workflows
  • Transaction tracking
  • Payment orchestration
  • Wallet management
  • Address validation
  • Transaction status updates
Institutions remain responsible for their own regulatory obligations and customer relationships. Transaction availability is also subject to StableStack’s supported corridors, compliance controls, and banking or liquidity partners.

Build on StableStack

StableStack can be used in three ways:

Extend Your Existing Operations

Use StableStack APIs to power internal treasury, settlement, and payment operations.

Embed Into Your Product

Expose StableStack-powered payments directly inside your customer experience.

Build a Payment Product

Use StableStack as the underlying infrastructure for wallets, cross-border payments, collections, and payouts.

Core Flow

1

KYC your customers and register them

Register each end-customer in StableStack with the appropriate customer type. Upload KYC documents to satisfy compliance requirements.Create a customer:
Upload KYC documents:
Upload identity documents (passport, national ID, utility bill) as multipart form data.
2

Provision stablecoin wallets per customer

Issue a dedicated stablecoin wallet to each customer on your platform. The wallet address is unique to the customer and can be used to receive inbound deposits.
3

Manage customer payout beneficiaries

Let customers save their preferred bank accounts or external wallets for fast repeat payouts.Add a bank beneficiary:
Add a wallet beneficiary:
4

Process customer payouts

Execute withdrawals on behalf of customers — to local bank accounts (remittance) or external stablecoin wallets.Bank payout (remittance):
Stablecoin wallet payout:
5

Fetch customer transaction history

Provide customers with a full transaction history or pull records for compliance reporting.
For a specific transaction:
6

Monitor all activity with webhooks

Configure webhooks to keep your core banking system in sync with every wallet event and payout status change.Key events to subscribe to:
  • wallet.transaction.inbound — Credit a customer’s account when funds arrive
  • wallet.transaction.outbound — Debit a customer’s account when funds leave
  • payout.completed — Confirm successful remittance delivery
  • payout.failed — Trigger retry logic or customer notification

Customer Account Architecture

A typical financial institution account structure on StableStack:

Compliance Touchpoints


Key APIs Used


Next Steps