Payment Request Link

Overview

A payment request link is a shareable URL that opens a hosted page containing the details and actions needed to complete a payment. It may display amount, currency, accepted methods, merchant information, expiration, and a QR code or wallet action. Data handled by Payment Request Link should use documented types, units, timestamp rules, nullable fields, and enum behavior to prevent silent interpretation errors.

Merchants should use HTTPS provider domains or verified custom domains, unique references, appropriate expiration, and clear payer instructions. The link connects a payer to a specific or reusable payment request without requiring the merchant to build checkout. Forwarded, expired, or spoofed links can create phishing and allocation risk. Testing Payment Request Link should cover malformed input, denied access, rate limits, timeouts, duplicates, asynchronous completion, and version changes.

For Payment Request Link, metrics should separate transport success from business success. Visiting the page or returning to the merchant does not prove payment completion. Anyone receiving the URL may access its content, so sensitive data should be minimized. Authenticated callbacks and authoritative status checks must drive order updates, with reconciliation for late or duplicate payments.

The Payment Request Link owner should publish stable error semantics and guidance on whether correction, retry, status lookup, or escalation is appropriate.

The Payment Request Link contract should define identifiers, validation, authorization, status semantics, errors, limits, and version behavior at the same boundary.

For Payment Request Link, the application should preserve a correlation path from request construction through response, asynchronous completion, and final business state.