Private draft / Integration work in development

Stela

One open standard for accepting bitcoin at the till.

Stela connects point-of-sale systems to bitcoin settlement providers through one common API. Independently implementable. Non-custodial. Open participation.

The problem

Every pairing is a bespoke integration.

Each point-of-sale system speaks its own dialect. Each settlement provider does too. Wire one POS to one provider and you have built one integration. Wire it properly, for every POS and every provider, and the build grows by multiplication, not addition.

Before: every POS wired directly to every settlement provider, N times M bespoke connections
N POS × M providers
After: each operator implements one common interface; Stela is not a central relay S
N + M implementations; direct operator connections
How it works

Three steps, the same on every till.

01 · Pair

Pair

The merchant links their till to their chosen settlement provider using a credential the provider issues. The credential stays with the till and provider; Stela is a specification, not a relay.

02 · Pay

Pay

The customer pays a standard Lightning invoice from any wallet. Supported payment methods and rate details depend on the provider's advertised capabilities.

03 · Settle

Settle

The provider settles the way the merchant has chosen: convert to AUD, part-convert, or keep the bitcoin. Payments are final.

Same three steps, regardless of which POS or which provider is on either end.

Two routes

The merchant chooses where settlement happens.

Stela does not prefer one route over the other. Both speak the same API to the till.

Route A

Exchange

A bitcoin exchange settles the sale: conversion to AUD, scheduled payouts, and the usual reconciliation a merchant already expects from a payment provider.

Route B

Self-custody

The merchant runs their own settlement server, such as BTCPay Server, and keeps the bitcoin. No provider sits between the till and the merchant's own node.

What the Stela standard never does

Not in the payment path, on purpose.

  • Never holds funds
  • Never sees customer or merchant data
  • Never sits in the payment path
  • Never charges per transaction
  • No memberships
  • No dues, no exclusivity

Governance

A standard, not a company gate.

Stela specification work uses open participation and rough consensus among implementers. No membership dues, preferred implementers or permission to implement. Conformance is self-tested and self-attested, not certification or endorsement by Hansetag.

Hansetag is the company brand behind OpenPOS and hosts this overview. It is not the name of a separate standards governing body. Hosting this page gives Hansetag no exclusive control of Stela. Licensing and formal infrastructure stewardship remain explicit decisions before publication.

Status

Stela is being drafted.

The specification and separate reference implementations remain in development. This overview does not publish the private source or claim production readiness.