Payment solution

Breez SDK: crypto payment solution

The verdict

Breez SDK is a developer toolkit for building self-custodial Lightning into your own app. A typical merchant cannot use it as-is; it is for the developer who would build a merchant product on top of it.

Who holds the funds
Merchant-controlled
Who holds the keys
Merchant
Self-hosting
Not required (hosted)
Lightning
Yes
Fiat settlement
No
Bank settlement
No

Best for: Product teams and developers building a custom self-custodial Lightning app or wallet.

Poor fit: Any merchant who wants to accept crypto without commissioning custom software.

Biggest tradeoff: Breez SDK is genuinely strong developer infrastructure: self-custodial, open-source, multi-language, with good Lightning support. But it is a building block, not a product. The entire merchant experience, POS, refunds, reporting, must be built, which is why it is not merchant-ready.

Confidence: Medium Last reviewed 2026-07-11

What it is

Breez SDK is a developer toolkit for embedding self-custodial Lightning payments into an app. It comes in flavors (the maintained Nodeless/Liquid and the current flagship Spark, a Bitcoin L2 with stablecoin support; the older Greenlight is deprecated), with multi-language bindings and a reference wallet app.

What it is not

It is not a merchant product. It is not a POS, a checkout, a wallet a merchant just installs, or a gateway. There is no merchant surface at all: no refunds, reporting, or accounting until a developer builds them. A merchant cannot use it without commissioning custom software.

How the payment flow works

A developer integrates the SDK into an application, which then holds a self-custodial wallet for its user. Payments settle in Bitcoin or Liquid (and stablecoins on Spark) to that wallet. Everything a merchant would see, the register, the receipt, the report, is something the developer must build.

Custody, keys, and settlement

The most important thing about any crypto payment solution is who controls the money and what happens if the provider goes away. Here is the structured answer, from primary sources.

Custody
Merchant-controlled
Key control
Merchant
Fiat settlement
No
Bank settlement
No
Settlement timing
Instant
Settles in
Cryptocurrency
Backup and recovery
Merchant

Conversion: Breez SDK is self-custodial: keys are held by the end user of the built app. There is no fiat conversion or bank settlement; the Spark flavor adds stablecoin support on a Bitcoin L2.

Getting your money: Funds live in the wallet of the app a developer builds, controlled by that app's user via a seed. Recovery is restore-from-seed; whether balances remain spendable if Breez swap/API infrastructure is down is not fully documented.

If the provider or hosted service becomes unavailable

Payments stop, but existing funds remain merchant-controlled.

Funds are self-custodial in the app built on the SDK, recoverable from the user's seed, so they remain merchant-controlled. However, some flows depend on Breez swap and node infrastructure, and whether balances stay fully spendable if that infrastructure is unavailable is not completely documented.

What you have to operate

As a merchant, nothing, because you cannot use it directly. As the developer who adopts it, you own and operate the entire application built on the SDK, including its infrastructure and updates.

Ongoing maintenance: Full software ownership: the built app, its updates, and its infrastructure.

Support: Developer documentation and community; not a merchant support channel.

Who this is right for

A product team or developer building a custom self-custodial Lightning app or wallet, who wants a well-supported, open-source foundation to build on.

Who should skip it

Any typical merchant. If you do not employ developers to build a payment app, this is not something you can use; you want a finished product instead.

Our evaluation

Money and control

Who holds your money and keys, whether you get dollars, and what happens if the provider goes away.

What we evaluate Rating Why Confidence
Custody model Who holds your money between the sale and settlement, you or a third party. Excellent Self-custodial by design: keys are held only by the end user of the built app. High
Settlement Whether you get dollars, crypto, or a choice, and when. Not applicable Settlement is whatever the developer builds; the SDK settles Bitcoin/Liquid to the app wallet, with no fiat. High
Fiat support Whether you can price and settle in dollars cleanly. Poor No fiat conversion or bank settlement; the SDK is crypto-only. High
Refunds Whether you can refund a payment, and how. Never inferred from an API. Not applicable There is no merchant refund surface; a developer would build any refund logic. High
Security model What you are trusting and what your exposure is: keys, custody, attack surface. Good Self-custody keys in the built app; seed backup and security are the developer's responsibility. Medium

