Payments
mode=payment with method=invisi asks the payer to send the specified asset and amount to the Request's independent recipient identity. Amounts are canonical decimal strings in asset base units, without floating point conversion. For an asset with six decimals, "10000000" means 10 tokens. Network, Core and token address establish asset identity; a display symbol does not.
Confirmation and wallet execution
Read the Session, display its options, then confirm through links.confirm. The service freezes the chosen network, asset and amount, allocates a receiving identity and stores the expected Note commitment. The wallet checks that the Request matches the selected option, validates the trusted Core deployment and constructs the output. Session options alone are insufficient execution instructions.
This is a partial PaymentRequest showing its payment field, not a complete response. All addresses and the identity are placeholders; execution requires actual values from the authenticated response:
{
"payment": {
"network": "eip155:8453",
"protocolAddress": "0x3333333333333333333333333333333333333333",
"tokenAddress": "0x1111111111111111111111111111111111111111",
"amount": "10000000",
"recipient": {"type": "identity", "identity": "0xEXAMPLE_RECEIVER_IDENTITY"}
}
}
The service retains receiving material such as the Note nonce; the payer receives the required identity. Idempotent confirmation and device handoff must preserve the original identity, requestId and deadline. The wallet uses its SDK's execution interface to prove and broadcast. IPP does not add a payer identity signature.
Optional Credential
After broadcasting, the client may send a hint to Request.links.credentials. This is the complete message shape; replace every ID and hash with the actual values. Submission requires the Session Token, and HTTP 202 means accepted only:
{
"ippVersion": 1,
"type": "credential",
"mode": "payment",
"method": "invisi",
"sessionId": "ses_EXAMPLE",
"requestId": "req_EXAMPLE",
"proof": {
"type": "note",
"transactionHash": "0xEXAMPLE_TRANSACTION_HASH",
"commitment": "0xEXAMPLE_NOTE_COMMITMENT"
}
}
Background discovery also works without a Credential. An invalid candidate cannot replace the saved requirements or invalidate another valid payment. A Credential contains no private key, Note opening or transaction to broadcast.
How receipt verification works
Facilitator recomputes the expected commitment from the saved requirements and obtains finalized evidence through Protocol RPC invisi_getNote for the pinned deployment. It checks the successful transaction, output event, asset, membership, canonical block and confirmation context. A transaction hash, safe observation or membership alone cannot complete redemption; finality must not be weakened.
The expected commitment binds the amount; RPC does not receive the private opening. Later merchant collection or spending of the Note does not erase historical receipt evidence.
Before success, receipt=null. Verification and evidence consumption are committed atomically; the Session becomes succeeded, with network, protocolAddress, transactionHash, commitment, blockNumber, blockHash and completedAt in its receipt. The merchant reads that receipt and current evidenceStatus through authenticated queries and fulfills the original order idempotently. Copied client JSON is not an independently verifiable signed receipt.
Extra or late payments become exceptions and cannot restore a failed Session. The recovery rules explain waiting, restoring the original transaction and handling exceptions.