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
What does it mean to "accept the payment"? #278
Comments
Happy to change this and #273 - this is the language that we've used since the first draft. Do you have suggestions for a more pithy description? |
Sorry @adrianba I missed your question earlier... Pithy? How about "..the user's shipping address after the user has accepted the payment request algorithm." ? It's not pithy, but it has something to link to and is precise. If you are looking for something that scans better than that I might propose "...the user's shipping address upon the user's agreeing to make the payment." Or something like that. After all, what we are saying here is that they user has clicked "okay". |
"...user's shipping address after obtaining the user's consent to pay via the 'user accepts the payment algorithm'."? |
I counted:
Based on that, it seems the sentence in section 11 could be slightly modified to say: "and ultimately the PaymentResponse object with the user's selected shipping Would it similarly make sense in 15.2.1 to change: "This is to ensure that the payment is not accepted" to Ian |
Editors reviewed this and concluded the spec is clear enough as is. |
In the PaymentAddress interface (last paragraph) it says "...the user's shipping address after the user has accepted the payment." I am pretty sure this means "after the user has completed interacting with the PaymentRequest user interface and indicated that they agree to make the payment". Later in the document there is a term "user accepts the payment request algorithm". If that is what is REALLY meant by this phrase, I suggest we turn it and its ilk into a reference to that algorithm. I would also suggest that the name be more pithy.
The text was updated successfully, but these errors were encountered: