@PUBPAY.me utilizes kind: 1 events (text notes) to represent payment requests, making them part of the social fabric of Nostr.
PubPay uses specific tags to define payment parameters, such as the amount, payer, and payment conditions. These tags make the payment request machine-readable and interoperable with other Nostr-based applications. Any client that understands these tags can display and process payment requests correctly.
This transparency ensures accountability and allows for public verification of payments through kind: 9735 events (zap receipts) linked to the original payment request.