Cybersource Developer Community Cybersource Developer Community

maninder · 06-04-2019

Hi,SHA-512 hash mismatch when we enter non-ascii characters in the hosted payment page fields such as Firstname, lastname and address.Example from Sandbox testing:Tested with following card information: Card number: 4111111111111111 Expiry:1222 CVV: ...

maninder · 05-13-2019

Hi,We upgraded our integration to support SHA512 hash and we noticed that the non-ASCII characters entered by the customers on the hosted payment page are not being posted back to us in proper UTF-8 encoding. This causes a mismatch between the hash g...

maninder · 06-10-2019

@jhoven Thank you very much for the information.We are using SIM integration and as we have no control over users input, we have to wait for Auth.net to fix it. Is there any escalation case number they provided, in case we want to call them to get an...

maninder · 06-10-2019

@jhoven I tried calling the support but they are of no help. Let me know if you can find something.

maninder · 06-06-2019

@Renaissance It will be great to see how you are handling the non-ascii characters. Will it be able to handle single quote ’ ? @RichardH Can you also give your input on how Auth.net suggest to handle the non-ascii characters in the response so we can...

maninder · 06-05-2019

@Renaissance I never see Lithuanian I with an accented bottom being entered.

maninder · 06-05-2019

@RichardH We are setting testmode in the request. We having the exact same issue in production as well. All of our clients are affected.As @Renaissance mentioned, it is entirely an encoding issue. We need to know how to handle the non-Ascii character...

Cybersource Developer Community Cybersource Developer Community

Your latest statistics

User Activity

Sha-512 hash mismatch

URGENT - PRODUCTION TRANSACTIONS FAILING BECAUSE OF HASH MISMATCH.

Re: Sha-512 hash mismatch

Re: Sha-512 hash mismatch

Re: Sha-512 hash mismatch

Re: Sha-512 hash mismatch

Re: Sha-512 hash mismatch