topic Re: SIM Returning Denied Card But Card Is Charged! in Integration and Testing

SIM Returning Denied Card But Card Is Charged!

ShadowDancerLV — Sat, 22 Dec 2012 21:27:50 GMT

I'm using SIM and I get periods where I get denials of credit cards but they're still being charged. Customer's real upset. Why does that happen?

Re: SIM Returning Denied Card But Card Is Charged!

RaynorC1emen7 — Sat, 22 Dec 2012 21:37:25 GMT

can you log into your mechant account and see what happend to the transaction? It is getting charge or just getting credit hold? If all else fail call support with the transactionID.

Re: SIM Returning Denied Card But Card Is Charged!

ShadowDancerLV — Sat, 22 Dec 2012 21:43:53 GMT

Yes there is a charge that has to be voided.

Re: SIM Returning Denied Card But Card Is Charged!

RaynorC1emen7 — Sat, 22 Dec 2012 22:06:51 GMT

So, you have to void it in the merchant account? Do you capture all the data return from authorize.net so you can see why it got decline? are you using relay response?

Re: SIM Returning Denied Card But Card Is Charged!

ShadowDancerLV — Sat, 22 Dec 2012 22:11:34 GMT

Sure do! Here's a list of values I captured:

3
1
6
The credit card number is invalid.
P
0
School
45.00
CC
auth_capture
41F1CED7D79B2249DE6778B4F34BE5B9
XXXX)(&?

Re: SIM Returning Denied Card But Card Is Charged!

RaynorC1emen7 — Sat, 22 Dec 2012 22:21:46 GMT

So the response said the credit card# is invalid but it still getting an auth/capture on the authorize.net side. what is the 0?

Re: SIM Returning Denied Card But Card Is Charged!

ShadowDancerLV — Sat, 22 Dec 2012 22:33:05 GMT

It's in the 7th position of the transaction response.

Re: SIM Returning Denied Card But Card Is Charged!

ShadowDancerLV — Sat, 22 Dec 2012 22:37:04 GMT

Closest thing would be the x_trans_id field.

Re: SIM Returning Denied Card But Card Is Charged!

RaynorC1emen7 — Sun, 23 Dec 2012 00:14:57 GMT

It's in the 7th position of the transaction response.

SIM relay response are by field name, and not by position. Only response for AIM are by position.

How did you find the transaction to void if the id is 0? 0 mean it didn't generate an transaction, I'm not sure how it will get charge at all at authorize.net

does SIM return error on certain card? does it error an A card consistently.

Re: SIM Returning Denied Card But Card Is Charged!

ShadowDancerLV — Sun, 23 Dec 2012 01:55:05 GMT

It returns instantly according to the user. I have code to tell me what position in the response array the value occupied that's how I counted the 7th position. Since this is the first time I've had to do forensics on this type of thing, I'm taking notes on how to improve it.

Re: SIM Returning Denied Card But Card Is Charged!

RaynorC1emen7 — Sun, 23 Dec 2012 02:21:25 GMT

So you are using AIM and not SIM. It still doesn't explain the 0 transactionID. And how did you find the transaction on the merchant account?

Might need to call support with the transactionID you got from the merchant account and see if they see anything different then the response you received.

Re: SIM Returning Denied Card But Card Is Charged!

ShadowDancerLV — Sun, 23 Dec 2012 02:21:13 GMT

It's SIM. I use the post method and send the Url with the values and then parse the response code. I only save keys in the array that have values (as a way of saving space in the DB).

Re: SIM Returning Denied Card But Card Is Charged!

ShadowDancerLV — Fri, 28 Dec 2012 03:20:56 GMT

Are there scenarios where a valid credit card submission would fail?

Re: SIM Returning Denied Card But Card Is Charged!

RaynorC1emen7 — Fri, 28 Dec 2012 12:17:51 GMT

yes, here is the list of possible response

http://developer.authorize.net/guides/AIM/wwhelp/wwhimpl/js/html/wwhelp.htm#href=4_TransResponse.html#1095094

Were you able to find out if the problem is code issue or authorize.net issue?

Re: SIM Returning Denied Card But Card Is Charged!

ShadowDancerLV — Sat, 29 Dec 2012 01:06:21 GMT

Yes. I already have this link up. The problem is I've records declines from the authorize.net service for invalid card numbers and duplicate transactions. The problem is that the user's are reporting that their cards are still being charged.

Re: SIM Returning Denied Card But Card Is Charged!

RaynorC1emen7 — Sat, 29 Dec 2012 01:24:39 GMT

Did you contact support with the transactionID for the invalid card number and duplicate transactions to see if they see any problem?

Re: SIM Returning Denied Card But Card Is Charged!

ShadowDancerLV — Sat, 29 Dec 2012 01:27:12 GMT

No. The business user ended up voiding transaction for the customer. Even worse is that not all the declines were logged in Authorize.Net. Many times it's an immediate bounce back to a denial.

Re: SIM Returning Denied Card But Card Is Charged!

RaynorC1emen7 — Sat, 29 Dec 2012 01:56:01 GMT

When you list

Sure do! Here's a list of values I captured:

3
1
6
The credit card number is invalid.
P
0
School
45.00
CC
auth_capture
41F1CED7D79B2249DE6778B4F34BE5B9
XXXX)(&?

Is the 0 the transactionID?, if so, it will not be logged in authorize.net because it didn't create a transaction.

What is that XXXX)(&?

Do you log when ther customer start a SIM? Maybe they click the submit mulitple time when they are on the CC entry form? And first one when thru and the second one become duplicate error?

edited. I just try to click it mulitple time and it did get a "This transaction cannot be accepted" error 97. So that not the same as your problem. Do you logged the date time the transaction happened?

Re: SIM Returning Denied Card But Card Is Charged!

RaynorC1emen7 — Sat, 29 Dec 2012 02:10:25 GMT

Do you have x_relay_always set to true?

Just try to understand how it might happened.

1)First SIM CC Entry. they enter wrong CC#

2)Second SIM CC Entry. Submit OK???

3)Somehow they get to SIM CC Entry a third time with the same invoice? but different x_fp_hash and get duplicate error??

Re: SIM Returning Denied Card But Card Is Charged!

ShadowDancerLV — Sat, 29 Dec 2012 10:50:06 GMT

x_relay_always is set to false. Should it be true?

Good thing I time stamped the denails. They happen at exactly the same time. Here's the entries in the log:

Local Time ResponseValue
2012-12-20 16:34:56.000 The credit card number is invalid.
2012-12-20 16:34:56.000 The credit card number is invalid.
2012-12-20 16:34:57.000 The credit card number is invalid.

2012-12-21 15:41:25.000 A duplicate transaction has been submitted.
2012-12-21 15:42:07.000 A duplicate transaction has been submitted.
2012-12-21 15:43:09.000 A duplicate transaction has been submitted.