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!

Accepted Reply

We have found the issue. Here was the solution in case anyone else has the same issue.


The default implementation of Apple Pay in Websphere Commerce suggest to have the merchant capabilities set to 'supportsDebit,supportsCredit,supports3DS,supportsEMV'.


We have found that with our particular payment processor that it did not accept EMV cards. The test cards (MasterCard,Discover,Amex) all defaulted to using EMV when paying with Apple Pay. As soon as we removed supportsEMV from the capabilities, the cards were passed as 3DS and the token could be further decrypted by the payment processor.

Replies

We have found the issue. Here was the solution in case anyone else has the same issue.


The default implementation of Apple Pay in Websphere Commerce suggest to have the merchant capabilities set to 'supportsDebit,supportsCredit,supports3DS,supportsEMV'.


We have found that with our particular payment processor that it did not accept EMV cards. The test cards (MasterCard,Discover,Amex) all defaulted to using EMV when paying with Apple Pay. As soon as we removed supportsEMV from the capabilities, the cards were passed as 3DS and the token could be further decrypted by the payment processor.

thank you very much kkachin

it helped me too
  • Hi Team,

    we had followed this and we had resolved this in test environment and facing issue again on production environment. Please suggest.

Add a Comment