Apple Pay fails with "Payment Not Completed" message before receiving delegate callbacks

Originator:jflinter11
Number:rdar://19978702 Date Originated:26-Feb-2015 04:39 PM
Status:Resolved Resolved:25-Mar-2015 03:24 PM
Product:iOS SDK Product Version:8
Classification:Other Bug Reproducible:Sometimes
 
This has been resolved by Apple as an intermittent server issue, which they claim to have fixed around 3/4/15.

Summary:
When paying with Apple Pay in an app, after authorizing the payment with Touch ID, occasionally the payment will fail with a “Payment Not Completed” message (similar to the effect that occurs when one calls the completion handler in paymentAuthorizationViewController:didAuthorizePayment:completion with PKPaymentAuthorizationStatusFailure). When this error occurs, the PKPaymentAuthorizationViewControllerDelegate doesn’t receive any callbacks (in other words, the error appears internal to Apple Pay and unrelated to the application code). This error appears to occur intermittently for some cards and persistently for others. Removing and re-adding the card seems to temporarily fix the issue. At Stripe, we’ve observed this error in several different apps (including ones not using Stripe).

Steps to Reproduce:
In an app that supports Apple Pay, begin a payment and use Touch ID to authorize a purchase.

Expected Results:
The PKPaymentAuthorizationViewController’s delegate receives the “paymentAuthorizationViewController:didAuthorizePayment:completion” callback, and upon calling completion(PKPaymentAuthorizationStatusSuccess), the PKPaymentAuthorizationViewController displays a success animation.

Actual Results:
The PKPaymentAuthorizationViewController displays a failure animation, and calls no methods on its delegate.

Regression:
The error is intermittent, but we’ve reproduced it with a Visa credit card on an iPhone 6. We first started seeing it/receiving error reports from our customers on February 24, 2015.

Notes:
As mentioned previously, removing the card from Apple Pay and re-adding it appears to temporarily solve the issue (although after doing this, we saw the same issue a few hours later).

Comments


Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!