Merchant Processing Overview. Chris Moore, Strategic Account Leader-Elavon. Agenda. Introduction Key personnel associated with Commonwealth of Virginia processing contract Credit Card Processing Costs, Tips on lowering those costs, reading your statement, and those darned chargebacks!
Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.
Chris Moore, Strategic Account Leader-Elavon
Elavon Sales (for new Public Bodies wishing to participate in the Elavon/Virginia Treasury contract)
Elavon/COV Treasury Contract Costs
Card Association Fees
Card Association Fees
Visa FANF fees
A Chargeback is a transaction disputed by the Cardholder or Card Issuing Bank
There are many reasons for chargebacks, but the most common are:
Merchants must be able to provide proof that the disputed transaction is valid and in accordance with Visa/MasterCard regulations or risk having their account debited for the disputed transaction amount as well as chargeback fee
For the merchant, a chargeback translates into:
Imposing a Convenience fee is permissible under the following conditions:
§ 2.2-614.1. Authority to accept revenue by commercially acceptable means; service charge; bad check charge.
A. Subject to § 19.2-353.3, any public body that is responsible for revenue collection, including, but not limited to, taxes, interest, penalties, fees, fines or other charges, may accept payment of any amount due by any commercially acceptable means, including, but not limited to, checks, credit cards, debit cards, and electronic funds transfers.
B. The public body may add to any amount due a sum, not to exceed the amount charged to that public body for acceptance of any payment by a means that incurs a charge to that public body or the amount negotiated and agreed to in a contract with that public body, whichever is less. Any state agency imposing such additional charges shall waive them when the use of these means of payment reduces processing costs and losses due to bad checks or other receivable costs by an amount equal to or greater than the amount of such additional charges.
C. If any check or other means of payment tendered to a public body in the course of its duties is not paid by the financial institution on which it is drawn, because of insufficient funds in the account of the drawer, no account is in the name of the drawer, or the account of the drawer is closed, and the check or other means of payment is returned to the public body unpaid, the amount thereof shall be charged to the person on whose account it was received, and his liability and that of his sureties, shall be as if he had never offered any such payment. A penalty of twenty-five dollars or the amount of any costs, whichever is greater, shall be added to such amount. This penalty shall be in addition to any other penalty provided by law, except the penalty imposed by § 58.1-12 shall not apply.
(2002, c. 719.)
Commonwealth of Virginia State Law
Are you compliant….
Ongoing compliance audits
Victim notification costs
Fines and Fee
Non-compliance (each brand issues separate fines)
Chargeback’s for fraudulent transactions
Sensitive info disclosure
Denial of service to customers
Possibility of business closure
Potential legal liabilities beyond the Association rulesNon-Compliance: Risks, Fines, Fees, Costs, Loss
In an effort to make the process of becoming PCI DSS compliant more streamline, the PCI Council has developed 4 new SAQ’s for merchant validation. New SAQ’s are as follows:
SAQ A: Addresses requirements applicable to merchants who have outsourced all cardholder data storage, processing and transmission.
SAQ B: Created to address requirements pertinent to merchants who process cardholder data via imprint machines or standalone dial-up terminals only.
SAQ C: Constructed to focus on requirements applicable to merchants whose payment applications systems are connected to the internet.
SAQ D: Designed to address requirements relevant to all service providers defined by a payment brand as eligible to complete an SAQ and those merchant who do not fall under the types addressed by SAQ A, B, or C.
The new questionnaires and further information can be found at: https://www.pcisecuritystandards.org