Web3 Access


Web3 Access is a Web3 wallet plugin for WordPress that allows you to accept cryptocurrency payments via MetaMask or other browser wallets for access to content on your WordPress website. Restrict specific content or entire Pages, Posts and custom content types to NFT owners, specific cryptocurrency holders or visitors that make a transaction via a web3 browser wallet.

See more Reviews here.


  • Restrict specific content including text, images, videos and more using the Web3 Access Restricted Content Gutenberg Block.
  • Restrict access to entire Pages, Posts and other post types.
  • Accept payments in Ethereum (ETH), Polygon (MATIC), Binance Smart Chain (BSC), Avalanche (AVAX), Fantom (FTM) and Solana (SOL) access to content.
  • Add custom ERC-20 tokens of your choice to accept crypto payments via browser wallets, allowing visitors to access your content.
  • Set prices in USD. Web3 Access automatically converts the price to the amount in tokens at the time of transaction. (limitations may apply for certain tokens)
  • Allow access to content via NFT ownership verification. See Details
  • *NEW Create subscriptions for limited time access to your content. Visitors can renew subscriptions with a Web3 payment or NFT Verification.

Supported Networks

The Web3 Access plugin currently supports the following networks:

  • Ethereum Mainnet
  • Polygon (MATIC)
  • Binance Smart Chain (BSC)
  • Avalanche (AVAX)
  • Fantom (FTM)
  • Solana (SOL) via Phantom Wallet – transaction payments support only. NFT verification under development for Solana.

Transaction Fee

We collected a 1% transaction fee for payments made on our supported Networks.

Our NFT Verification feature is free to use and can verify ownership for any tokens that exist on the networks above. ERC-1155 tokens have limitations, but can be verified via an OpenSea API Key.


Deze plugin heeft 1 blok.

  • Web3 Access Restricted Content


  1. Upload the web3-access folder to the /wp-content/plugins directory, or install the plugin through the WordPress plugins screen directly. You can also download the Web3 Access plugin at https://metapress.ca/download/.
  2. Activate the plugin through the ‘Plugins’ screen in WordPress
  3. Follow our How It Works guide.


See our FAQ

Additional support for this plugin at https://metapress.ca/contact/


