Get Multi-Link
OpenAPI SpecTest this endpoint live
Open the same request directly in API Explorer.
Server URL
Retrieves one multi-link belonging to the authenticated merchant, including its reusable checkout URL and QR-code URL.
Authorization
BearerAuth In: header
Path Parameters
The ID of the multi-link.
Header Parameters
Ensures that a request can be safely retried without causing duplicate operations. Typically used for actions like payment creation and operations such as refund and void to prevent accidental double processing.
- If a response is replayed due to using the same key, the response will include the header
Idempotent-Replayed: true. - Idempotency keys are scoped by [Key, Endpoint, HTTP Verb]; the same key on a different endpoint or method will not replay the original response.
- Responses are cached for 24 hours. After that, the cache is cleared, so idempotency is only guaranteed within 24 hours of the initial request.
Response Body
application/json
application/json
application/json
application/json
application/json
Create Multi-Link
Creates a reusable payment link and returns its URL and QR-code URL. Unlike a regular payment link, this endpoint does not create a single payment. Each time a cardholder opens the returned url or scans the QR code, ePay starts a new, independent payment session from the multi-link configuration. This is useful for a reusable checkout QR code - for example, a QR code where the cardholder enters the amount and completes payment with Vipps MobilePay. Configuration omitted from the request is resolved from the point of sale's current configuration when the multi-link is used. Redirect and notification URLs are not inherited; provide them explicitly when they are needed. URL values, including order-line image URLs, must use a domain registered for the selected point of sale.
Deactivate Multi-Link
Deactivates a multi-link so that its public URL and QR code can no longer start new payment sessions. This operation is idempotent: deactivating an already deactivated multi-link succeeds. Existing payment sessions created from the multi-link are not affected.