Beschreibung

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.

Screenshots

Cryptocurrency selection in FluentCart checkout.

Direct-to-wallet crypto payment screen with QR code and live blockchain monitoring. — Cryptocurrency selection in FluentCart checkout.

Installation

Install and activate FluentCart.
Install and activate Boriable for FluentCart.
Open FluentCart payment settings and select Boriable / Crypto-Currency.
Enter the public receiving address for each cryptocurrency or network you want to accept and enable the desired assets.
Configure the Boriable verification-service connection if it is not already provisioned for your installation.
Activate a Boriable Free or Pro service licence in the Licensing tab.
Enable the payment method in FluentCart.
Make a small real payment before accepting production orders and verify that the order proceeds from monitoring to confirmed and paid.

Never enter cryptocurrency private keys or recovery phrases into the plugin.

FAQ

Does Boriable hold my cryptocurrency?: No. Customers pay the public wallet addresses configured by the merchant. Boriable does not take custody of the payment.
Does Boriable need my wallet private key or seed phrase?: No. Boriable only needs public receiving addresses. Never provide private keys or recovery phrases.
Why does Boriable use an external service?: The external verification service independently monitors supported blockchains and reports confirmed payments back to FluentCart. This prevents the customer’s browser from being treated as the authority for payment settlement and allows the service entitlement and usage limits to be enforced centrally.
What happens if my Boriable licence expires while a payment is pending?: An invalid entitlement prevents new payment watches from being registered. Payments that Boriable already accepted for monitoring continue through their existing monitoring window and can still settle normally.
Is Boriable Free a trial?: No. Boriable Free is an ongoing service plan supporting TRX on TRON for up to 10 confirmed transactions per UTC calendar month. Pro expands the service entitlement to all supported assets and removes Boriable’s transaction-count limit.
Does Boriable charge a percentage of every transaction?: Boriable does not add a Boriable transaction percentage fee. Merchants can optionally configure their own fixed and/or percentage crypto payment adjustment. Blockchain network fees and third-party service costs may still apply.
Can I choose which cryptocurrencies appear at checkout?: Yes. Every asset you enable and configure with a valid receiving address is offered at checkout. Whether Boriable can actually register and monitor a payment for that asset depends on your active Boriable service plan — selecting an asset outside your plan’s entitlement (for example, a non-TRX asset on Boriable Free) returns a clear error instead of completing.
What happens when the price quote expires?: Quote validity and payment monitoring are separate. Boriable can continue monitoring an already-created payment during its configured monitoring window even after the displayed exchange-rate quote period has ended.
Does Boriable modify my FluentCart order total when I use a crypto adjustment?: No. The adjustment changes the cryptocurrency amount requested from the customer. The underlying FluentCart order total remains unchanged.

Rezensionen

Zu diesem Plugin liegen noch keine Rezensionen vor.

Mitwirkende und Entwickler

„Boriable for FluentCart“ ist Open-Source-Software. Folgende Menschen haben an diesem Plugin mitgewirkt:

Helmar Rudolph

„Boriable for FluentCart“ wurde in 1 Sprache übersetzt. Danke an die Übersetzer für ihre Mitwirkung.

Übersetze „Boriable for FluentCart“ in deine Sprache.

Interessiert an der Entwicklung?

Durchstöbere den Code, sieh dir das SVN-Repository an oder abonniere das Entwicklungsprotokoll per RSS.

Änderungsprotokoll

1.0.34

Corrected a settings-page hint that still said to click an asset „above“ — the asset switcher moved to the left side in an earlier release and the text hadn’t caught up.

1.0.33

Each cryptocurrency now has its own payment-page check interval, configurable in that asset’s own settings (Native assets / Stablecoins tabs) instead of being fixed by the plugin.
Added a store-wide „once detected“ check interval on the Timing & pricing tab, which speeds up checking for every asset once a blockchain transaction has been spotted and is awaiting confirmation.

1.0.32