30 mei 2024
This plug-in does exactly what’s described in the description fluidly with no issues. Let’s my personal website restrict content based off of, and sell NFTs.
23 augustus 2023
Amazing plugin and easy to use. Fast and good support.
17 februari 2023
I have been looking for the options of this plugin for over 2 months. I finally found it and tested it. It’s just great. I am using it to restrict content based on NFT ownership. At the beginning, without OpenSea api it was imposible, but thanks to the developer he added moralis api and now it works like a charm. If you want to fully customize it you might need to know some programming languages, but it compeltely fulfills its purpose.I am giving 5 stars and if I could I would give it more.Developer deserves donations for it’s great work, definitely I am going to do it.Please, keep updating it and thanks for your great project.
16 oktober 2022 1 reactie
TLDR; NFT Verification! Confirming ownership is one of the main purposes of the blockchain. Most plugins* lock NFT Verification behind a premium upgrade. Web3 Access does not. It was easy to set up and implement on my site. It’s nice to connect to a website, but what’s the point if I can’t verify if my visitor has the asset they need. Most plugins* put NFT Verification behind a premium barrier. Web3 Access does not. Confirming ownership is one of the main purposes of the blockchain and I can do that with this plugin with ease. The UI could use work or perhaps better options for front-end product layouts, but that’s design related. If this plugin doesn’t do anything else except keep working, it’s solid and is something I recommend. The OpenSea API can be difficult to deal with. Perhaps Moralis API works instead? Never tried. I wanted a simple way to block content and verify ownership of (ERC-721/ERC-20) assets. Maybe add a shortcode for disconnecting a wallet? Or Gutenburg support for multiple products? All in all, good stuff. Thank you! Thank you for creating and sharing this plugin. *at this time`
19 september 2022 1 reactie
I added all information about the NFT collection -ERC721- and i activated the restriction on some pages but nothing happened, still access granted. And when i activate the restriction for all the wrbsite there is no button in login page to connect the wallet. And many more options not working
Lees alle 6 beoordelingen

Bijdragers & ontwikkelaars

“Web3 Access” is open source software. De volgende personen hebben bijgedragen aan deze plugin.


Vertaal “Web3 Access” naar jouw taal.

Interesse in ontwikkeling?

Bekijk de code, haal de SVN repository op, of abonneer je op het ontwikkellog via RSS.



  • Added getGasPrice call for more accurate gas price estimates on transactions.


  • Bug fix when checking price for custom tokens not listed on Binance or CoinGecko.


  • Sepolia Test Network replaced Goerli


  • Try Catch added to display browser wallet errors


  • Updated deprecated ethereum provider chainId to RPC method


  • NFT Verification options added to restrict entire page content.


  • PHP session management updates
  • Wallet page refresh and token access updates.


  • Solana Wallet JS updates for when wallet is changed.
  • PHP session management updates to prevent headers already sent warning


  • New setting for custom Solana RPC URL incase mainnet-beta is returning 403 errors. Found under Web3 Access -> Wallet Addresses


  • Fixed a bug where Product JS would not load if page settings were not set.


  • Tested up to version 6.2.2 readme updated.


  • Bug fix for address reference during verification process.


  • Products can now be set to subscriptions, requiring a renewal payment or NFT Verification after the expiration time.
  • Update to the payment options during checkout. New Wallet Payment and NFT Verification tabs let visitors know the 2 options without needing to scroll down page for NFT Verification.
  • New [metapress-subscriptions] shortcode for displaying visitors subscriptions on a page.
  • Email notifications for subscription renewal reminders.


  • WordPress tested version update 6.2.0


  • Redirect loop set token param fix
  • Network images URL update fix


  • Bug fix when adding new NFT contracts for verification. Token Type option was blank.


  • Added support for Solana Network
  • Wallet Address Management Updates
  • New Wallet Connection Options
  • Ropsten Network removed, Sepolia Network added for testing.


  • Contract updates


  • Session manager updates to prevent warning logs in debug mode.


  • Admin notice for creating checkout page for product purchase buttons to appear.


  • Session variables added to verify access token ownership.


  • REST API Endpoint bug fix.


  • MetaProducts wording updated to Web3 Products


  • NEW Minimum Balance field for NFT and Token Verification process. Optionally change the required minimum Tokens or NFTs wallets need to hold in order to access your content.
  • NFT Verification update to check for existing access tokens so visitors do not need to verify again if they have a valid access token.


  • Checkout page Missing Product ID message fix.
  • Checkout page redirect bug fix.


  • Tested up to WordPress version 6.0.1


  • CSS styling for connect wallet button added. (.metapress-login-notice button.metamask-connect-wallet)


  • Removed JSON encoded data for deprecated CSS editor.


  • Added Binance and CoinGecko price API enable / disable for custom tokens.
  • Added Price (USD) field for custom tokens incase Binance / CoinGecko cannot find a price.


  • Updated 30 second nonce validation to 1 hour.


  • Updated readme.txt file


  • Tested up to WordPress version 6.0.0
  • Moved jquery-ui-smoothness CSS for admin dashboard into plugin files instead of external URL.


  • Sanitize and Escaping updates.
  • Stable Tag added to readme.txt


  • New Restrict Website Access option under Web3 Access -> Access Settings. Allows you to restrict access to all pages and website content.
  • New Allow Page Access option for individual Pages, Posts and supported content types. Only applicable when Restrict Website Access is enabled.
  • Added price label on Product Purchase buttons.
  • Added a View Page As Admin button when logged in as administrator to view restrict content pages.
  • Fixed a bug where Pending Transaction URLs were not linked to the explorer URL.


  • Added support for Fantom (FTM) Network and Testnet.


  • Removed web3 provider isMetaMask check to allow for Coinbase and other browser wallets.


  • Check if web3 provider is not null bug fix.


  • Added support for Avalanche (AVAX) Network and Avalanche Fuji Test Network


  • Added Web3 Access -> Styling admin page to customize Theme, Accent Colour and add Custom CSS.


  • New Web3 Access Restricted Content shortcode added for those not using the Gutenberg Block Editor
  • [metapress-restricted-content products=”{MetaProduct IDs comma separated}”] your restricted content [/metapress-restricted-content]


  • Added 1 Week and 1 Month options to Access Token expiration time setting.


  • Optional OpenSea Collection Slug parameter for MetaProduct NFT verification. If you are using a shared OpenSea contract address for NFT verification, you should request an OpenSea API Key and include the collection slug in your MetaProduct assets. This will check ONLY your collection and not all assets on the shared contract address.


  • OpenSea API Key setting (optional) added. If you need to verify visitors own ANY ERC-1155 token within a smart contract, you can add your OpenSea API Key under Web3 Access -> Smart Contracts (NFTs)
  • IMPORTANT: The Token Contract Address should be a unique address and not a shared collection address. For example, this address is a shared OpenSea address. Using a shared smart contract address may result in the NFT verification system returning true if a users address owns ANY asset that belongs to the shared address (smart contract).


  • Binance Smart Chain network added for Payments. (1% transaction fee)


  • New WooCommerce Filter setting added to hide WooCommerce Product Add To Cart buttons for products that require Web3 Access Products.


  • New Access Tokens Expire After setting under Web3 Access -> Settings
  • Access Token Exists server request updated to check for NFT verification access tokens. Previously only checked for paid transaction access tokens.


  • Admin custom tokens JS fix.


  • MetaMask initial loading process improved and updated to prepare for custom Network support.
  • Networks admin page added which will be a feature included in Pro (Premium) version of plugin.
  • Binance Smart Chain (BSC) added by default and can now be used for NFT ownership verification.
  • External Javascript libraries moved to internal plugin files to prevent delayed Connect Wallet button functionality.
  • Token ratio converter updated to support additional Networks and Tokens.


  • Just adding review link in plugin admin dashboard. More updates coming soon!


  • Connect Wallet button added to prompt user to connect MetaMask wallet.


  • Security updates to sanitize input and escape output variables.
  • PHP short tags removed.


  • Bug fix for Product Price number_format not working on certain PHP versions.


  • Bug fix where Product Price could not be set to 0 or empty.


  • Language & Text settings added to Web3 Access -> Language admin page.


  • Provide access to content based on visitors owning any NFT within a Collection.


  • Redirect to previous page on Checkout Shortcode. Redirects visitors to previous page after confirming NFT ownership for access to product.


  • Provide access to pages and content via NFT ownership verification.


  • Added support form custom tokens that exist on either Ethereum Mainnet or Polygon Mainnet. Add custom tokens under Web3 Access -> Tokens in your WordPress Dashboard.
  • Tokens must exist on either the Ethereum or Polygon Mainnet Network.
  • Tokens must use 18 decimals for values.


  • Plugin update testing.


  • Release