v1
latestOpenAPI 3.1.02026-07-2022194782.1 KBCreate a payment link
Creates a payment link to a Pay by Link page where the shopper can pay. The list of payment methods presented to the shopper depends on the currency and country parameters sent in the request.
For more information, refer to Pay by Link documentation.
Headers
A unique identifier for the message with a maximum of 64 characters (we recommend a UUID).
Request body
List of payment methods to be presented to the shopper. To refer to payment methods, use their payment method type.
Example: "allowedPaymentMethods":["ideal","applepay"]
List of payment methods to be hidden from the shopper. To refer to payment methods, use their payment method type.
Example: "blockedPaymentMethods":["ideal","applepay"]
The shopper's two-letter country code.
The date and time when the purchased goods should be delivered.
ISO 8601 format: YYYY-MM-DDThh:mm:ss+TZD, for example, 2020-12-18T10:15:30+01:00.
A short description visible on the payment page. Maximum length: 280 characters.
The date when the payment link expires.
ISO 8601 format with time zone designator Z: YYYY-MM-DDThh:mm:ss+TZD, for example, 2020-12-18T10:15:30Z.
The maximum expiry date is 70 days after the payment link is created.
If not provided, the payment link expires 24 hours after it was created.
A set of key-value pairs that specifies the installment options available per payment method. The key must be a payment method name in lowercase. For example, card to specify installment options for all cards, or visa or mc. The value must be an object containing the installment options.
Indicates if the payment must be captured manually.
The merchant account identifier for which the payment link is created.
This reference allows linking multiple transactions to each other for reporting purposes (for example, order auth-rate). The reference should be unique per billing cycle.
Metadata consists of entries, each of which includes a key and a value. Limitations:
- Maximum 20 key-value pairs per request. Otherwise, error "177" occurs: "Metadata size exceeds limit"
- Maximum 20 characters per key. Otherwise, error "178" occurs: "Metadata key size exceeds limit"
- A key cannot have the name checkout.linkId. Any value that you provide with this key is going to be replaced by the real payment link ID.
Defines a recurring payment type. Required when storePaymentMethodMode is set to askForConsent or enabled. Possible values:
- Subscription – A transaction for a fixed or variable amount, which follows a fixed schedule.
- CardOnFile – With a card-on-file (CoF) transaction, card details are stored to enable one-click or omnichannel journeys, or simply to streamline the checkout process. Any subscription not following a fixed schedule is also considered a card-on-file transaction.
- UnscheduledCardOnFile – An unscheduled card-on-file (UCoF) transaction is a transaction that occurs on a non-fixed schedule and/or has variable amounts. For example, automatic top-ups when a cardholder's balance drops below a certain amount.
A reference that is used to uniquely identify the payment in future communications about the payment status.
Website URL used for redirection after payment is completed. If provided, a Continue button will be shown on the payment page. If shoppers select the button, they are redirected to the specified URL.
Indicates whether the payment link can be reused for multiple payments. If not provided, this defaults to false which means the link can be used for one successful payment only.
The shopper's email address.
The language to be used in the payment page, specified by a combination of a language and country code. For example, en-US.
For a list of shopper locales that Pay by Link supports, refer to Language and localization.
Your reference to uniquely identify this shopper, for example user ID or account ID. The value is case-sensitive and must be at least three characters.
Your reference must not include personally identifiable information (PII) such as name or email address.
Set to false to hide the button that lets the shopper remove a stored payment method.
The physical store, for which this payment is processed.
Response
Created - the request has succeeded.
List of payment methods to be presented to the shopper. To refer to payment methods, use their payment method type.
Example: "allowedPaymentMethods":["ideal","applepay"]
List of payment methods to be hidden from the shopper. To refer to payment methods, use their payment method type.
Example: "blockedPaymentMethods":["ideal","applepay"]
The shopper's two-letter country code.
The date and time when the purchased goods should be delivered.
ISO 8601 format: YYYY-MM-DDThh:mm:ss+TZD, for example, 2020-12-18T10:15:30+01:00.
A short description visible on the payment page. Maximum length: 280 characters.
The date when the payment link expires.
ISO 8601 format with time zone designator Z: YYYY-MM-DDThh:mm:ss+TZD, for example, 2020-12-18T10:15:30Z.
The maximum expiry date is 70 days after the payment link is created.
If not provided, the payment link expires 24 hours after it was created.
A set of key-value pairs that specifies the installment options available per payment method. The key must be a payment method name in lowercase. For example, card to specify installment options for all cards, or visa or mc. The value must be an object containing the installment options.
Indicates if the payment must be captured manually.
The merchant account identifier for which the payment link is created.
This reference allows linking multiple transactions to each other for reporting purposes (for example, order auth-rate). The reference should be unique per billing cycle.
Metadata consists of entries, each of which includes a key and a value. Limitations:
- Maximum 20 key-value pairs per request. Otherwise, error "177" occurs: "Metadata size exceeds limit"
- Maximum 20 characters per key. Otherwise, error "178" occurs: "Metadata key size exceeds limit"
- A key cannot have the name checkout.linkId. Any value that you provide with this key is going to be replaced by the real payment link ID.
Defines a recurring payment type. Required when storePaymentMethodMode is set to askForConsent or enabled. Possible values:
- Subscription – A transaction for a fixed or variable amount, which follows a fixed schedule.
- CardOnFile – With a card-on-file (CoF) transaction, card details are stored to enable one-click or omnichannel journeys, or simply to streamline the checkout process. Any subscription not following a fixed schedule is also considered a card-on-file transaction.
- UnscheduledCardOnFile – An unscheduled card-on-file (UCoF) transaction is a transaction that occurs on a non-fixed schedule and/or has variable amounts. For example, automatic top-ups when a cardholder's balance drops below a certain amount.
A reference that is used to uniquely identify the payment in future communications about the payment status.
Website URL used for redirection after payment is completed. If provided, a Continue button will be shown on the payment page. If shoppers select the button, they are redirected to the specified URL.
Indicates whether the payment link can be reused for multiple payments. If not provided, this defaults to false which means the link can be used for one successful payment only.
The shopper's email address.
The language to be used in the payment page, specified by a combination of a language and country code. For example, en-US.
For a list of shopper locales that Pay by Link supports, refer to Language and localization.
Your reference to uniquely identify this shopper, for example user ID or account ID. The value is case-sensitive and must be at least three characters.
Your reference must not include personally identifiable information (PII) such as name or email address.
Set to false to hide the button that lets the shopper remove a stored payment method.
Status of the payment link. Possible values:
- active: The link can be used to make payments.
- expired: The expiry date for the payment link has passed. Shoppers can no longer use the link to make payments.
- paid: The shopper completed the payment.
The physical store, for which this payment is processed.
The date when the payment link status was updated.
ISO 8601 format: YYYY-MM-DDThh:mm:ss+TZD, for example, 2020-12-18T10:15:30+01:00.
The URL at which the shopper can complete the payment.