-
Notifications
You must be signed in to change notification settings - Fork 8
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
Address Consent Token never made available after initial login #63
Comments
@victorahm @acreilly Is this a feature that should be included by default or an optional feature? |
The above is just an idea at how you could give access to the access token, but without it, the gem only returns half the address to the checkout and no names. |
Thanks @prwhitehead I just wanted to get some eyes on it that have some deeper experience with the plugin than myself. |
Hello, As i'm working on a project that involves integrating Amazon Pay this is how I have addressed the issue of incomplete addresses:
The before action checks for a param and redirects back to the action once the cookie is set. This is then available other controller actions to pass around as required. I can put this in a pull request if you would like. |
I don't know if this is something that you decided to leave out of the gem or if the docs have been updated since, but there is no way to get the users full address (including name and address1) because Address Consent Token is never set, or made available to downstream functions after login.
As per the docs here https://pay.amazon.com/us/developer/documentation/lpwa/201953150, the following could be added to the login script:
views/spree/amazon/_login.html.erb
Now the
addressConsentToken
is available as a param to use on the address/delivery step.The text was updated successfully, but these errors were encountered: