Payment Links & RtP
Payment Links — reusable tokenized URLs for invoices and social commerce. Request to Pay — pain.013 push to the payer's bank.
Overview
Two distinct flows packaged in one app:
- Payment Links — the merchant generates a tokenized URL with an amount (or open amount) and shares it via DM, email, invoice, QR sticker, Instagram bio. Payer opens the link, pays from their banking app.
- Request to Pay (RtP) — the merchant pushes a
pain.013request directly to the payer's bank. The payer sees an approve/decline prompt in their banking app, no link to click.
Both flows settle through the same instant-payment rail and land in the merchant bank account in seconds.
When to use which
| Use case | Best fit |
|---|---|
| Invoice with link | Payment Link |
| Social commerce (Instagram bio) | Payment Link |
| Delivery-on-payment | RtP (no friction for payer) |
| Subscription billing | RtP (push, scheduled) |
| Static price (sticker on table) | Payment Link with QR encoding |
Creating a Payment Link
POST/links/api/v1/link
{
"amount": 250.00,
"currency": "MDL",
"description": "Invoice #INV-2026-001",
"expiresAt": "2026-06-30T23:59:59Z",
"reusable": false
}
Response: { "linkId": "...", "url": "https://pay.miapos.eu/L/abc...", "qrUrl": "..." }
Sending a Request to Pay
POST/links/api/v1/rtp
{
"payerIban": "MD12AG000000000000000000",
"amount": 75.00,
"currency": "MDL",
"description": "Subscription · June 2026"
}
Payer receives the request in their banking app within 1–2 seconds.