We are implementing in-app provisioning in our fintech app; We are reaching out to ask for your help in understanding what is going wrong so we can fix it.
What happens:
User taps “Add to Apple Wallet” → we present PKAddPaymentPassViewController → they tap Next → after a few seconds the flow fails with "Set Up Later" alert.
Device log:
"eligibility request failure",
"Received HTTP 500"
)'; underlyingError: 'Error Domain=PKPaymentWebServiceErrorDomain Code=0 "Unexpected error." UserInfo={PKErrorHTTPResponseStatusCodeKey=500, NSLocalizedDescription=Unexpected error.}'; userInfo: '{
PKErrorHTTPResponseStatusCodeKey = 500;
}'; >
Feedback Assistant ID: FB22176928 (In-App Provisioning issue 500 Internal Server Error)
Hi @andriiboberskyi,
You wrote:
[...] Feedback Assistant ID: FB22176928 (In-App Provisioning issue 500 Internal Server Error)
Thanks for your Feedback ID. It appears you may have resolved this issue already, but just in case you haven't, the most likely causes of the error are:
- Cryptographic payload issue (nonce, encryption key, malformed JSON)
- Card not found in issuer's backend
- Incorrect app data in your PNO pass metadata configuration (bundle ID mismatch, missing certificate)
- Nonce/session management problem (expiry, timing)
- Geographic/regional restriction
Please see the page below for more info:
Apple Pay on the Web Demo: In-App Provisioning
https://applepaydemo.apple.com/in-app-provisioning#5.4
If you haven't resolved this issue yet, please contact your PNO to verify your configuration and cryptographic setup.
Cheers,
Paris X Pinkney | WWDR | DTS Engineer
