Facilitator
Facilitator provides Checkouts, sessions, immutable requests, evidence verification and automatic redemption for native IPP. It supports self-hosted payment services, wallets and agents. Hosted InvisiPay integration follows the separate commercial payments contract.
Service boundary
The merchant creates a Checkout; the payer confirms an option and executes. Facilitator continuously discovers chain facts through trusted Protocol RPC, atomically redeems finalized evidence before the deadline and exposes Session, receipt, evidenceStatus and exceptionSummary. Merchants need no separate redemption call. GET is read-only.
The payment HTTP service does not construct, sign or broadcast user transactions, accept payer witnesses or private keys, or read chain nodes directly. Payers execute through their wallet and SDK, broadcasting directly or through a Broadcaster. Operators have separate explicit commands for wallet collection and credit draws using merchant receiving/spender authority; these are outside payer IPP requests.
Before integrating
Obtain the operator's HTTPS service address and merchant API Key. Confirm supported networks, pinned Core deployments, assets and finalized capability. IPP v1 messages and Core deployment versions are independent; a v1 HTTP path alone does not establish compatibility.
The merchant server stores credentials, Checkout associations with local orders/API operations and creation idempotency keys. Select a trusted cashier in advance. The default cashier entry uses https://dapp.invisipay.fi/checkout; use the actual creation response, since operators can configure another trusted frontend. Browser origins must be allowed by the service's CORS policy; CORS does not replace authentication.
Before enabling credit options, confirm wallet support for an externally supplied creditSharedKey, service decryption of the configured spender's deliveries and complete consistent RPC snapshots. Creation with initial payment additionally needs client and broadcast support for the combined operation. A protocol definition does not establish availability in every service.
The HTTP integration covers credential isolation, endpoints and examples; deadlines and recovery defines actions for unknown outcomes.
Trust and custody for self-hosting
Protocol RPC is the trust source for canonical-chain and finalized state. Pin the network, Core and deployment metadata, and reject client-selected verification sources. Dependency failures require waiting or errors without weaker finality or treating missing results as nonpayment. Finality conflicts stop new redemption for the affected deployment while preserving historical evidence.
The service encrypts private Sessions/Requests, Note receiving material and creditSharedKey. Back up the database and every historical storage key. Checkout Notes without ciphertext require original receiving material for recovery. Back up the receiving keystore and password separately; replacing the wallet does not migrate the previous owner's funds.
Explicit CLI collection/draw operations can use hot-wallet spending authority while cold-wallet private keys remain offline. Offline inventory/status reads are cached and cannot prove current holdings or credit availability. Later draws must validate current state and limits, restoring unknown submissions with a persistent operation ID rather than creating another draw after timeout.
Security and trust covers cross-component considerations. Obtain installation artifacts, runtime requirements and supported capabilities from the chosen operator's deployment guidance. Examples here do not designate a publicly available Facilitator instance.