Initial public release.<\/p>"},"ratings":[],"assets_icons":{"icon-256x256.png":{"filename":"icon-256x256.png","revision":3624280,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3624280,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3624280,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["0.1.0"],"block_files":[],"assets_screenshots":[],"screenshots":[]},"plugin_section":[],"plugin_tags":[1886,12611,40289,145009,6593],"plugin_category":[45],"plugin_contributors":[273447],"plugin_business_model":[],"class_list":["post-345878","plugin","type-plugin","status-publish","hentry","plugin_tags-bitcoin","plugin_tags-cryptocurrency","plugin_tags-lightning","plugin_tags-monero","plugin_tags-payment-gateway","plugin_category-ecommerce","plugin_contributors-bitrequest","plugin_committers-bitrequest"],"banners":{"banner":"https:\/\/ps.w.org\/bitrequest-for-woocommerce\/assets\/banner-772x250.png?rev=3624280","banner_2x":"https:\/\/ps.w.org\/bitrequest-for-woocommerce\/assets\/banner-1544x500.png?rev=3624280","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/bitrequest-for-woocommerce\/assets\/icon-256x256.png?rev=3624280","icon_2x":"https:\/\/ps.w.org\/bitrequest-for-woocommerce\/assets\/icon-256x256.png?rev=3624280","generated":false},"screenshots":[],"raw_content":"\n
Bitrequest is a non-custodial cryptocurrency payment gateway for WooCommerce. You configure your own wallet addresses (or an xpub for a fresh address per order), and payments arrive directly in your wallet. No middleman ever holds the money \u2014 not a processor, not Bitrequest.<\/p>\n\n
Payment detection runs client-side through the open-source Bitrequest payment app. The plugin records the transaction against the order and links you straight to a block explorer so you can verify on-chain before fulfilling.<\/p>\n\n
Supported currencies<\/strong><\/p>\n\n Bitcoin, Lightning Network, Litecoin, Dogecoin, Dash, Bitcoin Cash, Kaspa, Monero, Nano, Nimiq, and Ethereum \u2014 plus any ERC-20 token (USDT, USDC, and others) on Ethereum, Arbitrum, Polygon, BNB Smart Chain, and Base.<\/p>\n\n Key features<\/strong><\/p>\n\n Source code: https:\/\/github.com\/bitrequest\/bitrequest-woocommerce<\/p>\n\n This plugin relies on the following external services. No customer data is sent to any of them.<\/p>\n\n 1. Bitrequest payment app (bitrequest.github.io)<\/strong><\/p>\n\n What it is: the open-source Bitrequest payment application, which performs cryptographic address derivation and detects incoming payments by reading public blockchain data. It provides the checkout the customer interacts with.<\/p>\n\n What is sent and when: when a customer reaches the payment step, the plugin loads the app's JavaScript and CSS from this origin and opens the app in a checkout window. The request URL carries the order number, the store name, the amount, the chosen cryptocurrency and the receiving address derived for that order. No customer name, email, address or other personal data is transmitted. Loading the assets exposes the visitor's IP address and user agent to the host, as with any externally hosted resource.<\/p>\n\n Why it is required: the app and its libraries must be served from the same origin the checkout window points at, because the plugin verifies the window's origin before accepting a payment result from it. Splitting them would break that check.<\/p>\n\n Self-hosting: the \"Bitrequest URL\" setting accepts any host serving an unmodified build, so you can point the plugin at your own copy and remove this dependency entirely.<\/p>\n\n Provider: Bitrequest. Terms and conditions: https:\/\/github.com\/bitrequest\/bitrequest.github.io\/wiki\/Terms-and-conditions - Privacy \/ disclaimer: https:\/\/www.bitrequest.io\/privacy\/<\/p>\n\n 2. CoinMarketCap image CDN (s2.coinmarketcap.com)<\/strong><\/p>\n\n What it is: a public CDN serving cryptocurrency logo images.<\/p>\n\n What is sent and when: coin and token icons are loaded in the WordPress admin only - on the gateway settings screen, the orders list, the order edit screen and the payments overview. Loading an image exposes the logged-in administrator's IP address and user agent to CoinMarketCap. No order, store or customer data is sent, and no request is made from any customer-facing page.<\/p>\n\n Why it is required: the ERC-20 token picker covers roughly a thousand tokens, so their icons cannot practically be bundled with the plugin. Customer-facing pages use only icons bundled inside the plugin, so a shopper's browser never contacts this service.<\/p>\n\n Provider: CoinMarketCap Mgmt Limited. Terms of use: https:\/\/coinmarketcap.com\/terms\/ - Privacy policy: https:\/\/coinmarketcap.com\/privacy\/<\/p>\n\n 3. Lightning proxy (optional, merchant-configured)<\/strong><\/p>\n\n Only used if you enable Lightning. The plugin sends invoice status lookups to the proxy URL you enter in the settings - a host you choose and control, such as your own node or a service you have an account with. Requests contain the Lightning payment identifier for the order and nothing else. No proxy is contacted if Lightning is left disabled, and the plugin has no default proxy.<\/p>\n\n 4. Webhook URL (optional, merchant-configured)<\/strong><\/p>\n\n If you set a Webhook URL, the plugin POSTs order and transaction data to that address when a payment is detected. This is your own endpoint; leave the field empty and no request is made.<\/p>\n\n Note on block explorers<\/strong><\/p>\n\n Explorer links shown in the admin and in order emails are ordinary hyperlinks. Nothing is sent to a block explorer unless someone clicks one.<\/p>\n\n\n Lightning requires a connection to a Lightning node or proxy (LND, Core Lightning, LNbits, Spark, or Nostr Wallet Connect). It can be left disabled if you only want on-chain payments.<\/p>\n\n\n No. Payments go directly from the customer's wallet to yours. You pay only standard blockchain network fees.<\/p><\/dd>\n No. You configure your own wallet addresses or xpub. Bitrequest never holds, routes, or has access to your funds.<\/p><\/dd>\n None about your orders or customers. The payment app runs in the customer's browser and reads the public blockchain to detect payments. There is no analytics or telemetry. You can also self-host the app.<\/p><\/dd>\n Yes. Add USDT, USDC, or other ERC-20 tokens in the settings, on Ethereum mainnet or a Layer 2 (Arbitrum, Polygon, BSC, Base).<\/p><\/dd>\n It needs your secret view<\/em> key, which can only read incoming transactions \u2014 it can never spend funds. Because it is included in the checkout page, treat it as public and consider using a dedicated Monero account for your shop. No other supported currency requires a key.<\/p><\/dd>\n Customer-facing pages contact only the Bitrequest payment app, which is required to display the checkout and detect payment; it can be self-hosted to remove even that. Coin icons in the WordPress admin are loaded from CoinMarketCap. See the \"External services\" section for full details.<\/p><\/dd>\n Manually, from your wallet to an address the customer provides. Because funds are non-custodial, only you can move them.<\/p><\/dd>\n The plugin shows a recommended confirmation count per coin on each order and links you to a block explorer to verify before you fulfill.<\/p><\/dd>\n\n<\/dl>\n\n\n\n
External services<\/h3>\n\n
\n
\/wp-content\/plugins\/<\/code>, or install it through the WordPress Plugins screen.<\/li>\n\n
Does the plugin charge fees?<\/h3><\/dt>\n
Is it custodial?<\/h3><\/dt>\n
What data is sent to Bitrequest?<\/h3><\/dt>\n
Can I accept stablecoins?<\/h3><\/dt>\n
Does Monero need my private key?<\/h3><\/dt>\n
Does the plugin send anything to third parties?<\/h3><\/dt>\n
How are refunds handled?<\/h3><\/dt>\n
Do I need to wait for confirmations before shipping?<\/h3><\/dt>\n
0.1.0<\/h4>\n\n
\n