Virtual Accounts
Programmatically issue and manage named virtual accounts for customer deposits
Intro
Virtual Accounts let your platform give each end customer (whether individuals or businesses) their own named account for fiat deposits. Each Virtual Account is an isolated ledger inside your platform's balance at zerohash, so you can track, fund, and reconcile balances per customer through a single integration.
Your customers get a real account and routing number, held in their own name, that they can send money to over ACH, Wire, RTP or FedNow. When funds arrive, zerohash can automatically convert them into stablecoins or other crypto assets. USD is supported today, with more currencies and rails to follow. In order to be eligible for Virtual Accounts, a platform must be onboarded with zerohash LLC.
Accepted Bank Rails into Virtual Accounts
zerohash Virtual Accounts are able to receive credits from the following payment rails:
Automated Clearing House (ACH)
-
Please Note: ACH debits (pulls) are not possible into these accounts, but can be serviced through our Bank Rails product that leverages Plaid
-
Third party deposits are permitted via ACH
-
Same Day ACH has a $1M transaction limit enforced by NACHA, but zerohash will enforce it's own limits per rail based on our review process
Wire Transfers (Domestic and International)
- Please Note: These accounts can’t receive SWIFT payments directly. International senders can fund them via a USD wire routed through a US intermediary bank, including the intermediary’s details, the Virtual Account's routing number, and the full account number. Intermediary fees may apply.
-
Only first party deposits are permitted via FedWire and International Wire
-
No maximum payment size is enforced on wires by any network, but zerohash will enforce it's own limits per rail based on our review process
Instant Payments (RTP and FedNow)
-
Please Note: These accounts accept both RTP and FedNow transfers, which settle instantly, 24/7/365
-
Third party deposits are permitted via RTP and FedNow
-
The Clearing House and The Fed both impose a $10M per transaction limit on these rails, but zerohash will enforce it's own limits per rail based on our review process
Limits for Incoming Payments
zerohash will impose limits on incoming deposits to Virtual Accounts.
There are 3 dimensions for these limits that apply to each rail:
- Per deposit
- Per day
- Per 30 days
The exact limit thresholds are determined for Platforms by the zerohash finance team as the integration progresses. Limits will be clearly communicated to the Platform during the integration process.
How it works, in three steps
Create a named virtual account for your customer through the zerohash API.
Share the unique account and routing number with your customer so they can push funds in via ACH, Wire, RTP, or FedNow.
zerohash notifies you when funds arrive and applies the behavior you configured: hold the balance, or convert it and send it to a whitelisted wallet.
When to use Virtual Accounts
Use Virtual Accounts when your customers need a named account to push their own funds into, for example to fund a wallet, an investment account, or a payroll direct deposit, and optionally convert those funds into stablecoins or crypto.
Virtual Accounts are focused on the inbound, customer-initiated side: money your customers send in. If your platform needs to originate deposits or withdrawals on your customers' behalf, that's handled by our ACH + RTP product offering. The two are complementary: Virtual Accounts and ACH + RTP can be bundled for a complete fiat payments offering.
Use Cases
Use Case: Give each employee or contractor a named Virtual Account they can use as a direct-deposit destination. Wages arrive via standard payroll ACH, and can be automatically converted into a stablecoin.
Why it matters: A named account is what makes direct deposit possible, and the auto-conversion turns a paycheck into digital assets with no manual step for the recipient.
Use Case: Let customers push USD into their named account, then automatically convert to a stablecoin delivered to their on-chain wallet.
Why it matters: Simplifies the fiat-to-crypto experience and removes dependency on third-party exchanges.
Use Case: Assign each seller, freelancer, or merchant their own named Virtual Account so incoming funds can be tracked per customer.
Why it matters: Clean per-customer reconciliation without managing physical bank accounts.
Use Case: Give individuals or business units a named account to receive USD via domestic rails, then aggregate or convert those funds.
Why it matters: Collect funds locally without opening and managing a bank account for every customer.
Permitted/Restricted Jurisdictions for Virtual Accounts
Please refer to our overall list of permitted and restricted jurisdictions for zerohash. The same list applies for permitted activity tied to Virtual Accounts.
Updated 11 days ago