Global Trade

Move money across borders without rebuilding your payment infrastructure for every corridor. StableStack gives businesses and platforms a single orchestration layer for cross-border commercial payments. You can collect or fund transactions in local currency, move value through stablecoins when useful, and settle beneficiaries through local or international payment rails.

What You Can Build

Cross-border supplier payments
International commercial payments
Import and export settlement
USD settlement from emerging markets
Local currency collection and international settlement
Stablecoin-powered settlement
Supplier payouts through local banking rails
Treasury movement between markets

How the Flow Works

A typical cross-border payment can move through several layers: Source currency → StableStack → conversion / liquidity → settlement asset → payment rail → beneficiary StableStack handles the orchestration between these layers while exposing the transaction through a consistent API.

Example: Nigeria to China

A business in Nigeria needs to pay a supplier in China. NGN → USD → CNAPS → China Or, where stablecoins are used as the settlement layer: NGN → USDT/USDC → USD → CNAPS → China The appropriate route depends on the source of funds, destination, currency, liquidity, and supported payment rail.

Common Flows

Fiat to Fiat

NGN → USD Local currency is converted and routed to an international USD payment rail. Typical uses include:

Supplier payments
Import payments
International invoices
Repatriation
Cross-border business expenses

Fiat to Stablecoin to Fiat

NGN → USDT/USDC → USD Stablecoins can act as the settlement layer between the originating currency and the final fiat payout. This can be useful where the stablecoin network provides a more efficient path for moving value before the final local or international payout.

Stablecoin to Fiat

USDT/USDC → local currency → beneficiary bank account For example: USDT → NGN → NIBSS → Nigerian bank account Or: USDC → USD → Fedwire → US bank account

Payment Rails

The final payment can be routed through supported local or international rails, including NIBSS, Fedwire, SWIFT, CNAPS, SEPA, and supported local banking rails. See Supported Currencies and Rails for current corridor coverage.

Why StableStack

You do not need to build separate integrations for every combination of currency, blockchain, and payment rail. StableStack provides the orchestration layer between fiat currencies, stablecoins, blockchain networks, local payment rails, international payment rails, and liquidity providers. Your application can initiate the payment while StableStack handles the underlying route.

Core Flow

Onboard your suppliers as customers

Register each supplier (individual or business) as a customer in StableStack. This creates a managed profile you can attach wallets and payout methods to.

POST /business-customers

{
	"business_name": "Lagos Export Co.",
	"email": "finance@lagosexport.com",
	"country": "Nigeria",
	"phone": "+2348012345678"
}

Create a stablecoin wallet for the customer

Provision a USDC wallet for the supplier. This wallet acts as the staging point for funds before they are withdrawn to fiat.

POST /wallets

{
	"customer_id": "CUSTOMER_ID",
	"currency": "USDC",
	"network": "erc20",
	"description": "Supplier settlement wallet"
}

Add the supplier's bank account as a payout method

Save the supplier’s local bank details so payouts can be reused without re-entering account information each time.

POST /payout/methods/banks

{
	"customer_id": "CUSTOMER_ID",
	"account_number": "0123456789",
	"bank_code": "000004",
	"bank_name": "United Bank for Africa",
	"currency": "NGN",
	"country": "Nigeria",
	"recipient_name": "Lagos Export Co."
}

Check fees before initiating a payout

Fetch the current fee for a fiat payout so you can display costs transparently or build them into your pricing.

GET /payouts/fees?currency_type=FIAT&currency=USDC&recipient_currency=NGN&amount=5000

Pay the supplier — stablecoin to local bank

Initiate a bank withdrawal. StableStack converts the stablecoin to the recipient’s local currency and delivers it via local banking rails.

POST /payouts/banks

{
	"customer_id": "CUSTOMER_ID",
	"currency": "USDC",
	"account_number": "0123456789",
	"bank_name": "United Bank for Africa",
	"bank_code": "000004",
	"amount": "5000",
	"recipient_name": "Lagos Export Co.",
	"recipient_currency": "NGN",
	"recipient_country": "Nigeria"
}

Track the payment

Monitor the payout status via the transactions API or listen for real-time webhook events.

GET /customers/transactions/by_ref_id/{reference_id}

Relevant webhook events:

payout.initiated
payout.processing
payout.completed
payout.failed

Key APIs Used

Endpoint	Purpose
`POST /business-customers`	Register a supplier
`POST /wallets`	Create a stablecoin wallet
`POST /payout/methods/banks`	Save a bank payout method
`GET /payouts/fees`	Fetch fees before sending
`POST /payouts/banks`	Initiate a bank payout
`GET /customers/transactions/by_ref_id/{reference_id}`	Track transaction status

Next Steps

Authentication — Get your API key
Webhook Events — Set up real-time payout notifications
Supported Currencies — Full list of supported corridors

Get Started

Webhooks

Libraries

Coverage

Use Cases

Prohibited

What You Can Build

How the Flow Works

Example: Nigeria to China

Common Flows

Fiat to Fiat

Fiat to Stablecoin to Fiat

Stablecoin to Fiat

Payment Rails

Why StableStack

Core Flow

Key APIs Used

Next Steps

​What You Can Build

​How the Flow Works

​Example: Nigeria to China

​Common Flows

​Fiat to Fiat

​Fiat to Stablecoin to Fiat

​Stablecoin to Fiat

​Payment Rails

​Why StableStack

​Core Flow

​Key APIs Used

​Next Steps

What You Can Build

How the Flow Works

Example: Nigeria to China

Common Flows

Fiat to Fiat

Fiat to Stablecoin to Fiat

Stablecoin to Fiat

Payment Rails

Why StableStack

Core Flow

Key APIs Used

Next Steps