Table of Contents
Marketplace and payroll teams still wire ACH or SWIFT for contractor and seller payouts, then wait days for the money to land. Stablecoin payout rails flip that loop: convert fiat float to USDC (or another supported asset) and push it onchain to a whitelisted wallet in minutes.
The named object is a zerohash stablecoin payout: Modular Payouts (SDK or sequential APIs) and Single API Call Payouts (POST /payouts) that turn funded USD float into an onchain transfer. In August 2026, Visa also announced that Visa Direct clients can prefund and disburse stablecoin payouts powered by zerohash, which is why payments ops teams are mapping this stack now.
Facts below come from zerohash's Payouts product page, Modular Payouts SDK integration guide, Single API Call Payouts guide, API-powered Payouts integration guide, the August 5, 2026 Visa Direct partnership press release, and Visa's public Visa Direct Account and Wallet how-to. Field names, status machines, and asset lists are copied from those docs. No invented fees, settlement cut-offs, or country eligibility beyond what those pages state.
Key Takeaways
- Pick Modular Payouts for full UX control or Single API Call POST /payouts for one-shot submissions.
- Pre-onboard the Payor, fund USD float, then validate before live Idempotency-Key submits.
- Supported stables include USDC (15 networks), USDT, PYUSD, and RLUSD per zerohash docs.
- Track payment.settled (or Modular settled) via webhooks; email receipts are mandatory.
- Visa Direct can prefund and disburse stablecoin payouts powered by zerohash for eligible clients.
Who this is for
Use this path if you are a payments, marketplace, EOR, payroll, or PSP team that wants to offer stablecoin (or crypto) withdrawals beside wire, ACH, and RTP.
Skip it if you only need issuer primary mint (see How to Mint and Redeem USDC with Circle Mint or How to Mint and Redeem USDG with Paxos). Skip it if your spend rail is a stablecoin-backed card (see How to Issue a Stripe Stablecoin-Backed Card with Bridge). For the August 2026 Visa announcement context, start with SCI's news write-up Visa Adds Stablecoin Prefunding and Payouts to Visa Direct Through zerohash. For Circle's parallel payout product shape, keep How to Send a Circle Stablecoin Payout open as a comparison sheet.
What a zerohash stablecoin payout is
Per the Payouts docs, Payouts let Platforms allow end customers to send crypto or stablecoins to personal wallets almost anywhere zerohash supports, as an alternative next to wire, ACH, and RTP. A Modular Payout is defined in the SDK guide as the conversion of fiat to stablecoin plus an automatic onchain transfer to a destination address.
Asset support listed on the same page includes USD Coin (USDC) across 15 blockchain networks, Tether (USDT) across 4 networks, PayPal USD (PYUSD) on SOL and ETH, and Ripple USD (RLUSD) on SOL and XRPL, plus broader crypto assets (Bitcoin, Ethereum, Solana, and 30+ more).
Here's why that matters for operators: you are not asking beneficiaries to wait on a correspondent bank chain. You fund USD float, convert, and broadcast. The tradeoff is compliance state (Payor, Beneficiary, external account approval) and float replenishment after each settlement session.
Visa Direct context (prefunding and payouts)
On August 5, 2026, zerohash's press release stated that Visa Direct's stablecoin merchant prefunding and payout capabilities would become available for eligible Visa Direct clients, powered by zerohash. Visa Direct reaches more than 18 billion endpoints across eligible cards, accounts, and digital wallets in more than 195 countries and territories, per that announcement.
Stablecoin Insider's take: treat Visa Direct eligibility and zerohash Platform onboarding as separate gates. The public Visa Account and Wallet how-to covers Send Payout, Query, Validate, Get Account Balance, and Cancel on Visa's APIs. The developer steps below are the zerohash crypto/stablecoin payout control plane that sits under (or beside) that Visa Direct expansion for teams that are already on zerohash.
Step 1: Choose Modular vs Single API Call Payouts
zerohash documents two product shapes on the Payouts page:
- Modular Payouts: 4-step workflow (onboard Payor, onboard Beneficiary, link external account, initiate payout). Best when the Platform owns UX/UI, wants SDK or no-code helpers, and needs to control timing and state.
- Single API Call Payouts: onboard Payor once, then POST /payouts per transaction with complete details. zerohash orchestrates intermediary KYC, account linking, and payment steps. Best for licensed institutions with nested payors, simple stateless flows, or platforms that are not building custom payout UX.
| Lane | Best for | Primary docs | Operator check |
|---|---|---|---|
| Modular | Custom UX, SDK modals | SDK integration guide (v2.10.9+) | Webhooks for external_account and payment |
| Single API Call | One request per payout | new-payouts-api-integration-guide | validate:true then Idempotency-Key |
Step 2: Platform setup, API keys, and float funding
Before any payout, the Platform onboards to zerohash, adds users, creates API keys, and whitelists IPs (see the integration guide). Then fund the float account by sending fiat to the mutually decided bank details. Docs list placeholder ledger coordinates such as participant_code 00SCXM, account_group equal to your platform code (example PLAT01), account_label general, account_type available, asset USD.
In Cert, platforms are pre-funded. In production, after each settlement session you top up float to its original level (Net Delivery Obligation). The Modular SDK guide lists NDO wire due dates by session weekday (Monday session due Tuesday EOD, through Friday due Monday EOD), with US bank holidays rolling to the next valid business day.
Network fees are paid from a separate network_fee account label, or they accrue to the end-of-month invoice if that account is left unfunded.
Step 3: Onboard the Payor
Both product shapes require a Payor that is already registered with zerohash before live payouts. Modular docs use POST /participants/entity/new with entity KYB fields, control persons, beneficial owners, sanction screening timestamps, and then POST /participants/entity/documents so status can move from submitted to approved.
Single API Call docs add account models:
- fully_disclosed: Ultimate Payor is a legal zerohash customer, signs T&Cs, and is subject to KYB/KYC.
- omnibus: Payor is a licensed MSB that puts activity under its own licenses and is the legal zerohash customer.
US Payor onboarding for Single API Call uses onboarding_profile originator_entity on POST /participants/entity/new. EU flows use base URL https://api.zerohash.eu and extra fields (LEI, chamber of commerce number, expected volumes, activity locations). Keep the returned participant_code (example PAYOR1) for every later POST /payouts.
Step 4: Modular path (Beneficiary, wallet link, SDK payout)
If you chose Modular, follow the high-level flow in the SDK guide:
- Submit Beneficiary via POST /participants/beneficiaries/new (email or phone required; jurisdiction_code must include country and subdivision where applicable).
- Query until status is approved (Cert can force rejected with SSN 111111111 or pending review with sample names called out in docs).
- Request a client auth token with permission crypto-account-link, open the Account Link SDK (AppIdentifier.CRYPTO_ACCOUNT_LINK_PAYOUTS), and wait for CRYPTO_ACCOUNT_LINK_EXTERNAL_ACCOUNT_CREATED plus external_account_status_changed webhooks until status approved.
- Request a payout JWT with permission crypto-payouts, including external_account_id, quoted_asset (USD), and withdrawal_request_amount, then open AppIdentifier.PAYOUTS.
- Consume payment_status_changed webhooks: submitted → posted (onchain hash present) → settled (or rare failed).
The SDK UI shows transfer request amount, destination wallet nickname/address, withdrawal fee, network fee, and receive amount before the beneficiary confirms.
Step 5: Single API Call path (validate, then POST /payouts)
If you chose Single API Call, the operator spine is shorter after the Payor exists.
Validate first
Set validate: true on POST /payouts. zerohash runs schema checks, business-logic checks (account model, agreements), and address validation (deny-list and network compatibility). A 200 with empty body means the live request should succeed. Idempotency can be omitted in validate mode. That payload shape is taken from the Single API Call guide US validate example. Live submits omit validate and require an Idempotency-Key header. Same key + same body replays the original response; same key + different body returns 400.
Existing participants
After the first successful payout, reference Ultimate Payor, Beneficiary, and external account by participant_code / external_account_id instead of resubmitting full PII. Mix-and-match inline and reference IDs is supported.
Status machine
Webhooks use payload_type: payout.status_updated. Docs sequence sub_statuses from payor approval through beneficiary.external_account.approved, then payment.submitted → payment.posted → payment.settled (payout status completed). Terminal rejects can fire on payor, beneficiary, external account, or payment.failed.
Step 6: Email receipts and reconciliation
zerohash requires that the Payor receives an email receipt for each payout. Required fields mapped in the SDK guide include Order Number (payment_id), Order Type fixed as "Payout Transmission", Transmission Amount (total), Amount Received by Beneficiary, Fees (including network fee when the Payor incurs it), Date/Time (created_at), and Account ID (participant_code), plus platform support contacts and the verbatim zerohash support block (Zero Hash LLC, NMLS ID 1699379, Chicago address and phone).
Reconcile with GET /payments (Modular) or GET /payouts (Single API Call) using payout_id or idempotency_key. Surface on_chain_transaction_id in your transaction history once status is posted or settled.
Worked example: $200 USDC on Ethereum (Modular SDK)
Suppose a marketplace needs to pay a contractor 200 USD equivalent in USDC on Ethereum.
- Confirm Platform API keys, webhook URL, and USD float are live (Cert can skip real float).
- Ensure Payor PAYOR1 is approved with documents.
- Submit Beneficiary Lucas Martinez (or your real KYC payload); wait for approved.
- Open Account Link SDK; link an ETH wallet that supports USDC; wait for external account approved.
- Request payout JWT with withdrawal_request_amount "200", quoted_asset "USD", and the approved external_account_id.
- Open Payouts SDK; beneficiary confirms fees and receive amount (docs example: withdrawal fee 1.50, network fee 1.25, receive 197.25 USDC).
- Watch webhooks until settled; email the required receipt; include the onchain hash in your UI.
That example fee split is illustrative from the SDK guide's sample posted payload, not a price quote for your entity.
zerohash vs Circle payout: pick a lane
| Question | zerohash stablecoin payout | Circle stablecoin payout |
|---|---|---|
| Control plane | zerohash Platform + Payor float | Circle account / payout APIs |
| Visa Direct angle | Aug 2026 prefund/payout partnership | Separate Circle product path |
| Operator guide | This post | SCI Circle payout how-to |
On the flip side, do not assume every Visa Direct client automatically has zerohash Payouts enabled. Confirm product enrollment with both Visa and zerohash before promising contractors a stablecoin option in production.
Who it is not for
Skip this stack when:
- You lack a zerohash Platform contract, API keys, or payouts product enrollment.
- You only need issuer mint/redeem, not beneficiary wallet payouts.
- You need card spend funded by stablecoins rather than wallet withdrawals.
- Your compliance model cannot support fully_disclosed or omnibus account_model requirements.
- You cannot fund and reconcile USD float / NDO on the documented session schedule.
Building stablecoin payouts on zerohash? Map Payor onboarding, one Cert validate call, and one settled webhook before any production float wire.
Need the Circle parallel for USDC payouts? Use the Circle how-to next.
Visa Adds Stablecoin Prefunding and Payouts to Visa Direct Through zerohash: News context for the August 2026 Visa Direct + zerohash partnership.
FAQ
What is a zerohash stablecoin payout?
A platform-initiated conversion of funded fiat (typically USD float) into a stablecoin or crypto asset plus an onchain transfer to a beneficiary wallet, via Modular Payouts or Single API Call POST /payouts.
Which stablecoins can I send?
zerohash Payouts docs list USDC across 15 networks, USDT across 4 networks, PYUSD on SOL and ETH, and RLUSD on SOL and XRPL, plus additional crypto assets. Confirm your Platform enablement before promising a specific asset.
Should I use Modular or Single API Call?
Use Modular when you own the UX and want SDK account-link and payout modals. Use Single API Call when you want one POST /payouts after Payor onboarding and prefer zerohash to orchestrate intermediate steps.
Do I need to validate before every live payout?
Docs recommend validate:true for pre-flight checks. Live submits omit validate and require an Idempotency-Key so retries do not double-pay.
How does Visa Direct fit in?
In August 2026 Visa announced stablecoin prefunding and payouts for eligible Visa Direct clients powered by zerohash. Eligibility and product enablement are separate from a generic zerohash Platform integration.
What webhook marks success?
On Single API Call, payment.settled with payout status completed. On Modular SDK payments, watch for settled on payment_status_changed after posted includes the onchain hash.
Are email receipts optional?
No. zerohash requires Payor email receipts with specific fields and support contact blocks listed in the Modular SDK guide.
How is this different from Circle payouts?
Different control plane and commercial stack. Use this guide for zerohash (including Visa Direct partnership context). Use SCI's Circle payout how-to when Circle is the payout provider.
This content is provided for informational and educational purposes only and does not constitute financial, investment, legal, or tax advice; no material herein should be interpreted as a recommendation, endorsement, or solicitation to buy or sell any financial instrument, and readers should conduct their own independent research or consult a qualified professional.
){kind=link}