Secure Web3 Wallet Solution
Start withwallet.openweb3.io

An open platform specializing in Web3 payment solutions,
dedicated to providing users with simple, secure,
and efficient cryptocurrency and global fiat mixed payment services.

100+ Happy Customers & 500M+ Users

Get Started

API Docs

Visualizing Success

What's in Openweb3?

Open & Secure

Accept and send crypto payments as a business. Fast, easy and secure.

Globally

Accept crypto payments globally Whether you’re selling online or offline, need a ready-to-use or highly customisable solution, we’ve got you covered

Development

Easy to customize and extend, saving you time and money.One small snippet of code to help you scale your business quickly.

Interface Starter Kit

Large bundle of Web3 SDKs

Explore a comprehensive range of widgets
We provide developers with a large number of web3 industry SDKs and widgets, which can be
integrated with one click to start a business.

Browse API Docs

FAQs

We’ve got the answers

1.How do I proceed with integration?

1.1. Merchant basic information registration.
1.2. Generate merchant public and private keys; input the public key into the system for API call verification.
1.3. Obtain API key.
1.4. Create application to get App ID.
1.4.1. Configure Webhooks.
1.4.2. Obtain Webhook public key for callback verification.
1.5. Integrate SDK (Java/Go/Node.js) on the server, initializing/calling the SDK using API key + merchant private key.

2.What is the service model?

WaaS (Wallet as a Service) offers a cloud-native deployment model, supporting both public and private deployments.

3.How does my wallet work?

3.1. Hot/Cold Separation
WaaS provides hot wallet addresses for deposit and aggregation; assets received at hot wallet addresses can be periodically aggregated to the merchant's cold wallet.
3.2. Key Management
KMS black box mode, private keys cannot be exported online, ensuring high security.

4.How do I handle deposits/withdrawals on-chain?

4.1. Transaction Fees Transfer fees can be estimated via API, and merchants can also customize transaction fees.
4.2. Zero Value Attack Prevention A minimum deposit/withdrawal amount is set to prevent zero value attacks.

5.How do I manage my ledger?

Internal transfers in games are processed off-chain, supporting high concurrency. Only deposits/withdrawals are on-chain. Merchants can choose not to use WaaS ledger and maintain their own user token ledger while using WaaS for deposit and withdrawal services.

6.How do I perform token swaps?

Supports token asset exchange both on-chain and cross-chain.
6.1. Client-Side Swap During deposits, users can perform on-chain swaps (Uniswap) directly.
6.2. Merchant-Side Swap After deposits, WaaS will swap tokens in the hot wallet using OKX, Kucoin, Uniswap, etc.
6.3. Exchange Rate Interface Data sources from OKX, Kucoin, Coinbase, etc., are pulled regularly (every minute) to ensure real-time pricing during swaps.

7.How do I handle fiat payment channels?

Third-party integrations for fiat payment channels like credit card payments (e.g., Changely, Onramp).

8.Can I support wallet import?

Fully managed back-end wallets are seamless for users; Wallet-Connect is needed for login authentication; Ton-Connect is by default linked to the user's wallet.

9.What versions of frontend API/SDK are available?

React.

10.What versions of backend SDK are available?

Java, Go, Node.js.

Still have questions?

Please describe your case to receive the most accurate advice

Get started with
Openweb3today