October 28, 2006
Visa PCI security update
While none of the validation requirements themselves have changed, merchants moving into a new validation level will be responsible for complying with that category's validation responsibilities. For example, merchants moving from Level 4 to Level 2 must now have quarterly network security scans performed by a qualified independent scan vendor.
The revised criteria impact a relatively small number of merchants. Less than 1,000 Level 4 merchants are expected to move into the Level 2 category, while an equal number of former level 2 merchants processing fewer than 1 million e-commerce transactions per year will move to level 3.
Within the next two months, acquirers will identify any merchant changing levels. These merchants are required to validate PCI compliance with their acquirer by Sept. 30, 2007, generally 12 months from the date of identification.
Compliance with the Payment Card Industry Data Security Standard (PCI DSS) is required of all merchants and any entity that stores, transmits or processes cardholder data. Validation of compliance is part of that process, with validation requirements varying for merchants based on factors such as transaction volume.
A summary of the changes are listed in the chart below:
New Merchant Levels Defined
Merchant Level
New Criteria
Prior Criteria
Required Validation Action
Merchant Level 1
No change
Any merchant processing over 6 million Visa transactions per year or compromised in the past year, regardless of acceptance channel. No change to validation action for this level. Annual onsite audit and quarterly scans required.
Merchant Level 2
Any merchant processing 1 million to 6 million Visa transactions per year, regardless of acceptance channel. Any merchant processing between 150,000 and 6 million Visa e-commerce transactions per year. No change to validation action, but new definition expands the number of level 2 merchants to include former level 4 merchants. Annual self- assessment questionnaire and quarterly scans required.
Merchant Level 3
Any merchant processing 20,000 to 1 million Visa e-commerce transactions per year. Any merchant processing 20,000 to 150,000 Visa e-commerce transactions per year. No change to validation action, but new definition expands level 3 to include merchants formerly in level 2 processing fewer than 1 million e-commerce transactions per year. Annual self-assessment questionnaire and quarterly scans required.
Merchant Level 4
Any merchant processing less than 20,000 Visa e-commerce transactions per year, and all other merchants processing up to 1 million Visa transactions per year. Any merchant processing less than 20,000 Visa e-commerce transactions per year, and all other merchants processing up to 6 million Visa transactions per year. No change to validation action, but new definition reduces the number of level 4 merchants. Annual self-assessment questionnaire and quarterly scans may be required as specified by the member.
Despite debit's incredible growth in volume terms Mercator Advisory Group believes that the EFT networks that enable PIN debit are approaching a critical juncture. Signature debit, while currently facing a slightly slowing growth rate, is also the only debit solution fully enabled and successfully entering several new emerging markets, such as eCommerce, recurring bill payments, and those markets where cash is being displaced using Contactless and signature- less solutions. Left unchecked the increased growth in internet and mobile payments and cash replacement will occur primarily at the expense of growth in EFT transactions. This will be of some concern if these new markets grow as quickly as proponents hope. It is important to note that we are talking about future markets and the relative market share of transaction types in these emerging environments.
This report evaluates the consumer preference for debit instruments today, how these preferences can be shifted by the popular press and the payment industry itself, the targeting of three new markets by card associations for future growth: 1) online transactions, 2) recurring bill-pay environments, and 3) Contactless/signatureless environments intended to displace low- value cash transactions, and issues that make it difficult for EFT network operators to react unilaterally to enter these same evolving markets; and therefore, make co-operative plays related to technology standards and implementation a real consideration.
Tim Sloane, Director of the Debit Service for Mercator Advisory Group and the author of the report, indicates that despite strong growth rates across the board for debit, EFT network operators may need to start establishing plans to target these same markets.
"While predicting overall growth of all three evolving markets may be difficult, it is clear that internet payments will continue to grow significantly. If the recurring bills and cash replacement market segments also experience high growth, then EFT operators may find themselves facing a growing barrier to market entry not unlike that experienced when they had to deploy key pads on POS devices to enable PIN-based debit at the POS."
The report contains 26 pages and 12 Exhibits.
"NYPay brings together professionals in a collegial setting to network and dialogue on relevant issues in the dynamic payments industry," said Ronald Mazursky, Director, Edgar, Dunn & Company. "The model for this professional forum is based on the successful West Coast association, BayPay, which EDC co-founded in 2005 with membership now in the hundreds of active professionals."
"NYPay provides a much needed opportunity for payments professionals to stay current on industry developments while connecting with colleagues from various institutions. CashEdge is pleased to be involved as a founding member," said Demetris Papademetriou, Director, CashEdge, Inc.
Based on NYPay's stated membership profile, the association is seeking active professionals involved in the Financial Services Industry payments field who can contribute to the forum's regular discussion groups. Membership is by invitation only.
The survey revealed: 1) NAOPP's membership is overwhelmingly male; 2) 66.6 percent of NAOPP's members have been engaged in the industry for five years or greater; 3) 68.4 percent of the members are 45 years or age or older; and 4) 49 percent earn greater than $100,000 per year.
In addition, members indicated they are interested in educational programming including training at the regional acquirer's meetings as well as other types of training such as teleseminars and webinars. Members indicated they are interested in information on interchange, ethics, ISO registration and regulation, marketing via the Internet, new types of loyalty programs, and marketing and sales training.
Members further indicated they are interested in the following additional benefits:
- UPS/FEDEX/DHL mailing service or plan,
- Professional liability insurance,
- Long- and/or short-term disability insurance,
- Rental car discounts,
- Cellular telephone plans, and
- Discounted books or magazines.
- Broad willingness to use contactless cards.
- Greater acceptance with young consumers.
- High income consumers more likely to use contactless cards.
- Security and ease of use are top concerns
More than 50 percent of respondents, which translates into more than 100 million Americans, would use contactless cards to buy gasoline, items from fast food restaurants or corporate cafeterias, or groceries. More than 40 percent would use contactless cards to pay for convenience store items and transit fares (subway and bus fares and tolls). Almost 40 percent would use contactless cards to buy coffee or pay for parking, and 30 percent (60 million Americans) would use contactless cards for video games or at a vending machine or kiosk.
More than 50 percent of survey respondents between the ages of 18 and 24 indicated they would use contactless cards to buy a range of goods, including gas, groceries, fast food, coffee, convenience store items, transit fares and video games.
Consumers in households with incomes greater than $50,000 indicated they were more likely to use contactless cards than those with income less than $50,000.
Concerns about security and ease of use are the two main obstacles facing contactless card acceptance. Depending on the specific market, between 13 and 22 percent of respondents indicated security concerns would keep them from using contactless cards. The data indicates a need for companies leading contactless roll-outs to educate consumers about the cards' safety and how easy they are to use. "Contactless payments represent a significant opportunity for the payments ecosystem. Consumers benefit from the increased convenience while merchants gain speed at the point of sale," said Mark Friedman, President and CEO of Peppercoin. "In addition, when combined with Peppercoin's Virtual Prepaid and Merchant Loyalty offerings, contactless payments encourage consumers to return more frequently and spend more when they do -- translating into increased revenue for merchants."
Perhaps the most important aspect of bank or finance company statements is that customers frequently open them. While not all consumers read their statements rigorously, they are far more likely to open and read an account statement than they are other pieces of mail received from their bank. At the very least, consumers tend to save their statements - making receipt and retention of the information they contained more assured.
New technologies and techniques designed to enhance the presentation of account-related information have been around for a decade and are gaining ground. According to TowerGroup, as packaged software for statement creation becomes more widely used, both electronic and paper based statements will become increasingly viewed as strategic communications vehicles whose key role is to shape and direct the customer experience. TowerGroup anticipates consumer expectations of how information is presented to them from their bank to continue to increase, as consumers become more familiar with the Web and personalization capabilities available online.
The 2005/2006 survey data also points to the continued growth of debit activity at the POS. Over the past five years, consumers' average POS debit activity has grown from less than eight transactions a month to more than 11. The average total number of debit POS transactions made monthly has increased 21 percent in the last year, from 15 to 18 transactions per month.
Although PIN and signature debit both demonstrated transaction growth, preference of PIN debit over signature debit was 45 percent to 33 percent. Security was the leading response for choosing PIN debit as reported by 48 percent of respondents. Additionally, 57 percent of PIN-secured debit users reported that having the choice to receive cash back at the POS resulted in more usage of their cards.
PIN and Signature Debit Work Best Together
- 62 percent of ATM/debit cardholders reported using their ATM/debit cards at the POS in the 30 days prior to the survey. Over the past five years, consumers' average POS debit activity has grown from less than eight transactions a month to more than 11.
- Among all card users, 45 percent of consumers report using both PIN and signature methods, an increase from last year's 39 percent. The number of respondents using both is significantly greater than those who report utilizing a single method.
- Using both methods has a major effect on transaction volume: Those who use both PIN and signature debit account for 75 percent of all debit POS transactions made. Consumers utilizing both methods conduct an average of 23 transactions a month versus 14 for those who solely use signature and 10 for those using only PIN.
- The expanding number of locations accepting debit, particularly for small-ticket purchases, underscores the value of promoting both PIN and signature debit to consumers. Among respondents, PIN debit is the preferred debit option at discount stores, convenience stores, drug stores and do-it-yourself stores, while signature debit leads in food categories and specialty retail locations.
October 24, 2006
Taking advantage of lower rates with purchasing cards
We program all of our terminals, software and gateways to do the necessary prompts to take advantage of the lower rates purchasing cards offer.
|
|
Purchase Cards have been used by government agencies and corporations to streamline their buying processes for 20 years now. The last ten years has seen tremendous growth beyond the initial "early-adopter" and "getting it figured out" phases, and has grown into an established and growing market segment for enterprise payments. In fact, survey data reports that the annual U.S. Purchase Card spending grew from $80 billion to $110 billion between 2003 and 2005. Understanding Purchasing Cards and Their Use: What is a Purchase Card?On the surface, a Purchase Card may look like your average business or consumer credit card, but a closer examination reveals that Purchase Cards possess more features, capabilities and controls. A typical Purchase Card can be setup to control:
These extra control features help buying organizations manage their purchasing policies and processes. ISO Opportunity:Merchants are being asked to supply Level-3 transactions and need help selecting payment solutions capable of meeting their needs. Why are Purchase Cards Used? Purchase Cards are used by buying organizations to streamline their purchasing and payment processes. Cards may be used a variety of ways, but for routine purchases they are issued to authorized cardholders so they can place orders and make payments directly and efficiently on behalf of the buying organization. The key to obtaining the best rates for these transactions is to include line-item detail, also known as "Level-3." Payment processors can bring substantial value to the merchant by helping them qualify for the lower-cost Level-3 rates. This is even more important if the transaction sizes are large. Who is Using Purchase Cards and How Much? Purchase Card use is widespread, even if it is not highly visible. Most midsize and larger corporations have Purchase Card programs in place. Federal, state and local government agencies have multi-year contracts with their purchase card-issuing banks. Universities and utility groups have systems deployed. Purchase Card systems are offered by many commercial banks and other financial institutions. Why Merchants Care About Purchase Cards As more businesses and government users migrate to using purchase cards, merchants who accept purchase cards also benefit. Merchant benefits include: Finding Balance for the MerchantMerchants want to obtain these benefits, but they are also have issues that they need to balance. These include:
Understanding your Merchant Business: A Solutions-oriented ApproachMerchant processing requirements and solution selection may be influenced by their…
Transaction/business processes: Is a stand alone solution appropriate or one that can integrate into the merchant's ordering or finance system needed? IT infrastructure/systems in use: What systems does the merchant currently have and are they planning for change in the near future? What application software is used - SAP / Oracle / Quickbooks / etc. Select the Right Payment Service to Process Purchase CardsAccepting purchasing cards allows merchants to stay competitive and become a strategic supplier to corporate or government purchasing card users. These customers often require enhanced purchasing information beyond the standard financial information provided by most other card processing solutions. by Aaron Bills |
October 23, 2006
Some more tips on avoiding chargebacks
The skinny on chargebacks and disputes - Part II
By Ross Federgreen
here are many types of disputes and chargebacks. To respond appropriately, it's important to understand their distinctions and review chargeback notifications carefully.
Each specific chargeback is designated by a chargeback code. These codes are either a one- or two-digit number. MasterCard Worldwide and Visa U.S.A. may use the same chargeback designation number, but the definitions of the common number may be different.
There are five broad categories under which all chargeback codes are classified. These are: authorization, cardholder dispute, documentation request, fraud and processing error. The first step in shaping a correct response to a dispute or chargeback is understanding the specific category under which the reason code falls.
Once the category of the chargeback or dispute is understood, the next step is to carefully examine the associated documentation.
As detailed in Part l of this series (The Green Sheet, Aug. 28, 2006, issue 06:08:02 ), the entire process is specifically timed; you must be aware of when a response is due. Further, since the meaning of dispute codes varies by payment brand you must examine the jurisdiction to which you are responding. Jurisdictions include MasterCard Worldwide and Visa U.S.A. as well as others.
Next, examine the adjustment amount. This may give you a clue as to the underlying mechanisms for a specific chargeback. Clearly, you must respond specifically to the reason and the dispute type. Failure to respond to the specific area will lead to failure in your efforts to resolve a chargeback or dispute in your merchant's favor.
Analyzing a notification of chargeback
Here are five key areas you should examine whenever you receive a chargeback notification:
- Due date
- Jurisdiction
- Adjustment amount
- Reason
- Dispute type.
From the initiation perspective, two broad categories of chargeback or dispute exist: procedural and substantive. Procedural chargebacks are initiated by the card issuer for various processing errors or for violations of the MasterCard or Visa rules and regulations. Substantive chargebacks occur when cardholders initiate disputes.
Understanding the categories and the reasons why a chargeback or dispute falls into a particular category significantly increases your ability to respond in the appropriate manner.
Dispute/chargeback reason codes
There are over 100 valid reason codes. Many of the definitions have very subtle nuances and require specific conditions. To help the merchant successfully defend against these codes requires detailed understanding.
The vast majority of reason codes consist of two digits. If you receive a one-digit code, this indicates in the majority of cases that a warning bulletin violation has occurred. Reason Code 7 is an example. It is usually associated with the failure to receive a proper authorization.
For MasterCard, Visa and other noncard Association transactions, the same two-digit reason code can represent different conditions. Here are some examples:
Reason Code 47 under Diners Club International Ltd. is an unauthorized transaction that exceeds floor limit and for which no authorization was obtained. Visa Code 47 represents a fraudulent transaction and is associated with no authorization being obtained. Under MasterCard, Code 47 represents a transaction that exceeds floor limit, is not authorized and is fraudulent.
Code 54 under Diners is defined as a "claim or defense." It represents a situation in which a customer claims that a service or good is no longer viable, such as a timeshare or contract work. Under MasterCard, Code 54 represents a "cardholder dispute - not elsewhere classified (U.S. Region only)." Under Visa, Code 54 represents "cardholder dispute - not elsewhere classified (not region specific)."
On the other hand, Code 53 is defined the same way by Diners, Visa and MasterCard. The definition is "not as described." In this situation, the customer claims that the good or service is not as described. For example, a ring turns out to be 14-karat gold rather than 18-karat, etc.
Further complicating matters are reason codes that require a certain condition regardless of the card brand. Examples of this circumstance include Codes 24, 94 and 95. Code 24 is merchant service error, Code 94 is cancelled guaranteed reservation and Code 95 is advance deposit service.
Common chargeback scenarios
Here are three examples of chargebacks with common causes:
Reason Code 41: The cancelled transaction
Definition: The card issuer received a claim by the cardholder for one of the following reasons:
- The merchant was notified to cancel a recurring transaction but has since billed the customer.
- The transaction amount exceeds the preauthorized dollar amount range.
- The merchant was supposed to notify the cardholder prior to processing each recurring transaction but has not done so.
Most common causes for Reason Code 41:
- The cardholder withdrew permission to charge the account, cancelled payment of a membership fee or cancelled the card account.
- The card issuer charged back a previous recurring transaction, and the cardholder did not expressly renew or cancelled the card account.
- The merchant received notice before the transaction was processed that the cardholder account was closed or exceeded the pre-authorized dollar amount range and did not notify the cardholder in writing within 10 days before processing the transaction - or notified the cardholder in writing within 10 days of processing the recurring transaction, after which the cardholder notified the merchant not to charge.
Reason Code 81: Fraudulent transaction - card present environment
Definition: The card issuer received a sales receipt that is missing required information, indicating a potentially fraudulent transaction.
Specific situations in which this chargeback code may be used include those wherein the card issuer received a sales receipt that has no imprint of the card's embossed or magnetic-stripe information or the cardholder's signature and:
- the cardholder certifies he neither authorized nor participated in the transaction, or
- the card issuer certifies that no valid card with that account number existed on the transaction.
This chargeback is not valid for recurring payments and card-not-present transactions. However, it is valid for card-present sales on self-serve POS terminals, such as cardholder-activated gas pumps.
Most common causes for Reason Code 81:
The merchant or service establishment
- did not swipe the card through a magnetic-stripe reader
- did not make a manual imprint of the card account information on the sales receipt for a key-entered transaction
- completed a card-present transaction without obtaining the cardholder's signature on the sales receipt
- completed a card-not-present transaction but did not identify the transaction as a MO/TO or Internet purchase.
Reason Code 82: Duplicate processing
Definition: The card issuer received the same transaction more than once for posting to the cardholder's account.
Most common causes for Reason Code 82:
The merchant or service establishment
- entered the same transaction into the POS terminal more than once
- electronically submitted the same batch of transactions to its merchant bank more than once
- deposited with its merchant bank both the merchant copy and the bank copy of a sales receipt
- deposited sales receipts for the same transaction with more than one merchant bank
- created two sales receipts for the same purchase.
It is my hope this article will give you a better grasp of the multiple nuances involved in chargebacks. In part three we will discuss certain regulatory issues as well as specific methodologies to track and respond to chargebacks and disputes.
--
Bill Hoidas
District Sales Manager
Larger B2B/MOTO/Internet Accounts
Product Development Manager
Matrix Payment Systems
(847) 381-3482 office
(847) 381-4289 fax
http://paymentconsulting.net
John 3:16 For God so loved the world, that he gave his only begotten Son, that whosoever believeth in him should not perish, but have everlasting life.
October 05, 2006
YOU DON'T HAVE TO TAKE CHARGEBACKS LAYING DOWN-YOU CAN FIGHT!
have often written about the importance of merchant education and training. When it comes to chargebacks, keeping merchants up to date and on their toes is critical. These efforts ensure client retention.
Merchants typically get chargebacks for the usual two or three reason codes, and often for just one reason: an inability to issue timely refunds. For example, the lion's share of chargebacks for MO/TO merchants stem from failure to promptly issue refunds for returned merchandise, fraudulent transactions, defective goods, etc.
The refund issue can be a warning sign that a merchant is having cash-flow problems or experiencing a customer service meltdown.
Cracking the codes
A card issuer must meet all requirements for the reason code it is using for a given chargeback. Otherwise, the chargeback is invalid and can be re-presented by the merchant and acquirer, shifting the burden of loss back to the issuing bank and cardholder.
When ISOs send my team and me out to work with merchants, I often find that a substantial number of chargebacks could be re-presented if merchants better understood the rules and bothered to re-present improper and invalid chargebacks.
It always amazes me how often MO/TO merchants get chargebacks for transactions that have actually been refunded to cardholders. Yet, the merchants involved haven't bothered to re-present the chargebacks to the issuing bank.
You may find the following examples of MasterCard Worldwide and Visa U.S.A. reason codes helpful in understanding the chargeback process.
MasterCard Reason Code 4853
An issuer initiated a chargeback for MasterCard Reason Code 4853 (defective/not as described) after receiving a letter from a cardholder stating that he engaged in the transaction, returned the merchandise and was refused a credit.
However, after carefully reviewing the cardholder's letter, the merchant and acquirer noticed the chargeback was invalid because the cardholder didn't mention "a particular problem or defect" having to do with the merchandise. The letter only conveyed the decision to return it.
In cases like this, the merchant and acquirer can re-present the chargeback, shifting the burden of loss back to the issuer and cardholder.
More on MasterCard Reason 4853
In another example of MasterCard Reason Code 4853 (defective/not as described), an issuer initiated a chargeback based on a cardholder letter claiming the goods from a face-to-face transaction with a jeweler were not as described.
For supporting documentation, the issuer provided a cardholder letter stating the jeweler indicated that a ring purchased by the cardholder was solid 14-karat gold, but the ring was not worth the amount paid to the jeweler.
The cardholder also provided 1) the requisite appraisal from another jeweler verifying that the ring was gold plated, not solid 14-karat gold, and 2) a statement that the cardholder attempted to return the ring, but the jeweler refused to accept its return. The issuer did not, however, provide any documentation given to the cardholder by the jeweler stating the ring was sold as a solid 14-karat gold ring.
In this situation, the jeweler and acquirer can re-present the chargeback. They will prevail on the basis that the description on the sales ticket does not indicate the ring was presented as a solid 14-karat gold ring.
MasterCard Reason Code 4855
An issuer initiated a chargeback for MasterCard Reason Code 4855 (nonreceipt of merchandise) and supplied a letter from the cardholder involved. The letter stated the cardholder engaged in the transaction but never received the merchandise. And the cardholder contacted the merchant for a credit, but it was never issued.
To prove the cardholder received the merchandise, the acquirer provided a signed shipping receipt to the issuer. The issuer sent this signed receipt to the cardholder.
The cardholder examined the receipt and still refused to pay. The cardholder asserted he did not receive the merchandise, and the signature on the receipt was not his, nor did it belong to anyone he authorized to receive the merchandise.
If this dispute were to escalate into an arbitration case, MasterCard would rule in favor of the issuer because the cardholder still disputed the original sale's consummation and all further documentation that the acquirer supplied. This is the bad side of the chargeback process; it doesn't always result in the proper outcome.
The requirements for a re-presentment to a chargeback for nonreceipt of merchandise are very specific. The acquirer must provide proof that the cardholder or a person authorized by the cardholder received the merchandise.
Visa Reason Code 30
An issuer initiated a chargeback for Visa Reason Code 30 (services not provided or merchandise not received) based on a cardholder's claim that an ordered concert ticket was not received.
In response to the chargeback, the merchant provided proof of delivery showing the package was left at the cardholder's front door. The merchant also provided a delivery form, signed by the cardholder, authorizing the shipping company to leave the package at the door.
In this scenario, the merchant would prevail. It is unreasonable for the merchant to be responsible for the cardholder's decision to have the package left at the door. Note: There would be a different result if the merchant were unable to provide signed proof that the cardholder agreed to have the package left at the door without a signature.
Visa Reason Code 85
An issuer initiated a chargeback for Visa Reason Code 85 (credit not processed) based on the following scenario: A cardholder called a hotel to reserve a room for three nights and gave his credit card number to guarantee the room. The hotel informed him of its 24-hour cancellation policy and provided a confirmation number.
Three days before the reservation date, the cardholder called the hotel to cancel the reservation. The cancellation was accepted. But the cardholder was charged for a no-show on the arrival date. The cardholder then phoned the hotel, which explained it did not have record of the cancellation, so the charge was valid.
The hotel and acquirer re-presented the chargeback, claiming the hotel had no record of the cancellation and the issuer did not provide a cancellation number.
In this case, the hotel would prevail. Reason Code 85 requires a cancellation number be provided for a no-show transaction. If the cardholder was not given a cancellation code or if the cardholder lost the code, the issuer cannot pursue the chargeback.
These examples show how nit-picky the chargeback process can be. However, my experience in helping ISOs solve merchant chargeback problems has shown the process can be managed. Only a few chargeback scenarios apply to each merchant.
By having the proper processes in place, merchant chargebacks can be minimized. And when they do occur, they can often be re-presented, shifting the burden of loss back to the issuer.