Create a payment link
Creates a payment link to our hosted payment form where shoppers 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.
Header Parameters
A unique identifier for the message with a maximum of 64 characters (we recommend a UUID).
Request Parameters
List of payment methods to be presented to the shopper. To refer to payment methods, use their payment method type.
Example: "allowedPaymentMethods":["ideal","giropay"]
Information about your application. For more details, see Building Adyen solutions.
List of payment methods to be hidden from the shopper. To refer to payment methods, use their payment method type.
Example: "blockedPaymentMethods":["ideal","giropay"]
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.
Price and product information about the purchased items, to be included on the invoice sent to the shopper. This parameter is required for open invoice (buy now, pay later) payment methods such Afterpay, Clearpay, Klarna, RatePay, Riverty, and Zip.
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.
Dictates the behavior of how a potential chargeback should be booked when using Adyen Platforms.
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.
List of fields that the shopper has to provide on the payment page before completing the payment. For more information, refer to Provide shopper information.
Possible values:
- billingAddress – The address where to send the invoice.
- deliveryAddress – The address where the purchased goods should be delivered.
- shopperEmail – The shopper's email address.
- shopperName – The shopper's full name.
- telephoneNumber – The shopper's phone number.
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.
The shopper's full name. This object is required for some payment methods such as AfterPay, Klarna, or if you're enrolled in the PayPal Seller Protection program.
Your reference to uniquely identify this shopper, for example user ID or account ID. Minimum length: 3 characters.
Your reference must not include personally identifiable information (PII), for example name or email address.
Set to false to hide the button that lets the shopper remove a stored payment method.
An array of objects specifying how to split a payment when using Adyen for Platforms, Classic Platforms integration, or Issuing.
The physical store, for which this payment is processed.
Indicates if the details of the payment method will be stored for the shopper. Possible values:
- disabled – No details will be stored (default).
- askForConsent – If the
shopperReferenceis provided, the UI lets the shopper choose if they want their payment details to be stored. - enabled – If the
shopperReferenceis provided, the details will be stored without asking the shopper for consent. When set to askForConsent or enabled, you must also include therecurringProcessingModelparameter.
The shopper's telephone number.
A theme to customize the appearance of the payment page. If not specified, the payment page is rendered according to the theme set as default in your Customer Area.
The cardholder phone number need to be part of the authentication message for payment data. It is a requirement for Visa Secure Authentication Data Field Mandate effective August 2024.
Response parameters
After submitting a call, you receive a response message to inform you that your request was received and processed.
Depending on the HTTP status code of the response message, it is helpful to build some logic to handle any errors that a request or the system may return.