Skip to main content

IPP payments and credit

IPP defines a shared payment interaction for wallets, agents, merchants and payment services. mode identifies the business purpose (payment or credit); method identifies the execution method, such as invisi. Each Session has one mode and can offer several networks and assets.

This section covers native IPP. For the hosted InvisiPay merchant API, use the commercial payments documentation, which has its own resources, authentication and commercial confirmation policy.

From Checkout to receipt​

Merchant creates Checkout → read PaymentSession → confirm one option
→ immutable PaymentRequest / CreditRequest
→ wallet authorization and execution → service discovers, verifies and redeems evidence
→ GET original sessionUrl → status, receipt and exception summary
ObjectIntegration purpose
CheckoutMerchant creation response containing sessionUrl, checkoutUrl and expiresAt
PaymentSessionOptions, current status, unique activeRequestId, receipt and exception summary
PaymentRequestNetwork, Core, asset, amount and recipient identity for one payment
CreditRequestCredit creation terms, spender and protected shared key
CredentialOptional transaction hint; neither payment proof nor spending authority
receiptImmutable historical record embedded in the Session after successful redemption

One Checkout has one Session, one Request fixed at confirmation, and at most one successful receipt. Creation does not allocate execution material. Confirmation atomically persists that material and the requirements. Confirming the same option again recovers the original Request without refreshing its deadline or keys; selecting another option conflicts.

Responsibilities​

The merchant owns orders and caller authentication, selects a Facilitator and stores the order association. The wallet checks terms, generates proofs, obtains user authorization and broadcasts directly or through a Broadcaster. Core enforces funds and execution authority. Protocol RPC provides trusted chain facts and finality. Facilitator manages IPP objects and proactively discovers, verifies and redeems evidence through RPC.

The Facilitator HTTP payment service does not construct, sign or broadcast payer transactions and does not access chain nodes directly. Background reconciliation continues if the client closes its page or omits Credential submission. GET reads state without redeeming evidence or fulfilling an order.

Choose an integration path​

Merchants use the Facilitator integration to create and deliver a Session. Wallets obtain sessionUrl and session access from a trusted merchant, then follow complete operation links. Do not derive paths from object IDs.

Payments explains amounts, receiving material and evidence checks. Credit and later draws covers allowances and optional initial payment. Authorization, deadlines and recovery covers tokens, idempotency, terminal states and exceptions. See Facilitator for deployment and trust requirements.