You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We recently started to update the libraries to use Checkout v72 and it looks like by the time we updated the node library, the spec used for generation didn't have the PATCH-related models included.
We are currently reviewing changes from other libraries and we will catch-up with pending changes here.
Apologies for the inconvenience, we will keep the thread posted once we have updates to share
Somehow I figured that session PATCH will be added later but thought that payable attribute should be suppported because that's a part of existing endpoint. Not a problem for us, we can wait for the library to be fully updated to conform to Checkout v72 API.
I've checked the PR briefly and it only adds possibility to PATCH session with the payable attribute.
What I was looking for is having payable attribute on a POST session request(CreateCheckoutSessionRequest) - and I don't see that being implemented in the PR you've referenced.
payable is set to true (in the PATCH) to finalise the payment information before heading to the Checkout, I am not sure it plays a role during the creation of the session. Please let me know what you think. Thank you.
According to Adyen docs - it does play a role. I'm not sure what the default is, assuming it's true since doc explicitly guides to set payable=false to support updating amount.
I see that v32.1.0 was released supporting PaymentsApi.updateSession API(which is great 👍) but no payable attribute for PaymentsApi.sessions.
Assuming still waits for OpenAPI spec update from Checkout team.
Is there any ETA on this? We'd really like to take advantage of this feature but are currently blocked by the lack of the payable option in the POST request.
@zevada we are getting the specs fixed internally and soon they will be published. Once they are updated, we can prioritize patching the node library. We will keep this thread updated with the latests changes.
Activity
jeandersonbc commentedon Aug 13, 2026
Hey @AndrewBoklashko, thanks for reporting this. Since you are referring to "Update session amount" It seems that the fix for what you reported should land after this PR gets merged: https://github.com/Adyen/adyen-node-api-library/pull/1735/changes#diff-683720aab7617a53dd13218fe16e2f651707feee7546e6e8693f4adc49a74dfb
We recently started to update the libraries to use Checkout v72 and it looks like by the time we updated the node library, the spec used for generation didn't have the PATCH-related models included.
We are currently reviewing changes from other libraries and we will catch-up with pending changes here.
Apologies for the inconvenience, we will keep the thread posted once we have updates to share
AndrewBoklashko commentedon Aug 17, 2026
Thanks for the update @jeandersonbc
Somehow I figured that session PATCH will be added later but thought that
payableattribute should be suppported because that's a part of existing endpoint. Not a problem for us, we can wait for the library to be fully updated to conform to Checkout v72 API.gcatanese commentedon Aug 24, 2026
It is fixed by #1735
AndrewBoklashko commentedon Aug 24, 2026
@gcatanese we sure about it?
I've checked the PR briefly and it only adds possibility to PATCH session with the
payableattribute.What I was looking for is having
payableattribute on a POST session request(CreateCheckoutSessionRequest) - and I don't see that being implemented in the PR you've referenced.Or am I just missing something?
gcatanese commentedon Aug 25, 2026
Hey @AndrewBoklashko, I see that
payableis not supported in the POST /sessions. What is your use case exactly?payableis set to true (in the PATCH) to finalise the payment information before heading to the Checkout, I am not sure it plays a role during the creation of the session. Please let me know what you think. Thank you.AndrewBoklashko commentedon Aug 25, 2026
According to Adyen docs - it does play a role. I'm not sure what the default is, assuming it's
truesince doc explicitly guides to setpayable=falseto support updating amount.See https://docs.adyen.com/online-payments/build-your-integration/sessions-flow?platform=Web&integration=Components&version=6.31.1#create-payment-session
gcatanese commentedon Aug 25, 2026
You are correct, I am asking Checkout team to clarify. It looks like the OpenAPI spec is missing the attribute in case of
/sessionsPOST.AndrewBoklashko commentedon Sep 4, 2026
Any updates here?
I see that
v32.1.0was released supportingPaymentsApi.updateSessionAPI(which is great 👍) but nopayableattribute forPaymentsApi.sessions.Assuming still waits for OpenAPI spec update from Checkout team.
gcatanese commentedon Sep 7, 2026
@AndrewBoklashko Yes, the team hasn't been able to update the OpenAPI contract yet. I have reached out again.
zevada commentedon Sep 15, 2026
Is there any ETA on this? We'd really like to take advantage of this feature but are currently blocked by the lack of the payable option in the POST request.
jeandersonbc commentedon Sep 18, 2026
@zevada we are getting the specs fixed internally and soon they will be published. Once they are updated, we can prioritize patching the node library. We will keep this thread updated with the latests changes.
poojah-adyen commentedon Oct 7, 2026
@zevada the fix is available in the latest release
https://github.com/Adyen/adyen-dotnet-api-library/releases/tag/v36.1.0