Laqira Protocol

<p>Laqira Payments is a secure, efficient, and <strong>Fully Decentralized Asset-Agnostic Multi-Network Payment Gateway</strong> 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.</p>
<h3>Key Features:</h3>
<ul>
<li><strong>Fully Decentralized:</strong> Uses blockchain for secure, anonymous transactions without third-party oversight.</li>
<li><strong>Asset-Agnostic:</strong> Allows payments in <strong>any origin asset</strong> and provides stablecoin in destination to providers, minimizing risk and maximizing stability.</li>
<li><strong>Multi-Network Support:</strong> Supports diverse network payments, with user options dependent on provider acceptance and configuration.</li>
<li><strong>Chainlink Price Feeds:</strong> Automatic exact amount detection and stablecoin depeg detection for vendor settlement.</li>
<li><strong>Security:</strong> Utilizes HttpOnly cookies for JWT authorization and employs robust input hardening and sanitization throughout.</li>
</ul>
<h3>How LaqiraPayments Works:</h3>
<ol>
<li><strong>Provider Registration:</strong> Register on LaqiraPayments and receive a dedicated smart contract address (API key) where transparent financial records are carved.</li>
<li><strong>Plugin Setup:</strong> Install the LaqiraPayments plugin, input your API key, and configure settings.</li>
<li><strong>Customer Payment:</strong> Customers select the LaqiraPayments method, choose a network and cryptocurrency, connect their wallet, and complete the transaction.</li>
</ol>
<h3>External Services</h3>
<p>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.</p>
<p>1) Required Laqira runtime services<br />
* 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.<br />
* Domains that may be opened or requested: <code>laqirapay.com</code>, <code>laqirahub.com</code>.<br />
* 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.<br />
* 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.<br />
* Terms of Service: https://laqira.io/terms-and-conditions<br />
* Privacy Policy: https://laqira.io/privacy-policy</p>
<p>2) WalletConnect / Reown runtime services<br />
* 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.<br />
* 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>.<br />
* 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.<br />
* Required or optional: Required for WalletConnect/Reown wallet connection flows; optional if the customer uses an injected wallet flow that does not require WalletConnect.<br />
* Terms of Service: https://reown.com/terms-of-service<br />
* Privacy Policy: https://reown.com/privacy-policy</p>
<p>3) Wallet application providers and wallet discovery/deep-link services<br />
* 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.<br />
* 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>.<br />
* 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.<br />
* Required or optional: Optional; the customer chooses the wallet provider.<br />
* MetaMask / Consensys Terms of Service: https://consensys.io/terms-of-use<br />
* MetaMask / Consensys Privacy Policy: https://consensys.io/privacy-notice<br />
* Rainbow Terms of Service: https://app.userainbow.com/static/documents/terms-of-service.pdf<br />
* Rainbow Privacy Policy: https://rainbow.me/privacy</p>
<p>4) Merchant-configured RPC endpoints<br />
* 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.<br />
* 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.<br />
* 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.<br />
* 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.</p>
<p>5) Bundled chain metadata and default RPC references<br />
* 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.<br />
* 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>.<br />
* 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.<br />
* 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.<br />
* WalletConnect RPC Terms of Service: https://reown.com/terms-of-service<br />
* WalletConnect RPC Privacy Policy: https://reown.com/privacy-policy<br />
* Infura / Consensys Terms of Service: https://consensys.io/terms-of-use<br />
* Infura / Consensys Privacy Policy: https://consensys.io/privacy-notice<br />
* thirdweb Terms of Service: https://thirdweb.com/terms<br />
* thirdweb Privacy Policy: https://thirdweb.com/privacy-policy<br />
* Arbitrum Terms of Service: https://arbitrum.io/tos<br />
* Arbitrum Privacy Policy: https://arbitrum.io/privacy<br />
* BNB Chain Terms / Disclaimer: https://www.bnbchain.org/en/disclaimer<br />
* BNB Chain Privacy Policy: https://www.bnbchain.org/en/privacy-policy<br />
* Merkle Privacy Policy: https://www.merkle.io/privacy<br />
* Base Terms of Service: https://docs.base.org/terms-of-service<br />
* Base Privacy Policy: https://docs.base.org/privacy-policy<br />
* Polygon Terms of Use: https://polygon.technology/terms-of-use<br />
* Polygon Privacy Policy: https://polygon.technology/privacy-policy<br />
* Mantle Terms of Service: https://www.mantle.xyz/terms<br />
* Mantle Privacy Policy: https://www.mantle.xyz/privacy-policy</p>
<p>6) Blockchain explorers, explorer APIs, and transaction links<br />
* 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.<br />
* 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>.<br />
* 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.<br />
* Required or optional: Optional for clicked explorer links; explorer API metadata may be required by the selected wallet/library/network.<br />
* BscScan Terms of Service: https://bscscan.com/terms<br />
* BscScan Privacy Policy: https://bscscan.com/privacyPolicy<br />
* Etherscan Terms of Service: https://etherscan.io/terms<br />
* Etherscan Privacy Policy: https://etherscan.io/privacyPolicy<br />
* Arbiscan Terms of Service: https://arbiscan.io/terms<br />
* Arbiscan Privacy Policy: https://arbiscan.io/privacyPolicy<br />
* BaseScan Terms of Service: https://basescan.org/terms<br />
* BaseScan Privacy Policy: https://basescan.org/privacyPolicy<br />
* PolygonScan Terms of Service: https://polygonscan.com/terms<br />
* PolygonScan Privacy Policy: https://polygonscan.com/privacyPolicy</p>
<p>7) Remote payment metadata, token metadata, ABI, and IPFS endpoints<br />
* 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.<br />
* 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.<br />
* 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.<br />
* 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.<br />
* Required or optional: Required when the selected payment configuration depends on remote metadata; optional when required metadata is already available locally.<br />
* 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/ .</p>
<p>8) Static bundled library references that are not plugin runtime services<br />
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.</p>
<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>
<p>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.</p>
<p><strong>Important Note:</strong> 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.</p>
<h3>Source Code</h3>
<p>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>.</p>
<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>
<p>For support or bug reports, please visit the official support page at <code>https://laqirahub.com/laqira-pay/introduction</code> or the support forum.</p>


