Merchant examples

Download working Pay by Paybyte examples.

These packages are reference merchant integrations for PBE Mainnet and are meant to be copied onto a compatible PBE web node and adapted. They use the Paybyte Ice interface, keep credentials out of the browser, and include explicit setup files instead of silently changing your merchant database.

Examples, not hidden infrastructureThe downloadable folders are ordinary PHP/JavaScript examples. They use public PBE-PAY APIs and, where required, the Commerce webhook credentials already configured on the merchant-controlled PBE node.

Paybyte Coffee Mug checkoutReal 50 PBE wallet handoff + exact payment polling. Includes README.txt and a no-op database.sql because this checkout example requires no merchant tables. Golden Sword webhook fulfilmentReal 25 PBE payment + signed server-to-server webhook + idempotent MySQL inventory grant. Includes README.txt and the required database.sql.

Coffee Mug checkout

Use this example when you want the smallest real checkout flow: create a unique payment reference, open the Paybyte wallet with the immutable payment tuple, and display canonical confirmation progress. It is intentionally not a production order database.

Included file	Purpose
README.txt	Installation, configuration and expected checkout flow.
database.sql	Intentional no-op; no merchant tables are required for this polling example.
config.js	Public product, amount, recipient, node and wallet settings.
assets/paybyte-pay.js	PBE-PAY browser helper used for request/status/wallet handoff.

Golden Sword webhook fulfilment

Use this example when a merchant application must automatically grant something after payment. The customer browser never decides fulfilment. A signed PBE webhook updates merchant-owned MySQL state and grants the fake item exactly once.

Included file	Purpose
README.txt	Manual installation, webhook configuration, security notes and cleanup.
database.sql	Three disposable merchant demo tables. Import manually before running the example.
demo-config.php	Public demo values such as recipient, amount, node URL and callback URL. No secrets.
webhook.php	HMAC-authenticated webhook receiver and fulfilment entry point.

Database changes are manualThe Golden Sword example checks that its tables exist and stops with a setup message if they do not. It never issues CREATE TABLE from a browser request.

Where credentials live

The webhook example deliberately does not ship database passwords, manageToken or signingSecret. When installed under a PBE web node it reads those from the node's existing config/config.php. Public example settings live separately in demo-config.php.

Server docs vs. standalone nodes

The Developer portal and these hosted downloads are part of the Paybyte.org/server distribution. Standalone node packages omit /web/developers and direct developers to Paybyte.org for the canonical documentation and example archives. The payment protocol itself does not depend on Paybyte.org.