This page contains the release notes for Pay by Link, Checkout API, and Drop-in/Components for web, iOS, Android, React Native, and Flutter starting from 2020.
Release notes
Learn about the latest updates to our API, and Drop-in/Components for web, iOS, and Android.
This API version is supported by our Java, NodeJS, PHP, Python, Ruby, Go, and .NET libraries.
You can find all the Adyen libraries on GitHub.
- POST
/paymentMethods
- The
details
array has been removed. - The list of issuers for payment methods like iDEAL or Dotpay, is now in the
paymentMethods.issuers
array. - For cards, if the
paymentMethods.brands
array has a single element, the value of thepaymentMethods.name
is now the brand name of the available card brand, instead of Credit Card.
- The
- POST
/payments
checkoutAttemptId
replacesconversionId
.
- POST
/paymentLinks
amount.value
fields now must be integers. Values like 10.5 now produce a validation error.
- GET
paymentLinks/{linkId}
- New
status
value, paymentPending for payment methods that have a pending state. Previously, such states had the completed status.
- New
- For payment link resources,
storePaymentMethodMode
replacesstorePaymentMethod
from previous versions. The allowed values forstoredPaymentMethodMode
are:- disabled (default), the shopper's payment details are not stored.
- enabled and
shopperReference
is provided, the shopper's payment details are stored. - askForConsent, the shopper can choose in the Pay by Link UI if they want their payment details to be stored.
- POST /sessions: creates a payment session for Web Drop-in and Web Components integrations.
- POST
/paymentMethods
- For payment methods with issuer lists, each issuer object now has a
disabled
field indicating if the issuer is available.
- For payment methods with issuer lists, each issuer object now has a
- POST
/payments
- Responses with
action.type
: qrCode now contain theexpiresAt
field which has the expiry date in ISO8601 format. - In your request, you can now send all the fields from the EMV 3D Secure 2.1.0 specification.
mpiData.tokenAuthenticationVerificationValue
- Responses with
- POST
/orders
- The initial amount of the order is always returned in the
amount
object.
- The initial amount of the order is always returned in the
- POST
/paymentLinks
- Fixed an issue where the payments page didn't show a phone number field when configured as part of
requiredShopperFields
.
- Fixed an issue where the payments page didn't show a phone number field when configured as part of
- POST
/payments
and POST/donations
requests:
- POST
/payments
- All address fields are now optional.