Recent strange behavior with the Payments app

Over the past two weeks we have been getting customer feedback that our custom tenders are not completing correctly on a relatively frequent basis. I can't repro this and I'm about 90% sure that it's not a bug in our code, as I haven't touched that area in months, but you never know :]

Has there been any changes to the Payments app over the past couple of weeks that might cause an Activity-launching Tender to not create a Payment when setResult(RESULT_OK, data) is called with just the amount in the data?

Dan

10 |2000

Attachments: Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Jeffrey Blattman ♦♦ commented · Oct 17, 2016 at 11:20 AM

Did the payment get to the server at all?

0 ·

Dan commented · Oct 17, 2016 at 11:22 AM

Hi Jeff, no a payment is not attached to the order at all. So essentially our app closes and the user is looking at the same screen they were when they launched via the tender to begin with

0 ·

Jeffrey Blattman ♦♦ commented · Oct 18, 2016 at 06:55 PM

No we would not have knowingly broken that interface. I looked at the code, and if the result is not ok, or if the amount is null, it silently drops the result and does nothing. Do you keep any sort of audit trail on your said about what responses you return for which order IDs? If so, you could map that back to specific merchant issues.

0 ·

question