Crypto payments can now be used for FluentCart subscriptions under store-managed billing — both the first payment and each renewal invoice. This is invoice-style, not silent auto-charging: the customer completes each renewal like a normal checkout.
Order receipts and the order list now show the specific cryptocurrency used for a payment (for example „Crypto – TRX“) instead of a generic label.
Documented the automatic Coinbase price-fallback service in the External Services section.
General WordPress.org coding-standard and packaging improvements.

1.0.31

Every supported cryptocurrency can now be enabled and offered at checkout on any Boriable plan. The Boriable service determines whether it can process a given asset under your current plan when a payment is registered, rather than the plugin restricting which assets you can configure.
Added a „Cancel this payment“ option to the crypto payment page, letting a customer cancel a not-yet-paid crypto payment and mark the order cancelled.
Added Base (an Ethereum layer-2) and Litecoin as native payment assets.
The Native assets and Stablecoins settings tabs now use a vertical asset switcher instead of one long list, with each tab showing at a glance whether that asset is configured and enabled.
Fixed a Solana payment amount rounding issue that could cause some wallets to send a slightly different amount than quoted, preventing the payment from being detected.
General WordPress.org coding-standard and packaging improvements.

1.0.30

Corrected several admin-facing settings descriptions on the Timing & pricing tab, and a few other strings introduced in 1.0.29, that were showing in English on the German (de_DE) admin interface instead of the translated text.
Fixed a pre-existing German mistranslation on the crypto payment page where „quote“ (a price quote) had been translated as if it meant a literary citation.
The Advanced tab now explains that Boriable automatically falls back to a second market-data provider if CoinGecko is temporarily rate-limited or unavailable; this behavior existed since 1.0.29 but was not previously documented in the settings screen.

1.0.29

Asset badges now verify the actually persisted FluentCart settings after Ajax Save before resolving yellow unsaved state to green or gray.
The Cryptocurrency payment method is no longer offered at checkout when the Boriable service licence does not currently allow new payments, instead of appearing and then failing after selection.
A fresh install no longer risks being unable to accept crypto payments if the site’s scheduled-task runner never fires the initial service-configuration refresh.
The service authentication secret now refreshes on the same schedule as the rest of the service configuration, instead of only when the licence is reactivated.
Cryptocurrency price quoting now automatically falls back to a second market-data provider if the primary one is temporarily rate-limited or unavailable.
Crypto Diagnostics now caches the service health check briefly instead of making a fresh request on every page load, and shows a dismissible notice if a payment-confirmation callback was recently rejected.
Database errors during payment creation no longer surface raw technical detail to the customer; the underlying error is recorded for the site administrator instead.
Imported Boriable settings are now validated against the same limits enforced when saving settings directly.
Raised the default minimum Bitcoin order value and default unique-quote spread to more realistic values for current network conditions and typical concurrent checkout volume.
Added basic rate limiting to the public payment-status and quote-refresh endpoints.
Added an internal automated test suite covering wallet-address validation, amount calculations and payment-confirmation signature verification (development only; not included in the distributed plugin).
Updated the translation template and German (de_DE) translation for new and changed admin-facing strings introduced in this release, and corrected an existing German mistranslation on the crypto payment page.

1.0.28

Synchronize gray/yellow/green asset badges immediately after FluentCart completes an Ajax settings save.

1.0.27

Fix live gray/yellow/green asset badge updates by tracking the actual FluentCart field events instead of rediscovering remounted Vue controls.

1.0.26

Restored live gray/yellow/green asset badge updates after FluentCart dynamically remounts settings controls.
Badge state now resolves Boriable controls by setting key first and uses delegated input/change/click observation so unsaved toggle and wallet-address changes immediately turn yellow.

1.0.25

Added native XRP payments on XRP Ledger mainnet, including settings validation, checkout selection, pricing, QR/address guidance, diagnostics, and Worker monitoring.

1.0.24

Completed a localization sweep for remaining customer/admin-facing error and diagnostic strings.
Fixed the German QR verification instruction not loading because the translation catalogue still contained the older unnumbered-placeholder msgid.

