NO CENTRAL ORDER LEDGER

Keep payments working without Paybyte.org.

PBE-PAY proof lives in signed transactions on the PBE chain. Merchants may run their own node and point checkout/status/webhook infrastructure at it.

What Paybyte.org is not

Paybyte.org is a primary public node, explorer, wallet host and documentation site. It is not a required custodial payment processor and it does not own merchant order state. A merchant can operate a node, receive PBE directly, verify its own payment references and deliver its own webhooks.

Recommended merchant layout

Architecture

Customer browser
    │  opens PBE wallet / signs locally
    ▼
PBE network  ────────────────┐
                             │ canonical transaction proof
Merchant-controlled PBE node│
    │                        │
    ├─ status verification   │
    └─ signed webhook ───────┘
           │
           ▼
Merchant application database → fulfil exactly once

Failover

For read-only status and blockchain queries, applications can maintain multiple compatible node URLs. Before trusting a failover node, verify networkId=1, chainId=PBE-MAINNET, protocol compatibility, the frozen mainnet genesis hash and reasonable synchronization state.

Reorganizations

Node synchronization uses a common-ancestor incremental reorganization path and atomic chain replacement where necessary. Merchant integrations must still treat confirmation depth as confidence rather than mathematical finality and react to payment.reorged.

Deep-history limitationPBE 0.0.1 does not yet implement hard finality or a trusted checkpoint mechanism. A sufficiently strong alternate history or long network partition can therefore create deep-reorganization risk. Newly syncing nodes should bootstrap from known compatible nodes and verify the frozen genesis identity.