Bitzaro
ENLog in
Get Bitzaro

Published

What is Wallet-as-a-Service? How WAAS Lite lets a business accept stablecoin payments

Wallet-as-a-Service (WAAS) lets a business use a provider's wallets, transfers and payouts instead of building and securing its own. Bitzaro offers it two ways: WAAS, one API for developers, and WAAS Lite, the same engine in a dashboard, so a team new to crypto can collect payments without developers.

Bitzaro WAAS LiteBitzaro WAASWallet-as-a-Service FAQGlossary

Wallet-as-a-Service, in plain words

With Wallet-as-a-Service, a provider runs the wallets and the blockchain side, and your business uses them through an API or a dashboard. At Bitzaro, WAAS is one API for wallets, transfers and payouts, and it is the engine behind every Bitzaro product.

Bitzaro holds custody: it holds and protects the keys, keeps balances segregated per user, and exposes them to you through the API. Wallets are created and signed through multi-party computation (MPC), so no single private key exists to be lost or stolen, and transfers go through KYT compliance screening.

WAAS or WAAS Lite?

WAAS is for teams that want to build on the API. Access starts with a conversation, then sandbox and live API keys. WAAS Lite is the same engine in a dashboard, for merchants and platforms that want to accept or manage crypto payments without building a full blockchain payment stack. It needs no developers, and because it is the same engine and the same account, a WAAS Lite merchant can add the API later without migrating balances.

WAAS Lite suits e-commerce businesses, online platforms, service providers, merchants that need dedicated wallet addresses for their customers, and teams without blockchain engineers.

How a business starts with WAAS Lite

  1. A short call with Bitzaro.
  2. Business verification (KYB): company registration, business address, directors or authorized representatives, and beneficial ownership where applicable.
  3. Google Authenticator, set up at your first login.
  4. A test (UAT) environment to try it, then an API key if you want one.

WAAS Lite collects USDT on Ethereum, BNB Smart Chain and Tron. Other tokens may be supported depending on your use case.

A Onetime Payment Link is a payment request tied to one order. It can fix the token and the chain, with one address, or fix the token and let the customer pay on any chain, with up to three addresses (Ethereum, BSC and Tron), so the customer can pay however is easiest for them. Partial payments, even across chains, add up until the order is paid.

With Clients, a merchant registers its own members and gives each one a dedicated wallet address and a unique wallet link. Members don't need a full Bitzaro account. Gathering then consolidates the funds in Client wallets into the merchant's main balance, whenever the merchant starts it.

How incoming payments are screened

Every incoming payment is screened for fraud before it settles into your pooled balance, using Elliptic's data. Each payment gets a risk level. LOW and MED payments move to the merchant balance automatically; a HIGH payment waits for the merchant to approve or reject it, and a rejected payment is refunded to its source.

If a source address's risk level rises after a payment, Self-Healing moves the funds to the higher-risk wallet and logs the move in Replace History, with the old and new address, the reason, the time and the chain. A higher-risk classification is a risk-management signal, not proof of wrongdoing.

Withdrawals are screened too: the destination address is checked first, LOW and MED withdrawals need a Google Authenticator code, and a HIGH-risk one needs your manual approval after you review the risk report.

Network fees: the Gas Station

Moving funds on a blockchain costs gas, the fee paid for transactions on that network. In WAAS Lite, merchants top up the Gas Station on each chain. It shows the gas balance per chain and logs every network fee it pays, so the costs are in one place.

For developers: webhooks and the API

WAAS Lite sends webhooks for four events: Onetime Payment Callback, Chain Event, Gathering and User KYC. A webhook reports an event; your own system stays responsible for its fulfilment rules and business logic. Treat API keys as sensitive credentials: store them securely and never expose them in client-side code. Transaction History has filters and a CSV export, and the full API reference is at waaslite.readme.io.

Questions, answered.

A way for a business to use a provider's wallets, transfers and payouts instead of building its own. Bitzaro's WAAS is one API for wallets, transfers and payouts; Bitzaro holds the keys and keeps balances segregated per user.

WAAS is the API for teams building their own product. WAAS Lite is the same engine in a dashboard, so a merchant can collect crypto payments without developers, and add the API later without migrating balances.

WAAS Lite collects USDT on Ethereum, BNB Smart Chain and Tron. Other tokens may be supported depending on your use case.

Yes. Merchants top up the Gas Station on each chain, and it logs every network fee it pays.

It waits for the merchant to approve or reject it, and a rejected payment is refunded to its source. LOW and MED payments move to the merchant balance automatically.

No. WAAS Lite works from a dashboard. The API and webhooks are there when you want them, with the full reference at waaslite.readme.io.

Still need help? Visit the Help Center.

Read next

InsightsBitzaro WAAS LiteBitzaro WAASWallet-as-a-Service FAQGlossary