Action Code 59 - Suspected Fraud

[robunicourt]

Hello,

Starting October 15, 2021 (one month ago), we began receiving a new Action Code on some transactions, 59, Suspected Fraud.

We have never seen it is happening at least daily.

Our rate of declined transaction has increased as a result.

The types of transactions we accept, nor the volume has changed.

Also, the behavior of the code seems to not make sense, for example, we'll see a successful transaction, followed immediately by a 59 - SUSPECTED FRAUD decline and then an immediate success all on the same card:

Payment Oct 15, 2021 17:53 PDT Success $49.00 usd

Payment Oct 15, 2021 17:56 PDT Declined $1.30 usd -> Declined: 59 - SUSPECTED FRAUD

Payment Oct 15, 2021 17:57 PDT Success $8.80 usd

It's also happening to clients we've had using the same card in some cases for years.

Is anyone experiencing this and can anyone from Visa explain what's happening here as from what I can tell, it seems to be broken or at best mislabeled?

Regards,

Rob

[jenn_kh]

Hi and welcome to the community, @robunicourt! Thank you for reaching out. An agent is looking into this and will get back with you as soon as possible. If any community members have had a similar experience, please feel free to respond in this thread. - Jenn

[SLi]

Hi @robunicourt,

Please share the following information with us so we may investigate further:

1. End Point URL
2. Request Header
3. Request Body
4. Response Header (include the x-correlation-id)
5. Response Body

[robunicourt]

Hello Stacey,

Thanks so much for getting back to me so quickly!

We integrate directly with Recurly who integrate with TSys, per each of their support teams they're both passing that code all the way through from Visa's API.

I don't have access to the original API request or response but I can confirm that the 59 code is listed in your documentation under ActionCode (https://developer.visa.com/guides/request_response_codes#action_code) and is being passed through.

I not sure its a purely API error vs. something being changed on the processing/approval side.

Rob

[SLi]

Hi @robunicourt,

If TSYS is the one integrating with the Visa APIs, TSYS should reach out to their Visa Account Manager (AM) to report the issue. AMs will be able to help with any technical questions TSYS might have. 

[robunicourt]

Trust me, I've tried, they simply say they're passing on an action code from you.

If I understood what this action code was supposed to mean and why it just started appearing on October 15th perhaps I could make some more progress with them.

Can you help, or perhaps direct me to someone who can?

Rob

[SLi]

Hi @robunicourt,

Visa Developer Platform is for the developer community, banks, and merchants to build solutions with our APIs to market to their customers. If you have questions on the APIs on Visa Developer, I would be happy to help. Since you are not integrating our APIs directly and I don't know which API is returning Action Code 59, I apologize that I cannot help you in this situation. 

Please try contacting Visa via the below link, fill out the form, then submit it.

https://usa.visa.com/Forms/contact-us-form.html

[plusguy]

Hello Rob,

I know it's an old thread, but did you find a solution for this issue? Our approval rate took a hit with this new error as well Suspected Fraud (about 10% less).

We use Chargebee connected to Worldpay directly. Looks like you had similar configuration with Recurly.

Thanks for the help.

[jenn_kh]

Thank you for reaching out to the community, @plusguy. An agent will get back to you with more information as soon as possible. If any community members know a solution, please feel free to respond in this thread. -Jenn

[I_Doroteo3]

Hi @plusguy, 

Are you able to provide more information as to what company you are working for so that I can relay this issue to the correct team?

From what you said previously you are working with Worldpay which uses Chargebee.

You can also reach out to Developer@visa.com to provide more information.

Thanks, 

Illana