Ran across an issue, where i (a PSP) was trying to make a test payment via a payment page our merchants display to their customers.
The deal get's approved, but the name of the merchant in the wallet (iOS app) is "my" merchant name, and the domain is the one related to this merchantID.
My question is --- can i use an on-boarded Merchant's certificate (that i registered with the relevant API), to start an ApplePaySession in a safari browser, when the MerchantID/domain is theirs, but the client is in my (PSP) page?
Meaning - I'm a PSP serving the buyer a unique payment page (i.e "https://psp.com/paymentPage?unique=123456"), and this page is for payment to my Merchant, that i registered in my developer acc. with certificate and domain (i.e "https://myMerchant.com").
Will this cause issues when i try to start in safari an ApplePaySession, with that MerchantID, but in my PSP domain?
And if this is a problem - how do i (as a PSP) ensure the deal is shown as related to the actual Merchant in the buyer's transaction record in their Apple wallet app ?...