Stablecoin collections and payouts

How it runs

• Match each payout to a PO or commercial invoice reference the supplier already expects on their bank statement.
• Quote NGN or GHS off the OTC desk, lock it, then fund in USDT or USDC — the all-in cost is known before money moves.
• Skip the correspondent chain that turns a T+0 purchase order into a T+5 arrival with unexplained intermediate fees.

How it runs

• Upload a CSV or push via API with payee, amount, corridor and preferred rail (local bank vs stablecoin wallet).
• Contractors in crypto-native markets can opt into stablecoin delivery; everyone else lands in local fiat without a second vendor.
• Exceptions (bad IBAN, wrong network, compliance hold) stay on the same status feed as successful lines — finance does not chase emails.

How it runs

• Net inbound stablecoins by settlement cycle, then pay out merchant balances in NGN or GHS on your schedule.
• Keep your merchant ID or sub-merchant reference on every payout line so recon matches the acquiring ledger.
• One FX conversion for the cycle instead of a bank markup on every individual merchant transfer.

How it runs

• Split a single funded balance across thousands of seller IDs — each line carries the store or creator reference your ledger already uses.
• Same instruction can send NGN or GHS to a seller bank and USDT or USDC to a creator wallet without splitting into two ops runs.
• Export a settlement file keyed by seller ID for marketplace finance and tax reporting.

How it runs

• Replace prefunded NGN/GHS nostros with just-in-time stablecoin settlement to the payout partner.
• Partner pays the beneficiary on local rails; you see partner funding status without waiting on nostro statements.
• Move corridor liquidity on weekends and holidays when SWIFT and local cut-offs would otherwise freeze the book.

How it runs

• Issue a payment link or deposit address per checkout / invoice — payer sends stablecoins on a supported network.
• On-chain risk screening runs before credit, so compliance is not a bolt-on after the money has landed.
• Auto-convert to NGN or GHS at desk pricing, on the same inbound ledger.

How it runs

• One wallet or collection reference per merchant ID — attribution does not depend on memo fields that payers forget.
• Aggregate inbound per MID, then settle the merchant’s local bank per your agreement.
• Merchant statements and your platform ledger share the same MID key for dispute and refund handling.

How it runs

• Dedicated deposit address or memo per client / sub-wallet so attribution is automatic on arrival.
• Screen before credit; rejected deposits never touch the client’s available balance.
• Credit as stablecoin or convert into the book currency your product already uses for margin and spending.

How it runs

• Settle net obligations 24/7 without waiting for correspondent banking hours or nostro cut-offs.
• Each member posts or receives stablecoin against a shared cycle reference; optional fiat cash-out per member preference.
• Both sides export the same cycle ID so bilateral recon does not invent two different truths.

How it runs

• Push funds from one entity’s USDT or USDC balance to another entity’s NGN or GHS books on one stack.
• Each hop carries a booked FX rate and a group reference — intercompany and external counterparties use the same trail.
• Reverse the flow when Entity B needs to repatriate or fund Entity A — collections and payouts are the same rails.

How it runs

• Collect or hold local currency in-corridor, then convert into stablecoins when you want to move the float.
• Bridge liquidity to the HQ entity on-chain — weekends and cut-offs no longer freeze repatriation.
• Off-ramp to EUR or USD at desk pricing into the group treasury account, with one recon feed across the hop.