We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hello,
We have an issue while using the parameter splitCardFundingSources in the https://checkout-test.adyen.com/v71/paymentMethods endpoint. We're also using the last v16 SDK.
splitCardFundingSources
Here's our code :
new PaymentMethodsRequest([ 'splitCardFundingSources' => true, // with other parameters ]);
The issue :
This exception is throw by this method which use this other method.
This error occurred due to this enum in the OpenAPI schema : https://github.com/Adyen/adyen-openapi/blob/main/json/CheckoutService-v71.json#L9919 and the endpoint return paymentMethod as with credit and debit cards.
credit
debit
Could you take a look at it?
Thanks
The text was updated successfully, but these errors were encountered:
Hi @pgrimaud,
Thanks for reaching out here with this issue. We're looking into it.
Best, Jilling Adyen
Sorry, something went wrong.
Any update?
Our apologies for the wait. We had some other things on our plate but finally got around to fixing it, this fix should be released next week!
Successfully merging a pull request may close this issue.
Hello,
We have an issue while using the parameter
splitCardFundingSources
in the https://checkout-test.adyen.com/v71/paymentMethods endpoint. We're also using the last v16 SDK.Here's our code :
The issue :
This exception is throw by this method which use this other method.
This error occurred due to this enum in the OpenAPI schema : https://github.com/Adyen/adyen-openapi/blob/main/json/CheckoutService-v71.json#L9919 and the endpoint return paymentMethod as with
credit
anddebit
cards.Could you take a look at it?
Thanks
The text was updated successfully, but these errors were encountered: