Comments (2)
I just tested v71
, the label of the credit card payment method changed in Dutch from "Credit Card" to "Credit en Debit card".
v68
v71
I don't think there are any exciting changes that we need to deal with, according to https://docs.adyen.com/online-payments/release-notes/?integration_type=api&version=71:
Breaking Changes
POST /paymentLinks:
expiresAt
format is now ISO 8601 with a time zone offset indicator (YYYY-MM-DDThh:mm:ss+TZD
). For example, 2020-12-18T10:15:30+01:00. This format is consistent with the other timestamps that we return.Previously, the format included the timezone indicator Z.
For the /payments request to store payment details or make a payment with stored payment details:
You now must include the recurringProcessingModel parameter.For the /sessions request to store payment details:
You now must include the recurringProcessingModel parameter.For the /paymentMethods/balance request to check a gift card balance:
You now must include theamount
parameter.For Pix, the /payments response no longer includes
action.url
. You must useaction.qrCodeData
to render the QR code.POST
/payments
- The
fraudResult.results
list now no longer contains theFraudCheckResult
for each list item. Each list item now only contains the values of the individual risk checks. See code samples.POST
/paymentMethods
- The format of the
expiryYear
returned for stored cards is now the last two digits of the year.Changed
POST /paymentMethods:
- To comply with EU consumer choice regulations, The
name
of the payment method group for cards is now Cards instead of Credit Card. When you use Drop-in with this API version, the payment method list shows this payment method group as Cards.POST /payments:
- When you make a partial payment with a gift card, and the shopper gets redirected for 3D Secure 2 authentication, the return URL includes
redirectResult
instead ofMD
andPaRes
. This aligns with other 3D Secure redirect flows.POST /paymentLinks:
- When you create a payment link through the API, the setting to store payment method details in the Customer Area no longer works. Instead, you have to use the
storePaymentMethodMode
parameter to indicate if the details of the payment method will be stored.metadata
: more than 80 characters will result in a validation error.You must now make a /payments or /sessions request to store payment details. You can no longer configure it from the Customer Area.
For the /sessions request:
- The storePaymentMethod parameter. Use
storePaymentMethodMode
instead.- If the required reference parameter isn't included, you now get a validation error.
For /payments and /sessions requests including line items for custom risk rules:
You can now use thelineItems
parameter instead ofadditionalData.riskdata.basket
.Removed
In the Customer Area, on the Settings > Checkout Settings page:
- Turning on the enableRecurring toggle no longer adds the required parameters to store payment details in payment requests.
- Turning on the enablePayout toggle no longer adds the required parameters to store payment details for payouts.
New
The
/storedPaymentMethods
endpoint:
- Make a GET request to list the stored payment details for a shopper, if there are any available.
- Make a DELETE request to disable stored payment details to stop charging a shopper with the particular recurring detail ID.
For /sessions and
/paymentLinks
requests:
You can now include thestorePaymentMethodMode
parameter to set when to store the shopper's payment details.For the /paymentMethods request:
When you include theshopperReference
parameter, stored payment details in the response now contain thesupportedRecurringProcessingModel
parameter.For specific industries, such as hospitality, you can specify a reason when making a merchant-initiated transaction with stored payment details. In the /payments request, include the
industryUsage
parameter to specify a reason for the payment. Possible values:
- delayedCharge.
- noShow.
- installment.
POST
/sessions
- authenticationData object in the request.
POST
/payments
- authenticationData object in the request.
- paymentMethod object in the reponse.
POST
/payments/details
- authenticationData object in the request.
- paymentMethod object in the reponse.
Fixed
For /payments and /sessions requests to make payments with stored payment details:
When you includeshopperInteraction
: ContAuth andrecurringProcessingModel
: CardOnFile, the transactions now always get processed as CardOnFile payments.If you contacted our Support Team to enable filtering payment methods based on your store, when making a /paymentMethods or /sessions request including store:
The response now includes only payment methods available for the specified store.For /paymentMethods and /sessions requests including allowedPaymentMethods with scheme and card in the array:
The response no longer includes wallet payment methods.Deprecated
Fields related to 3D Secure authentication are now grouped under the new
authenticationData
object. The old 3D Secure authentication fields have been deprecated.
from wp-pronamic-pay-adyen.
Upgraded in 21da986.
from wp-pronamic-pay-adyen.
Related Issues (20)
- Multiple Adyen payments for single Pronamic Pay payment HOT 4
- Backward compatibility from version `3` to `4` HOT 4
- Only display Apple Pay payment method if supported HOT 2
- Add support for recurring payments via Adyen HOT 1
- Update to `adyenAdyen/adyen-web` `v5.27.0` for Swish payment method always triggers an error on mobile HOT 2
- Use `npm` for `Adyen/adyen-web`
- Add MobilePay payment method HOT 1
- API-only payment methods not redirecting to action URL
- Swish missing return parameter `redirectResult` HOT 5
- Improve Adyen drop-in error handling HOT 2
- Adyen ยป Klarna Pay Later ยป "have to be manually captured" HOT 1
- Class does not exist `\Pronamic\WordPress\Pay\Gateways\Adyen\Integration`
- Add feature to customize the Merchant Order Reference HOT 1
- No action after clicking payment button on our Adyen payment page HOT 2
- Problem with Blik payments on Adyen, no `IPv6` support? HOT 11
- Use Adyen's Apple Pay certificate HOT 1
- Update Adyen Web Drop-in from version `3.23.0` to `5.14.0` HOT 1
- API key with `<` `>` characters not saved correctly? HOT 1
- Auto submit versus show pay button HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. ๐๐๐
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google โค๏ธ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from wp-pronamic-pay-adyen.