Overview
Banks, microfinance institutions, neobanks, and remittance platforms can embed StableStack to offer their end-customers stablecoin accounts, cross-border payouts, and real-time transaction visibility — without building blockchain infrastructure from scratch. StableStack handles custody, rails, and compliance tooling so you can focus on your product.Core Flow
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.
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.
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:
Process customer payouts
Execute withdrawals on behalf of customers — to local bank accounts (remittance) or external stablecoin wallets.Bank payout (remittance):Stablecoin wallet payout:
Fetch customer transaction history
Provide customers with a full transaction history or pull records for compliance reporting.For a specific transaction:
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 arrivewallet.transaction.outbound— Debit a customer’s account when funds leavepayout.completed— Confirm successful remittance deliverypayout.failed— Trigger retry logic or customer notification
Customer Account Architecture
A typical financial institution account structure on StableStack:Compliance Touchpoints
| Requirement | StableStack Capability |
|---|---|
| Customer identity | POST /individual-customers or POST /business-customers + KYC upload |
| Transaction audit | GET /transactions with full history |
| Payout traceability | Reference IDs on every payout |
| Real-time monitoring | Webhook events for every state change |
Key APIs Used
| Endpoint | Purpose |
|---|---|
POST /individual-customers | Register an individual customer |
POST /business-customers | Register a business customer |
POST /customers/{customer_id}/kyc | Upload KYC documents |
GET /customers | List all customers |
POST /wallets | Issue a wallet to a customer |
GET /wallets/{customer_id}/customer | View all wallets for a customer |
POST /payout/methods/banks | Save a customer’s bank beneficiary |
POST /payout/methods/wallets | Save a customer’s wallet beneficiary |
GET /payout/methods/{payout_method_id} | Retrieve a beneficiary |
POST /payouts/banks | Execute a bank payout for a customer |
POST /payouts/wallets | Execute a wallet payout for a customer |
GET /payouts/fees | Pre-check payout fees |
GET /customers/transactions/by_customer_id/{id} | Full transaction history per customer |
Next Steps
- Authentication — Get your API key
- Webhooks — Set up real-time event notifications
- Webhook Security — Verify webhook signatures
- Supported Currencies — Available corridors