Post

Replies

Boosts

Views

Activity

Comment on domainName missing from create payment sessions request in sandbox
Our design is for our backend to make the paymentSession call and return the response to the frontend. However, we are doing an exact field mapping while reading the response, which meant the backend errored out validation when it couldn't find domainName in the response. In addition, the "new" fields (like initiativeContext) being returned weren't mapped and hence not sent back to frontend, meaning signature validation later on would have failed as well.
Nov ’25
Comment on domainName missing from create payment sessions request in sandbox
Our design is for our backend to make the paymentSession call and return the response to the frontend. However, we are doing an exact field mapping while reading the response, which meant the backend errored out validation when it couldn't find domainName in the response. In addition, the "new" fields (like initiativeContext) being returned weren't mapped and hence not sent back to frontend, meaning signature validation later on would have failed as well.
Replies
Boosts
Views
Activity
Nov ’25
Comment on domainName missing from create payment sessions request in sandbox
We can see the response format has now reverted back to the "old" format. Until that, ApplePay in our preprod environments was fully down. Would this change happen again? If so, is there a possibility of an announcement or notification so we can be better prepared?
Replies
Boosts
Views
Activity
Nov ’25
Comment on domainName missing from create payment sessions request in sandbox
Understood, thank you! This has been our behaviour for years, but we will change our design as suggested. This change will require some time tho, so I hope the response format doesn't change again soon.
Replies
Boosts
Views
Activity
Nov ’25