Skip to content

Pay-to-Play deployment settings ​

Choose these settings before following Deploy a new instance with the pay-to-play prefix. Hosting a new viewer or publishing compatible navigation is not a reason to replace the payment contract.

Choose independent authorities

SettingMeaning
INTENDED_PAYMENT_ADMINCreates service channels and changes their payees/collectors. This account does not acquire customer voucher-signing or refund-destination authority.
INTENDED_CAM_ROOT_OWNERChanges workflow resources and contract bindings. It can differ from the payment administrator.
NULL_CLAIM_PERIODReserve channel 0's fixed withdrawal wait, from 0 to 2,592,000 seconds. Zero means no wait. Service channels receive their own fixed waits later.

The business operation creates PayToPlay with reserve channel 0. It does not create service channels or register customer keys. The separate PayToPlayUI projection supplies signing details; the CAM root binds both.

Use the shared procedure to prepare, host and publish the exact bundle. At an intentionally selected hosting pause, repeat the same operation and enter the hosted URI when prompted; do not start another deployment. Independent projection-deployer and CAM-owner configurations are described in operation inputs.

Accept each nominated ownership separately

If an intended owner differs from its current creator, the release nominates it; it does not sign acceptance on its behalf. The payment nominee calls acceptOwnership() on contracts.payments.address in the business artifact. The CAM nominee accepts on root.contract.address in the final publication artifact.

Neither handover has a built-in waiting period. The current owner retains authority until acceptance. Selecting the creator as final owner needs no handover. Later payment-admin changes use that payment contract's own transferOwnership/acceptOwnership sequence, independently of CAM ownership.

Check records and current readiness

pay-to-play/release/verify checks the selected operation's original-source evidence without signing. It accepts recorded pending handoffs as historical facts, not as completed current acceptance.

Before opening service, inspect both owners and pending owners, the intended root bindings, hosted-resource integrity and a known position read. Create any service channel under the payment admin, confirm its payee and collector, and select ChannelCreated by event topic rather than assuming it is the receipt's only log.

Qualify the clients before replacement

Current calls include createChannel(payee, collector, claimPeriod) and capped, invoice-bound collection. A zero collector disables collection; only its configured nonzero address may submit vouchers. Clients must decode the collector field in channel and position views.

Vouchers use the PayToPlay/2 domain and the payment contract's address, not the CAM host. A replacement address invalidates old signatures for the replacement and moves no balances or permanent keys automatically. Preserve the original instance and make an explicit service/client migration decision before public cutover.

Use Update an existing app for compatible CAM or projection changes, recovery for incomplete retained work, and source verification for Sourcify retries. Local release practice uses separate public fixture credentials and no customer funds.

Source: payment rules, creation and admin nomination. User guide.