PBE-PAY v1

Accept Paybyte without giving the browser authority.

Merchant integrations create the order tuple on the server, hand that immutable request to a compatible wallet, and verify the exact reference, recipient and amount against PBE before fulfilment.

Non-custodial settlementThe recipient is a merchant-controlled PBE address. Paybyte does not need custody of merchant funds or an external order ledger.

Recommended flow

Create order server-side→Generate PBE-PAY request→Customer signs locally→Verify exact tuple→Wait for policy depth→Fulfil exactly once

Choose a path

Integrate a checkoutBuild the minimum server-authoritative payment flow.Try the sandboxWalk through the customer-facing flow without moving PBE.Automate fulfilmentUse signed server-to-server events and idempotent order handling.Download examplesUse the Coffee Mug polling or Golden Sword webhook reference packages.

Protocol reference

This section is operational merchant guidance. The normative HTTP surface remains in the Commerce API and Commerce webhook developer references.