Laqira Protocol

Laqira Payments is a secure, efficient, and Fully Decentralized Asset-Agnostic Multi-Network Payment Gateway for WooCommerce, enabling businesses to accept digital payments seamlessly with advanced blockchain technology. It offers enhanced flexibility and security, transparent financial statements, and in-app wallet features for users.
<h3>Key Features:</h3>
<ul>
<li>Fully Decentralized: Uses blockchain for secure, anonymous transactions without third-party oversight.</li>
<li>Asset-Agnostic: Allows payments in any origin asset and provides stablecoin in destination to providers, minimizing risk and maximizing stability.</li>
<li>Multi-Network Support: Supports diverse network payments, with user options dependent on provider acceptance and configuration.</li>
<li>Chainlink Price Feeds: Automatic exact amount detection and stablecoin depeg detection for vendor settlement.</li>
<li>Security: Utilizes HttpOnly cookies for JWT authorization and employs robust input hardening and sanitization throughout.</li>
</ul>
<h3>How LaqiraPayments Works:</h3>
<ol>
<li>Provider Registration: Register on LaqiraPayments and receive a dedicated smart contract address (API key) where transparent financial records are carved.</li>
<li>Plugin Setup: Install the LaqiraPayments plugin, input your API key, and configure settings.</li>
<li>Customer Payment: Customers select the LaqiraPayments method, choose a network and cryptocurrency, connect their wallet, and complete the transaction.</li>
</ol>
<h3>External Services</h3>
This plugin connects to external services to complete wallet connections, read blockchain data, send blockchain transactions, load payment metadata, verify payment state, and open provider or explorer links. No external request is made merely by activating the plugin. After a merchant configures payment contract, wallet, RPC, or metadata settings, the plugin may contact configured or bundled payment/blockchain services during checkout/payment flows, scheduled cache refreshes, transaction verification, payment metadata loading, or when a user clicks an external link shown by the plugin.
1) Required Laqira runtime services 
* What the service is used for: Laqira services are used for provider registration links, support/documentation links, Laqira Pay account or wallet pages, Laqira-hosted payment metadata, payment contract metadata, token/network metadata, and payment verification data when the merchant configures Laqira-hosted endpoints or Laqira Pay account flows. 
* Domains that may be opened or requested: <code>laqirapay.com</code>, <code>laqirahub.com</code>. 
* What data is sent and when: When an administrator or customer clicks a Laqira link, the browser sends normal HTTPS request data such as IP address, user agent, referrer, and any data included in the destination URL. When the merchant uses Laqira-hosted configuration or metadata endpoints, the browser or store server may send configured provider/payment metadata, payment contract identifiers, token/network identifiers, transaction hashes, wallet addresses where required for payment verification, and normal HTTPS request data. 
* Required or optional: Required when the merchant uses Laqira provider registration, Laqira-hosted metadata, or Laqira Pay account/payment metadata flows; optional for support/documentation/account links. 
* Terms of Service: https://laqira.io/terms-and-conditions 
* Privacy Policy: https://laqira.io/privacy-policy
2) WalletConnect / Reown runtime services 
* What the service is used for: These services power the wallet connection modal, wallet discovery, WalletConnect sessions, WalletConnect relay/RPC features, session verification, telemetry/status endpoints used by the wallet connection libraries, and wallet deep-link routing. 
* Domains that may be requested by the generated checkout bundle or opened from the admin settings link: <code>cloud.walletconnect.com</code>, <code>api.web3modal.org</code>, <code>rpc.walletconnect.org</code>, <code>relay.walletconnect.org</code>, <code>pulse.walletconnect.org</code>, <code>echo.walletconnect.com</code>, <code>verify.walletconnect.com</code>, <code>verify.walletconnect.org</code>, <code>secure.walletconnect.org</code>, <code>secure-mobile.walletconnect.com</code>, <code>secure-mobile.walletconnect.org</code>, <code>walletconnect.com</code>, <code>walletconnect.org</code>, <code>reown.com</code>. 
* What data is sent and when: When a customer opens the wallet modal, searches/selects a wallet, scans a QR code, connects a wallet, or signs/submits a blockchain transaction, the browser may send wallet connection metadata, project ID, selected chain/network, wallet address or session identifiers, relay messages, transaction/session metadata, and normal HTTPS/WebSocket request data such as IP address and user agent. 
* Required or optional: Required for WalletConnect/Reown wallet connection flows; optional if the customer uses an injected wallet flow that does not require WalletConnect. 
* Terms of Service: https://reown.com/terms-of-service 
* Privacy Policy: https://reown.com/privacy-policy
3) Wallet application providers and wallet discovery/deep-link services 
* What the service is used for: The bundled wallet connection libraries include support for wallet-specific discovery pages, mobile deep links, install links, and optional wallet-specific connection flows for providers such as MetaMask / Consensys, Rainbow, Safe, Coinbase Wallet, Phantom, Solflare, Trust Wallet, and other wallets exposed by the bundled wallet libraries. 
* Domains that may be opened or requested depending on the wallet selected by the customer: <code>metamask.io</code>, <code>metamask.app.link</code>, <code>metamask-sdk.api.cx.metamask.io</code>, <code>mm-sdk-analytics.api.cx.metamask.io</code>, <code>fwd.metamask.io</code>, <code>rainbow.me</code>, <code>rainbow.download</code>, <code>rnbwapp.com</code>, <code>enhanced-provider.rainbow.me</code>, <code>learn.rainbow.me</code>, <code>www.rainbowkit.com</code>, <code>app.safe.global</code>, <code>phantom.app</code>, <code>solflare.com</code>, <code>t.me</code>, <code>go.cb-w.com</code>, <code>meldcrypto.com</code>, <code>apps.apple.com</code>, <code>play.google.com</code>, <code>chrome.google.com</code>, <code>microsoftedge.microsoft.com</code>, <code>addons.mozilla.org</code>, <code>addons.opera.com</code>, <code>trustwallet.com</code>. 
* What data is sent and when: These requests occur when the wallet connection UI is loaded, when the customer chooses a supported wallet, opens a wallet deep link, follows an install link, or uses a wallet-specific connection flow. The browser may send wallet/app selection metadata, chain/network information, wallet connection/session identifiers, public wallet address where required by the selected wallet flow, and normal HTTPS request data such as IP address and user agent. 
* Required or optional: Optional; the customer chooses the wallet provider. 
* MetaMask / Consensys Terms of Service: https://consensys.io/terms-of-use 
* MetaMask / Consensys Privacy Policy: https://consensys.io/privacy-notice 
* Rainbow Terms of Service: https://app.userainbow.com/static/documents/terms-of-service.pdf 
* Rainbow Privacy Policy: https://rainbow.me/privacy
4) Merchant-configured RPC endpoints 
* What the service is used for: Merchants may configure RPC endpoints so the plugin can read smart contract data, refresh payment/network metadata, check balances and allowances, verify transactions, estimate gas, and broadcast transactions requested by the customer. 
* Domains that may be requested: Any RPC endpoint configured by the merchant in the plugin settings or returned by the merchant’s configured payment metadata. 
* What data is sent and when: During checkout/payment flows, scheduled cache refreshes, transaction verification, or payment metadata loading, the browser or store server may send blockchain query data such as chain ID, contract address, token address, wallet address where needed, transaction hash, transaction payload data, token/contract metadata requests, and normal HTTPS request data such as IP address and user agent. 
* Required or optional: Required when the selected payment configuration depends on a merchant-configured RPC endpoint. The merchant is responsible for choosing RPC providers whose Terms of Service and Privacy Policy are suitable for the store’s use case.
5) Bundled chain metadata and default RPC references 
* What the service is used for: Bundled wallet/web3 libraries include default chain metadata and fallback RPC references for providers and networks such as thirdweb, Arbitrum, BNB Chain, Merkle, Base, Polygon, Mantle, WalletConnect RPC, and Infura / Consensys. These references may be used by the selected wallet, configured network metadata, merchant/network settings, or bundled library when the customer starts a blockchain payment flow. 
* Domains that may be requested depending on the configured network, selected wallet, and bundled library defaults: <code>bsc-dataseed.binance.org</code>, <code>rpc.walletconnect.org</code>, <code>56.rpc.thirdweb.com</code>, <code>api.avax.network</code>, <code>arb1.arbitrum.io</code>, <code>mainnet.base.org</code>, <code>polygon.drpc.org</code>, <code>rpc.mantle.xyz</code>, <code>eth.merkle.io</code>, <code>mainnet.infura.io</code>, <code>goerli.infura.io</code>, <code>sepolia.infura.io</code>, <code>arbitrum-mainnet.infura.io</code>, <code>arbitrum-goerli.infura.io</code>, <code>polygon-mainnet.infura.io</code>, <code>polygon-mumbai.infura.io</code>, <code>optimism-mainnet.infura.io</code>, <code>optimism-goerli.infura.io</code>, <code>avalanche-mainnet.infura.io</code>, <code>avalanche-fuji.infura.io</code>, <code>linea-mainnet.infura.io</code>, <code>linea-goerli.infura.io</code>, <code>celo-mainnet.infura.io</code>, <code>celo-alfajores.infura.io</code>, <code>aurora-mainnet.infura.io</code>, <code>aurora-testnet.infura.io</code>, <code>palm-mainnet.infura.io</code>, <code>palm-testnet.infura.io</code>, <code>starknet-mainnet.infura.io</code>, <code>starknet-goerli.infura.io</code>, <code>starknet-goerli2.infura.io</code>. 
* What data is sent and when: If a bundled/default RPC endpoint is used during a selected wallet or network flow, the request may include JSON-RPC data such as wallet address, transaction payload data, contract addresses, chain ID/network details, transaction hash, and normal HTTPS request data such as IP address and user agent. 
* Required or optional: Required only when the selected wallet/network/library flow uses one of these bundled/default RPC endpoints. Not every bundled RPC URL is called by the plugin. 
* WalletConnect RPC Terms of Service: https://reown.com/terms-of-service 
* WalletConnect RPC Privacy Policy: https://reown.com/privacy-policy 
* Infura / Consensys Terms of Service: https://consensys.io/terms-of-use 
* Infura / Consensys Privacy Policy: https://consensys.io/privacy-notice 
* thirdweb Terms of Service: https://thirdweb.com/terms 
* thirdweb Privacy Policy: https://thirdweb.com/privacy-policy 
* Arbitrum Terms of Service: https://arbitrum.io/tos 
* Arbitrum Privacy Policy: https://arbitrum.io/privacy 
* BNB Chain Terms / Disclaimer: https://www.bnbchain.org/en/disclaimer 
* BNB Chain Privacy Policy: https://www.bnbchain.org/en/privacy-policy 
* Merkle Privacy Policy: https://www.merkle.io/privacy 
* Base Terms of Service: https://docs.base.org/terms-of-service 
* Base Privacy Policy: https://docs.base.org/privacy-policy 
* Polygon Terms of Use: https://polygon.technology/terms-of-use 
* Polygon Privacy Policy: https://polygon.technology/privacy-policy 
* Mantle Terms of Service: https://www.mantle.xyz/terms 
* Mantle Privacy Policy: https://www.mantle.xyz/privacy-policy
6) Blockchain explorers, explorer APIs, and transaction links 
* What the service is used for: The plugin and bundled blockchain libraries may generate links to blockchain explorers or include explorer API metadata so customers or administrators can inspect transaction hashes, addresses, or network data. 
* Domains that may be opened or referenced depending on the selected network: <code>bscscan.com</code>, <code>api.bscscan.com</code>, <code>etherscan.io</code>, <code>api.etherscan.io</code>, <code>goerli.etherscan.io</code>, <code>sepolia.etherscan.io</code>, <code>arbiscan.io</code>, <code>api.arbiscan.io</code>, <code>basescan.org</code>, <code>api.basescan.org</code>, <code>mantlescan.xyz</code>, <code>api.mantlescan.xyz</code>, <code>snowtrace.io</code>, <code>api.snowtrace.io</code>, <code>polygonscan.com</code>, <code>solscan.io</code>. 
* What data is sent and when: A request is sent when a customer or administrator clicks an explorer link, or when a bundled library queries explorer API metadata for a supported chain. The browser or API request may include the transaction hash, wallet or contract address, selected network, and normal HTTPS request data such as IP address and user agent. 
* Required or optional: Optional for clicked explorer links; explorer API metadata may be required by the selected wallet/library/network. 
* BscScan Terms of Service: https://bscscan.com/terms 
* BscScan Privacy Policy: https://bscscan.com/privacyPolicy 
* Etherscan Terms of Service: https://etherscan.io/terms 
* Etherscan Privacy Policy: https://etherscan.io/privacyPolicy 
* Arbiscan Terms of Service: https://arbiscan.io/terms 
* Arbiscan Privacy Policy: https://arbiscan.io/privacyPolicy 
* BaseScan Terms of Service: https://basescan.org/terms 
* BaseScan Privacy Policy: https://basescan.org/privacyPolicy 
* PolygonScan Terms of Service: https://polygonscan.com/terms 
* PolygonScan Privacy Policy: https://polygonscan.com/privacyPolicy
7) Remote payment metadata, token metadata, ABI, and IPFS endpoints 
* What the service is used for: The plugin reads remote JSON, ABI, token, network, and metadata files so it can load supported assets, contract ABIs, chain metadata, wallet metadata, and payment configuration data. This includes the server-side request made by <code>BlockchainService::getRemoteJsonCid()</code> to the CID/metadata URL returned by the configured Laqira payment contract. 
* Domains that may be requested depending on the selected network and bundled library metadata: <code>ipfs.io</code>, <code>arweave.net</code>, <code>4byte.sourcify.dev</code>, <code>raw.githubusercontent.com</code>, <code>docs.soliditylang.org</code>, and any merchant-configured CID, ABI, token, network, or RPC metadata URL. 
* What data is sent and when: When the plugin refreshes blockchain configuration data or the checkout interface needs token/network/ABI metadata, the browser or store server requests the remote URL and sends normal HTTPS request data such as IP address and user agent. If the URL includes a CID, token, contract, network, or transaction identifier, that identifier is sent as part of the request URL. 
* Under which conditions: Requests are sent only after the merchant has configured the payment contract/RPC settings or when checkout/payment screens need the metadata to display available networks and assets. 
* Required or optional: Required when the selected payment configuration depends on remote metadata; optional when required metadata is already available locally. 
* Terms of Service / Privacy Policy: For Laqira-hosted metadata, see https://laqira.io/terms-and-conditions and https://laqira.io/privacy-policy . For the <code>ipfs.io</code> public gateway, see https://ipfs.tech/legal/ ; IPFS privacy background is documented at https://docs.ipfs.tech/concepts/privacy-and-encryption/ .
8) Static bundled library references that are not plugin runtime services 
Generated JavaScript bundles include third-party wallet/web3 library strings, documentation URLs, example URLs, package metadata, app-store install links, wallet deep-link domains, browser issue URLs, standards URLs, and optional media/embed references. These strings may appear in bundled JavaScript, but Laqira Payments does not intentionally call them as plugin runtime services unless a customer clicks a link, the selected wallet opens its own deep link, the selected wallet/library flow uses that service, or a merchant explicitly configures one of those URLs.
<ul>
<li>Examples found in bundled libraries: <code>docs.metamask.io</code>, <code>medium.com</code>, <code>ethstats.net</code>, <code>snowtrace.io</code>, <code>api.snowtrace.io</code>, <code>solscan.io</code>, <code>go.cb-w.com</code>, <code>t.me</code>, <code>apps.apple.com</code>, <code>play.google.com</code>, <code>chrome.google.com</code>, <code>microsoftedge.microsoft.com</code>, <code>addons.mozilla.org</code>, <code>addons.opera.com</code>, <code>www.youtube.com</code>, <code>player.vimeo.com</code>.</li>
</ul>
Note: Some bundled Composer, JavaScript, CSS, and license files contain documentation URLs, issue tracker URLs, example URLs, standards URLs, or project homepages. Those references are not automatically contacted by Laqira Payments during normal plugin operation. The lists above focus on domains that the generated runtime bundle, wallet libraries, configured blockchain/payment metadata, or user-clicked links may actually request or open.
Important Note: No external request is made merely by activating the plugin. After administrator configuration, external requests may occur during checkout/payment screens, scheduled cache refreshes, wallet connection, blockchain reads, transaction submission or verification, payment metadata loading, or when a user clicks an external link shown by the plugin.
<h3>Source Code</h3>
Human-readable source code, build tools, and build instructions for the generated JavaScript bundles are available at https://github.com/LaqiraProtocol/laqira-payments . The checkout bundle is generated from the source files under <code>src/</code> with <code>npm run build</code>; the release ZIP is generated with <code>tools/build-release-artifact.sh</code>.
<h3>Translations</h3>
<ul>
<li>English (en_US)</li>
<li>Chinese (zh_CN)</li>
<li>Hindi (hi_IN)</li>
<li>Spanish (es_ES)</li>
<li>Italian (it_IT)</li>
<li>Turkish (tr_TR)</li>
</ul>
<h3>Support</h3>
For support or bug reports, please visit the official support page at <code>https://laqirahub.com/laqira-pay/introduction</code> or the support forum.

