Payments card unmasking not working in sandbox |
|||||
Issue descriptionChrome Version: Stable 58.0.3029.110 OS: Linux, Windows, unknown if others Environment: Sandbox only; prod works at top-of-tree What steps will reproduce the problem? (1) Turn on both the Google Payments sandbox and Chrome Sync sandbox flags (2) Log out and back in to Chrome so that sandbox cards from payments.sandbox.google.com are synced to Chrome (3) Try to unmask one of them; any CVC should work on sandbox What is the expected result? The full card pan is unmasked and autofilled What happens instead? The RPC from Payments appears to report success, but Chrome replies with the "unable to confirm your card at this time" error.
,
May 25 2017
https://dump-truck.appspot.com/. It's worked regularly before but I don't know how long ago that was.
,
May 25 2017
I am getting an error message on the client when I unmask:
[3019:3019:0525/105105.227613:ERROR:payments_client.cc(515)] Got data: {"error":{"code":"NOT_FOUND","user_error_message":"An unexpected error has occurred. Please try again later."}}
,
May 25 2017
I see your error in the logs too, Sashi. Roger's and my attempts worked fine on the Payments backend, though. The error was that your card wasn't found--could it be you were trying to unmask a prod card with the sandbox flags on, causing an environment mismatch?
,
May 25 2017
Updated description: rogerm@ confirmed this also appears in current stable.
,
May 25 2017
Got this error after making sure it is the same card on my client and sandbox server. FWIW, this is the same error I have always got when unmasking in sandbox.
[8700:8700:0525/113236.618232:ERROR:payments_client.cc(515)] Got data: <!DOCTYPE html>
<html lang=en>
<meta charset=utf-8>
<meta name=viewport content="initial-scale=1, minimum-scale=1, width=device-width">
<title>Error 502 (Server Error)!!1</title>
<style>
*{margin:0;padding:0}html,code{font:15px/22px arial,sans-serif}html{background:#fff;color:#222;padding:15px}body{margin:7% auto 0;max-width:390px;min-height:180px;padding:30px 0 15px}* > body{background:url(//www.google.com/images/errors/robot.png) 100% 5px no-repeat;padding-right:205px}p{margin:11px 0 22px;overflow:hidden}ins{color:#777;text-decoration:none}a img{border:0}@media screen and (max-width:772px){body{background:none;margin-top:0;max-width:none;padding-right:0}}#logo{background:url(//www.google.com/images/branding/googlelogo/1x/googlelogo_color_150x54dp.png) no-repeat;margin-left:-5px}@media only screen and (min-resolution:192dpi){#logo{background:url(//www.google.com/images/branding/googlelogo/2x/googlelogo_color_150x54dp.png) no-repeat 0% 0%/100% 100%;-moz-border-image:url(//www.google.com/images/branding/googlelogo/2x/googlelogo_color_150x54dp.png) 0}}@media only screen and (-webkit-min-device-pixel-ratio:2){#logo{background:url(//www.google.com/images/branding/googlelogo/2x/googlelogo_color_150x54dp.png) no-repeat;-webkit-background-size:100% 100%}}#logo{display:inline-block;height:54px;width:150px}
</style>
<a href=//www.google.com/><span id=logo aria-label=Google></span></a>
<p><b>502.</b> <ins>That’s an error.</ins>
<p>The server encountered a temporary error and could not complete your request.<p>Please try again in 30 seconds. <ins>That’s all we know.</ins>
,
May 25 2017
Your Payments-side call was a success this time. I'm getting the impression Payments sandbox is blocking the return RPC somehow...
,
May 25 2017
,
May 25 2017
Update: Looks like a permissions issue somewhere on Payments' end, we're looking into it
,
May 25 2017
There was a whitelist that needed updating after https://codereview.chromium.org/2675883005/ that got missed. This issue is now fixed regardless of Chrome version.
,
Jun 27 2017
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by rouslan@chromium.org
, May 25 2017