Who offers stablecoin merchant settlement?

Merchant acquirers, payment service providers and processors that let merchants take their settlement in stablecoins.

Goldsky

Stablecoin merchant settlement

Talk to our team

What is stablecoin merchant settlement?

Stablecoin merchant settlement is an acquirer or payment provider paying a merchant’s proceeds in stablecoins instead of a bank transfer, to the wallet and network the merchant picked, on any day of the week.

Acquirers, payment service providers and processors offer it because merchants want their money outside banking hours and cut-offs, and every payout still has to match the settlement on the merchant’s statement.

Goldsky can run the payout as a task you write, which screens the merchant’s wallet, hands the transaction to your signer and returns the confirmed hash to record; converting the funds, holding the keys and the settlement records stay with you and your providers.

How stablecoin merchant settlement works

The diagram follows one merchant’s settlement from the wallet it chose to the payout on its statement, and shows who does each step. Your setup may differ.

Record the settlement walletStablecoin, network and wallet the merchant chose

Conversion providerFund the payout walletSettlement funds converted to stablecoins

ComposeStart the payout and screen the walletA failed check holds the settlement

Wallet or custody providerSign the payoutUnder limits per merchant and batch

ComposeBuild the payoutSent to your signing endpoint

Record the payout against the settlementTransaction hash on the merchant’s statement

Payout landsStablecoins reach the merchant’s wallet

Goldsky
Your provider

How to settle merchants in stablecoins

A TypeScript task that you write and Goldsky hosts takes each merchant’s approved settlement, screens the merchant’s wallet, sends the payout to your signer and waits for it to confirm. The transaction hash comes back to the task, which records it against the settlement.

What you’ll need

Goldsky Compose
A conversion provider that turns settlement funds into stablecoins
A screening provider with an API for wallet checks
A custody provider with an approval policy that can sign EIP-712 typed data and EIP-7702 authorizations, reached through a signing endpoint you host
Your settlement system and merchant statements

Record the merchant’s settlement wallet
A merchant who opts into stablecoin settlement chooses the stablecoin, the network and the wallet in place of a bank account.
Your merchant records hold the wallet and network beside the bank details they replace. Treat a change of wallet like a change of bank account, with the same verification, or a takeover of the merchant’s login redirects its settlement.
Fund the payout wallet in stablecoins
Settlement funds are owed in fiat, so they’re converted before they can be paid as stablecoins.
Your conversion provider turns the batch’s settlement funds into the stablecoins merchants chose and delivers them to your payout wallet. Fund the whole batch before it starts, or some merchants are paid and the rest wait.
Start the payout and screen the wallet
Handled by Goldsky Compose
Each settlement should go only to a wallet that passes your screening when you pay.
The merchant’s wallet is checked against your sanctions and risk rules before the payout is built. A wallet that fails is held for review and the settlement stays owed.
Your settlement system can start a Compose task with an HTTP call, and the task calls your screening provider’s API before it pays.
Call a task over HTTP (opens in a new tab)
Build the payout and send it for signing
Handled by Goldsky Compose
The settlement has to become a transaction on the network the merchant chose and reach whoever holds the key.
The transaction carries the merchant’s wallet and the settlement amount, and a payout built twice for one settlement pays the merchant twice. A reorg (the chain replacing its newest blocks) can drop a payout after it was included, so it needs resending, not a second settlement.
With Goldsky Compose, a webhook wallet sends the signing endpoint you host each payout as a UserOperation (the transaction format smart-account wallets use) to sign, plus, the first time it sends on a chain, an EIP-7702 authorization that lets your address act as a smart account there. Compose submits the signed payout, gas-sponsored, waits for the confirmations you set and can replay it if a reorg drops it.
Use a webhook wallet (opens in a new tab)
Sign the payout
Moving settlement funds takes a signature from a key held under rules about who can approve what.
Your signing endpoint holds your limits per merchant and per batch: it reads the recipient and amount from the payout’s call data, checks them, then asks your custody provider to sign. A key with no rules around it lets anyone who can change the settlement logic move the payout wallet’s funds.
Record the payout against the settlement
Merchants reconcile what they were paid against their statement, and so do you.
Once the task has seen the payout confirm to the depth you set, your settlement system marks the settlement paid with the transaction hash the task returned and shows it on the merchant’s statement. A payout held or still unconfirmed stays open until someone resolves it.

What you control

Your team: Record the merchant’s settlement wallet
Record the payout against the settlement
Your providers: Conversion provider
Wallet or custody provider