Operations

What running this actually takes day to day, and whether it produces records your books can use.

What we evaluate Rating Why Confidence
Hosting requirements Whether you have to run a server or a node. The biggest burden divider. Not applicable A merchant hosts nothing directly; the developer's built product carries any hosting. High
Ease of setup Honest effort to go live, not marketing easy. Poor For a merchant there is no setup: a development project must precede any use. High
Accounting and records Whether it produces records your books and CPA can use. Not applicable No reporting or accounting surface exists; a developer would build it. High
Employee workflow What your staff actually have to do, and whether multiple users are supported. Not applicable No merchant or staff workflow; this is a toolkit. High
Merchant support Who helps when it breaks, and how good that help is. Not applicable Support is developer-facing; there is no merchant support relationship. High
Offline capability Whether it works when the internet or a node is down. Not confirmed Offline behavior depends on the built app and the swap infrastructure; not documented for a merchant. Low

Technical capability

What the solution can actually do: Lightning, on-chain, stablecoins, and how extensible it is.

What we evaluate Rating Why Confidence
Lightning support Whether you can take Lightning, and what that requires operationally. Good Strong Lightning support across flavors (Nodeless/Liquid and the newer Spark). High
On-chain support Whether you can take on-chain, with what confirmation and fee reality. Good On-chain and Liquid are supported as building blocks. Medium
Open source Whether you can inspect and self-host it, and whether it is actively maintained. Excellent MIT-licensed and open-source, with a reference wallet app. High
Operational maturity Whether this is a stable product or an early project. Good An active project; the Greenlight flavor is now deprecated and Spark is the current flagship. Medium
Developer ecosystem Whether you can extend it if you need to. Mostly for infrastructure and API-first tools. Excellent Multi-language bindings, docs, and a reference app; this is the product's real strength. High

Cost, clarity, and privacy

What it really costs all in, how clearly that is disclosed, and what using it reveals.

What we evaluate Rating Why Confidence
Fees What it really costs, all in, and how transparent that cost is. Not confirmed The SDK is free/open-source, but Spark end-user fees are deferred to an external page that was not retrieved. Low
Documentation quality Whether a merchant can actually learn to run this. Good Solid developer documentation; some fee and pricing pages 404'd. Medium
Privacy What using this reveals, and to whom: address reuse, KYC, on-chain linkage. Good Self-custodial and no KYC at the SDK level; specifics depend on the built app. Medium

We rate each area on its own. There is no overall score, because averaging areas this different, a self-hosted server's independence against a gateway's convenience, would hide the tradeoff you need to see. How we rate.

Pricing

Setup
$0 (SDK) (the SDK is free; building the app is the real cost)
Transaction fee
Depends on flavor (Liquid/Lightning/swap fees; Spark end-user fees not published)

The SDK is free and open-source. The real cost is commissioning and maintaining the app built on it. Spark end-user fees are deferred to an external page that was not retrieved; treat them as unconfirmed. Last verified 2026-07-11.

Limitations

  • It is an SDK, not a merchant product: a developer must build the entire experience.
  • No POS, checkout, refunds, reporting, or accounting out of the box.
  • No fiat conversion or bank settlement.
  • Spark end-user fees are not published (deferred to an external page).
  • Whether funds stay spendable during Breez infrastructure outages is not fully documented.

What we are still verifying

We publish what our documentation review supports and mark the rest as unverified. These questions are open. We will answer them with hands-on testing before we treat them as fact.

Open questionCurrent confidence
What are the exact end-user fees on the Spark flavor? Low
Do funds stay spendable if Breez swap/API infrastructure is down? Low

What are the exact end-user fees on the Spark flavor?

Why it matters: Fees are deferred to an external page that was not retrieved; they affect any app built on it.

Planned lab validation: Retrieve the Spark fee schedule from docs.spark.money.

