Posts

Post marked as solved
1.2k Views

Apple Pay onlinePaymentCryptogram missing from token

Hello,We are currently trying to implement Apple Pay on the Web. We have everything set up according to the documentation and guides. We are currently using WebSphere Commerce with Cybersource as the payment gateway.We have been able to successfully process a payment token that uses a Visa test card. However, we are noticing issues with the other card types (MasterCard, Amex, Discover). We are using Cybersource Decryption method. Per our contact with Cybersource, when they decrypt any of the three cards mentioned prior, they are discovering that onlinePaymentCryptogram field is missing in the JSON from the payment token. This blocks further decrypting the token and we are unable to process those card types.We have tried using the test credit cards that Apple provides and also the ones that Cybersource provides and have the same outcome for both. Could this be an issue where Apple is sending incorrect information or the payment token is set up incorrectly before it gets sent to our server for processing? Are there any known differences between card types in respect to the payment token setup? Is there a certain way to decrypt the payment token based on which card type that it is?We are currently based in US and in sandbox mode for testing.If there is any other information that is needed to diagnose, I will happily supply.Thanks!
Asked
by kkachin.
Last updated .
Post marked as unsolved
89 Views

ApplePay not working on iOS 14+

We have apple pay on the web within our ecommerce site. We have identified that devices with iOS 14+ are not able to complete the merchant verification process. The user clicks the apple pay button, the payment sheet pops up and immediately shows payment cannot be completed and goes away. However, when using any device that is lower than iOS 14 (verified on 13.6.1 and 12.4.9) we are able to see that the payment sheet stays and allows the user to place an order. Has there been any changes on Apple's end? Perhaps requiring us to send more/different parameters along with the request for merchant verification? Thanks, Kyle
Asked
by kkachin.
Last updated .