POS compatibility
Clover: crypto payment compatibility
The verdict
Clover has no built-in crypto acceptance, but unlike some registers it has a Custom Tender system a crypto app could plug into. Whether a ready-to-use crypto app exists, and whether it reports and settles cleanly, is still unverified.
Parallel acceptance means the crypto payment runs beside the POS. The POS does not process or confirm the crypto payment. The sale must be recorded or reconciled separately.
- Native support
- No
- Parallel acceptance
- Available
- New hardware
- Uses existing hardware
- Setup effort
- Not confirmed (depends on the custom-tender app or crypto tool chosen)
- POS reporting
- Not confirmed
- Refunds
- Not confirmed
How we know: Clover frames custom tenders as additional payment methods you build, implying crypto is not built in, and secondary sources list only card, Apple Pay, and contactless. We did not retrieve a definitive built-in tender enumeration, so this rests on framing plus corroboration.
Who this is right for
A low-to-mid-volume Clover merchant, a retail shop, cafe, or service business, who wants to accept crypto occasionally and is willing to reconcile it by hand for now. Clover's custom-tender system makes a cleaner, on-device flow genuinely possible, which is more than some registers offer, so Clover is a reasonable place to start if you go in knowing the polished, verified version does not exist yet.
Who should probably skip it
A high-volume table-service restaurant, or any Clover merchant who needs a crypto flow that is proven to appear in reporting and settle cleanly today. The pieces are promising but unverified, and at volume an unverified reconciliation path is expensive to get wrong. If you expected Clover itself to take and settle crypto, that is not what happens today.
What you gain and what you give up
You gain a real extension point: Clover's Custom Tender API is a genuine, documented place for a crypto app to live on the device, with refund handling built into the design. You give up certainty: we cannot yet confirm that a ready-to-use crypto app exists, nor that a custom-tender payment shows up in your Clover reports or settles into your account. Until that is verified, treat it like Square's beside-the-register flow: promising, but a two-system, reconcile-by-hand job.
Build a printable counter QR card for free with the Payment Card Builder. No account, nothing to install.
Why Clover is different
Clover has something many registers do not: a documented Custom Tender API. It is the most important thing to understand about crypto on Clover, and the easiest to misread, so we will be precise about what it does and does not mean.
What a Custom Tender is
Clover lets approved apps add their own payment method to the register, supported on all Clover devices. An app can present a QR or wallet flow, book the sale against the order, and the design even includes refund handling. That is a real, first-class extension point, not a workaround.
Why that is genuinely promising
On a register with no such system, crypto can only sit beside the POS and be hand-recorded. Clover's Custom Tender API means a crypto payment could, in principle, be taken and recorded on the device itself, a cleaner path than a purely beside-the-register flow.
Capability is not a solution
Here is the distinction that matters. A platform capability means "someone could build this." A merchant-ready solution means "you can install it and use it today." We confirmed the capability from Clover's own developer docs. We did not confirm that a finished, reliable crypto app actually exists for it, nor that its payments show up in your reports and settle into your account.
What that means for you
Do not choose Clover expecting a polished crypto button today. Do consider it a platform with a credible path to something better, which we will verify hands-on before we claim it works. Until then, plan for the beside-the-register, reconcile-by-hand reality.
How crypto acceptance works with Clover
- Parallel acceptance (non-integrated): A beside-the-register flow.
- Third-party integration: A supported but non-first-party connection.
Our evaluation
Cost and setup
- Setup
- Not confirmed
- Hardware
- Not confirmed (Clover hardware has its own cost; crypto adds none documented)
- Monthly
- Not confirmed
- Transaction fee
- Not confirmed (unknown whether Clover charges on custom tenders)
- Conversion fee
- Not confirmed
- Settlement fee
- Not confirmed
No crypto-specific or custom-tender pricing was verified. Confirm current pricing with Clover and with any app or processor you pair. Last verified 2026-07-11.
CryptoLic Lab
CryptoLic does not stop at reading documentation. We independently validate what platforms and vendors claim by setting things up and running them ourselves, then we publish what we actually observed. For this platform, that hands-on validation is in progress. Nothing below is marked verified until we have tested it, so you can trust a "verified" label when you eventually see one.
| What we will verify | Status |
|---|---|
| Crypto custom-tender app exists in App Market | Pending verification |
| Custom-tender checkout flow | Pending verification |
| POS reporting / tender representation | Pending verification |
| Settlement of custom-tender funds | Pending verification |
| Refund workflow | Pending verification |
| Accounting export | Pending verification |
| Customer receipt | Pending verification |
| Offline behavior | Pending verification |
| Hardware (Station, Mini, Flex) | Pending verification |
| Verified wallets | Not yet tested |
| Verified processors | Not yet tested |
| Verified screenshots | Not yet tested |
| Verified photographs | Not yet tested |
Reconciling a crypto sale that never touched your Square deposits is exactly what the The Merchant Accounting & Bookkeeping Toolkit is built for: a parallel-flow routine and a clean year-end package for your CPA.
Recommended configuration by business type
| If you are | Best method | Why |
|---|---|---|
| A low-to-mid-volume shop or cafe on Clover | A beside-the-register crypto flow, recorded in Clover | Works today without depending on an unverified app; reconcile the crypto sale by hand. |
| Curious about the Custom Tender path | Wait for our lab validation, or trial a custom-tender app cautiously | The capability is real, but no app is confirmed to report and settle cleanly yet. |
| A high-volume table-service restaurant | We recommend waiting | Unverified reporting and settlement at volume is expensive to get wrong. |
Give cashiers a word-for-word routine for crypto at the register with the The Counter Crew Playbook.
Common problems and fixes
Likely cause: The API is a developer capability, not a finished merchant app. It means someone could build crypto acceptance, not that a ready-to-use one exists and works.
Fix: Treat crypto on Clover as unverified today: use a beside-the-register flow and record it, until we confirm a real app reports and settles cleanly.
If that fails: Watch this page; our lab validation will confirm whether a usable app exists.
Likely cause: A custom tender can record a payment on the device while the actual funds are handled by the app or processor off Clover; whether Clover settles it is unverified.
Fix: Reconcile the Clover record against the app or processor each day; do not assume Clover settled the money.
If that fails: Use the CryptoLic Accounting Toolkit's parallel-flow reconciliation if this becomes a burden.
Sources and verification
Last content review 2026-07-11 Documentation verified
- Native support
- 2026-07-11
- Integration
- 2026-07-11
- Pricing
- 2026-07-11
- Hardware
- 2026-07-11
- Refund workflow
- 2026-07-11
- Reporting reconciliation
- 2026-07-11
- Content reviewed
- 2026-07-11
- Editorial update
- 2026-07-11
- Clover Developer Documentation (index) Supports: Clover exposes a custom-tender developer surface
- Custom tender — Use cases and design requirements Supports: Custom tenders let apps add payment methods on all Clover devices
- Creating custom tender apps Supports: Custom-tender apps support QR/wallet flows and can process refunds
- Working with orders Supports: Payments attach to Clover orders with id/amount/type
- Clover Network Supports: No native crypto acceptance; Fiserv/First Data ownership
- BitPay Integration Guide Supports: No official BitPay-Clover integration found
Change log
- 2026-07-11 Initial publication. Documentation review complete; hands-on lab validation in progress.
Spotted something out of date? Send a correction. We verify every submission against primary sources; vendor contact never changes a rating.
Questions
Does Clover let my customers pay me in cryptocurrency?
Not with a built-in tender. Clover's documented payment methods are cards, Apple Pay, and contactless. Crypto acceptance would depend on a custom-tender app or a separate wallet beside the register, and we have not yet confirmed a ready-to-use crypto app exists.
What is the Custom Tender API, and does it mean Clover supports crypto?
It is a developer capability that lets approved apps add a payment method to the register, including QR or wallet flows and refunds. It means crypto acceptance can be built for Clover. It does not mean a finished, reliable crypto app already exists, or that its payments report and settle cleanly. That difference is the whole point.
Is Clover better than other registers for crypto?
On paper its Custom Tender system is a stronger extension point than a register that offers no such thing. But "stronger on paper" is not "proven in practice." Until we verify a real app reports and settles, treat Clover as a promising but unconfirmed option.
Will a crypto sale show up in my Clover reports?
Unknown. Clover's docs describe custom tenders but do not confirm whether a custom-tender payment appears in merchant reporting or settles into your account. This is one of the first things our lab will test; until then, reconcile Clover against your crypto tool.
How this compares
Every platform we cover is rated the same way. Here is where the others land.
| Platform | Level | The short version |
|---|---|---|
| Square | Parallel acceptance | Square has no built-in crypto acceptance. You can take crypto beside the register and record it in Square as an external payment, then reconcile by hand. |
| Toast | Parallel acceptance | Toast has no built-in crypto guest payment. A partner-tender path may exist but is unconfirmed, and how crypto behaves with restaurant basics like split checks and tips is entirely unverified, so most restaurants should wait. |
| Shopify POS | Parallel acceptance | Shopify supports crypto on its online checkout, but not at the in-person POS. At the register, crypto runs beside Shopify, and even recording it in Shopify POS is unverified. |
Learn the fundamentals