HELP! FRAUD
Answered
I use GPI as IO recommends them as a payment processor. I got a call from someone today saying their credit card was charged and it matches a job from 3 weeks ago.
What do people do in these situations?! Do I just get screwed? If so, how do I make sure this NEVER happens again?
This was way too easy for them to do, and I had zero clue that it was potentially fraud...
Any help is greatly appreciated.
Thank you,
You can't vote. Please authorize!
You can't vote. Please authorize!
You can't vote. Please authorize!
How much did the customer get charged for and what is the name of the customer so I can see if anything happened on our end! If you have the lead number for the event that would be helpful too! If there is any other information that you think we might need to know let me know!
How much did the customer get charged for and what is the name of the customer so I can see if anything happened on our end! If you have the lead number for the event that would be helpful too! If there is any other information that you think we might need to know let me know!
Here is what we found.
- the IP address that made payment was (172.226.36.36) and is from your geographic area.
- we would not consider an excessive amount of attempts to have been made.
- automatic emails mentioning the payment being received were sent to the customer and read.
- the credit card that went through had the same name as customer.
Based on this information we would recommend the following:
- ask global what settings they can change to make credit card submission more strict. Ask whether they are verifying the card name, zip code, and other address information is required to be accurate before processing. You can have them toggle these on or off to protect yourself from fraud. If they are already verifying the card name, then it's likely your customer used their own card for this transaction or the wrong name was given by the real person that contracted the event with you.
- ask your customer to pay for the event. If you did the event and they truly didn't pay, they should, right? If they refuse, it's more likely that they are the ones that used a stolen card. If we had to guess, this is what we would guess. And if this is the case, there is nothing we can do to resolve it. It's not possible for us to know when someone is using a card they stole.
- some attempts made after the event occurred showed your account was logged in. If you were not doing these or are unsure, you should take a couple actions. First reset your password. Second, make sure no one in your company is doing this for any reason, whether accidental or intentional.
Here is what we found.
- the IP address that made payment was (172.226.36.36) and is from your geographic area.
- we would not consider an excessive amount of attempts to have been made.
- automatic emails mentioning the payment being received were sent to the customer and read.
- the credit card that went through had the same name as customer.
Based on this information we would recommend the following:
- ask global what settings they can change to make credit card submission more strict. Ask whether they are verifying the card name, zip code, and other address information is required to be accurate before processing. You can have them toggle these on or off to protect yourself from fraud. If they are already verifying the card name, then it's likely your customer used their own card for this transaction or the wrong name was given by the real person that contracted the event with you.
- ask your customer to pay for the event. If you did the event and they truly didn't pay, they should, right? If they refuse, it's more likely that they are the ones that used a stolen card. If we had to guess, this is what we would guess. And if this is the case, there is nothing we can do to resolve it. It's not possible for us to know when someone is using a card they stole.
- some attempts made after the event occurred showed your account was logged in. If you were not doing these or are unsure, you should take a couple actions. First reset your password. Second, make sure no one in your company is doing this for any reason, whether accidental or intentional.
Replies have been locked on this page!