Crypto Payments for FluentCart - the Nerd Edition
Boriable 1.0: Boringly Reliable Crypto Payments for FluentCart
It started innocently enough.
We wanted FluentCart to accept TRX.
Not through a giant crypto processor. Not through somebody else’s checkout. And without a custodian holding the merchant’s funds.
Just:
Customer chooses crypto → sends directly to the merchant’s wallet → FluentCart knows when the money arrived.
Several murdered assumptions, one dead Schrödinger’s cat, a Cloudflare D1 database, multiple blockchain APIs and an unreasonable number of ten-cent transactions later, Boriable 1.0 exists.
The fundamental idea
Boriable is completely non-custodial.
Merchants provide public receiving addresses. Customers pay those addresses directly. Boriable never handles private keys, seed phrases or funds.
But that creates the interesting problem:
How does WordPress know the payment really happened?
Our answer was to deliberately not trust WordPress with settlement verification.
The FluentCart plugin registers an expected payment with the Boriable Verifier, running independently on Cloudflare. The verifier monitors the relevant blockchain and, once payment is detected and confirmed, sends a signed callback to WordPress.
Only then does FluentCart mark the transaction paid.
In other words:
WordPress is the client. Boriable is the verifier.
One plugin, quite a few blockchains
Boriable 1.0 now supports:
Native: TRX, ETH, BNB, POL, SOL, LTC, XRP and BTC
Stablecoins: USDC on Ethereum/Polygon and USDT on Ethereum/TRON
And yes, we discovered that supporting “crypto” is wonderfully misleading terminology. Every chain has its own peculiarities.
Our ERC-20 monitoring alone produced internal codenames including “Ten at a Time” and “Ten Block Nailer” as we worked around RPC block-range restrictions and made transaction discovery deterministic.
Licensing became part of the architecture
During discussions with FluentCart, MD Jewel raised an important point: blockchain verification should happen on centralized infrastructure controlled by us rather than inside the distributed WordPress plugin.
Fortunately, by then we had essentially already built that.
The verifier became Boriable’s SaaS boundary, while FluentCart Software Licensing provides the entitlement.
That means modifying the local PHP plugin cannot magically enable the service. The verifier independently decides whether a new payment watch may be registered.
Importantly, licensing never interferes with money already in flight. If Boriable accepted responsibility for monitoring a payment, it finishes the job.
Free vs. The Full Beast™
Boriable Free: TRX, up to 10 confirmed transactions/month.
Boriable Pro: all supported assets, with no Boriable transaction limit.
During testing, Free successfully accepted a TRX payment, detected and confirmed it, settled the FluentCart order and updated its usage counter.
Then we used Boriable Free to purchase Boriable Pro with TRX.
We hadn’t actually planned that test.
We rather liked it.
Activating Pro immediately transformed checkout into what inevitably became known during development as The Full Beast™.
And Schrödinger’s cat?
At one point FluentCart said the gateway was disabled while Boriable’s settings said it was enabled.
Both were technically correct.
We had accidentally conflated gateway enabled with gateway licensed.
Later, a licensing API mysteriously returned 153 KB of “invalid JSON.”
It was the HTML homepage of helmar.live.
Our licensing authority was pointing at the wrong WordPress installation.
Schrödinger’s cat did not survive the investigation.
The diagnostic did.
Why “Boriable”?
Somewhere during development the name appeared.
Eventually its meaning became obvious:
Boring + Reliable.
Crypto can be volatile, complicated and exciting.
Payment infrastructure shouldn’t be.
The ideal Boriable transaction is profoundly uneventful:
Customer pays.
Merchant receives.
FluentCart marks the order paid.
Nobody thinks about Boriable.
That may be the highest compliment payment software can receive.
Boriable 1.0 — Boringly reliable crypto payments for FluentCart.
Read the full story here: https://helmar.live/boriable/the-nerd-edition
Hey Helmar! A little feedback, offered with affection from a fellow nerd 😄
There’s an interesting story here, but I’ll be honest: even I found the sheer length a bit overwhelming for a community post.
I think this would work really well as a blog post. Here, I’d just share the short version: what it does, why it matters to a store owner, and a link for those of us who want to nerd out on the details.
You’ve clearly put a lot into this. I’d just give people an easier way in. A shorter post might get more people curious enough to read the full story 🙂
Jorge de los Reyes You're absolutely right. Done. :)
And would it work for membership sites with recurring payments—monthly, quarterly, semi-annually, or annually?
José Carlos Estirado Good question!
Jorge de los Reyes See the other thread.
José Carlos Estirado Jorge de los Reyes - Just confirmed it. If the store is set to "store billing", the customer gets to pay for his subscription through his backend page, and can then choose whichever payment channel is present, including crypto. Scan the QR code, pay in crypto, wait for the blockchain to reflect it, get the order marked as "paid". Sweet. :)