內容簡介
Boriable for FluentCart 外掛為 FluentCart 提供非保管的加密貨幣支付功能，讓顧客能直接將加密貨幣發送至商家設定的錢包地址，無需擔心資金的保管問題。
【主要功能】
• 支援多種加密貨幣支付
• 無需保管資金或私鑰
• 自動完成交易確認
• 可選擇啟用的資產類型
• 免費與專業版計畫選擇
外掛標籤
開發者團隊
原文外掛簡介
Boriable adds non-custodial cryptocurrency payments to FluentCart. Customers send cryptocurrency directly to wallet addresses configured by the merchant. Boriable does not take custody of funds and does not require wallet private keys or recovery phrases.
After checkout, the plugin registers the expected payment with the Boriable verification service. The service monitors the relevant public blockchain. When the expected transaction is detected and confirmed, a signed callback is sent to the merchant’s WordPress site and the corresponding FluentCart transaction can be completed automatically.
Supported assets
Boriable Pro supports:
TRX on TRON
ETH on Ethereum and Base
BNB on BNB Smart Chain
POL on Polygon
SOL on Solana
BTC on Bitcoin
LTC on Litecoin
XRP on XRP Ledger
USDC on Ethereum and Polygon
USDT on Ethereum and TRON
Merchants choose which supported assets to enable and provide the corresponding public receiving addresses.
Boriable Free and Pro
Every supported asset can be enabled and configured in the plugin regardless of plan — the plugin itself does not restrict which payment methods you can set up or offer at checkout.
What the external Boriable verification service will actually register and monitor depends on your plan. Boriable Free covers TRX payments on the TRON network for up to 10 confirmed transactions per UTC calendar month. Boriable Pro covers the complete supported asset set with no Boriable transaction-count limit. Blockchain network fees and any fees charged by external infrastructure providers are separate from Boriable.
Both plans use the external Boriable verification service. A valid Boriable service entitlement is required to register new payment watches, and the service declines to register a payment for an asset outside the current plan’s entitlement. If an entitlement later becomes invalid or expires, already registered payments continue to be monitored so that payments already in flight are not abandoned.
Direct-to-wallet, non-custodial design
Boriable does not create or control merchant wallets. Cryptocurrency is sent directly from the customer to the merchant-configured receiving address. Never enter a private key or recovery phrase into Boriable.
Payment monitoring
Boriable separates the exchange-rate quote period from the blockchain monitoring period. The payment page reports monitoring, detection and confirmation status and uses adaptive status polling according to the selected asset and payment state.
Crypto payment adjustments
Merchants may optionally add a percentage adjustment, a fixed adjustment in the store currency, or both to the crypto amount requested from the customer. These adjustments affect the amount payable in cryptocurrency; they do not modify the underlying FluentCart order total.
External services
Boriable relies on external services to perform its core payment-verification function. By installing, configuring and activating Boriable for use with the Boriable service, the merchant authorizes the plugin to communicate with these services as described below.
Boriable verification service – required for payment monitoring and settlement. When a new payment is registered, technical payment data is sent to the service, including payment/order/transaction identifiers, selected asset and network, the merchant’s public receiving address, expected amount, store currency and amount, quote/monitoring timestamps, site URL and service-entitlement identifiers. Customer names, email addresses and wallet private keys are not required for blockchain verification. The service monitors public blockchain data and returns signed payment-status information to the merchant site.
Service information: https://helmar.live/boriable/
Terms of service: https://helmar.live/boriable/terms/
Privacy policy: https://helmar.live/shop/datenschutz/
Boriable licensing service – required to activate and validate the Boriable service entitlement. The licensing request includes the licence key, site URL and Boriable product identifier. The licensing authority is supplied to the plugin by the Boriable verification service.
Service information: https://helmar.live/boriable/
Terms of service: https://helmar.live/boriable/terms/
Privacy policy: https://helmar.live/shop/datenschutz/
CoinGecko API – used to obtain cryptocurrency/store-currency market prices when no manual price override is configured. Requests include the cryptocurrency identifier and requested store currency. The plugin’s request user-agent also identifies the Boriable version and merchant site URL. A merchant may optionally configure a CoinGecko Demo API key.
CoinGecko API: https://www.coingecko.com/api
API terms: https://www.coingecko.com/en/api_terms
Privacy policy: https://www.coingecko.com/en/privacy
Coinbase spot-price API – used only as an automatic fallback price source when CoinGecko is rate-limited or temporarily unavailable, so a pricing-provider outage does not block crypto checkout. Requests include only the cryptocurrency symbol and requested store currency (for example “BTC-USD”); no personal, order or customer data is sent. The plugin’s request user-agent also identifies the Boriable version and merchant site URL.
Coinbase API: https://docs.cdp.coinbase.com/coinbase-business/track-apis/prices
Terms of service: https://www.coinbase.com/legal/user_agreement/united_states
Privacy policy: https://www.coinbase.com/legal/privacy
Blockchain explorers may be opened when an administrator follows a transaction link from Boriable. Those sites are visited only when the link is opened and are governed by their own terms and privacy policies.
Translation
Boriable uses the WordPress internationalization system with the boriable-for-fluentcart text domain. A POT template is included in languages. Translations are provided through WordPress.org’s community translation system once the plugin is listed.
Source code
All of Boriable’s own PHP, JavaScript and CSS is included in this plugin exactly as authored — no build step, bundler or minifier is used to produce it. The only bundled third-party asset is the MIT-licensed node-qrcode library described below.
Bundled QR code library
The payment page uses the MIT-licensed node-qrcode 1.5.4 library. Upstream source/build information: https://github.com/soldair/node-qrcode . Bundle provenance is documented in QR-CODE-BUILD.txt; the licence is in LICENSE-node-qrcode.txt.