Laqira Payments for WooCommerce

Laqira Payments for WooCommerce: Fully Decentralized Asset-Agnostic Multi-Network Crypto Payment Gateway for WooCommerce.

zenobank

Start Accepting Crypto Payments in 2 minutes.
0.1% Flat Fee and no KYC.
Binance Pay payments go directly to your Binance account (no merchant account required).
For On Chain payments (Arbitrum, Base, Ethereum, etc.), choose between Custodial and Non Custodial mode.
Custodial: we hold the funds for you. 
Non Custodial: funds go directly to your own wallet. 
<a href="https://pay.zenobank.io/demo" rel="nofollow ugc">Checkout demo</a>
Questions? Check the <a href="https://zenobank.io/#faqs" rel="nofollow ugc">FAQs</a> 
<a href="https://zenobank.io/support" rel="nofollow ugc">24/7 Support:</a>
<h3>External services</h3>
This plugin sends order data (amount, currency) to api.zenobank.io to process crypto payments.
<a href="https://zenobank.io/terms" rel="nofollow ugc">Terms of Service</a> | <a href="https://zenobank.io/privacy" rel="nofollow ugc">Privacy Policy</a>

Zeno Crypto Checkout for WooCommerce


Simplest and cheapest way to accept crypto in our stores


Best payment gateway

Lowest fees. USDT & USDC Payments. Supports Binance Pay and popular wallets like MetaMask, Phantom, Trust Wallet, etc...

Laqira Payments for WooCommerce vs Zeno Crypto Checkout for WooCommerce