Laqira Payments for WooCommerce

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

miniOrange

miniorangesecurity

<p>The [<a href="https://plugins.miniorange.com/web3-wordpress-login" rel="nofollow ugc">Web3 – Crypto wallet Login & NFT token gating</a>] plugin allows users to Sign Up/log in to a WordPress website using their cryptocurrency wallet. It also helps to NFT token gate exclusive content of the WordPress site. Here only users who have specified NFTs in their crypto wallet can access locked content.</p>
<p>To understand the functionality and flow of your Web3 wallet login button, please refer to the Setup Guide [<a href="https://developers.miniorange.com/docs/wordpress-web3/features/enable-web3-wallets" rel="nofollow ugc">here</a>].</p>
<p>Our Web3 Authentication plugin uses digital signature verification for crypto login. This increases the security of WordPress crypto login.</p>
<p>During crypto wallet signup, our Web3 plugin creates a regular WordPress user account, so existing plugins, and customizations will continue to work as intended.</p>
<p>Watch video embedded below to get an overview of the plugin functionality<br />
<span class="embed-youtube" style="text-align:center; display: block;"><iframe loading="lazy" class="youtube-player" width="750" height="422" src="https://www.youtube.com/embed/YigW54vg22k?version=3&rel=1&showsearch=0&showinfo=1&iv_load_policy=1&fs=1&hl=en-US&autohide=2&wmode=transparent" allowfullscreen="true" style="border:0;" sandbox="allow-scripts allow-same-origin allow-popups allow-presentation allow-popups-to-escape-sandbox"></iframe></span></p>
<h3>The key takeaways from the video you shouldn’t miss:</h3>
<ul>
<li>The miniOrange Web3 Authentication Plugin allows for secure access to gated content using NFT tokens.</li>
<li>Website owners can control access to specific pages by configuring token details and content gating.</li>
<li>Testing the configuration ensures that only users with the required NFT token can access the content.</li>
<li>Users can easily log in with their crypto wallets, simplifying the authentication process.</li>
<li>Error pages are displayed when users don’t have the necessary NFT token in their wallets.</li>
<li>The plugin provides flexibility to enable or disable profile completion forms for new crypto users.</li>
</ul>
<p>The Web3 authentication login plugin supports both <strong>Hot and Cold Wallet Log in.</strong></p>
<h3>Hot Wallets Supported for Crypto Login</h3>
<p>MetaMask, WalletConnect, Coinbase, Trust, Edge, XUMM, MyAlgo, Pera Wallet, Nami, Typhon, Flint, VeWorld Electrum, Robinhood, Binance, Mycelium, AtomicDEX, Jaxx, Samourai, Huobi, Luno, ZenGo, Crypto.com, Bitcoin IRA, Exodus etc</p>
<h3>Cold Wallets Supported for Crypto Login</h3>
<p>Ledger Nano S, Ledger Nano X, Gamestop, Trezor, KeepKey, CoolWallet Pro, Safepal S1, Keystone Pro, Ellipal Titan, etc</p>
<h3>Supported Blockchains</h3>
<p>[<a href="https://plugins.miniorange.com/ethereum-wordpress-nft-integration" rel="nofollow ugc">Ethereum</a>], [<a href="https://plugins.miniorange.com/polygon-wordpress-nft-integration" rel="nofollow ugc">Polygon</a>], [<a href="https://plugins.miniorange.com/algorand-wordpress-nft-integration" rel="nofollow ugc">Algorand</a>], [<a href="https://plugins.miniorange.com/solana-wordpress-nft-integration" rel="nofollow ugc">Solana</a>], [<a href="https://plugins.miniorange.com/loopring-wordpress-nft-integration" rel="nofollow ugc">Loopring Layer 2</a>], [<a href="https://plugins.miniorange.com/cronos-wordpress-nft-integration" rel="nofollow ugc">Chronos</a>], [<a href="https://plugins.miniorange.com/xrpl-nft-token-gating" rel="nofollow ugc">XRPL</a>], Binance, Avalanche, , Base Layer 2, Cardano, All EVM based blockchains, Vechain etc</p>
<h3>Supported Token Standards</h3>
<p>ERC20, ERC721, ERC1155, BEP20, BEP721, BEP1155, SPL Token, Algorand’s asset IDs etc.</p>
<p>To know more about our plugin please click [<a href="https://plugins.miniorange.com/web3-wordpress-login" rel="nofollow ugc">here</a>].</p>
<h3>FREE VERSION FEATURES</h3>
<p>In the free version of the plugin, you can log in to the WordPress website using a crypto wallet. The login with Crypto Wallet button can be displayed on the WP login default page. List of features-</p>
<ul>
<li>Login with Crypto wallet button available at WP login default page</li>
<li>Option to hide the Login with Crypto wallet button</li>
<li>Login with Crypto wallet support for MetaMask, Wallet Connect, Coinbase, Phantom, MyAlgo Wallet.</li>
</ul>
<p>Explore comprehensive feature lists and pricing plans for all premium versions by clicking [<a href="https://plugins.miniorange.com/web3-wordpress-login#pricing" rel="nofollow ugc">here</a>]</p>
<h3>STANDARD VERSION FEATURES</h3>
<ul>
<li>All free version features are included</li>
<li>Shortcode for Login with Crypto Wallet button</li>
<li>Custom styling for Login Button</li>
<li>Custom Redirect after login</li>
<li>Enable/Disable profile completion for new users that signup to your site using crypto wallet</li>
</ul>
<h3>PREMIUM VERSION FEATURES</h3>
<p>The premium version of the plugin has additional features where you can also restrict/lock/gate specific pages, posts, and videos on their WP website and allow users to access the content based on the NFTs owned in their Crypto Wallet. List of features-</p>
<ul>
<li>All Standard version features are included</li>
<li>NFT Token gated content</li>
<li>Multiple NFT contract addresses supported</li>
<li>Regex based rule(All child pages will block automatically under the configured URL)</li>
<li>Support cold wallets like ledger, trezor, etc</li>
<li>Support Added for Hedera, Algorand and Solana Blockchain</li>
<li>Connect wallet to existing WordPress profile</li>
</ul>
<h3>ENTERPRISE VERSION FEATURES</h3>
<p>The enterprise version of the plugin additionally lets you assign roles based on the NFT collection owned in their crypto wallets. Users who login in with a crypto wallet to the WordPress website is assigned a role based on their NFT collection.</p>
<ul>
<li>All Premium version features are included</li>
<li>WordPress role mapping based on NFT owned by crypto user</li>
<li>NFT token gated section of page/post</li>
<li>Disconnect Button</li>
<li>Customize end user experience for NFT gated content access flow</li>
</ul>
<h3>ALL-INCLUSIVE VERSION FEATURES</h3>
<p>All-in-one WordPress management with the support of add-ons / Third Party Plugin compatibility.</p>
<ul>
<li>WooCommerce Coupon mapping based on NFTs ownership</li>
<li>BuddyBoss/BuddyPress Profile Mapping based NFTs owned by end user</li>
<li>LearnDash Attribute/Group/Course Mapping based on NFTs owned by user</li>
<li>MemberPress membership mapping based on NFTs held by crypto user</li>
<li>Crypto wallet user video analytics for Brandmax plugin</li>
</ul>
<h3>WooCommerce – Web3 Integration Add-on</h3>
<p>The add-on can be used for Crypto wallet login/Wallet connect to WooCommerce login and registration page. You can create NFT token gating and NFT gated WooCommerce stores where access can be restricted. Users who have required NFT collection in their wallet have access to the restricted products on WooCommerce stores.</p>
<p>You can also employ NFT gated WooCommerce for giving discounts, here users who have specific NFT or token collection in their wallet are given discounts or certain benefits.</p>
<p>You can restrict access to WooCommerce coupon affiliate programs based on the NFTs owned by the user wallet.</p>
<p>Add NFT images to the user media library so that they print that NFT on WooCommerce Products like T-shirt, Mugs, Canvas, etc.</p>
<ul>
<li>NFT/Token gating WooCommerce-discount based on token owned in wallet [<a href="https://plugins.miniorange.com/woocommerce-coupon-discount-based-on-nft" rel="nofollow ugc">Setup Guide</a>] [<a href="https://www.youtube.com/watch?v=Fpc38jsJDPY" rel="nofollow ugc">Video</a>]</li>
<li>Gate exclusive products for the NFT users [<a href="https://plugins.miniorange.com/woocommerce-product-gating-based-on-nft-token" rel="nofollow ugc">Setup Guide</a>] [<a href="https://www.youtube.com/watch?v=vnNS-i6_wpE" rel="nofollow ugc">Video</a>]</li>
</ul>
<h3>MemberPress – Web3 Integration Add-on</h3>
<p>MemberPress will give you the ability to confidently create, manage and track membership subscriptions. Admin can now add NFT Token Gating to Memberpress Memberships created.[<a href="https://plugins.miniorange.com/membership-mapping-based-on-nfts" rel="nofollow ugc">Setup Guide</a>] [<a href="https://www.youtube.com/watch?v=LqWNjyHxVk8" rel="nofollow ugc">Video</a>]</p>
<h3>BuddyBoss – Web3 Integration Add-on</h3>
<p>Profiles created in BuddyBoss can be NFT Token Gated using miniOrange BuddyBoss Integration Addon. Admin can now add NFT Token Gating to BuddyBoss Profile Types created. [<a href="https://plugins.miniorange.com/wp-buddyboss-web3-integration-addon" rel="nofollow ugc">Setup Guide</a>] [<a href="https://www.youtube.com/watch?v=S3OBh-duVHM" rel="nofollow ugc">Video</a>]</p>
<h3>LearnDash – Web3 Integration Add-on</h3>
<p>Admin can now Restrict Access to the Courses published on LearnDash.</p>
<p>When a User logins using our Web3 Login Button, then the user will be assigned courses in LearnDash based on the NFT owned by the user.[<a href="https://plugins.miniorange.com/web3-learndash-integrator" rel="nofollow ugc">Setup Guide</a>] [<a href="https://www.youtube.com/watch?v=jZO8fbgDtL4" rel="nofollow ugc">Video</a>]</p>
<h3>Use cases for Web3 authentication plugin</h3>
<ul>
<li>
<p>Login with web3 Cryptocurrency wallet: Use one of a variety of hot wallet like MetaMask, WalletConnect, Edge, Electrum, Coinbase, Trust, Robinhood, Binance, Mycelium, AtomicDEX, Jaxx, Samourai, Huobi, Luno, ZenGo, Crypto.com, Bitcoin IRA, and Exodus for WordPress website login. Popular cold wallets like Ledger Nano S, Ledger Nano X, Trezor, KeepKey, CoolWallet Pro, Safepal S1, Keystone Pro, and Ellipal Titan can also be used for WordPress website login</p>
</li>
<li>
<p>Token gated content: Restrict posts, pictures, content, and videos on your website based on NFT collection in web3 wallet. Make it mandatory for users to buy specific NFT collections to access the restricted content. For purchasing NFT collections redirected the users to famous NFT marketplaces like OpenSea, Rarible, and Mintable</p>
</li>
<li>
<p>Sensitive documentation: Ownership of NFTs in your crypto wallet allows you to access secure and sensitive information in an organization</p>
</li>
<li>
<p>Role Assigning: WordPress website owners can assign roles to the users of their website according to the NFT collection in their wallet</p>
</li>
<li>
<p>Restrict access: You can even choose to restrict users who hold certain NFTs from gaining access to pages, images, videos, or documents that you do not want them to see.</p>
</li>
<li>
<p>Token-gated communities: The plugin can be used to restrict access on [<a href="https://www.miniorange.com/blog/nft-token-gated-zoom-meetings-and-webinar/" rel="nofollow ugc">Zoom</a>], [<a href="https://www.miniorange.com/blog/nft-token-gated-discord/" rel="nofollow ugc">Discord</a>], [<a href="https://blockchain.miniorange.com/nft-token-gating-for-google-drive/" rel="nofollow ugc">Google Drive</a>], [<a href="https://www.miniorange.com/blog/circle-nft-token-gating/" rel="nofollow ugc">Circle</a>], and gaming channels based on NFT collection.</p>
</li>
</ul>
<h3>Customer Use-cases:</h3>
<p><strong>Explore our customer use-case pages for insights into our Web3 authentication solutions below:</strong></p>
<ul>
<li>[<a href="https://plugins.miniorange.com/xrpl-nft-token-gating" rel="nofollow ugc">NFT Token Gating for XRPL Blockchain</a>]</li>
<li>[<a href="https://plugins.miniorange.com/wp-video-nft-token-gated" rel="nofollow ugc">Woocommerce Product Views based on NFT Tokens</a>]</li>
</ul>
<h3>NFT Marketplace</h3>
<p>Please try out our NFT Marketplace solution [<a href="https://plugins.miniorange.com/wordpress-nft-marketplace-creator-wp-nft-maker" rel="nofollow ugc">here</a>].</p>
<p><strong>Explore our customer use-case pages for insights into our NFT Marketplace solutions below:</strong></p>
<ul>
<li>[<a href="https://plugins.miniorange.com/woocommerce-nft-marketplace" rel="nofollow ugc">Convert woocommerce as NFT Marketplace</a>]</li>
<li>[<a href="https://plugins.miniorange.com/wp-bulk-nft-minting" rel="nofollow ugc">Bulk upload of NFTs for minting</a>]</li>
</ul>
<h3>Privacy</h3>
<p>miniOrange Web3 login plugin does not store anything other than the wallet address, on your server.</p>
<h3>Contact Us</h3>
<p>Feel free to reach out to us. Send an email at web3@xecurify.com for any inquiries.<br />
User can now also connect to us on <a href="https://discord.com/invite/TRKFdck2r6" rel="nofollow ugc">Discord</a></p>


Web3 – Crypto wallet Login & NFT token gating


Kiran from MiniOrange was extremely helpful throughout the onboarding process to help educate me about this plugin. She also provided some customizations to fit the needs of my website. If I could give her 6-stars I would.


Great plugin, excellent support.

Users can sign up for your WordPress using their crypto wallets. Gate content based on NFTs owned. Web3 authentication plugin supports crypto wallets  …

Laqira Payments for WooCommerce vs Web3 – Crypto wallet Login & NFT token gating