Do funds stay spendable if Breez swap/API infrastructure is down?

Why it matters: Self-custody is documented, but independent spendability during an outage is not fully stated.

Planned lab validation: Review recovery/exit documentation and, if built, test an app under simulated outage.

CryptoLic Lab

CryptoLic does not stop at reading documentation. We independently validate what vendors claim by setting things up and running them ourselves, then we publish what we actually observed. For this solution, that hands-on validation is not scheduled. 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 verifyStatus
Confirm it is a developer SDK, not a merchant product Pending verification
Spark fee schedule Pending verification
Provider-outage spendability Pending verification
Holding your own keys?

If you control the keys, you own the security. The The Merchant Security Playbook covers backups, recovery, and keeping funds safe.

Keeping the books straight?

Whichever solution you choose, the crypto has to reconcile against your books. The The Merchant Accounting & Bookkeeping Toolkit gives you a routine and a clean year-end package for your CPA.

Sources and verification

Last content review 2026-07-11 Documentation verified

Custody
2026-07-11
Settlement
2026-07-11
Pricing
2026-07-11
Availability
2026-07-11
Kyc
2026-07-11
Supported assets
2026-07-11
Integrations
2026-07-11
Refunds
2026-07-11
Open source
2026-07-11
Content reviewed
2026-07-11
Editorial update
2026-07-11

How we verify and date facts.

  • Breez Breez · Checked 2026-07-11 Supports: Breez SDK is developer infrastructure for embedding Lightning
  • Breez SDK docs Breez · Checked 2026-07-11 Supports: SDK for developers; self-custodial; no merchant surface
  • Breez SDK - Spark Breez · Checked 2026-07-11 Supports: Spark is the current flagship flavor; stablecoin support; Greenlight deprecated
  • breez GitHub org GitHub/Breez · Checked 2026-07-11 Supports: Active multi-language SDK
  • breez-sdk-liquid LICENSE GitHub/Breez · Checked 2026-07-11 Supports: MIT license
  • misty-breez GitHub/Breez · Checked 2026-07-11 Supports: Reference wallet app (Misty Breez)

Change log

  1. 2026-07-11 Initial publication as the reference not-merchant-ready case. Documentation review complete; Greenlight noted as deprecated, Spark as the current flavor.

Spotted something out of date? Send a correction. We verify every submission against primary sources; vendor contact never changes a rating.

Questions

Can my business use Breez SDK to accept crypto?

Not directly. Breez SDK is a developer toolkit, not a finished product. A merchant cannot use it without a developer building an application on top of it. If you do not have engineers, you want a ready-made solution instead, which is exactly why we mark this not merchant-ready.

Is Breez SDK self-custodial?

Yes. Keys are held only by the end user of the app built with the SDK. That is a genuine strength, but it is a property of the toolkit, not a merchant experience you can buy.

Why does CryptoLic cover an SDK a merchant cannot use?

To be useful precisely by saying so. Vendors and AI summaries sometimes present SDKs as if they were products. We include Breez SDK to draw the line clearly: this is for your developer, not for you, and no amount of capability changes that.

How this compares

Every solution we cover is evaluated the same way. Here is where the others land.

SolutionCategoryReadinessThe short version
IBEX Infrastructure or developer platform R1 Not merchant-ready IBEX is Lightning and settlement infrastructure delivered through a single API for banks, fintechs, and platforms. A typical merchant cannot use it directly; a developer must build on it.
BTCPay Server Self-hosted acceptance platform R3 Workable with effort BTCPay Server is the reference self-custody answer: free, open-source software that takes Bitcoin and Lightning straight to your own wallet, in exchange for running and maintaining a server.

Related reading

Not sure this is the right one?

Compare it against the others in the Payment Solutions Decision Center, or start from what you actually need.

Something went wrong. Please try again in a moment. If the problem continues, contact us.
Thanks! Check your inbox to confirm your subscription.

Join the CryptoLic Insider

Practical cryptocurrency payment guidance for small businesses. Get occasional security tips, implementation guides, product updates, and launch announcements. No spam