-
Notifications
You must be signed in to change notification settings - Fork 113
New issue
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
Click to pay for advanced(manual) flow. #1045
Comments
Hi @EvgeniyKulago! Thank you for creating this Git issue, it will make sharing updates easier. As I mentioned earlier, I've contacted the API owners, and I'll get back to you as soon as I have any updates. Kind Regards, Djoyke |
Hi @EvgeniyKulago, Apologies for the late response here, but I just wanted to let you know that the respective fields have been added to the library and are released. Best, Jilling |
This issue has been automatically marked as stale due to inactivity and will be closed in 7 days if no further activity occurs. |
@jillingk Does that mean that everything needed for Click to pay advanced flow is provided now, or are there more changes coming? |
Hi @jonekdahl, These fields were added by our respective click to pay team so I think it's fair to assume everything required for this flow is there! Best, Jilling |
This issue has been automatically marked as stale due to inactivity and will be closed in 7 days if no further activity occurs. |
Hello. Could you please include click to pay type into Adyen.Model.Checkout.CardDetails
example:
///
/// Enum Click to Pay for value: clicktopay.
///
[EnumMember(Value = "clicktopay")]
ClickToPay = 6,
Originally posted by @EvgeniyKulago in #1044 (comment)
I've tested click to pay type by including Adyen Sdk project into my solution directly and modifying CardDetails.Type with new click to pay type. Adyen Payment endpoint returns 200 for 'clicktopay' type with redirect action in result. It also works for card type but it's hard to deserialize payment method model from Adyen UI because there is no click to pay type.
The text was updated successfully, but these errors were encountered: