Entries tagged with “chargebacks”.

If your small business is taking credit card payments through a credit card processor, then you may have had to go through the often long and painful chargeback process. If you haven’t, you should probably learn as much as you can so you can be fully prepared. Chargebacks are one of the more frustrating realities of accepting credit card payments, but they can be much easier to handle with a little background knowledge of how the process works.

This infographic displays the chargeback process step-by-step, from the customer’s request of a chargeback to the resolution of the case. Check it out to learn more about what you can do to speed the process along, and to get a favorable resolution more frequently.


“When good people…cease their vigilance and struggle, then evil men prevail.” - Pearl S. Buck

When I was learning to ride a motorcycle my instructor gave me one piece of advice that always stayed with me.  He said “keep your head on a swivel.”  In other words, while I had to make sure that I was doing everything I should be doing, I also had to make sure that I was constantly looking out for what other people may be doing.  That way I could correct my course, or at least take some action to ensure that what the other people were doing wouldn’t put me in danger.  While this is certainly good advice for riding motorcycles, it is also good advice for data security.  It may seem like a stretch, but bear with me.

In securing our customers’ payment data, we have a guideline (actually a set of fairly stringent requirements) in the form of the Payment Card Industry Data Security Standards (PCI DSS).  To learn more about these standards visit this site.  Following these guidelines ensures that we are doing what we “should” in terms of protecting the data.  But that doesn’t mean that others won’t be taking action to put you (and your data) in danger – in the form of data compromise.  That means that you have to stay vigilant for what others might be doing – “keep your head on a swivel” –  to ensure that you are addressing newly identified risks and vulnerabilities that may not be addressed by the guidelines.

Recent trends indicate that small merchants are increasingly becoming targets of data thieves.  In a recent interview, Vantiv Vice President David Mattei stated, “…now we’re seeing an increase in the number of breaches in which smaller numbers of cards are compromised. Small, independent merchants are being targeted because of the ease with which fraudsters can compromise those payment systems.” That means that as small merchants, even if we are PCI DSS compliant, we must remain vigilant against potential attack.  One way to foil the fraudsters in this case is with the use of a P2P Encryption and tokenization solution. In this instance, the data is removed from the merchant system and replaced with “tokens,” or abstract representations of the cardholder data.  While merchants can still use the data to run reports, issue refunds or fight chargebacks, data thieves would find the tokens to be worthless.

The lesson in all of this is that we must remain on guard against new threats, even if we are doing everything “by the book.”  Leveraging secure technologies like tokenization can help ease the burden of compliance and render you and your customers more secure in the long run.

Sometimes it is the small things that make a difference.  I had a conversation with a friend last week about the pros and cons of using a payment aggregator for processing, as opposed to a traditional merchant account.  While we had a pretty lengthy discussion ranging over a variety of topics, there was one detail that stuck in my colleague’s mind.  I had asked how her merchant name shows up on receipts.  She hadn’t thought about that before and said she was going to go back and check it out.  Sure enough, she said, the merchant name showed up as something that even she would have found difficult to recognize as her business.  Why does that matter?  One word – chargebacks.

Often when customers don’t recognize the name on their statement, they will call their issuing bank and chargeback the purchase. If your merchant name is not immediately recognizable to customers on their statements, you run the risk of getting hit with unnecessary chargebacks.  Not only does this result in one-time charges and fees to the merchant, but repeated chargebacks can result in increased fees and may even cause processors, whether traditional processors or aggregators, to suspend the merchant’s ability to process payments.

This is a fairly easy thing to check, and to fix.  If you are unable to change your merchant name, and there are some legitimate reasons why that might be the case, then make sure your customers know what to look for on their statements.  This can be done either as a message on the receipt or on your website.  If you have a storefront, you may place a sign next to the register.  Anything that might reduce the likelihood of confusion on your customers’ part can help you reduce the likelihood of chargebacks.

Another year has flown by and the busy season at ProPay is about to begin. We want our merchants to have a successful and stress free holiday season. This is the perfect time to make sure our merchants are up to date on the latest fraud schemes. A fraudulent buyer, chargeback or theft of data can put a damper on your end of year sales.  Here are just a few of the most prevalent fraud trends today.

Spam— Unsolicited email, possibly fraudulent from a company that you didn’t authorize to send you messages.

Phishing/Spoofing— Phishers will impersonate a legitimate company by sending fake emails or creating fake Web sites in order to acquire your personal information—like PINs, credit card or bank account numbers.

Spyware— Software that records your personal information without you realizing it. Several anti-spyware software programs are available to combat spyware.

E Commerce Fraud- Before you buy anything online, ask yourself if the site is legitimate. Look seal from trusted companies that have certified the site as safe and secure. If the deal sounds too good to be true, it probably is.

Get-out-of-debt fraud— Many online debt elimination resources are fraudulent. Be wary. Investigate them thoroughly. If they aren’t a legitimate 501(c)(3) nonprofit organization, then it’s likely that they’re trying to take advantage of your debt-related vulnerability.

International schemes— Don’t respond to emails that suggest you have won or inherited money from someone in a foreign country—Nigeria and Eastern European countries are where many of these emails originate. And any scheme that asks you to give advance money for a larger sum in return is too good to be true, and will always be fraudulent.

Evil twin— A fake Wi-Fi network set up near to and often using a similar name as a real public Wi-Fi network, like those in libraries, parks, and coffee shops. If you unknowingly join the evil twin network, the criminal behind it will have access to all of the information on your computer.

Take a few moments to review this list and to research other fraud trends that could impact you and your business. The small investment of time will be worth it in the long run. Here’s to a successful holiday season and a strong push to the finish line in 2011.

As you read and familiarize yourself with the payment card industries risk and fraud best practices there are several ideas and theories that certainly can and do help mitigate risk.  Although, one such practice often seems overlooked, card transaction declines.  Card transaction declines can be very insightful and help prevent chargebacks and losses.  This practice, like many others, just takes a little bit of time and understanding to develop.

Decline reason codes are a first line of defense against fraudsters using stolen cards.  “Hold-Call” or “Pick up Card” decline codes are obviously very direct and paint a clear picture for a merchant.  Merchants who understand these messages and can tie them to more than just one specific transaction will have discovered a great tool in helping eliminate disputes.   The ability to tie these decline codes to a customer, IP address, physical location, or the like will be able to not only avoid the initial fraudulent order, but will be able to prevent the fulfillment of orders to the seemingly endless supply of other stolen cards a fraudster may be using.

Unfortunately not all declined card transactions are as clear as the codes described above.  In those instances rates and velocities can be very useful.  Decline rates can vary greatly from merchant to merchant, but certainly should not be overlooked.  Excessive card declines from a specific IP address, physical location, city, state, or even for a specific item you are selling should all be red flagged.  This will allow you to take a closer look at certain transactions and customers, giving you a greater opportunity to more thoroughly review those higher risk instances.