Post

Replies

Boosts

Views

Activity

Comment on Error during In-App Provisioning (eligibility step, PKErrorHTTPResponseStatusCodeKey=500)
@DTS Engineer Thank you so much for your reply. Could you please share the nonce that was initially provided to the "add payment pass request", as well as the nonce included in the encrypted card data? Our provider insists that everything is functioning correctly on their side, so we’d like to review and compare the logs from all parties to better understand where the discrepancy might have occurred. Would it be possible for you to provide this information?
Mar ’26
Comment on Error during In-App Provisioning (eligibility step, PKErrorHTTPResponseStatusCodeKey=500)
Thank you so much for your reply. Could you please share the nonce that was initially provided to the "add payment pass request", as well as the nonce included in the encrypted card data? Our provider insists that everything is functioning correctly on their side, so we’d like to review and compare the logs from all parties to better understand where the discrepancy might have occurred. Would it be possible for you to provide this information?
Mar ’26
Comment on Error during In-App Provisioning (eligibility step, PKErrorHTTPResponseStatusCodeKey=500)
Thank you very much for your response. Could you please share the nonce that was initially provided to the "add payment pass request", as well as the nonce included in the encrypted card data? Our provider insists that everything is functioning correctly on their side, so we’d like to review and compare the logs from all parties to better understand where the discrepancy might have occurred. Would it be possible for you to provide this information?
Mar ’26
Comment on Error during In-App Provisioning (eligibility step, PKErrorHTTPResponseStatusCodeKey=500)
Hi , Thank you for sharing this. If you manage to resolve it, please share the solution here as well; it would be very helpful.
Replies
Boosts
Views
Activity
Mar ’26
Comment on Error during In-App Provisioning (eligibility step, PKErrorHTTPResponseStatusCodeKey=500)
Hi @csdevfr, Thank you for sharing this. If you manage to resolve it, please share the solution here as well; it would be very helpful.
Replies
Boosts
Views
Activity
Mar ’26
Comment on Error during In-App Provisioning (eligibility step, PKErrorHTTPResponseStatusCodeKey=500)
@DTS Engineer Thank you so much for your reply. Could you please share the nonce that was initially provided to the "add payment pass request", as well as the nonce included in the encrypted card data? Our provider insists that everything is functioning correctly on their side, so we’d like to review and compare the logs from all parties to better understand where the discrepancy might have occurred. Would it be possible for you to provide this information?
Replies
Boosts
Views
Activity
Mar ’26
Comment on Error during In-App Provisioning (eligibility step, PKErrorHTTPResponseStatusCodeKey=500)
Thank you so much for your reply. Could you please share the nonce that was initially provided to the "add payment pass request", as well as the nonce included in the encrypted card data? Our provider insists that everything is functioning correctly on their side, so we’d like to review and compare the logs from all parties to better understand where the discrepancy might have occurred. Would it be possible for you to provide this information?
Replies
Boosts
Views
Activity
Mar ’26
Comment on Error during In-App Provisioning (eligibility step, PKErrorHTTPResponseStatusCodeKey=500)
Thank you very much for your response. Could you please share the nonce that was initially provided to the "add payment pass request", as well as the nonce included in the encrypted card data? Our provider insists that everything is functioning correctly on their side, so we’d like to review and compare the logs from all parties to better understand where the discrepancy might have occurred. Would it be possible for you to provide this information?
Replies
Boosts
Views
Activity
Mar ’26