Do I need a website to use payment links?

No. The link is the checkout. Businesses that sell by message, phone, or in person often never build one, and the payments reconcile exactly like integrated ones.

Can one link take more than one payment?

Yes — a link can be single-use or left collecting. A workshop seat or a recurring service is often sold from one link that takes many payments, each producing its own order and receipt.

What happens when a link expires?

It says so. Links expire after 30 days by default, and an expired link shows a clear message rather than failing in a way the customer has to interpret or report back to you.

Can I brand the page a link points at?

Yes — it's the same hosted checkout, so your logo, colors, typeface, and corner style apply, and it can run on your own domain.

/// Method · Flexible

Take a payment without building anything.

A payment link is the whole checkout behind a URL: create it in the back office with an amount and a description, send it however you already talk to the customer, and the payment lands in the same place as everything else. No integration, no developer, and no website required — which makes it the fastest way to take a first real payment.

See Protocore Gateway All payment methods

Lines of code

Any

Method behind the link

30d

Default expiry

EUR

Same payout as the rest

/// How it runs

Link to paid, four steps.

[ 01 ]
CREATE
Set an amount and a description in the back office — single-use or collecting.
[ 02 ]
SEND
Share the URL by e-mail, message, or QR — wherever you already reach the customer.
[ 03 ]
PAY
They land on the same hosted checkout, with every method you have switched on.
[ 04 ]
TRACK
The link's row shows its status and payment count; the payout is the usual one.

/// 01

What it's actually used for

Invoices a customer can pay in one click, deposits taken over the phone, a service booked by message, a market stall taking payment by QR, and the first payment a new business ever takes. It's also the fastest way to test whether customers will pay at all, before anyone builds a checkout around the idea.

[ 01 ]Invoices, deposits, bookings, and phone orders
[ 02 ]QR codes for in-person and printed use
[ 03 ]A first real payment before any integration exists

/// 02

Links with a back office behind them

Links accumulate into a real desk rather than a list of URLs: every link with its amount, status, and payment count, totals for what's been collected this month and paid today, and search across all of it. A link can close after one payment or keep collecting, and expired links say so instead of failing quietly in front of a customer.

[ 01 ]Single-use or multi-use, with a default 30-day expiry
[ 02 ]Per-link status, amount, and payment count
[ 03 ]Collected-this-month and paid-today totals on the same screen

/// 03

What it takes to switch on

Nothing — links are available as soon as you have an account, and they present whichever methods you have enabled. When you later add an API integration, the link payments and the API payments land in the same back office against the same model.

/// FAQ

Pay by link — questions merchants ask.

No. The link is the checkout. Businesses that sell by message, phone, or in person often never build one, and the payments reconcile exactly like integrated ones.
Yes — a link can be single-use or left collecting. A workshop seat or a recurring service is often sold from one link that takes many payments, each producing its own order and receipt.
It says so. Links expire after 30 days by default, and an expired link shows a clear message rather than failing in a way the customer has to interpret or report back to you.
Yes — it's the same hosted checkout, so your logo, colors, typeface, and corner style apply, and it can run on your own domain.