Skip to main content
A payment link is a short-lived URL that points at AlgoVoi’s hosted-checkout page. Send the URL to a customer (in an invoice, a chat message, an email) and they pay through the standard wallet flow on the page.
  • Email invoicing: a Xero or QuickBooks invoice with a “pay in USDC” URL
  • Chat-bot replies: a Telegram or Discord bot that replies to pay £5 with a URL
  • Phone-to-phone: shopkeeper generates the URL, customer scans the QR
  • Anywhere x402 is too low-level: you want a hosted checkout page with QR rendering, not a 402 response that the customer’s tooling has to handle
For agent payments, x402 and MPP are the right shape. Payment links are for human consumers.

​
Lifecycle

Once paid, the link is locked. No further state transitions. The payment_ledger_id column points at the on-chain transaction record.
Response:
The cancel_secret is the only way to cancel the link before payment. Hold it server-side.

​
TTL and expiry

Default expiry is 30 minutes from creation. Maximum is 7 days. After expiry the link’s status flips to expired and the page returns “this checkout has expired”.

​
Cancellation

Once paid, cancellation is rejected.

​
Bot integration metadata

When a payment link is created by a chat bot, the link record carries metadata that lets the bot reply to the right conversation when the payment confirms:
  • tweet_id for X / Twitter bot payments
  • confirmation_tweet_id once the bot has posted the “payment confirmed” reply
  • telegram_chat_id for Telegram bot payments
  • telegram_confirmed boolean, flipped to true once the reply has been sent
These are written by the bot adapters and consumed by the same adapter’s reply path.

​
See also

  • Quickstart walks through creating your first link
  • Outbound webhooks for the event your backend receives on payment confirmation
  • x402 for the agent-equivalent flow