---
title: Taking Bitcoin without a payment processor
url: https://namegarage.com/blog/bitcoin-without-a-processor
author: Namegarage
date: '2026-11-16'
description: How Namegarage checks a Bitcoin payment with two block explorers, and
  why a seller command never trusts one read.
ai-disclosure: ai-autonomous
---

# Taking Bitcoin without a payment processor

This article was generated with AI and published without human review.

Namegarage accepts Bitcoin for direct domain purchases. The buyer pays a
wallet address shown on the invoice, without a payment processor. Our payment
service checks the chain evidence before the seller accepts the payment.

The payment service holds no private key. Wallet software exports receive
addresses, and the loader derives them independently from the account public
key. A mismatch refuses the address file. The website allocates a separate
address to each invoice.

## Two explorers must agree

We read Bitcoin through mempool.space and blockstream.info. A payment counts
only when both report the same outputs and values to the invoice address,
confirmed in the same block and at least three blocks deep. Disagreement
holds the payment. An unavailable explorer leaves the recorded evidence
unchanged rather than treating a missing answer as proof.

The reconciler checks recorded payments again, including after the seller
accepts them. Each transaction output has one ledger identity, so another
scan cannot count it twice. Version checks stop an overlapping run from
overwriting a newer invoice state.

## Acceptance and transfer are separate steps

The seller's confirm command checks fresh chain evidence before it records
the sale. A payment for a domain that cannot be sold needs resolution or a
return; it does not authorize another domain's transfer.

Before the seller manually pushes the domain at GoDaddy, a separate push
check requires every payment to be six blocks deep, with nothing on hold and
fresh evidence. It withdraws the sale's listings from supported marketplaces
and reads them again. An unreadable marketplace or a listing still present
prevents the check from passing. The seller separately confirms withdrawals
that require a dashboard or other manual work.

## The rehearsal keeps the checks

Bitcoin test purchases settle on signet, whose coins have no monetary value.
They run the same confirm, withdrawal and push-check path. Test mode routes
portfolio changes to a rehearsal database, marks notices, and simulates
marketplace withdrawals. Recording a completed rehearsal never tells the
operator to transfer a real domain.

## Why the catalog packages get a patch

The buyer's invoice and seller commands are outside the public catalog API.
HTTP catalog routes, the four public MCP tools, A2A and UCP retain their
contracts and component versions.

SDK 0.3.1 and both compatibility packages carry the coordinated release
metadata. Skill 1.3.1 pins that SDK version. Their public methods, types and
read-only boundaries are unchanged. The package archives contain release
metadata, so changing that metadata needs new immutable versions. The
published SDK 0.3.0 and skill 1.3.0 artifacts keep their original bytes.

The SDK and both compatibility packages are now available on
[npm at 0.3.1](https://www.npmjs.com/package/@namegarage/sdk/v/0.3.1).
Catalog skill 1.3.1 is available through
[ClawHub](https://clawhub.ai/namegarage/skills/catalog) or its
[immutable GitHub tag](https://github.com/namegarage/skills/tree/v1.3.1).
The [skills.sh listing](https://www.skills.sh/namegarage/skills/catalog)
still serves the previous snapshot;
[upstream #2600](https://github.com/vercel-labs/skills/issues/2600)
tracks that refresh. The coordinated release remains upcoming.
