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?