-
Notifications
You must be signed in to change notification settings - Fork 135
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
Show example of .complete("unknown") #584
Labels
Comments
Talked to @zkoch, he mentioned 3D Secure can lead to "unknown". |
@marcoscaceres , are you OK to close this issue? |
Was going to add something to the .complete() example. I'll update the bug title to not confuse people. |
marcoscaceres
changed the title
Real use case for .complete("unknown") - or mark "at risk"
Show example of .complete("unknown")
Aug 21, 2017
@marcoscaceres, can we close this issue now? Ian |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As part of #583, we've somewhat struggled to come up with a real use case for completing a payment response with "unknown".
Although "unknown" feels like a good idea, can anyone think of a real use case where:
If we can't come up with something useful, we should probably mark it "at risk".
Also noting that Chrome (on desktop) currently treats
.complete("unknown")
the same as.complete("success")
, in that it just closes the payment sheet and doesn't inform the user about anything.I'm not sure yet what we will do in Firefox. It will depend on the outcome of this discussion, I guess.
In the spec, "unknown" plays no role in any algorithm.
The text was updated successfully, but these errors were encountered: