Error during In-App Provisioning (eligibility step, PKErrorHTTPResponseStatusCodeKey=500)

Question

Created Mar ’26

Replies 3

Boosts 2

Participants 3

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)

Answered by DTS Engineer in 894521022

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

Answer 1

DTS Engineer OP

Apple

Jun ’26

Recommended

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

Answer 2

andriiboberskyi OP

1w

Hi, @DTS Engineer

In-app provisioning consistently fails at the eligibility step: PKProvisioningErrorDomain Code=5, PKErrorHTTPResponseStatusCodeKey=500 → PKPaymentWebServiceErrorDomain Code=0 "Unexpected error"; internalDebugDescriptions ("eligibility request failure","Received HTTP 500"). Occurs before Terms & Conditions.

From logs (Wallet + Apple Pay profiles active): the eligibility CFNetwork request returns HTTP 500 with a 525-byte body that isn't visible on-device; broker smp-device-content.apple.com; request configuration EV_ECC_V2, paymentNetwork MasterCard.

Key facts:

Manual "Add to Wallet" of the same card works. Our PNO (Mastercard) confirmed in writing that the in-app request never reaches their systems — only manual provisioning is seen, with no inbound request from Apple for in-app. So the 500 appears to be generated within Apple's infrastructure before forwarding to the network. The In-App Provisioning entitlement is enabled on our App ID (com.nebeussolutions.mobile). This points to an allow-list / entitlement / app-authorization issue on Apple's side rather than a cryptographic/PNO payload issue. Full details (device SEID, correlation IDs, sysdiagnose) are in Feedback FB22176928.

Could an Apple engineer review FB22176928 and confirm whether our ADAM ID is on the allow list and the entitlement is fully granted server-side, and provide the server-side reason for the 500?

Answer 3

DTS Engineer OP

Apple

3d

Accepted Answer

Hi @andriiboberskyi,

You wrote:

Could an Apple engineer review FB22176928 and confirm whether our ADAM ID is on the allow list and the entitlement is fully granted server-side, and provide the server-side reason for the 500?

Yes. We have corrected the allowlist to include your Adam ID. Please reattempt your provisioning flow with the app distributed via TestFlight. Once confirmed, please reply to your existing bug report (FB22176928) with the results.

Best,

Paris X Pinkney |  WWDR | DTS Engineer