Bitzaro is a digital asset platform for individuals and businesses to manage, receive, use and integrate supported digital assets.
Its product ecosystem includes consumer-facing products such as Bitzaro Wallet and Bitzaro Card, as well as business products for payments, invoicing and infrastructure. Bitzaro separates the product experience that users see from the underlying services that perform blockchain operations.
Bitzaro serves both individual users and businesses.
Individuals can use products such as Bitzaro Wallet and Bitzaro Card. Businesses can use products such as WAAS, WAAS Lite, Bitzaro Invoice and Onramp depending on whether they need infrastructure, merchant collections, invoicing or fiat-to-crypto functionality.
Bitzaro offers different products for different digital asset use cases.
Important: Product availability, features and eligibility can vary by account, jurisdiction and current product configuration.
Bitzaro products can share underlying services while maintaining separate user experiences and use cases.
A user may initiate an action through a product such as Bitzaro Wallet while underlying infrastructure performs functions such as address generation, transaction execution, gas handling or risk screening. Sharing infrastructure does not mean that the products are interchangeable.
WAAS provides underlying wallet and blockchain infrastructure, while WAAS Lite provides a ready-to-use merchant payment workflow built on top of that infrastructure. WAAS handles infrastructure functions such as wallet operations, address generation, blockchain execution and gas. WAAS Lite gives merchants a Dashboard and API for Client Management, payment links, payment tracking, risk controls, balances, withdrawals and webhooks.
Most users do not need to understand the technical details of blockchain infrastructure to use Bitzaro’s user-facing products.
Bitzaro products are designed to handle many underlying functions such as transaction execution and gas. Users should still understand basic safety steps such as selecting the correct network, checking the recipient address and reviewing transaction details before confirming a transfer.
No. Product availability can depend on jurisdiction, product eligibility, verification requirements and current service availability.
A product appearing on the Bitzaro website does not automatically mean every user in every country is eligible to use it. The eligibility information shown during the relevant onboarding or product flow should be treated as the current position.
Yes. Digital asset products, supported assets, networks, fees, limits and third-party integrations can change over time.
For time-sensitive information, use the latest value shown in the relevant Bitzaro product interface, fee schedule, Help Center article or other approved current source.
Important: Avoid relying on old screenshots or copied fee tables when the live product displays different information.
Bitzaro Wallet is Bitzaro’s digital asset wallet for receiving, sending and managing supported assets across supported blockchain networks.
The Wallet provides the user-facing experience while Bitzaro’s underlying infrastructure handles supported wallet operations, blockchain execution and gas. Depending on the features available to the account, the Wallet can also surface Card, Multisignature and risk-management functions.
Bitzaro Wallet is designed for users who want to manage digital assets without managing every blockchain-specific operation themselves.
It can also support teams that need additional approval controls through Multisignature and users who want access to supported transaction risk-management features.
Bitzaro Wallet supports core digital asset management and selected connected Bitzaro features.
Bitzaro Wallet supports the assets and networks currently made available through Bitzaro’s wallet infrastructure.
Supported coverage can change. Always confirm the asset and network displayed in Bitzaro before initiating a deposit or withdrawal rather than relying on an older list.
Important: The sender and receiver must use compatible asset and network combinations.
A digital asset can exist on more than one blockchain network, and the sending and receiving networks must be compatible.
For example, the same stablecoin may be available on several networks. Before transferring funds, verify the asset, network and destination address shown by the receiving service.
Important: Using an unsupported or incorrect network can prevent funds from being credited correctly and recovery may not be possible.
For supported Bitzaro Wallet flows, users do not need to maintain every network’s native token separately solely to pay gas.
The underlying infrastructure manages gas as part of supported transaction execution. The way a fee is charged or displayed can still depend on the product and transaction.
Your Main Wallet is created when you sign up. It holds your funds, and you reload your Bitzaro Card from it.
Yes. You can create and name wallets to organise funds around your needs, such as a Savings wallet or a Business wallet.
Risk Matrix is Bitzaro’s risk-analysis layer for supported wallet and transaction workflows.
It can use blockchain analytics information and Bitzaro risk logic to provide risk-related information about supported transaction sources or destination addresses.
Important: Risk Matrix is a risk-management tool. It does not guarantee that a wallet, transaction or counterparty is safe or unsafe.
No. A LOW-risk result means the transaction or address received a lower-risk classification based on the information available at that time.
Blockchain data and risk intelligence can change. A lower-risk classification should not be treated as a guarantee that an address, transaction or counterparty is risk-free.
No. A HIGH-risk classification is a risk signal, not proof of fraud, criminal activity or wrongdoing.
Higher-risk results may lead to additional controls, segregation or review depending on the applicable product workflow.
Yes. Risk information can change when new blockchain activity or additional intelligence becomes available.
An address that previously received one classification may later interact with different counterparties or become associated with new risk information. Some Bitzaro workflows are designed to respond to those changes rather than relying only on the first screening result.
Where the applicable screening feature is available, a supported destination address can be assessed before the transfer is completed.
The result can include information such as a risk level, detected labels and analysis details. Users should consider the result together with the context of the intended transaction.
For supported Risk Matrix screening workflows, downloadable risk reports can be available.
A report can include information such as the risk level, detected labels and analysis details associated with the screening result.
Multisignature is a Bitzaro Wallet feature for situations where stronger approval or multi-party authorization is required before funds can be moved.
It uses Bitzaro’s authorization layer to apply additional signing controls instead of relying only on the ordinary single-user transaction flow.
Multisignature can be useful for teams, shared treasury arrangements and users who want additional authorization rules for selected wallet activity.
The exact approval requirements depend on how Multisignature is configured.
Card functions can be surfaced through the Wallet-facing experience while Card issuance and settlement remain part of the separate Card infrastructure.
Supported Wallet-facing Card functions can include application, reload, Card status, spending history, alerts and Card management.
No. Bitzaro Invoice and Bitzaro Wallet show separate balances. The Main Wallet balance previously shown in Invoice can now be viewed in Bitzaro Wallet. Invoice has its own balance and new wallet addresses.
Bitzaro Card allows eligible users to reload supported digital asset value onto a Card balance for supported everyday spending. USDT converts when you pay.
The Card product combines a Bitzaro user-facing management experience with separate card issuance and settlement infrastructure.
Card eligibility depends on the current Card programme, country availability, identity verification and other applicable eligibility requirements.
Completing KYC is one part of the process and does not by itself guarantee Card approval.
A virtual Card is issued digitally, while a physical Card is a physical payment card delivered to an eligible user.
Virtual Cards are suited to supported online and digital-wallet transactions. Physical Cards can additionally support eligible in-store and ATM use where available. Fees and features can differ between Card types.
Apply through the supported Bitzaro Card or Wallet experience and complete the required application and verification steps.
Important: Card approval remains subject to eligibility, compliance and issuer requirements.
No. Your Bitzaro Wallet and your Bitzaro Card each have their own balance. Reload your card from your Main Wallet before you spend.
Digital asset value must first be reloaded onto the Card balance before it becomes available for Card spending.
You reload your Bitzaro Card from your Main Wallet. Open the Card section in the Bitzaro Wallet app, tap Reload, enter the amount, check the fee, then confirm with your passkey. If you don’t have a passkey, use your Google Authenticator code instead. The minimum reload is 50 USD.
Before confirming a reload, review the amount, the resulting Card balance and the reload fee shown.
Holding digital assets in Bitzaro Wallet does not automatically make the same value available for Card spending.
Check whether the required Card reload has been completed and whether the Card shows an available spending balance.
A completed crypto-to-Card funding transaction should not be assumed to be automatically reversible.
Review the amount and the reload fee carefully before confirming the reload. If you believe a reload was made in error, contact support promptly.
You can use an eligible Bitzaro Card where the underlying card network and merchant accept the transaction, subject to applicable restrictions.
Yes, where the merchant accepts the Card and the transaction meets the applicable Card programme requirements.
Virtual Cards are particularly suited to eligible online card-not-present transactions.
Where ATM functionality is supported for your Card, a physical Card can be used at eligible ATMs subject to limits and fees.
An ATM operator may impose its own fee in addition to any Card programme fee.
A Card transaction can be declined even when the Card itself is valid.
Where the applicable Card management control is available, you can freeze the Card to stop supported new transactions.
Freezing is useful if the Card is lost, stolen or you notice activity you do not recognize.
Freeze the Card as soon as possible and contact Bitzaro through an official support channel.
Do not wait for an unauthorized transaction to occur before taking action.
Replacement is available for eligible Cards through the applicable Card management process.
Replacement availability, delivery and fees depend on the Card type and current Card programme terms.
Card fees can include issuance, renewal, reload, ATM, foreign-currency and replacement charges depending on the action.
Because fee figures can change, use the current fee shown in the product or approved Card fee schedule rather than relying on an older FAQ value.
Important: A fee-bearing action should display the applicable current fee before confirmation whenever supported.
Yes. Card limits can depend on Card type, jurisdiction, verification status and programme requirements.
Use the limits shown in the current product interface as the applicable limits for the account.
Bitzaro WAAS is the underlying wallet and blockchain infrastructure layer used for supported on-chain operations.
Its responsibilities include wallet operations, address generation, blockchain transaction execution, gas handling and infrastructure used beneath other Bitzaro products.
No. Bitzaro Wallet is a user-facing product, while WAAS is underlying infrastructure.
A user can initiate a transaction through the Wallet interface while WAAS performs supported blockchain operations underneath.
No. WAAS is primarily infrastructure rather than a ready merchant operations dashboard.
WAAS Lite is the separate merchant-facing product that provides Dashboard, payment-management and API workflows on top of underlying infrastructure.
WAAS is most relevant to businesses, platforms and product teams that need deeper wallet or blockchain infrastructure access and have the engineering resources to integrate it.
A direct infrastructure integration generally gives a business more responsibility for its own product interface, payment logic, reconciliation and operational controls.
WAAS supports core infrastructure functions used by supported Bitzaro products and integrations.
Yes. Address generation is one of the core infrastructure functions associated with WAAS.
Higher-level products can use those addresses in their own customer, payment or wallet workflows.
Yes. Gas handling forms part of WAAS transaction execution for supported blockchain operations.
The way a gas cost is ultimately presented to a user or merchant depends on the product or commercial arrangement using the infrastructure.
No. Some products use an intermediate API or service layer rather than connecting directly.
For example, the current product architecture routes Bitzaro Invoice and Payroll operations through the Wallet V2 API to reach the underlying execution infrastructure.
A direct WAAS integration can suit a business that wants greater control over its own application and has the technical resources to build the surrounding workflow.
WAAS Lite is better suited to businesses that want ready merchant payment tools instead of building the full payment-management layer themselves.
WAAS Lite packages Client Management, Onetime Payment Links, risk workflows, balances, Gas Station, reports and webhooks into a merchant-facing Dashboard and API.
Bitzaro WAAS Lite is a merchant-facing digital asset payment product that combines a Dashboard and API with ready payment-management workflows.
WAAS Lite orchestrates merchant operations while underlying WAAS infrastructure performs supported custody and blockchain execution.
WAAS Lite is designed for merchants and platforms that want to accept or manage crypto payments without building a complete blockchain payment stack themselves.
WAAS Lite combines customer, payment, risk, treasury and integration tools for merchant operations.
A Client represents an individual customer, member or user managed by the merchant.
Creating separate Client records helps the merchant associate wallet and payment activity with the correct customer instead of relying on one generic merchant address for everyone.
Yes. WAAS Lite supports dedicated wallet functionality for individual merchant Clients.
This makes it easier to attribute deposits and payment activity to a specific customer or member.
Dedicated Client wallets improve attribution, reconciliation and reporting.
The current WAAS Lite design provides a unique wallet link for a Client.
Applicable payment and Onetime activity can then be associated with that Client record for clearer tracking.
An Onetime Payment Link is a payment request created for a specific transaction or order.
The merchant can associate an order with the payment request and share the resulting payment flow with the customer. Once the required payment condition is met, the payment status can be updated and the merchant can be notified.
A payment link creates a structured payment record rather than an unlabelled transfer to a generic wallet address.
Yes. WAAS Lite supports partial payments for applicable Onetime payment requests.
Multiple qualifying transactions can contribute toward the amount required by the payment request until the required total is reached.
Applicable Onetime configurations can support cross-chain partial payment scenarios.
The payment request and supported routes determine which networks can contribute to the payment. Merchants should rely on the networks shown in the current product when creating the payment request.
Yes. An Onetime payment can be configured for a fixed supported token and fixed network.
In that configuration, the payer should use the specified payment route and address.
Yes, for supported multi-chain configurations.
The merchant can define a token while allowing payment through one of the supported networks made available for that request.
The networks available to a merchant or Onetime request depend on the current product configuration.
The current documented multi-chain Onetime flow includes Ethereum, BNB Smart Chain and TRON. Always use the network options shown when creating the payment request as the current source of truth.
WAAS Lite detects and tracks the payment, then continues the applicable payment, screening and routing workflow.
Yes. Supported WAAS Lite payment flows include risk screening and risk-based handling.
The applicable screening stage and subsequent handling depend on the payment configuration and product workflow.
A higher-risk payment can require additional handling instead of automatically following the standard lower-risk flow.
Important: A higher-risk classification is a risk-management signal and should not be presented as proof of wrongdoing.
Self-Healing is a risk-management mechanism that can respond when the assessed risk level associated with funds changes after receipt.
If the risk level increases, the system can migrate funds to the appropriate higher-risk wallet and record the migration.
Blockchain risk information can change as addresses interact with new counterparties or new intelligence becomes available.
Self-Healing is designed to respond to those changes rather than assuming the first risk assessment remains permanent.
Replace History is the audit record for address migrations triggered by Self-Healing.
Gathering allows a merchant to aggregate funds from Client wallets into the merchant’s main balance structure.
This lets merchants preserve Client-level attribution for incoming payments while later consolidating funds for treasury or operational use.
The current documented WAAS Lite configuration describes Gathering as merchant-triggered rather than fully automatic.
The merchant initiates the aggregation when appropriate for its operational workflow.
Yes. WAAS Lite includes Balance and Withdrawal functionality for supported merchant balances.
Additional authentication and risk controls can apply depending on the balance and withdrawal destination.
Yes. The current WAAS Lite flow requires Google Authenticator for supported withdrawal actions.
This provides an additional authorization step beyond ordinary account access.
Gas Station manages the blockchain gas requirements associated with supported WAAS Lite merchant operations.
The current product design supports sponsored and self-managed gas configurations. Gas usage can also be tracked for operational reporting.
Yes. Transaction History records supported merchant activity and provides filters for operational review.
Yes. Applicable transaction and gas records can support CSV export for reporting and reconciliation.
Exported records can help finance, operations and compliance teams reconcile merchant activity.
Yes. WAAS Lite provides API access for merchants that want to automate supported payment operations.
Merchants that do not require automation can also perform supported workflows through the Dashboard.
An API key is a credential used by the merchant’s system to authenticate supported API requests.
API keys should be treated as sensitive credentials, stored securely and never exposed publicly or embedded insecurely in client-side applications.
Yes. WAAS Lite can send supported event notifications to a merchant-provided callback URL.
Webhooks allow the merchant’s system to react to relevant events without constantly polling WAAS Lite for changes.
Webhooks can help synchronize payment and customer events with the merchant’s own systems.
Not necessarily. A webhook reports an event; the merchant remains responsible for its own fulfilment rules and business logic.
The merchant should verify the event type and any required internal conditions before taking irreversible fulfilment actions.
Merchant onboarding begins with contacting Bitzaro and completing the required business verification.
After onboarding, the merchant receives access to the applicable environment and configures the required account-security controls before using supported payment and withdrawal functions.
Bitzaro Invoice is a business payment product for creating, sending, tracking and managing digital asset invoices.
It gives businesses a structured invoicing workflow rather than requiring every commercial payment to be handled as an ordinary wallet-to-wallet transfer.
Bitzaro Invoice is designed for B2B merchants and teams that need structured crypto collection and payment records.
An invoice adds business context and payment tracking around the transfer.
Yes. The current product architecture supports Project and team-member management.
This allows businesses to organize invoicing activity around operational roles rather than requiring every action to be handled through one person.
Bitzaro Invoice supports different payment paths depending on the payer and configuration.
A payer within the supported Bitzaro environment can use an in-system payment flow, while external collection can use an Onetime-based payment link.
Yes. A single invoice can receive multiple partial payments until the required total is reached.
The invoice tracks progress toward the outstanding amount as additional qualifying payments are received.
The amount received is recorded against the invoice, while the remaining amount continues to be outstanding.
Further payments can be made until the invoice is fully paid.
The current product design allows individual payments to move into the merchant wallet workflow as they are received rather than waiting for the full invoice amount.
The invoice itself continues tracking the remaining outstanding amount.
Supported Invoice payment flows can use Bitzaro’s wallet and risk infrastructure to route incoming funds according to the applicable risk classification.
This supports separation into the relevant LOW, MEDIUM or HIGH wallet workflow where applicable.
A Project organizes related invoices, team activity and funds around a specific business purpose.
Projects can have assigned team members and can be connected to the applicable Group Wallet structure.
A Group Wallet is a wallet structure used by relevant Project, Invoice and Payroll workflows.
It helps businesses organize funds according to operational structure rather than treating every commercial payment as an unrelated transaction.
The current product architecture includes Payroll workflows within the Invoice environment.
No. The current architecture separates Payroll preparation, approval and execution stages.
This allows different roles to participate in the process rather than combining all control into a single unrestricted action.
After the required preparation, approval and funding conditions are met, the payout workflow moves through the relevant API and underlying execution infrastructure to the employee destination wallet.
The exact operational steps depend on the current Payroll configuration.
Bitzaro Onramp is a fiat-to-crypto service that allows eligible users to obtain supported digital assets using an available fiat payment route.
For business integrations, the Onramp experience can be embedded within a merchant’s own application, H5 environment or webpage.
Onramp is relevant to merchants whose users hold fiat but need to obtain crypto as part of the merchant’s service.
It can reduce the need for a user to leave the merchant environment, obtain crypto separately and then return to transfer it manually.
The current product design supports an API-based merchant integration with an embeddable Onramp URL.
The merchant can pre-bind the destination wallet address associated with the relevant user.
After the applicable purchase and verification steps are completed, the supported digital asset can be delivered to that destination through the underlying infrastructure.
In the documented merchant integration, the destination address is pre-bound by the merchant rather than freely changed by the user during the purchase flow.
This helps the merchant control the intended destination within the integrated experience.
Identity verification can be required as part of the Onramp flow.
The applicable verification requirement can depend on user status, transaction activity, jurisdiction and current compliance rules.
No. Payment-method availability can vary by jurisdiction, currency, provider and current product configuration.
The payment options shown during the transaction should be treated as the current available methods for that user and flow.
No. Onramp availability depends on jurisdiction, payment-provider availability, eligibility and applicable legal or compliance requirements.
Users and merchants should rely on the current onboarding and transaction flow for availability.
KYC means Know Your Customer and refers to the process used to verify an individual’s identity.
KYC supports customer identification, eligibility, compliance and risk-management requirements for applicable Bitzaro products.
KYB means Know Your Business and refers to verification of a business customer.
Verification helps Bitzaro support customer identification, anti-money laundering, sanctions, fraud-prevention and product-eligibility controls.
The exact information required can vary according to product, user type, jurisdiction, transaction activity and risk.
Not necessarily. Verification requirements can differ by product, user type, jurisdiction, transaction level and applicable risk.
Additional information can be requested when required by the relevant product or compliance process.
Bitzaro uses a KYC service built on top of Sumsub for supported identity-verification workflows.
The Bitzaro product layer can consume this verification service rather than each product implementing a completely separate KYC process.
Supported Bitzaro workflows can use blockchain analytics information together with Bitzaro risk-management logic to assess wallet or transaction risk.
The resulting assessment can influence whether activity follows the standard flow or receives additional controls.
No. Risk screening provides a risk assessment based on available data; it does not guarantee that a wallet or transaction is completely free from risk.
Risk information can change as blockchain activity and intelligence evolve.
Yes. A supported transaction can require additional handling when relevant compliance, fraud or risk indicators are detected.
The exact review process depends on the product and the applicable risk or compliance rule.
Segregation helps prevent funds with materially different risk profiles from being mixed automatically.
Google Authenticator provides an additional authentication factor for supported Bitzaro actions.
For example, the current WAAS Lite flow uses it during security setup and for applicable withdrawal authorization.
No. Never share passwords, OTPs or authenticator codes with another person.
If someone unexpectedly asks for a security code, stop and verify that you are using an official Bitzaro channel.
Take action immediately to secure the account and any connected Card or wallet activity.
Some Bitzaro products and transactions have fees.
The applicable fee can depend on the product, transaction type, asset, network, Card action, conversion, withdrawal or merchant agreement.
Important: Where a fee applies to a user action, use the current amount shown before confirmation or in the approved current fee schedule.
Fees are operational information that can change, so one current source of truth is safer than duplicating figures across multiple pages.
The latest fee shown in the product interface or approved fee schedule should take priority over older copied content.
A transaction hash, or TX hash, is a unique identifier for a blockchain transaction.
It can be used to locate the transaction on the relevant blockchain explorer and review details such as status, sending address, receiving address, amount and confirmations.
Confirmations indicate that a blockchain transaction has been included in the network history and that additional blocks have been added afterwards.
A Bitzaro product can require a minimum confirmation condition before treating a payment as complete.
A transaction can remain pending because of network, confirmation, product-processing or risk-review conditions.
A successful blockchain transfer does not always mean the full Bitzaro product workflow has finished.
Confirmed blockchain transfers are generally irreversible and should not be treated like ordinary reversible card payments.
Always check the recipient address, asset, network and amount before confirming a transfer.
Using the wrong or unsupported network can prevent funds from being credited correctly and recovery may not be possible.
Keep the asset, amount, network used, intended network, destination address and transaction hash, then contact the relevant support team.
Important: Do not send another transaction until you have confirmed the correct network and destination.
Once a blockchain transaction has been confirmed, Bitzaro may not be able to recover funds sent to an address entered incorrectly.
Contact support promptly with the transaction details, but do not assume recovery is technically possible.
Provide enough transaction information for support to identify the product and transaction without sharing security credentials.
Important: Never include passwords, OTPs or authenticator codes.
Start by checking the transaction hash on the relevant blockchain explorer.
If the transaction is not confirmed on-chain, the issue may relate to the blockchain transaction itself. If it is confirmed but the Bitzaro product has not updated, the issue may relate to payment detection, confirmation rules, amount, risk screening, product processing or merchant integration.
Check the blockchain transaction and the payment configuration before assuming the payment failed.
Verify both the merchant endpoint and the actual WAAS Lite payment status.
No. Webhook delivery and blockchain payment status are different.
Always check the payment record and blockchain transaction rather than treating a missing callback as proof that no payment occurred.
The current Transaction History design supports filtering using transaction hash together with other transaction fields.
Supported filters can include network, token, address, date and transaction type.
The Wallet balance and Card balance are separate.
Digital asset value must first be reloaded onto the Card balance before it becomes available for Card spending.
Freeze the Card using the available Card controls and contact Bitzaro through an official support channel as soon as possible.
Provide the relevant Card transaction details without sharing passwords, OTPs or authentication codes.
Stop repeated attempts and check the Card balance, PIN, Card status, ATM compatibility and applicable limits.
If the issue continues, contact support before making additional attempts. Repeated incorrect PIN attempts can lead to additional Card restrictions.
A Card can be valid while a particular merchant still declines the transaction.
Possible causes include merchant-category restrictions, merchant-acquirer rules, geographic restrictions, transaction limits, unsupported transaction types or issuer/network controls.
Choose WAAS when you need deeper infrastructure control; choose WAAS Lite when you want ready merchant payment workflows.
Use Bitzaro Invoice when the main workflow is structured invoicing and projects; use WAAS Lite when the main workflow is broader merchant payment collection and customer wallet management.
Yes, where the relevant products and account configuration support the business use case.
A business can have different requirements for collections, invoices, customer wallets, Card programmes, fiat-to-crypto purchasing and underlying wallet infrastructure. The appropriate combination depends on the business model and technical requirements.