The payment window

A payment link opens our payment window, a page on pay.gjold.com where the payer pays for one order. It asks for payment details and nothing else.

What the payer sees

The window shows your shop's name and logo, the amount, and the payment methods that you have: a card form, Apple Pay on devices that support it, and MobilePay. It shows nothing else of the order, such as its items, and asks for nothing but the payment. Anything else that you need, such as the payer's email address, belongs in your checkout, before the payer gets here.

The window is in Danish, English, Norwegian, or Swedish: the language that the link asks for, or else the best match for the payer's browser.

Paying

1. The payer chooses a payment method, and enters their card details or opens Apple Pay or MobilePay.
2. If the payer's bank asks for it, the window sends them to 3-D Secure: the bank's own page, which may hand over to the bank's app. With MobilePay, the payer approves the payment in the MobilePay app instead.
3. The bank authorizes the payment, or declines it.

A declined payment shows the reason in the window, in the payer's language, and the payer can try again, with the same card or another, as many times as they like until the link expires. You hear of a payment only once it succeeds: a decline is between the payer and their bank.

When the payment succeeds, the window sends the payer to your shop's success page, or shows a confirmation of its own if the link has none.

A link is for one payment

The window keeps the link's state on our servers, so the payer can reload the page, go back, or move to another device, and pick up where they were. A link can be paid only once, and for its whole amount, so the payer can't pay twice by opening it twice.

The URL carries no payment data, and the window shows nothing of the payer, so a link that is shared or leaked tells no one anything about them. But anyone who has it can pay it, which is why its address is a long random string.

Card details stay with us

The payer types their card details into our window only, never into your site, so your systems never see a card number. That is what keeps a shop that uses payment links out of most of PCI DSS.

From an app

An app opens the payment window in the system's browser view, where Apple Pay, 3-D Secure, and the switch to MobilePay or a banking app work as they do in the browser. The implementation note on the payment window says how, and what to avoid.