Accept Lightning Payments From BlueWallet Users

Yes. BlueWallet is an open-source Bitcoin wallet with built-in Lightning, so BlueWallet users can pay any Lightning invoice, and a business that accepts Lightning through the Amboss Payments API can receive from them directly. BlueWallet sunset its custodial Lndhub.io node in 2023, per Bitcoin Magazine's report on the change, but the app still sends and receives Lightning, with the rail invisible to the payer.

Does BlueWallet support Lightning?

Yes, for both sending and receiving. BlueWallet runs Lightning alongside its on-chain wallet and connects through LndHub, so a user can move a balance in and out of the app. To pay you, a customer opens the Lightning wallet, scans your invoice as a QR code, and confirms.

The BlueWallet Lightning page describes the receive flow directly:

Receive instant payments. Generate invoices that can be easily shared.

There is one history worth keeping straight. BlueWallet used to provide a custodial Lightning wallet through its own Lndhub.io node, which it retired in 2023. The BlueWallet LndHub repository still describes the open software it built:

Wrapper for Lightning Network Daemon (lnd). It provides separate accounts with minimum trust for end users.

Today a BlueWallet user connects to a self-hosted or third-party LndHub, but the payment they send to you is a standard Lightning payment either way.

How do you receive payments from BlueWallet users?

You do not build a BlueWallet integration. You accept Lightning once and every BlueWallet user becomes a potential payer. The flow is four steps:

1. Integrate the Amboss Payments API and create a Lightning invoice for the order amount.
2. Show the invoice to the customer as a QR code or a copyable string at checkout.
3. The customer scans it inside BlueWallet and confirms the send from their Lightning balance.
4. The payment routes over Lightning and settles to you in seconds. You fulfill the order.

The payer never chooses a network and never needs an account with you. Live Lightning capacity and routing data are published on the Amboss Space Lightning explorer.

How do you integrate BlueWallet receiving into checkout?

Receiving from BlueWallet is the standard Lightning receive flow: create an invoice, then confirm settlement. A Lightning invoice is a self-contained string defined by the BOLT 11 payment-encoding specification, so the same code path accepts BlueWallet, Cash App, Strike, and any other Lightning sender.

The Amboss Payments API is GraphQL. A single create_receive mutation returns the BOLT 11 invoice you show the customer:

mutation CreateReceive {
  payment {
    transaction {
      create_receive(
        input: {
          wallet_id: "your-wallet-id"
          amount: "50000"
          description: "Order #1234"
        }
      ) {
        status
        payment_request
        payment_hash
      }
    }
  }
}

Send it to the https://rails.amboss.tech/graphql endpoint with your x-api-key. The payment_request field is the lnbc... string you render as a QR code, and you confirm settlement with the payment.completed webhook, as documented in the Amboss Payments API documentation. Lightning settles atomically, so there is no pending state that reverses a week later.

Where does Amboss Payments fit?

Lightning is an open standard, which is why a single integration receives from every wallet. Because BlueWallet is open source and connects over LndHub, the way a BlueWallet customer pays you is the same standard Lightning receive as any other sender. Amboss Payments gives you that integration as a managed API on the Lightning Network, with no node to operate. If you want to talk through volume, settlement, or pricing, contact the Amboss team.