04 · In a link

A payment URL is sometimes all you need.

Tokenized links shareable by DM, email, or printed as a QR sticker. Or Request to Pay — a push notification straight to the payer's banking app.

ChannelsURL · QR sticker · pain.013 push
SurfaceAny device with a browser or banking app
UseInvoices, deposits, RtP, donations
StatusLive · creator in Portal + API

Two flavors, one underlying rail.

Payment Links and Request to Pay are sister features for cases where the merchant and buyer are not face-to-face and a full checkout page is overkill.

Payment Links are tokenized URLs. The merchant creates one (in the Portal or via API), sets an amount and a description, and shares the link by any channel — email, SMS, printed as a QR on a coffee-shop sticker. The buyer opens the link in any browser and pays in seconds.

Request to Pay (RtP) goes one level deeper. Instead of a URL, the merchant pushes a payment request directly to the buyer's banking app (ISO 20022 pain.013). The buyer sees a notification, taps Approve, done. No URL to open, no app to switch, no QR to scan. Same rail, settled in seconds.

How it works.

From the cashier's tap to the merchant's bank account.

1
Create the link or RtP
In the Merchant Portal, fill amount and description. Or hit POST /links. Or POST /rtp with the buyer's IBAN.
2
Share it
For links — copy the URL, share via any channel. Or print as a QR sticker. For RtP — the buyer gets a push notification automatically.
3
Buyer pays
Opens the link in any browser, or taps Approve in their bank notification. Biometric confirmation.
4
Settled in seconds
Funds land in the merchant's account. Webhook fires with signed payment proof.
5
Link expires automatically
One-time use by default. Configurable for multi-use (donations, recurring monthly).

For everywhere a full checkout is too much.

Links are the right primitive when the buyer arrives from outside the merchant's funnel.

Invoices

B2B and B2C. Send the invoice as a PDF with a Pay link at the top — paid before it hits the inbox.

Deposits & bookings

Hotel reservations, salon bookings, workshop sign-ups. Share a link, get the deposit.

Static QR stickers

Coffee shop counter, parking meter, donation box. One sticker, unlimited buyers.

Personal IBAN replacement

Freelancers stop sharing IBANs by DM. One persistent link instead.

Group fundraisers

Office collections, community causes. One link, many payers, automatic reconciliation.

RtP for subscriptions

Monthly push request, buyer approves once per cycle in their bank app — no card on file.

What's in the box.

Built so the merchant can self-serve and the buyer doesn't have to install anything.

For the merchant

  • Create links from the Portal or via API
  • Tokenized URLs — no IBAN exposed
  • One-time or persistent (your choice)
  • Static QR stickers via the Portal
  • RtP for direct push notifications

For the buyer

  • Open the link in any browser — no app needed
  • Pay from your own banking app
  • For RtP — tap Approve in the bank notification, no link to open
  • Receipt by email + bank statement
  • Refunds initiated by the merchant

"A URL is a checkout that needs no website."

Try it, or build with it.

If you sell — start with the User Guide. If you build — go straight to the integration docs.