1.0.23

Restores the original native POL EIP-681 QR payload with Polygon chain ID 137 and the payment amount in atomic POL units.

1.0.22

Changes native POL QR payloads to a Polygon-targeted EIP-681 URI without an amount, improving Trust Wallet scan behavior while avoiding atomic-value misinterpretation.

1.0.21

Prevents native POL and BNB QR codes from being misinterpreted as Ethereum payment requests by encoding the receiving address only on those networks.
Corrects the German copy-button translation.

1.0.20

Refactors accounting/refund note copy into shorter semantic translation strings for cleaner gettext maintenance.
Improves German blockchain-monitoring wording. No functional changes.

1.0.19

Adds a captured crypto/fiat accounting snapshot to FluentCart transaction metadata and appends a private, idempotent Boriable accounting note when a crypto payment is confirmed.
Records exchange rate, rate source/observation time, fiat value, tax/VAT total, crypto amount/network, blockchain transaction/time and confirmation time.
Documents the recommended refund basis: original transaction-currency value converted using a fresh crypto quote at refund time; refunds remain manual.

1.0.18

Restored the optional CoinGecko Demo API key to the customer-facing Advanced tab.

1.0.17

Removed the customer-facing Infrastructure tab.
The Boriable Worker endpoint is now built into the plugin and service authentication is provisioned automatically for each licensed site.

1.0.16

Correct German software-licensing terminology, including “Lizenz erneut prüfen” instead of the erroneous driver-licence translation. No functional changes.

1.0.15

Fix cryptocurrency checkout asset selector initialization so enabled wallet options load correctly.

1.0.14

Prevent background UI remounts from forcing the Licensing tab back to Checkout while licence actions are running.
Keep licence action clicks isolated from FluentCart tab handlers.
Correct the internal plugin version constant to match the release metadata.

1.0.13

Refresh the top licence plan badge immediately after activate, recheck or deactivate.

1.0.12

Fix licence action buttons after FluentCart dynamically mounts or remounts the Licensing tab.

1.0.11

Optimizes FluentCart settings import lookup to avoid slow meta-key/meta-value query warnings. No import behavior changes.

1.0.10

Removes internal licensing authority and product ID details from the merchant-facing Licensing screen. No functional changes.

1.0.9

Restored live gray/yellow/green asset status badges across FluentCart tab remounts.
Gray means saved disabled, yellow means unsaved or enabled without a valid wallet, and green means saved, enabled and ready.

1.0.8

Fixed settings import on brand-new FluentCart destinations by creating the gateway settings record when necessary.
Hardened import file handling across FluentCart dynamic settings remounts and repeated selection of the same JSON file.

1.0.4

Fresh settings sessions now open on the Checkout tab.
Licence state is bound to the Boriable product and current site instead of accepting stale local entitlement data.
Added uninstall cleanup for Boriable licence/cache options and scheduled hooks.

1.0.2

Submission build version bump after WordPress.org reported that version 1.0.1 had already been uploaded. No functional changes from 1.0.1.

1.0.1

Fresh installs now start with all cryptocurrency assets disabled until the merchant explicitly enables them.
Boriable licence state now uses a plugin-specific WordPress option so stale or unrelated FluentCart licensing data cannot appear as an active Boriable entitlement.

1.0.0

Initial public release.
Non-custodial direct-to-wallet crypto payments for FluentCart.
Native TRX, ETH, BNB, POL, SOL and BTC support.
USDC on Ethereum and Polygon; USDT on Ethereum and TRON.
Independent blockchain verification with signed settlement callbacks.
Free and Pro service entitlements with server-side plan enforcement.
Free plan includes TRX and up to 10 confirmed transactions per UTC calendar month.
Diagnostics dashboard, transaction history and chain-specific inspection tools.
Quote-lock and extended payment-monitoring windows.
Optional percentage and fixed crypto payment adjustments.
Adaptive payment-page status polling and visual monitoring progress.
Settings import/export with protected licence and transaction data.