Skip to content
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

Express Checkout - Payment Token Adjustment #616

Closed
angelleye opened this issue Dec 19, 2016 · 8 comments
Closed

Express Checkout - Payment Token Adjustment #616

angelleye opened this issue Dec 19, 2016 · 8 comments
Assignees
Milestone

Comments

@angelleye
Copy link
Collaborator

Our checkout flow for Express Checkout with payment tokens enabled is a little confusing.

Currently, if I have items in the cart and I click to checkout with Express Checkout, we're enabling the billing agreement in the SEC request, which forces this sort of a message at PayPal...

image

When I click Agree and Continue, I'm sent back to the review page where I see the option to save the billing agreement to my account...

image

This seems backwards. If I don't want to save my account details with the site, then I should not have to agree to a billing agreement with PayPal.

If payment tokens are enabled in EC, I think we need to output our "Save PayPal account for future use." option right there next to the EC button on product pages and the cart page. Or maybe underneath it...whatever fits best in most cases. We can have this in its own div, of course, so people can easily move it around if they need to.

This way, the buyer can choose whether or not they want to save the PayPal account to their account prior to ever getting sent to PayPal. If they do NOT choose this, then we would leave the billing agreement parameters out of the SEC request so that they would not have to agree to a billing agreement on the PayPal pages. If they do choose to save it, then we could include the BA parameters as necessary.

Once they get to the review page they won't need a check box to save because they've already done that.

@kcppdevelopers
Copy link
Contributor

I have one question: if user is logged in website and Tokenized Payments Enable in this note how can we handle SEC request parameter?

@angelleye
Copy link
Collaborator Author

Not sure I understand why that would change the flow I outlined above..??

@kcppdevelopers
Copy link
Contributor

In the Express Checkout payment method, if guest checkout is enable then we are not forcing customer to create an account right? If user will not create an account or if user is logged in website, how can we save billing agreement details to account?

@kcppdevelopers
Copy link
Contributor

kcppdevelopers commented Dec 19, 2016

If payment tokens are enabled in EC, I think we need to output our "Save PayPal account for future use." option right there next to the EC button on product pages and the cart page. Or maybe underneath it...whatever fits best in most cases. We can have this in its own div, of course, so people can easily move it around if they need to.

[Regarding "Save PayPal account for future use." option next to the EC button on product pages and the cart page, currentlly we have just URL for Ajax request. so can't pass option value of "Save PayPal account for future use." SEC request. If we want to pass ""Save PayPal account for future use." option value then we need to change that logical part used Form ajax insted to just URL. ]

I think we should not invest much time on this issue, becuase we have already paln to rebuid Express Checkout payment.

Let me know your suggestion.

@angelleye
Copy link
Collaborator Author

Can we set it up so that if they click the option to save their account it would then force them to create an account / login?

@kcppdevelopers
Copy link
Contributor

Yes, we can force them to create an account / login. but option next to the EC button on product pages and the cart page it will take more time. for implementing option next to the EC button on product pages and the cart page we have to used Form ajax, currentlly we have just used url.

@angelleye
Copy link
Collaborator Author

Okay. I guess we can just leave it this way for now so that we can get 1.3.0 released, and then we can improve upon this when we redo EC altogether in 1.4.0.

@kcppdevelopers
Copy link
Contributor

Issue #630

angelleye pushed a commit that referenced this issue Apr 27, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant