For businesses
Plan around a payment you can verify.
Local commerce and trade between distant communities motivate the design. Production merchant services remain a future goal.
CONTENT REVIEWED / 4 OCTOBER 2026
Serve a community through its local ledger
A business in a future habitat or settlement should be able to receive a locally ordered payment while a remote region is disconnected. Availability still depends on local connectivity, consensus, custody and the region’s adopted rules. A partition without sufficient finality resources can stop settlement.
Bind the invoice to the intended payment
A signed payment request can identify the exact currency, recipient, destination Zone, amount, purpose, expiry and nonce. The payer must review those fields and authorize the resulting transaction. An invoice, browser download or queued command alone does not debit funds.
The recipient must independently check the actual ledger result and current payment state. A screenshot or a relay delivery acknowledgment is insufficient.
Choose the acceptance state deliberately
Local block inclusion, recipient maturity and regional finality answer different questions. Prefunded channels aim to provide signed local payment receipts; they depend on verified funding and timely local monitoring of stale closes. A distant watchtower cannot promise a response within a local dispute window.
A cross-region order may remain pending until finalized export evidence arrives, is imported exactly once and reaches local maturity. The business should expose that pending state and its dependency to both parties.
Account for the same value once
The source debit precedes destination credit. Import does not issue new RLD, and a retained export record is evidence rather than an additional balance. Accounting must distinguish spendable outputs, escrow and unresolved exports on compatible selected histories; disconnection prevents an instantly current global view.
An onward or return journey is a new finalized export and unique import. A returned receipt never releases the original source debit.
Evaluate before integrating
Use an exact public fixture to test invoice review, amount conservation, duplicate rejection, restart and recipient verification. Publish sanitized reproducible findings with the source commitment and observed limits. Consumer wallets, operational funding, independent custody, service capacity and outside review remain required before a real-value product.
Continue exploring
