Skip to main content

Addresses, payment codes and requests

Identify what was entered​

InputWhat it can representWhat remains to validate
Ordinary chain addressA receiving account on a networkNetwork, asset, amount and recipient control
0i privacy addressProtocol-defined public receiving materialEncoding, deployment, asset and execution route
Short address / aliasA resolvable identifierCurrent resolution, registration and complete receiving material
Payment code / linkAn address or a request entry pointFormat, source, fixed Request and trusted service
Transaction hashA public transaction locatorIt is neither a recipient address nor a spending credential

The 0i prefix does not fix a chain or asset. Full privacy addresses do not encode chain ID; select the network and asset separately. A short address is not a truncated display string. Never encode a visual abbreviation containing an ellipsis as a usable address.

Receiving flow​

  1. Choose ordinary or private receiving and the account.
  2. Pin the network and actual token identity and inspect supported capabilities.
  3. Create a payment request using the current interface, or encode an ordinary address with supported parameters.
  4. Display the bound asset, network, optional amount and memo.
  5. Generate a scannable QR from the actual payload; copy, download and share the same latest payload.

Changing the asset, account or amount can invalidate the displayed terms. Use request sequencing or cancellation to prevent late responses from replacing the newest request. Disable copying, downloading and sharing stale codes while generating, or explicitly identify that they no longer match the current interface. Show encoding errors rather than decorative pseudo-QR patterns.

Payer validation​

Native IPP first reads a Session, presents options, then confirms to obtain a fixed Request. Follow authenticated links and validate the asset, network, amount, deployment, recipient and deadline. See IPP payment. Merchant Checkout has separate API credentials, amount units and states; see merchant payments.

A reachable URL is not necessarily trusted. Validate allowed deep-link schemes and paths. External endpoints require origin and destination checks; do not forward user credentials or access local/internal services at arbitrary supplied URLs. Keep the original request for recovery when a service is unavailable rather than inventing a recipient.

QR acceptance checks​

  • Test actual payload encode/decode round trips, not just appearance.
  • Cover long addresses and requests, asset precision, Unicode memos, exported images and scaling.
  • Respect encoder capacity, quiet zones and contrast. A center logo must not prevent decoding.
  • Test App scanning, web copy, external-wallet opening and rejected signatures independently.

Legacy IPP codes and current native IPP Requests may use different wire formats. Follow the parser and contract in version compatibility; matching an ipp or 0i prefix is not enough to reuse a legacy implementation.