Answers about Bitzaro's Wallet-as-a-Service: WAAS, the full API, and WAAS Lite, the dashboard for collecting crypto payments.
Wallet-as-a-Service (WAAS) lets a business give its users crypto wallets through an API, without building custody, key management and blockchain infrastructure itself. Bitzaro WAAS is one API for creating wallets, moving funds and paying out, with custody and fraud checks handled by Bitzaro.
They run on the same engine. WAAS is the full API, for teams that build their own experience and control every detail. WAAS Lite wraps the same engine in a dashboard, so a team can start collecting crypto payments without writing code.
Merchants and platforms that want to accept crypto payments without building a blockchain payment stack: e-commerce businesses, online platforms, service providers, merchants that want a dedicated wallet for each customer, and teams without blockchain engineers.
No. WAAS Lite runs from a console, so a finance or operations team can collect payments without writing code. The API is there if you want to automate later.
WAAS Lite collects on Ethereum, BNB Smart Chain and Tron. USDT is the main supported token; other tokens may be supported depending on your use case.
USDT and USDC across Ethereum, BNB Smart Chain, Tron and Solana, along with the native asset on each network.
It starts with a short call with Bitzaro. Then you complete a business (KYB) verification, set up Google Authenticator at first login, and try the console in a test environment. An API key is optional, only if you want to automate.
Through an Onetime Payment Link tied to an order. The link can fix one token on one chain, or let the customer choose Ethereum, BSC or TRON. Partial payments, even on different chains, add up until the order is paid in full.
Yes. With the Client feature you register your own members and give each one a dedicated wallet address and a unique wallet link, without them needing a full Bitzaro account. Every payment is then matched to the right customer.
Yes. Every incoming payment is screened for fraud before it settles into your balance. The source wallet is rated LOW, MED or HIGH risk using blockchain analytics from Elliptic.
It waits for you. LOW and MED payments move to your merchant balance automatically, but a HIGH-risk payment needs you to approve or reject it, and a rejected payment is refunded to its source. Bitzaro notes that a high-risk rating is a risk signal, not proof of wrongdoing.
Self-Healing keeps funds correctly classified when risk changes after payment. If the risk level of a source address rises, the funds move to the matching higher-risk wallet, and the move is logged in Replace History.
Bitzaro does. With Bitzaro WAAS, Bitzaro holds and protects the keys, keeps balances segregated per user, and gives you access to them through the API. Wallets are created and signed through multi-party computation (MPC), so no single private key exists to be lost or stolen. WAAS Lite runs on the same infrastructure.
The destination address is screened before any withdrawal. A LOW or MED-risk destination needs your Google Authenticator code; a HIGH-risk destination needs a manual approval after you review the risk report.
Yes. In WAAS Lite you top up the Gas Station with each chain's own token, such as ETH, BNB or TRX, and it covers the network fees on that chain. Gas Station shows your gas balance per chain and logs every use.
There are two plans: pay per transaction while you are starting out, or a flat monthly fee for unlimited collection volume once volume is steady. The current prices are on bitzaro.com/waas-lite.
Yes. WAAS Lite has an API for automating payment operations and sends four webhook events: Onetime Payment Callback, Chain Event, Gathering and User KYC. The technical reference is at waaslite.readme.io. A webhook reports an event; your own system still decides when to release goods.
Yes. WAAS Lite and WAAS are the same engine and the same account, so you can add the API without migrating balances.
Yes. Wallets, payment pages and payout flows can carry your brand, so your users stay inside your product while Bitzaro handles the chain infrastructure and the screening underneath.