Please Log in or Create an account to join the conversation.
It's due to the hash check failing, which failed due to not supplying the hash in your gateway settings. Supplying the hash should resolve this for future purchases.I realized I did not have an MD5 hash set in Authorize.net nor the gateway setting in CBSubs, so I hope that fixes the first issue, but please advise if it's something else. If this is required input to avoid the error/notification perhaps the field in the gateway settings should be mandatory?
It maybe retries since the hash check has been failing. You'll need to review the details of the notification see what exactly is happening. It's possible the payment went through, but CBSubs rejected it due to the hash check. You'll need to check your received payments to be sure.I'm not sure what the cause for #2 is. Authorize.net says that Error 11 is the result of a duplicate transaction being submitted . Why would that be happening? I assumed users are possibly being click-happy, but it has happened 25 times since Dec. 31, which seems very high.
Please Log in or Create an account to join the conversation.
Note that the MD5 Hash Value can be up to 20 characters long, including upper- and lower-case letters, numbers, spaces, and punctuation. More complex values will be more secure.
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.