Skip to main content

Payment Requests

Notareum replaces ambiguous payment links with cryptographically verified payment requests. A merchant creates a .nota file that specifies the exact amount, token, and destination address. The customer’s wallet parses the file, displays the verified merchant name and amount, and requires only a single confirmation. Today’s payment flows rely on user trust:
  • The merchant publishes an address in plain text
  • The customer copies it or scans a QR code
  • There is no cryptographic link between the merchant identity and the address
  • Phishing pages substitute attacker-controlled addresses with no detection
Billions of dollars are lost annually to address substitution attacks. Notareum eliminates this class of fraud by binding the merchant identity to the payment destination with a verified signature.

The Notareum payment flow

Building a payment request

Verification levels for payment requests

Higher levels give customers stronger guarantees that the merchant is who they claim. Payment processors serving high-value transactions should register as Institutional to command maximum trust.

Receipts as .nota files

After payment, the merchant issues a receipt .nota containing the on-chain transaction hash, amount paid, and a signature. Customers can archive receipts as portable, cryptographically verifiable records. This replaces traditional email receipts with a machine-readable, tamper-evident alternative.

Integration benefits

  • Fraud elimination: no way to substitute the destination address without breaking the signature.
  • Unified UX: a single file format works across any chain and wallet.
  • Audit trail: receipts are self-contained and verifiable years later.
  • Compliance: signed requests satisfy the FATF Travel Rule for covered transactions.