Hi, We had a very similar issue: Apple Pay In-App Provisioning was failing before the Terms & Conditions screen, and the device logs showed an eligibility step failure with HTTP 500. In our case, the issue was related to the WSD key identifier used in the MBPAC / MBPAD payload. The identifier was configured without the required .1 suffix. After changing it from a value like 123456 to 123456.1, provisioning started working correctly. This may not be the root cause in your case, but it is worth checking the WSD key identifier, key index, and MBPAC / MBPAD payload structure with your backend/payment network configuration.

Update: we found the root cause and the issue is now resolved. In our case, the WSD key identifier was configured incorrectly. The identifier had to include the .1 suffix, but our initial configuration used the value without this suffix. We changed the value in our system from something like 123456 to 123456.1, and Apple Pay In-App Provisioning started working correctly. It looks like Apple validates the MBPAC / MBPAD payload structure during provisioning, so an incorrect WSD key identifier can cause the eligibility step to fail with HTTP 500 before Terms & Conditions.