Hello, I'm following up on this issue because I've now been redirected multiple times between different Apple support channels without reaching anyone who can help resolve the problem. So far I have: Contacted Apple Developer Support. Contacted Apple Business Register (ABR) support. Followed the guidance provided by each team. Been redirected back and forth without identifying the team responsible for enabling or configuring Web Push Provisioning for our verified organization. Our current status: ABR organization is verified. In-App Provisioning is already live in production. We are attempting to enable Web Push Provisioning for the same organization. We have completed the documented prerequisites but are unable to proceed because the required backend configuration appears to be unavailable.

@Lfc Did you find the exact root cause of your error? { statusCode = 500; statusMessage = 'Broker Service Response exception'; } I am getting the same error, and verified my encryption using Test Vectors. Even after decrypting both payloads, one documented encrypted data and the second my encrypted data, I am not finding any issue with encryption, as mentioned. It would be helpful for me if you can explain the exact root cause of this issue. .

@VidhyaSri21 , I have also been facing the same encryption issue as on my Feedback assistant . I got an update from DTS that "The error is due to bad encryption. Please review whether your cryptography matches the expectations outlined in the Getting Started with Apple Pay: In-App Provisioning, Verification, Security, and Wallet Extensions (v4)" guide. I have matched my encryption using test vectors, and the output matches my code's output. Can you guide me, how did you get the exact root cause of your encryption?

Nope! I am still waiting for a reply from Apple.