tag:blogger.com,1999:blog-88874737418746691032024-03-21T16:28:08.612-04:00Merchant AccountA blog about merchant accounts and credit card processing.msshttp://www.blogger.com/profile/02682453100579738680noreply@blogger.comBlogger43125tag:blogger.com,1999:blog-8887473741874669103.post-80003176858186064552012-07-15T12:16:00.000-04:002012-07-15T12:16:35.947-04:00Merchant Account Application Requirements<div>
<div class="separator" style="clear: both; text-align: center;">
<a href="http://paymentprocessingservices.blogspot.com/2008/07/what-is-billing-descriptor.html" imageanchor="1" style="clear: right; float: right; margin-bottom: 1em; margin-left: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjLJub2FwzCRShClJwsJ3Pi0S9P99s7-UJyBHOSC2yX_Uck3Oo2siTI9-N1oMBMH7b0IO5cPqk2y2C_zetCsGTVbQBcij3mEwGYmFQu2AhnBCz2_oM3Pp5kISBwv68vthbAmE-t_oegnMf_/s1600/Merchant+Account+Application+Requirements.jpg" /></a></div>
Provided your organization is qualified to apply for a US-based merchant processing account and has received an acceptable payment processing <a href="https://www.unibulmerchantservices.com/">proposal</a>, you can commence the application process. There are a number of requirements that need to be met and, to understand why the process is so stringent, you need to understand exactly what is it that you are applying for. A merchant account is a form of line of credit that a merchant processing bank is extending to the applicant. When you accept a transaction, your merchant account bank will "acquire" it, usually at the end of the day, and will automatically deposit the payment amount, after subtracting the interchange fee and its own processing cost, into your checking account. At the same time it will submit a request for payment to your customer's card issuing bank. Your merchant bank will pay you before it gets paid. That is the reason why they have set in place an application process, designed to establish the credit worthiness of both the applicant organization and its principals. Following is a list of requirements that you will have to meet:<br />
<ul>
<li><strong>Merchant Account Application.</strong> You will provide in this form details about both your business and yourself, including address (business and personal), social security number, tax ID (if applicable), phone numbers, email address, web address, bank account info, etc.</li>
<li><strong>Personal Guarantee (for-profit businesses only).</strong> All new businesses and a great many established ones are required to provide a personal guarantee before establishing payment processing services.</li>
<li><strong>Articles of Incorporation.</strong> Unless your establishment is a sole proprietorship, you will have to provide a proof that it has been legally incorporated.</li>
<li><strong>Business License.</strong> If your business activity is regulated and requires a license, either a federal or a state one, you will need to provide it.</li>
<li><strong>Business Financial Statements.</strong> Unless your organization has been formed recently, you will have to provide its financial statements (typically it is required that you produce financial statements for the two years preceding the application date).</li>
<li><strong>Personal Financial Statements.</strong> Typically requested in place of business financial statements, personal financials might be requested in addition to them. Personal tax returns for the latest two years are typically sufficient.</li>
<li><strong>Processing Statements.</strong> If you are currently processing credit cards and are looking for a new service, you will be asked to produce your three latest processing statements.</li>
<li><strong>Voided Check.</strong> You will need to provide a voided copy of a check for the bank account that you want your money to be deposited into. The check has to have your "Doing Business As" (DBA) name printed on it. If you have not yet received your checks, you will need to provide a signed bank letter stating your account details.</li>
</ul>
As you see, there are quite a few requirements for applicants to accept credit and debit cards and it is by no means certain that you will be approved. Still, if you provide the needed paperwork and have decent credit history, chance are that you will get your merchant account service.</div>
<div>
<br />
<a href="http://www.addthis.com/bookmark.php" onclick="window.open('http://www.addthis.com/bookmark.php?wt=nw&pub=unibul&url='+encodeURIComponent(location.href)+'&title='+encodeURIComponent(document.title), 'addthis', 'scrollbars=yes,menubar=no,width=620,height=520,resizable=yes,toolbar=no,location=no,status=no,screenX=200,screenY=100,left=200,top=100'); return false;" target="_blank" title="Bookmark and Share"><img alt="Bookmark and Share" border="0" height="16" src="http://s9.addthis.com/button1-addthis.gif" width="125" /></a></div>msshttp://www.blogger.com/profile/02682453100579738680noreply@blogger.com0tag:blogger.com,1999:blog-8887473741874669103.post-27662118003622801192012-07-08T11:22:00.001-04:002012-07-08T11:22:59.277-04:00Merchant Account Qualifications<div class="separator" style="clear: both; text-align: center;">
<a href="http://blog.unibulmerchantservices.info/2012/07/merchant-account-processing-minimum.html" imageanchor="1" style="clear: right; float: right; margin-bottom: 1em; margin-left: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh6dZnGylZhAkD9yqDNRMhmDylbE84EUkYiE_TdvUfK9Og264-c9gXIJW2QQqj6TT_PbWJkm8qzVmmTwTkpKMQpZfjkcnCkdGwd89uecouKIkFtbKBmboxWxOi8q8inruziiAdP7lsizbL4/s1600/Merchant+Account+Qualifications.jpg" /></a></div>
There are certain requirements that applicants for US-based merchant accounts have to comply with. It is the responsibility of merchant account <a href="https://www.unibulmerchantservices.com/">providers</a> to ensure that all applicants:<br />
<ul>
<li><strong>Are legally registered within the US.</strong> Applicants for merchant services have to be either incorporated as businesses within the state that they reside in or they have to be registered with the local municipality and obtain a "Doing Business As" (DBA) name. Individuals are not allowed to establish merchant account processing services. Foreign establishments are also excluded from obtaining US-based payment processing accounts.</li>
<li><strong>Have a physical address and a registered agent within the USA.</strong> Applicants for US merchant services need to provide available a contact person within the US and a physical office for the merchant processing bank to inspect.</li>
<li><strong>Have a bank account with a US bank.</strong> The bank account into which the merchant will have his or her funds deposited must be opened with a US bank.</li>
</ul>
Only if the applicant complies with the above requirements, the merchant account processor will proceed with the application.msshttp://www.blogger.com/profile/02682453100579738680noreply@blogger.com0tag:blogger.com,1999:blog-8887473741874669103.post-90420596732248001702012-06-24T12:21:00.003-04:002012-06-24T12:21:47.852-04:00eCommerce Merchant Account Rates<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi-KK5PG294oT6qC4k7W-ep66nqvwjxUFZJNJreXznenvn6NbEu-VvM34DFYLe4Kvr4p2OAiNad7QlPuE0DRifRGh29jOLRD-iIGia37Qf_ZLSBWeH2D0mu0jMQ5j8V1_0jnOa9poxzeQ2c/s1600/eCommerce+Merchant+Account+Rates.jpg" imageanchor="1" style="clear: right; float: right; margin-bottom: 1em; margin-left: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi-KK5PG294oT6qC4k7W-ep66nqvwjxUFZJNJreXznenvn6NbEu-VvM34DFYLe4Kvr4p2OAiNad7QlPuE0DRifRGh29jOLRD-iIGia37Qf_ZLSBWeH2D0mu0jMQ5j8V1_0jnOa9poxzeQ2c/s1600/eCommerce+Merchant+Account+Rates.jpg" /></a></div>
<a href="https://www.unibulmerchantservices.com/free-authorize-net-merchant-account">ECommerce merchants</a> pay higher processing rates than their retail counterparts. The reason is that card-not-present transactions are more likely to generate customer disputes than card-present ones. Customer disputes, especially if not addressed properly, often lead to chargebacks, which are costly for both the merchant and its payment processing provider. So the premium that card-not-present transactions are charged pays the insurance against possible chargebacks. Following is a list of the components of the eCommerce merchant account processing costs and what we think is a reasonable rate for each one of them:<br />
<ul>
<li><strong>Discount rate.</strong> Rates for web merchant accounts have fallen substantially over the last few years and you should not be charged more than 2.19% for credit cards and 1.98% for debit cards for consumer types of cards. You should keep in mind that commercial, business, rewards and some other types of cards are charged at a significantly different interchange rate which, as its main component, directly affects the discount rate that you will be offered. When evaluating a pricing proposal, you should be aware of the pricing structure that your prospective merchant account processor is using. There are several types, most of which will give you a flat rate, in one form or another, for all types of credit and debit cards. The problem with these models is that, in order to make money on all transactions, merchant processing banks have to provide a rate that is higher than the highest possible interchange that you are likely to incur. Your best option would probably be the pass-through pricing model which adds your merchant account provider's payment processing costs to the interchange fees, thus ensuring that no transaction is overcharged.</li>
<li><strong>Transaction fee.</strong> Online merchant account users should not pay more than $0.25 per transaction.</li>
<li><strong>Application and set up fees.</strong> You should not pay any set up or application fees!</li>
<li><strong>Payment gateway fee.</strong> Payment processing gateway is the service that will connect your website's shopping cart with your processing bank and will transmit payment information between them. It should be set up for free and the monthly gateway fee should not exceed $15.</li>
<li><strong>Monthly statement fee.</strong> A bank fee that every merchant services provider will charge you. You should not agree to anything higher than $10.</li>
<li><strong>Support fee.</strong> Another monthly fee. You should not pay any such fees.</li>
</ul>
Make sure to carefully examine the fine print in the merchant processing agreement before signing it and make sure your payment processor does not hide anything from you.<br />
<br />
<a href="http://www.addthis.com/bookmark.php" onclick="window.open('http://www.addthis.com/bookmark.php?wt=nw&pub=unibul&url='+encodeURIComponent(location.href)+'&title='+encodeURIComponent(document.title), 'addthis', 'scrollbars=yes,menubar=no,width=620,height=520,resizable=yes,toolbar=no,location=no,status=no,screenX=200,screenY=100,left=200,top=100'); return false;" target="_blank" title="Bookmark and Share"><img alt="Bookmark and Share" border="0" height="16" src="http://s9.addthis.com/button1-addthis.gif" width="125" /></a>msshttp://www.blogger.com/profile/02682453100579738680noreply@blogger.com0tag:blogger.com,1999:blog-8887473741874669103.post-72364229784299700632012-06-21T23:47:00.001-04:002012-06-21T23:47:15.306-04:00Retail Merchant Account Rates<div class="separator" style="clear: both; text-align: center;">
<a href="http://paymentprocessingservices.blogspot.com/2008/06/regular-merchant-account-vs-third-party.html" imageanchor="1" style="clear: right; float: right; margin-bottom: 1em; margin-left: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiz3VZfBk8JeEI2iRSnSTj__u6id0CnWxMOB0BCmRY0x1pZDBM-78kay1bttR2RK7IBbPzgs-qjbbsTLq9h5J20scZpBvOt8YziEAc9ElGK0-OkhffNvxW3P2dwg7Dff4rKopU29ZarLS7N/s1600/Retail+Merchant+Account+Rates.png" /></a></div>
Merchant account rates are the sum of interchange rates and the processing costs incurred by the merchant bank. Following is a breakdown of retail merchant account processing rates and our suggestions what you should be looking for (or you can just visit our <a href="https://www.unibulmerchantservices.com/">website</a>).<br />
<ul>
<li><strong>Discount rate</strong>. You should pay no more than 1.69% for credit cards and 1.40% for debit cards. These are the rates for consumer cards which are the most widely used. Various business to business, rewards and other cards often get charged at a higher interchange rate (the base processing rates set by Visa and MasterCard). You need to ask your merchant services provider what pricing structure they are using. The best choice for you will be the pass-through pricing which will ensure that the payment processing costs they add to the interchange fees are the same for all types of cards and you will not get overcharged.</li>
<li><strong>Transaction fee</strong>. You should not agree to anything higher than $0.20 (it will be the same for debit and credit cards).</li>
<li><strong>Set up fee.</strong> You should not pay any set up or application fees!</li>
<li><strong>Monthly maintenance fee</strong>. Every merchant account provider will charge you such a monthly fee, although they might give it different names. You should not be paying more than $10.</li>
<li><strong>Support fee</strong>. Another monthly fee. You should not pay any such fees.</li>
</ul>
You will also need a payment processing terminal and your merchant account provider will provide you one and configure it to work with their system. You can purchase the terminal from a third party as well. Other than that, be sure to carefully review the whole merchant processing agreement for charges that may make it more expensive than it seems.<br />
<br />
<a href="http://www.addthis.com/bookmark.php" onclick="window.open('http://www.addthis.com/bookmark.php?wt=nw&pub=unibul&url='+encodeURIComponent(location.href)+'&title='+encodeURIComponent(document.title), 'addthis', 'scrollbars=yes,menubar=no,width=620,height=520,resizable=yes,toolbar=no,location=no,status=no,screenX=200,screenY=100,left=200,top=100'); return false;" target="_blank" title="Bookmark and Share"><img alt="Bookmark and Share" border="0" height="16" src="http://s9.addthis.com/button1-addthis.gif" width="125" /></a>msshttp://www.blogger.com/profile/02682453100579738680noreply@blogger.com0tag:blogger.com,1999:blog-8887473741874669103.post-14576702122574939692012-06-17T12:24:00.001-04:002012-06-17T12:24:33.841-04:00Merchant Account Providers<div>
<div class="separator" style="clear: both; text-align: center;">
<a href="http://www.unibulmerchantservices.com/wp-content/uploads/2009/12/12-Content-Features-Every-eCommerce-Website-Must-Include-210x300.jpg" imageanchor="1" style="clear: right; float: right; margin-bottom: 1em; margin-left: 1em;"><img border="0" src="http://www.unibulmerchantservices.com/wp-content/uploads/2009/12/12-Content-Features-Every-eCommerce-Website-Must-Include-210x300.jpg" /></a></div>
Merchant account providers like <a href="https://www.unibulmerchantservices.com/">UniBul</a> enable businesses to accept credit and debit cards for payment. Whether an organization accepts cards in a card-present or in a card-not-present environment, they need a merchant account to do that.</div>
<div>
<br />
In order for a company to become a provider of merchant account services, it first has to be authorized by the Credit Card Associations of Visa and MasterCard. The process involves a check of the credit worthiness of both the business and its principals, a review of the applicant's business and marketing plans and the payment of the registration fees which are $5,000 for each Association. Although banks, that are members of Visa and MasterCard, can and do provide merchant processing services, more typically they outsource this responsibility to third parties. By doing so, they become sponsors of these third parties in their applications with Visa and MasterCard. Merchant account processors are known as Independent Sales Organizations ISO) when they are registered with Visa and as Member Service Providers (MSP) when they are registered with MasterCard. Businesses apply for both registrations at the same time, through their sponsor bank. Upon approval of the application, the sponsor bank becomes an acquiring bank for the ISO/MSP. This means that it acquires the sales receipts that the merchants, using its payment processing services, generate and it is then responsible for paying the merchant the transaction amounts, minus its processing costs and the interchange fees. In the mean time the merchant processing bank submits a payment request, through Visa or MasterCard, to the bank that issued the card used in the particular transaction. ISOs and MSPs are obligated to display the name(s) of their acquiring bank(s) on every page of their website and other promotional materials. Usually this sign is placed in the footer of the website.</div>
<br />
<div>
Once registered, ISOs and MSPs can sign up sales agents to source merchants for them. The sales agents, however, cannot advertise themselves as providers of merchant account processing services. They are only authorized to represent the ISO/MSP and must identify themselves as agents to these companies.</div>
<br />
<div>
<br />
<a href="http://www.addthis.com/bookmark.php" target="_blank" title="Bookmark and Share"><img alt="Bookmark and Share" border="0" height="16" src="http://s9.addthis.com/button1-addthis.gif" width="125" /></a></div>msshttp://www.blogger.com/profile/02682453100579738680noreply@blogger.com0tag:blogger.com,1999:blog-8887473741874669103.post-33374439086523471922012-06-15T23:16:00.001-04:002012-06-15T23:16:22.490-04:00Payment Gateway<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg0G3_pkSWohIle51h1eqRtDcqmjBui12X51NrPxpKizJVq2G-fB5DuzSrEHfXOESKVKhgr8tOlppi92vU7TvfplTnpzZ2BquqXrDJl5GoMkmyaOD3fNIrGB4BRAH76512-Fi4okvo_jXY0/s1600/Payment+Gateway.jpg" imageanchor="1" style="clear: right; float: right; margin-bottom: 1em; margin-left: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg0G3_pkSWohIle51h1eqRtDcqmjBui12X51NrPxpKizJVq2G-fB5DuzSrEHfXOESKVKhgr8tOlppi92vU7TvfplTnpzZ2BquqXrDJl5GoMkmyaOD3fNIrGB4BRAH76512-Fi4okvo_jXY0/s1600/Payment+Gateway.jpg" /></a></div>
<strong>Definition.</strong> A payment gateway is a web-based service that transmits payment information from an eCommerce website to a merchant processing bank. It is the eCommerce equivalent of the physical terminal used by merchants in card-present payment acceptance environments. The collected information is encrypted to ensure that personal data is transmitted in a secure fashion.<br />
<br />
<strong>How it works.</strong> A payment processing gateway connects the eCommerce website's shopping cart with the merchant processing bank's system. The stages of the process are as follows: <br />
<ul>
<li>A customer places an order on an eCommerce website and submits his or her payment information.</li>
<li>The payment information is encrypted using a secure socket layer (SSL) service and sent to the merchant's server.</li>
<li>The eCommerce gateway then collects the payment information and, after another SSL encryption, transmits it to the merchant account provider's server.</li>
<li>The merchant processing bank then sends the payment details to the appropriate Credit Card Network (Visa or MasterCard).</li>
<li>If the cardholder used a Discover or an American Express card, the payment processing provider serves as an acquiring bank and decides whether or not to authorize the transaction; then forwards the response to the merchant.</li>
<li>The Credit Card Network forwards the transaction to the card issuing bank.</li>
<li>The Issuer either authorizes or declines the transaction and sends a response code (through the exact same channel) back to the merchant bank. The response codes for declined transactions provide details for the reason the transaction did not get approved.</li>
<li>The merchant processing bank then sends the response code (through the eCommerce payment gateway) to the merchant's website and it is presented to the cardholder.</li>
<li>The whole process, from submitting the payment to receiving the response, takes seconds.</li>
<li>The merchant then provides the service or ships the product and settles the transaction. It is very important that transactions do not get deposited prior to the product being shipped. If the cardholder notices the charge on his or her card statement or transaction activity (now available online in almost real time), prior to receiving the merchandise, the transaction may be disputed, initiating a chargeback.</li>
<li>At the end of the business day, all authorized transactions (also called a "batch") are submitted to the merchant processing bank for settlement.</li>
<li>The merchant bank then deposits the total transaction amount, minus interchange fees and processing costs, into the merchant's bank account.</li>
<li>The entire process takes approximately 2-3 business days.</li>
</ul>
Card payment processors typically provide eCommerce gateways as part of the merchant account. They charge a monthly fee for the service ($10 - $25) and may charge a fee for the set up as well. Every major online payment gateway supports the latest fraud prevention solutions, including the Address Verification (AVS) and Card Verification (CVC2, CVV2, CID) services.<br />
<br />
<a href="https://www.unibulmerchantservices.com/free-authorize-net-merchant-account">Here is our solution</a>.<br />
<br />
<a href="http://www.addthis.com/bookmark.php" target="_blank" title="Bookmark and Share"><img alt="Bookmark and Share" border="0" height="16" src="http://s9.addthis.com/button1-addthis.gif" width="125" /></a>msshttp://www.blogger.com/profile/02682453100579738680noreply@blogger.com0tag:blogger.com,1999:blog-8887473741874669103.post-77963739863439065382012-06-13T21:55:00.002-04:002012-06-13T22:00:28.513-04:00What Is a Merchant Account?<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhLCYr73zjDiAwQ_94bxdFYntn5pkuT_aR6vM3IfyVdu9R-td0e1xK7NuVNTknMyuFUmZibo2alPIHVdiYCyIgbFgafTgXdM7ZpXEEdfVOopz_K9gnUDu4SaX9jmjkADAwVAfj-hkvh1Vh5/s1600/What+Is+a+Merchant+Account.jpg" imageanchor="1" style="clear: right; float: right; margin-bottom: 1em; margin-left: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhLCYr73zjDiAwQ_94bxdFYntn5pkuT_aR6vM3IfyVdu9R-td0e1xK7NuVNTknMyuFUmZibo2alPIHVdiYCyIgbFgafTgXdM7ZpXEEdfVOopz_K9gnUDu4SaX9jmjkADAwVAfj-hkvh1Vh5/s1600/What+Is+a+Merchant+Account.jpg" /></a></div>
<strong>Definition.</strong> A merchant account is a payment card processing service that a merchant bank provides to a merchant (it is the type of service <a href="https://www.unibulmerchantservices.com/">UniBul</a> provides). It represents a form of line of credit that the merchant bank extends to the merchant and it allows the merchant to accept the card brands, specified in the processing agreement.<br />
<br />
<strong>How it Works.</strong> When a merchant accepts a cardholder's payment information, it is transmitted to the merchant bank. The merchant bank then pays the merchant the transaction amount, minus the interchange fees and the processing costs, and submits a payment request to the bank that issued the card used to make the purchase. The issuing bank then pays the merchant bank the transaction amount, minus the interchange fees, and posts the transaction on the cardholder's monthly statement. The cardholder then pays the issuing bank to close the cycle.<br />
<br />
<strong>Types of Merchant Accounts.</strong> There are a number of different merchant account types but the most widely used are:<br />
<ul>
<li><strong>Card-Present Merchant Accounts.</strong> This type of merchant account service includes all payment processing solutions that use payment terminals to read the account information from the magnetic stripe of a card that is swiped through. Because the merchant is in actual possession of the card (hence, card-present) as the payment is being made, these merchant accounts are considered less likely to generate fraudulent transactions and enjoy lower processing rates.</li>
<li><strong>Card-not-Present Merchant Accounts.</strong> Included in this group are all card payment processing services where the card account information is manually entered into the merchant bank's system, using a web browser or a telephone keypad. The card itself is absent (hence, card-not-present). Because the merchant is never in possession of the card and the information is given to him or her, card-not-present transactions are considered more likely to generate fraudulent activity or processing errors and are processed at higher rates. There are two distinct sub-groups here:<br /><ul>
<li><strong>ECommerce Merchant Accounts.</strong> These merchant accounts are used by web-based merchants and enable consumers to enter their payment card information into a payment form on the merchant's website. Once submitted, the payment details are automatically transmitted, via a payment gateway, to the merchant bank.</li>
<li><strong>Mail Order and Telephone Order Merchant Accounts.</strong> Also known as MO/TO merchant accounts, these payment acceptance solutions enable merchants to enter the payment information, provided to them by their customers into a form on the merchant bank's payment system's website or, using a telephone keypad, to call it into the merchant bank's system.</li>
</ul>
</li>
</ul>
<a href="http://www.addthis.com/bookmark.php" target="_blank" title="Bookmark and Share"><img alt="Bookmark and Share" border="0" height="16" src="http://s9.addthis.com/button1-addthis.gif" width="125" /></a>msshttp://www.blogger.com/profile/02682453100579738680noreply@blogger.com0tag:blogger.com,1999:blog-8887473741874669103.post-19592838211270858622012-06-12T22:39:00.002-04:002012-06-13T22:01:48.372-04:00Interchange Fees<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEifWK7wjku30wMg8EuLu0Ab18uxiMQT2ETUFLOwZwmVyg2Xk0lI3_PXLj75QQT3zeQK_MBGC_BKh7mgQrfgFUHQ2566YflD49w1lRk-709zaHMrZGMHUcJ_NKGLcwB4tOre7HSZHgnpZJym/s1600/Interchange+Fees.jpg" imageanchor="1" style="clear: right; float: right; margin-bottom: 1em; margin-left: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEifWK7wjku30wMg8EuLu0Ab18uxiMQT2ETUFLOwZwmVyg2Xk0lI3_PXLj75QQT3zeQK_MBGC_BKh7mgQrfgFUHQ2566YflD49w1lRk-709zaHMrZGMHUcJ_NKGLcwB4tOre7HSZHgnpZJym/s1600/Interchange+Fees.jpg" /></a></div>
In the payment card industry interchange is the fee that an acquiring bank pays to a card issuing bank when a card (issued by the card issuing bank) is used to pay for a product or a service, provided by a merchant who has a merchant account with the acquiring bank. The issuing bank pays the acquiring bank the transaction amount minus the interchange fee. The acquirer then pays the merchant the transaction amount minus both the interchange fee and its own payment processing cost.<br />
<br />
Interchange rates are published annually by both Credit Card Networks - Visa's and MasterCard's and are available for everyone to see. They represent the largest chunk of the total transaction processing costs that merchants pay for accepting payment cards. Various estimates put their share at anywhere between 70% - 90%. Interchange rates are typically comprised of a percentage of the transaction amount (for example 1.94%) plus a fixed fee (for example $0.10). Various factors come into play when interchange fees are established. Generally, payments taken in a card-not-present environment are processed at a higher interchange than payments taken in a card-present environment. That is the reason why eCommerce merchant account and MOTO merchant account users pay higher processing fees than, say, retail merchant account users.<br />
<br />
Since interchange rates are set by Visa and MasterCard, merchants have no leverage over them. It is, however, important to know what they are, so that, when negotiating with prospective merchant account providers, you will know exactly what you are being offered. There are several merchant processing pricing structures and this article will not go over all of them but probably the best model is the pass-through one. It works by simply adding your merchant services provider's processing cost to interchange, ensuring that every single transaction is processed at the same rate. You will only have to make sure that these processing costs are not inflated and a simple referral to the interchange chart will help you do just that.<br />
<br />
See how we have structured our own interchange pricing <a href="https://www.unibulmerchantservices.com/interchange-plus-credit-card-processing">model</a>.<br />
<br />
<a href="http://www.addthis.com/bookmark.php" target="_blank" title="Bookmark and Share"><img alt="Bookmark and Share" border="0" height="16" src="http://s9.addthis.com/button1-addthis.gif" width="125" /></a>msshttp://www.blogger.com/profile/02682453100579738680noreply@blogger.com0tag:blogger.com,1999:blog-8887473741874669103.post-38891380445757713842012-06-09T00:30:00.002-04:002012-06-15T23:21:20.145-04:00Merchant Requirements for Securing Cardholder InformationTo protect your merchants, cardholders, and the integrity of the payment system, each of the credit card processing companies has in place a set of requirements governing the safekeeping of account information (<a href="https://www.unibulmerchantservices.com/">UniBul</a> very much included). Following is a brief overview of the most critical aspects of those requirements.<br />
<br />
<table border="1" cellpadding="0" cellspacing="0"><tbody>
<tr><td valign="top" width="133">Storage of Cardholder Information</td><td valign="top" width="505"><ul class="unIndentedList">
<li> Do not store the following under any circumstance:<ul>
<li> Full contents of any track from the magnetic stripe on the back of the card.</li>
<li> Card-validation code-the three-digit value printed on the signature panel of a MasterCard, Visa, Discover<b> </b>Card, JCB, or Diners Club<strong> </strong>card, and four-digit code printed on the front of an American Express<strong> </strong>card.</li>
</ul>
</li>
<li> Store only that portion of the customer's account information that is essential to your business-i.e. name, account number or expiration date.</li>
<li> Store all material containing this information (e.g., authorization logs, transaction reports, transaction receipts, car rental agreements, and carbons) in a secure area limited to authorized personnel.</li>
</ul>
</td></tr>
<tr><td valign="top" width="133">Destruction of Cardholder Information</td><td valign="top" width="505">Destroy or purge all media containing obsolete transaction data with cardholder information.</td></tr>
<tr><td valign="top" width="133">Use of Agents or Third Parties (Vendors, Processors, Software Providers, Payment Gateways, or Other Service Providers)</td><td valign="top" width="505"><ul class="unIndentedList">
<li> Advise each merchant account provider or credit card processing contact (representing each of your card brands) of any agents that engage in, or propose to engage in, the processing or storage of transaction data on your behalf-regardless of the manner or duration of such activities.</li>
<li> Make sure these payment processing agents adhere to all rules and regulations governing cardholder information security. Any violation by your card processing agent may result in unnecessary financial exposure and inconvenience to your business.</li>
</ul>
</td></tr>
<tr><td valign="top" width="133">Reporting a Security Incident</td><td valign="top" width="505"><ul class="unIndentedList">
<li> In the event that transaction data is accessed or retrieved by any unauthorized entity, notify the merchant services provider or merchant processing contact for each card brand immediately.</li>
<li> This report will not only minimize risk to the payment system, but protect your customers in the most responsible manner. Systems and procedures are in place to immediately stop the unauthorized use of compromised data, but are effective only when you (and every small business merchants accounts provider) do your part to promptly report a security incident.</li>
</ul>
</td></tr>
</tbody></table>
<br />
<a href="http://www.addthis.com/bookmark.php" target="_blank" title="Bookmark and Share"><img alt="Bookmark and Share" border="0" height="16" src="http://s9.addthis.com/button1-addthis.gif" width="125" /></a>msshttp://www.blogger.com/profile/02682453100579738680noreply@blogger.com0tag:blogger.com,1999:blog-8887473741874669103.post-25346688226556803272012-06-07T22:59:00.001-04:002012-06-07T22:59:33.014-04:00Recurring Payments<strong>What are Recurring Payments?</strong> Recurring payment plans exist when a cardholder authorizes a merchant to charge his or her credit or debit card on a regular basis (e.g., monthly, quarterly or annually). Payment amounts can be fixed or they can vary and the plan exists until it is canceled by the cardholder. A good example of a recurring payment plan would be an auto insurance policy that has been set up so that the insured's credit card is charged monthly and the service will be provided indefinitely, or until it is canceled by the consumer. All merchant processing accounts support this feature.<br />
<br />
<strong>Benefits for Merchants:</strong><br />
<ul>
<li>Providing additional payment processing options. Customers like having payment options at the checkout.</li>
<li>Increasing enrollment in online payment processing. It is a great time-saving tool.</li>
<li>Reducing customer service calls. By automatizing the process merchants ensure less payment-related issues.</li>
<li>Improving cash flow. Recurring payment card processing plans ensure that less mistakes will be made and less payments will be returned.</li>
<li>Reducing delinquencies. Setting up the payment schedule beforehand ensures less delinquencies.</li>
<li>Improving collections. Since the payments are processed automatically, they are easier to collect.</li>
<li>Increasing customer retention. Consumers, too, enjoy the convenience of recurring payment plans.</li>
</ul>
<strong>Benefits for Cardholders:</strong><br />
<ul>
<li>Convenience of setting up the payments once. It's fast, easy and simple. You don't have to go over it again.</li>
<li>Time savings. Once the plan is set up, you are done. Payments are made automatically thereafter.</li>
<li>Stress relief. You don't have to keep on checking when the bill is due and worry about being late on a payment.</li>
<li>Cost savings. No more post stamps to stick on payment envelopes.</li>
<li>Earning points on rewards program. Some merchants qualify for various credit card reward programs.</li>
</ul>
Depending on the type of merchant account that you have, recurring payment plans may be set up differently. Ask your credit card processing provider for assistance if you are not sure how it is done.<br />
<br />
<a href="http://www.addthis.com/bookmark.php" target="_blank" title="Bookmark and Share"><img alt="Bookmark and Share" border="0" height="16" src="http://s9.addthis.com/button1-addthis.gif" width="125" /></a>msshttp://www.blogger.com/profile/02682453100579738680noreply@blogger.com0tag:blogger.com,1999:blog-8887473741874669103.post-29068323049449778492012-06-06T22:55:00.004-04:002012-06-06T22:55:41.523-04:00Merchant Payment Account Easy Payment Service<a href="http://blog.unibulmerchantservices.org/2011/07/e-commerce-credit-card-processing-banks.html"><img alt="Merchant Payment Account Easy Payment Service" border="0" id="BLOGGER_PHOTO_ID_5631482132794685314" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjHEewGLi1dq2mGP5_N7LFzkr_00YU146CjH_HPKvSEtBocwR9fwgGQ-vn_EXWnCgagVJDUEp3JKSKsSeo1DyoXn2yfL2hAp2fdlMqGNmeZuQiy4mp-gFuYbJU3MdMY1Cl3wIoAs7ihqBBv/s320/Merchant+Payment+Account+Easy+Payment+Service.jpg" style="cursor: hand; cursor: pointer; float: right; height: 193px; margin: 0 0 10px 10px; width: 300px;" title="Merchant Payment Account Easy Payment Service" /></a>Visa's Easy Payment Service (VEPS) for merchant payment account users enables face-to-face retailers from more than 98 percent of Merchant Category Codes (MCCs) to accept credit cards and other bank cards without the need for a signature and only need to print out a receipt upon a request from the customer.<br />
<br />
The VEPS program offers retailers the potential to speed up the check-out process at the point of sale, improve customer satisfaction and provide operating efficiencies for merchant payment account users. It can also help increase customer retention by helping cardholders use their bank cards quickly, securely and easily.<br />
<br />
<h3>
<b>Merchant Payment Account Easy Payment Service Advantages</b></h3>
<br />
For qualifying payments, the VEPS program:<br />
<div>
<ul>
<li>Eliminates the need for card acceptors to obtain a signature.</li>
<li>Eliminates the transaction receipt requirement, unless specifically requested by the cardholder.</li>
<li>Eliminates the necessity for retailers to store sales receipts and bans issuers from placing retrieval requests.</li>
<li>Provides strong chargeback protection against fraudulent transactions and for the receipt requirement.</li>
</ul>
<div>
<br /></div>
</div>
<h3>
Which Transactions Qualify</h3>
<br />
Transactions qualify for the VEPS service if they comply with all of the following criteria:<br />
<div>
<ul>
<li>The transaction takes place at a qualified merchant payment account user.</li>
<li>It is a purchase (as opposed to credit) transactions with a valid card.</li>
<li>It is a card-present environment (for amounts of $25 and lower) or unattended environment ( for $15 and under).</li>
<li>Payments are authorized.</li>
<li>Applies to all MCCs except those explicitly excluded (list is provided below).</li>
<li>All card types are eligible, including magnetic-stripe, chip-and-PIN and proximity payments.</li>
<li>The POS device must read and transmit unaltered magnetic-stripe, chip, or contactless payment information.</li>
<li>The information must be transmitted in the authorization message.</li>
</ul>
</div>
<h3>
Unqualified Merchants</h3>
<br />
The following business types are not qualified for VEPS:<br />
<div>
<ul>
<li>Wire Transfer Money Orders.</li>
<li>Insurance Services.</li>
<li>Automated Fuel Dispensers.</li>
<li>Travel Related Arrangement Services.</li>
<li>Catalog Merchants.</li>
<li>Combination Catalog and Retail Merchants.</li>
<li>Outbound and Inbound Telemarketing Merchants.</li>
<li>Continuity / Subscription Merchants.</li>
<li>Manual and Automated Cash Disbursements.</li>
<li>Financial Institutions - Merchandise and Services.</li>
<li>Betting, including Lottery Tickets, Casino Gaming Chips, Off-Track Betting, and Wagers at Race Tracks.</li>
<li>Intra-Government Purchases.</li>
<li>International Automated Referral Service.</li>
<li>GCAS Emergency Services.</li>
<li>Intra-Company Purchases.</li>
</ul>
There are no program registration requirements. If a merchant payment account user is eligible, they should just run the transaction as they normally would, skipping the signature, and offering the sales receipt as an optional service.<br />
<br />
(<a href="https://www.unibulmerchantservices.com/">Read more</a>.)</div>msshttp://www.blogger.com/profile/02682453100579738680noreply@blogger.com0tag:blogger.com,1999:blog-8887473741874669103.post-21523155889025633862012-06-06T22:54:00.002-04:002012-06-06T22:54:58.849-04:00E-Commerce Merchant Account Chargeback Requests<a href="http://blog.unibullmerchantservices.org/2011/07/merchant-credit-card-account-chargeback.html"><img alt="E-Commerce Merchant Account Chargeback Requests" border="0" id="BLOGGER_PHOTO_ID_5634154741112036626" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgSPdhDy9gnm-LelQ-F15k4WUyvnhJ-YymfXQ8t9Dd76gWs5hqgxrsW5Dcq1MNUn2Mor5pycAWLMScs2bm6Ash6uhhn9aoDjwma4jd82p5e_mhN8OGT-90u47yCU6kgVEjxmTjtoHuGQ7lT/s320/E-Commerce+Merchant+Account+Chargeback+Requests.jpg" style="cursor: hand; cursor: pointer; float: right; height: 210px; margin: 0 0 10px 10px; width: 300px;" title="E-Commerce Merchant Account Chargeback Requests" /></a>A chargeback, as previously stated, is the reversal of a portion, or the entire amount, of a card transaction that is being disputed, resulting in a refund to the issuer and debit to the e-commerce merchant account provider or the retailer in the amount listed to the dispute. Chargebacks can be initiated as a result of a processor's or retailer's failure to provide a complete and on-time response to a sales ticket retrieval request or for the failure of the retailer to follow applicable credit card processing procedures.<br />
<br />
If the card issuer has sufficient evidence that supports a dispute of a transaction, the e-commerce merchant account provider will not require the submission of a ticket retrieval request prior to initiating a chargeback request. An image of the sales receipt supporting the chargeback request must be submitted to the processor within five business days of the issuer initiating it, except for disputes related to authorizations where the evidence is saved as an electronic record. The content of a processor's or retailer's response to a retrieval request may constitute sufficient evidence needed to resolve the dispute.<br />
<br />
Each chargeback request needs to contain the following pieces of information:<br />
<div>
<ul>
<li></li>
<li>Details of any correspondence between the customer and the retailer documenting the authenticity of the chargeback request; or</li>
<li>Sufficient evidence supporting the dispute.</li>
</ul>
Additionally required information regarding some types of transactions may include the following:</div>
<div>
<div>
<ul>
<li>For airline e-commerce merchant account transactions, the original ticket if a paper ticket was produced, a copy of the original ticket with adequate proof that the consumer did not use the ticket or evidence of the sale of an electronic ticket (such as the confirmation code);</li>
<li>Assignment of claim by a consumer that received a refund; and</li>
<li>Other documentation that may be requested by the processor.</li>
</ul>
<div>
Upon receiving the chargeback request from the issuer, each processor or retailer is required to repay the amount of the resulting Chargeback to the Association (Visa or MasterCard). If the evidence proves that the chargeback was indeed improper, they should request a re-presentment.</div>
</div>
</div>
<div>
<br /></div>
<div>
<div>
If Visa or MasterCard does not receive sufficient evidence supporting the chargeback request from the card issuer within the time-frame stated (five business days) or if the Association does receive a request that is not compliant with the above requirements, a chargeback may not be processed or if it had done so already, the Association may process a re-presentment.<br />
<br />
(Learn more <a href="https://www.unibulmerchantservices.com/">here</a>.)</div>
</div>msshttp://www.blogger.com/profile/02682453100579738680noreply@blogger.com0tag:blogger.com,1999:blog-8887473741874669103.post-58272624668435753622012-06-05T19:16:00.001-04:002012-06-06T23:18:17.773-04:00<table border="0" cellpadding="10" cellspacing="0" id="textEdit" style="display: table;">
<tbody>
<tr>
<td align="left" style="color: black; font-family: Georgia, 'Times New Roman', Times, serif; font-size: 12pt; text-align: left;" styleclass=" style_MainText" valign="top"><div style="color: black; font-family: Arial, Helvetica, sans-serif; font-size: 18pt; letter-spacing: -1px; text-align: left;" styleclass=" style_Headers">
<span style="color: #ff950c; font-size: 16pt;"><strong>Where Is My Debit Discount?</strong></span></div>
<div style="color: #666666; font-family: Arial, Helvetica, sans-serif; font-size: 8pt; letter-spacing: normal; text-align: left;" styleclass=" style_RSSAuthor">
by UniBul on 5/10/2012 </div>
<div style="margin-bottom: 0px; margin-top: 0px;">
<br /></div>
<div>
<span style="font-family: Arial, Helvetica, sans-serif;"><a class="imgCaptionAnchor" href="http://blog.unibulmerchantservices.com/where-is-my-debit-discount/" shape="rect" track="on"><img align="left" border="0" height="73" hspace="5" name="ACCOUNT.IMAGE.3" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhSDyuex05bGHwSOlRBQCCUcuVkCd5pHc4aOcb2k3eAv2xhXcqz1kAwA4EttYyCVnocXgvwO0nJPFO_QkW2624kcm5m_wbHQj46UGiKqiqj7H2sP3E3HZgO77xEPgByjl4BOvtXljOatDEt/s1600/Where+Is+My+Debit+Discount+1.jpg" style="text-align: left;" vspace="5" width="94" /></a> <span style="font-family: Arial, Helvetica, sans-serif; font-size: 12pt;">The retailers had promised us lower prices at the checkout, once the fees they are charged for accepting debit cards were reduced. Well, these fees were cut by no less than 45 percent. So where is my promised discount?</span></span></div>
<div align="right" style="margin-left: 30px; text-align: right;">
<span style="font-family: Arial, Helvetica, sans-serif;"><a href="http://blog.unibulmerchantservices.com/where-is-my-debit-discount/" linktype="1" shape="rect" style="color: #ff950c; text-decoration: underline;" target="_blank" track="on">Read more.</a></span></div>
<div style="margin-bottom: 0px; margin-top: 0px;">
<br /></div>
</td>
</tr>
</tbody>
</table>
<br />
<table border="0" cellpadding="10" cellspacing="0" id="textEdit" style="display: table;">
<tbody>
<tr>
<td align="left" style="color: black; font-family: Georgia, 'Times New Roman', Times, serif; font-size: 12pt; text-align: left;" styleclass=" style_MainText" valign="top"><div style="color: black; font-family: Arial, Helvetica, sans-serif; font-size: 18pt; letter-spacing: -1px; text-align: left;" styleclass=" style_Headers">
<span style="color: #ff950c; font-size: 16pt;"><strong>You Can’t Get in Trouble with Prepaid</strong></span></div>
<div style="color: #666666; font-family: Arial, Helvetica, sans-serif; font-size: 8pt; letter-spacing: normal; text-align: left;" styleclass=" style_RSSAuthor">
by UniBul on 5/11/2012 </div>
<div style="margin-bottom: 0px; margin-top: 0px;">
<br /></div>
<div>
<span style="font-family: Arial, Helvetica, sans-serif;"><a class="imgCaptionAnchor" href="http://blog.unibulmerchantservices.com/you-cant-get-in-trouble-with-prepaid/" shape="rect" track="on"><img align="left" border="0" height="73" hspace="5" name="ACCOUNT.IMAGE.3" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjHF7u_GBc910Kipqj_Fp2BGm_zfLTRsJJxhbO-F_sLGrPIWxuWMFxxsMTle0HPHuNpgSaMmOkofqFSJaqfQB6BRPErD7LEHKBYuc0ogHwC65abhgnD6Q3ATFVaoPO5eessiYC3b4TCmDnR/s1600/You+Can%27t+Get+in+Trouble+with+Prepaid+1.jpg" style="text-align: left;" vspace="5" width="94" /></a> <span style="font-family: Arial, Helvetica, sans-serif; font-size: 12pt;">That may not be the official tagline for the campaign that has been launched to tout the virtues of the latest American Express prepaid card, but it sure could be. The way I see it, prepaid cards, even the best among them, are still very much the payment cards of choice for the unbanked.</span></span></div>
<div align="right" style="margin-left: 30px; text-align: right;">
<span style="font-family: Arial, Helvetica, sans-serif;"><a href="http://blog.unibulmerchantservices.com/you-cant-get-in-trouble-with-prepaid/" linktype="1" shape="rect" style="color: #ff950c; text-decoration: underline;" target="_blank" track="on">Read more.</a></span></div>
<div style="margin-bottom: 0px; margin-top: 0px;">
<br /></div>
</td>
</tr>
</tbody>
</table>
<br />
<table border="0" cellpadding="10" cellspacing="0" id="textEdit" style="display: table;">
<tbody>
<tr>
<td align="left" style="color: black; font-family: Georgia, 'Times New Roman', Times, serif; font-size: 12pt; text-align: left;" styleclass=" style_MainText" valign="top"><div style="color: black; font-family: Arial, Helvetica, sans-serif; font-size: 18pt; letter-spacing: -1px; text-align: left;" styleclass=" style_Headers">
<span style="color: #ff950c; font-size: 16pt;"><strong>EMV, NFC, Mobile Wallets and Credit Card Fraud Liability</strong></span></div>
<div style="color: #666666; font-family: Arial, Helvetica, sans-serif; font-size: 8pt; letter-spacing: normal; text-align: left;" styleclass=" style_RSSAuthor">
by UniBul on 5/8/2012 </div>
<div style="margin-bottom: 0px; margin-top: 0px;">
<br /></div>
<div>
<span style="font-family: Arial, Helvetica, sans-serif;"><a class="imgCaptionAnchor" href="http://blog.unibulmerchantservices.com/emv-nfc-mobile-wallets-and-credit-card-fraud-liability/" shape="rect" track="on"><img align="left" border="0" height="73" hspace="5" name="ACCOUNT.IMAGE.3" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjdmUOpxag2VlHpfcxH4SpgTlubwO9vXE5MYaL8IBUj7fKqePdwTodzpyWYNamwZ523MLavlJ4TPt00qO4iRDAAhL7DdedvhxLyCYrfIkfxXIcjkMcraET6ln6vuqPArnkXK46iPzJGpH3a/s1600/EMV,+NFC,+Mobile+Wallets+and+Credit+Card+Fraud+Liability.jpg" style="text-align: left;" vspace="5" width="103" /></a> <span style="font-family: Arial, Helvetica, sans-serif; font-size: 12pt;">Beginning in October 2015, merchants who have not upgraded to chip-and-PIN-compliant point-of-sale (POS) terminals, will be liable for the full amount of any fraud losses, which will, incidentally, hugely benefit mobile wallet operators.</span></span></div>
<div align="right" style="margin-left: 30px; text-align: right;">
<span style="font-family: Arial, Helvetica, sans-serif;"><a href="http://blog.unibulmerchantservices.com/emv-nfc-mobile-wallets-and-credit-card-fraud-liability/" linktype="1" shape="rect" style="color: #ff950c; text-decoration: underline;" target="_blank" track="on">Read more.</a></span></div>
<div style="margin-bottom: 0px; margin-top: 0px;">
<br /></div>
</td>
</tr>
</tbody>
</table>
<br />
<iframe allowtransparency="true" src="//www.facebook.com/plugins/like.php?href=http%3A%2F%2Fwww.facebook.com%2FUniBul&send=false&layout=box_count&width=450&show_faces=true&action=like&colorscheme=light&font&height=90" frameborder="0" scrolling="no" style="border: none; height: 90px; overflow: hidden; width: 450px;"></iframe>
<br />
<a href="http://www.facebook.com/UniBul" linktype="facebook" shape="rect"><img alt="Find UniBul Merchant Services on Facebook!" border="0" height="36" src="https://imgssl.f1.constantcontact.com/ui/images1/ic_fbk_36.png" width="36" /></a>
<a href="http://www.twitter.com/UniBul" linktype="twitter" shape="rect"><img alt="Follow UniBul Merchant Services on Twitter!" border="0" height="36" src="https://imgssl.constantcontact.com/ui/images1/ic_twit_36.png" width="36" /></a>
<a href="http://www.linkedin.com/groups/Merchant-Account-Services-107582?gid=107582&trk=hb_side_g" linktype="linkedin" shape="rect"><img alt="Connect with UniBul Merchant Services on LinkedIn!" border="0" height="36" src="https://imgssl.constantcontact.com/ui/images1/ic_lkdin_36.png" width="36" /></a>
<a href="http://blog.unibulmerchantservices.com/" linktype="blog" shape="rect"><img alt="Read our Blog!" border="0" height="36" src="https://imgssl.constantcontact.com/ui/images1/ic_blog_36.png" width="36" /></a>msshttp://www.blogger.com/profile/02682453100579738680noreply@blogger.com0tag:blogger.com,1999:blog-8887473741874669103.post-64092473850013572492012-06-05T19:11:00.000-04:002012-06-06T23:18:50.012-04:00<table border="0" cellpadding="10" cellspacing="0" id="textEdit" style="display: table;">
<tbody>
<tr>
<td align="left" style="color: black; font-family: Georgia, 'Times New Roman', Times, serif; font-size: 12pt; text-align: left;" styleclass=" style_MainText" valign="top"><div style="color: black; font-family: Arial, Helvetica, sans-serif; font-size: 18pt; letter-spacing: -1px; text-align: left;" styleclass=" style_Headers">
<span style="color: #ff950c; font-size: 16pt;"><strong>The More You Use Your Debit Card, the Lower Your Credit Score</strong></span></div>
<div style="color: #666666; font-family: Arial, Helvetica, sans-serif; font-size: 8pt; letter-spacing: normal; text-align: left;" styleclass=" style_RSSAuthor">
by UniBul on 5/15/2012 </div>
<div style="margin-bottom: 0px; margin-top: 0px;">
<br /></div>
<div>
<span style="font-family: Arial, Helvetica, sans-serif;"><a class="imgCaptionAnchor" href="http://blog.unibulmerchantservices.com/the-more-you-use-your-debit-card-the-lower-your-credit-score/" shape="rect" track="on"><img align="left" border="0" height="73" hspace="5" name="ACCOUNT.IMAGE.3" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiLheZ4Md-rZ-3eiLau5dbLJalI0sAJLQ3LcIDdr3AX39qOqE6TQC91pLoy9YcStgtgR7WmcJnHbZy6qtkhRsvJQjRwEFo4orCYo4jzO993DhagWh8FW7qLaIq47GUdEx01sq7WbxAQaQbY/s1600/The+More+You+Use+Your+Debit+Card,+the+Lower+Your+Credit+Score.jpg" style="text-align: left;" vspace="5" width="93" /></a> <span style="font-family: Arial, Helvetica, sans-serif; font-size: 12pt;">That is the conclusion of a recent study by two researchers from the Federal Reserve Bank of Boston. The economists say that they set out to verify the anecdotal negative relationship between the use of debit cards and credit scores and have indeed confirmed the validity of this common assumption.</span></span></div>
<div align="right" style="margin-left: 30px; text-align: right;">
<span style="font-family: Arial, Helvetica, sans-serif;"><a href="http://blog.unibulmerchantservices.com/the-more-you-use-your-debit-card-the-lower-your-credit-score/" linktype="1" shape="rect" style="color: #ff950c; text-decoration: underline;" target="_blank" track="on">Read more.</a></span></div>
<div style="margin-bottom: 0px; margin-top: 0px;">
<br /></div>
</td>
</tr>
</tbody>
</table>
<br />
<table border="0" cellpadding="10" cellspacing="0" id="textEdit" style="display: table;">
<tbody>
<tr>
<td align="left" style="color: black; font-family: Georgia, 'Times New Roman', Times, serif; font-size: 12pt; text-align: left;" styleclass=" style_MainText" valign="top"><div style="color: black; font-family: Arial, Helvetica, sans-serif; font-size: 18pt; letter-spacing: -1px; text-align: left;" styleclass=" style_Headers">
<span style="color: #ff950c; font-size: 16pt;"><strong>Prepaid Cards Keep Getting Better</strong></span></div>
<div style="color: #666666; font-family: Arial, Helvetica, sans-serif; font-size: 8pt; letter-spacing: normal; text-align: left;" styleclass=" style_RSSAuthor">
by UniBul on 5/14/2012 </div>
<div style="margin-bottom: 0px; margin-top: 0px;">
<br /></div>
<div>
<span style="font-family: Arial, Helvetica, sans-serif;"><a class="imgCaptionAnchor" href="http://blog.unibulmerchantservices.com/prepaid-cards-keep-getting-better/" shape="rect" track="on"><img align="left" border="0" height="73" hspace="5" name="ACCOUNT.IMAGE.3" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiIhnnr2DR5GyO3f5Sw9eH4nBHfgZ7MK4xotSUnvPscPdiGgogelCO07b6LaXEgEPeh_5tTaDtxxJEupB6PvHwgjSjjbBwwUljAPeP2u6NT1Tw0YPt9dnqtjkWtaSvXi4IZEW0_GmuQon3e/s1600/Prepaid+Cards+Keep+Getting+Better+1.png" style="text-align: left;" vspace="5" width="100" /></a> <span style="font-family: Arial, Helvetica, sans-serif; font-size: 12pt;">Chase is the latest big bank to enter the prepaid card market in a serious way. AmEx's prepaid card is still the best option for everyone with a poor FICO score whose primary goal is to get back into the credit system, because it offers a path to a charge card. Everyone else, however, now has a choice between two very good prepaid cards.</span></span></div>
<div align="right" style="margin-left: 30px; text-align: right;">
<span style="font-family: Arial, Helvetica, sans-serif;"><a href="http://blog.unibulmerchantservices.com/prepaid-cards-keep-getting-better/" linktype="1" shape="rect" style="color: #ff950c; text-decoration: underline;" target="_blank" track="on">Read more.</a></span></div>
<div style="margin-bottom: 0px; margin-top: 0px;">
<br /></div>
</td>
</tr>
</tbody>
</table>
<br />
<table border="0" cellpadding="10" cellspacing="0" id="textEdit" style="display: table;">
<tbody>
<tr>
<td align="left" style="color: black; font-family: Georgia, 'Times New Roman', Times, serif; font-size: 12pt; text-align: left;" styleclass=" style_MainText" valign="top"><div style="color: black; font-family: Arial, Helvetica, sans-serif; font-size: 18pt; letter-spacing: -1px; text-align: left;" styleclass=" style_Headers">
<span style="color: #ff950c; font-size: 16pt;"><strong>Increased Lending, Higher Balances Lead to Lower Credit Card APRs</strong></span></div>
<div style="color: #666666; font-family: Arial, Helvetica, sans-serif; font-size: 8pt; letter-spacing: normal; text-align: left;" styleclass=" style_RSSAuthor">
by UniBul on 5/16/2012 </div>
<div style="margin-bottom: 0px; margin-top: 0px;">
<br /></div>
<div>
<span style="font-family: Arial, Helvetica, sans-serif;"><a class="imgCaptionAnchor" href="http://blog.unibulmerchantservices.com/increased-lending-higher-balances-lead-to-lower-credit-card-aprs/" shape="rect" track="on"><img align="left" border="0" height="73" hspace="5" name="ACCOUNT.IMAGE.3" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgYexUYsuN28iBE6V-Zm740WmDGMfWR2B8ynrRmxuaMCOSOR3yDTQYAL-X0YQQ1tKJg7G7bP0iVrHKyNJBcBOpGzxPqh-FvyCixA90mGVEeLRpovGFIfBy3ly8if9kjkSBMzGfCa6n9hPbN/s1600/Increased+Lending,+Higher+Balances+Lead+to+Lower+Credit+Card+APRs.jpg" style="text-align: left;" vspace="5" width="107" /></a> <span style="font-family: Arial, Helvetica, sans-serif; font-size: 12pt;">That is how two Cleveland Fed researchers interpret the fall of credit card interest rates in the past two years. They find an inverse relationship between the changes in the interest rate and the outstanding credit card debt.</span></span></div>
<div align="right" style="margin-left: 30px; text-align: right;">
<span style="font-family: Arial, Helvetica, sans-serif;"><a href="http://blog.unibulmerchantservices.com/increased-lending-higher-balances-lead-to-lower-credit-card-aprs/" linktype="1" shape="rect" style="color: #ff950c; text-decoration: underline;" target="_blank" track="on">Read more.</a></span></div>
<div style="margin-bottom: 0px; margin-top: 0px;">
<br /></div>
</td>
</tr>
</tbody>
</table>
<br />
<table border="0" cellpadding="10" cellspacing="0" id="textEdit" style="display: table;">
<tbody>
<tr>
<td align="left" style="color: black; font-family: Georgia, 'Times New Roman', Times, serif; font-size: 12pt; text-align: left;" styleclass=" style_MainText" valign="top"><div style="color: black; font-family: Arial, Helvetica, sans-serif; font-size: 18pt; letter-spacing: -1px; text-align: left;" styleclass=" style_Headers">
<span style="color: #ff950c; font-size: 16pt;"><strong>Americans Are Slashing Credit Card Debt and Other Facts</strong></span></div>
<div style="color: #666666; font-family: Arial, Helvetica, sans-serif; font-size: 8pt; letter-spacing: normal; text-align: left;" styleclass=" style_RSSAuthor">
by UniBul on 5/12/2012 </div>
<div style="margin-bottom: 0px; margin-top: 0px;">
<br /></div>
<div>
<span style="font-family: Arial, Helvetica, sans-serif;"><a class="imgCaptionAnchor" href="http://blog.unibulmerchantservices.com/americans-are-slashing-credit-card-debt-and-other-facts/" shape="rect" track="on"><img align="left" border="0" height="73" hspace="5" name="ACCOUNT.IMAGE.3" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhAfxwk-NZvF450VZDhYJNJp2FasQtSBBCHzL8rY9PVOP55fT2r6WUk7S4Tnu4MVC62sZ_zTyvG4Ke86HavINQ7BQN3LifL0rzlEq09sxxGypiBQO52UFXqMbg0WjLqKt14QIbkiDwllzSz/s1600/Americans+Are+Slashing+Credit+Card+Debt+and+Other+Facts+6.jpg" style="text-align: left;" vspace="5" width="109" /></a> <span style="font-family: Arial, Helvetica, sans-serif; font-size: 12pt;">We've been tracking the various credit card statistics in real time on our blog, but I thought that we could all benefit from a summary of what has taken place so far and from some historical perspective. So here are some charts for you.
</span></span></div>
<div align="right" style="margin-left: 30px; text-align: right;">
<span style="font-family: Arial, Helvetica, sans-serif;"><a href="http://blog.unibulmerchantservices.com/americans-are-slashing-credit-card-debt-and-other-facts/" linktype="1" shape="rect" style="color: #ff950c; text-decoration: underline;" target="_blank" track="on">Read more.</a></span></div>
<div style="margin-bottom: 0px; margin-top: 0px;">
<br /></div>
</td>
</tr>
</tbody>
</table>
<br />
<table border="0" cellpadding="0" cellspacing="10" id="textEdit" style="text-align: center;">
<tbody>
<tr>
<td align="left" style="text-align: left;" valign="bottom" width="36"><a href="http://www.facebook.com/UniBul" linktype="facebook" shape="rect"><img alt="Find UniBul Merchant Services on Facebook!" border="0" height="36" src="https://imgssl.f1.constantcontact.com/ui/images1/ic_fbk_36.png" width="36" /></a></td>
<td align="left" style="text-align: left;" valign="bottom" width="36"><a href="http://www.twitter.com/UniBul" linktype="twitter" shape="rect"><img alt="Follow UniBul Merchant Services on Twitter!" border="0" height="36" src="https://imgssl.constantcontact.com/ui/images1/ic_twit_36.png" width="36" /></a></td>
<td align="left" style="text-align: left;" valign="bottom" width="36"><a href="http://www.linkedin.com/groups/Merchant-Account-Services-107582?gid=107582&trk=hb_side_g" linktype="linkedin" shape="rect"><img alt="Connect with UniBul Merchant Services on LinkedIn!" border="0" height="36" src="https://imgssl.constantcontact.com/ui/images1/ic_lkdin_36.png" width="36" /></a></td>
<td align="left" style="text-align: left;" valign="bottom" width="36"><a href="http://blog.unibulmerchantservices.com/" linktype="blog" shape="rect"><img alt="Read our Blog!" border="0" height="36" src="https://imgssl.constantcontact.com/ui/images1/ic_blog_36.png" width="36" /></a></td>
<td align="right" style="color: black; font-family: Arial, Helvetica, sans-serif; font-size: 12pt; text-align: right;"><br /></td>
</tr>
</tbody>
</table>msshttp://www.blogger.com/profile/02682453100579738680noreply@blogger.com0tag:blogger.com,1999:blog-8887473741874669103.post-6215295773592828302010-01-07T18:35:00.004-05:002011-02-07T00:00:21.690-05:00Screening New Merchants<a href="http://blog.unibulmerchantservices.com/4-steps-to-screening-merchant-account-applicants"><img id="BLOGGER_PHOTO_ID_5570807253103533506" style="FLOAT: right; MARGIN: 0px 0px 10px 10px; WIDTH: 320px; CURSOR: hand; HEIGHT: 218px" alt="" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiVWQ-x60ZnQD1p3oYFykSA-DAHPmbeBYBGoopSQ7OUFOND7wRNPLr2-GJCYQavFtlpbV0X3aLH6VjaRwKYcfQYA4bgo06V5ZIV-HXVpWm-a_UtGq1vLJfZtkB49X5_A-_7II3h0Okp9cIA/s320/1130Bucks-NPSL-blog480.jpg" border="0" title="4 Steps to Screening Merchant Account Applicants" alt="4 Steps to Screening Merchant Account Applicants"/></a><br /><div>Before signing a merchant agreement, acquiring banks must verify that the merchant that is applying for a merchant account is a valid business. Such verification must include at least all of the following:<br /><br /><br /><ul><br /><br /><li>Credit check, background investigations, and reference checks of the merchant.<br /><br />If the credit check of the merchant raises questions, the acquirer also should conduct a credit check of:<br /><br /><br /><ul><br /><br /><br /><li>The owner, if the merchant is a sole proprietor; or</li><br /><br /><li>The partners, if the merchant is a partnership; or</li><br /><br /><li>The principal shareholders, if the merchant is a corporation.</li></ul></li><br /><br /><li>Inspection of the premises and records to ensure the merchant has the proper facilities, equipment, inventory, agreements and personnel required and if necessary, license or permit and other capabilities to conduct the business. If the merchant has more than one outlet, the acquirer must inspect at least one outlet from which it will acquire card transactions.</li><br /><br /><li>Inquiry to the Member Alert to Control (High-risk) Merchants (MATCH) system. If an acquirer chooses to enter into a merchant agreement with a merchant that is listed in the MATCH system, the acquirer will be responsible for all fraudulent transactions.</li><br /><br /><li>Investigation of the merchant’s previous merchant agreements.</li></ul>An acquirer is not required to conduct a credit check of a public or private company that has annual sales revenue in excess of $50 million (or the foreign currency equivalent), provided the acquirer reviews, and finds satisfactory, the most recent annual report of the merchant, including audited financial statements. A private company that does not have a recent audited financial statement is subject to a credit check and inspection even if its annual sales revenue exceeds $50 million.<br /><br /><!-- AddThis Button BEGIN --><br /><br /><script type="text/javascript">// <![CDATA[ addthis_pub = 'Merchant Account'; addthis_brand = 'Merchant Account'; addthis_options = 'favorites, email, digg, delicious, myspace, facebook, google, live, more'; // ]]></script><br /><br /><a onmouseover="return addthis_open(this, '', '[URL]', '[TITLE]')" title="Bookmark and Share" onclick="return addthis_sendto()" onmouseout="addthis_close()" href="http://www.addthis.com/bookmark.php"><img height="16" alt="" src="http://s9.addthis.com/button1-bm.gif" width="125" border="0" /></a><br /><br /><script src="http://s7.addthis.com/js/152/addthis_widget.js" type="text/javascript"></script><br /><br /><br /><!-- AddThis Button END --></div>msshttp://www.blogger.com/profile/02682453100579738680noreply@blogger.com0tag:blogger.com,1999:blog-8887473741874669103.post-88312018974915357202009-12-26T13:16:00.002-05:002009-12-31T19:06:39.659-05:00MasterCard Fraud Loss Control Program StandardsIn order to be eligible for counterfeit loss reimbursement, a member bank must make a good-faith attempt to demonstrate the existence and use of meaningful controls to limit total fraud losses and losses for all fraud types.<br /><br /><b>Acquirer Fraud Loss Control Programs</b><br /><br />An acquirer's fraud loss control program must meet the following minimum requirements, and preferably will include the recommended additional parameters. The program must automatically generate daily fraud monitoring reports or real-time alerts. Acquirer staff trained to identify potential fraud must analyze the data in these reports within 24 hours. To comply with the fraud loss control standards, acquirers also must transmit complete and unaltered data in all card-read authorization request messages, and also CVC 2 for all card not present (formerly MO / TO), voice, and e-commerce transactions.<br /><br />Additionally, acquirers with high fraud levels must:<br /><ul><li>Install "read and display" terminals in areas determined to be at high risk for fraud or counterfeit activity, or<br /></li><li>Install EMV chip terminals.<br /></li></ul><b>Acquirer Authorization Monitoring Requirements</b><br /><br />Daily reports or real-time alerts monitoring merchant authorization requests must be generated at the latest on the day following the authorization request, and must be based on the following parameters:<br /><ul><li>Number of authorization requests above a threshold set by the acquirer for that merchant.</li> <li>Ratio of non-card-read to card-read transactions that is above the threshold set by the acquirer for that merchant.</li> <li>PAN key entry ratio that is above threshold set by the acquirer for that merchant.</li> <li>Repeated authorization requests for the same amount or the same cardholder account.</li> <li>Increased number of authorization requests.</li> <li>"Out of pattern" fallback transaction volume.<br /></li></ul><b>Acquirer Merchant Deposit Monitoring Requirements</b><br /><br />Daily reports or real-time alerts monitoring merchant deposits must be generated at the latest on the day following the deposit, and must be based on the following parameters:<br /><ul><li>Increases in merchant deposit volume.</li><li>Increase in a merchant's average ticket size and number of transactions per deposit.</li><li>Change in frequency of deposits.</li><li>Frequency of transactions on the same cardholder account, including credit transactions.</li><li>Unusual number of credits, or credit dollar volume, exceeding a level of sales dollar volume appropriate to the merchant category.</li><li>Large credit transaction amounts, significantly greater than the average ticket size for the merchant's sales.</li><li>Credits issued subsequent to the receipt of a chargeback with the same account number and followed by a second presentment.</li><li>Credits issued to an account number not used previously at the merchant location.</li></ul><strong>90-day Rule</strong><br /><br />The acquirer must compare daily deposits against the average transaction count and amount for each merchant over a period of at least 90 days, to lessen the effect of normal variances in a merchant's business. For new merchants, the acquirer should compare the average transaction count and amount for other merchants within the same merchant code (MCC) assigned to the merchant. In the event that suspicious credit or refund transaction activity is identified, if appropriate, the acquirer should consider the suspension of transactions pending further investigation.<br /><br /><strong>150% Recommendation</strong><br /><br />To optimize the effectiveness of fraud analysis staff, merchants that appear in the monitoring reports should exceed the average by 150% or more. However, the amount over the average is at the acquirer's discretion.<br /><br /><b>Recommended Additional Acquirer Monitoring</b><br /><br />MasterCard recommends that acquirers additionally monitor the following parameters:<br /><ul><li>Fallback methods.</li><li>Credit transactions (such as refunds) and merchant authorization reversals.</li><li>Transactions conducted at high-risk merchants.</li><li>Personal account number (PAN) key-entry transactions exceeding ratio.</li><li>Abnormal hours or seasons.</li><li>Inactive merchants.</li><li>Transactions with no approval code.</li><li>Transactions that were declined.</li><li>Inconsistent authorization and clearing data elements for the same transactions.</li></ul><!-- AddThis Button BEGIN --><script type="text/javascript"><!-- addthis_pub = 'Merchant Account'; addthis_brand = 'Merchant Account'; addthis_options = 'favorites, email, digg, delicious, myspace, facebook, google, live, more'; // --></script><a title="Bookmark and Share" onclick="return addthis_sendto()" onmouseover="return addthis_open(this, '', '[URL]', '[TITLE]')" onmouseout="addthis_close()" href="http://www.addthis.com/bookmark.php"><img src="http://s9.addthis.com/button1-bm.gif" alt="" border="0" height="16" width="125" /></a><script src="http://s7.addthis.com/js/152/addthis_widget.js" type="text/javascript"></script><br /><!-- AddThis Button END -->msshttp://www.blogger.com/profile/02682453100579738680noreply@blogger.com0tag:blogger.com,1999:blog-8887473741874669103.post-13448153256137490332009-12-14T19:33:00.001-05:002012-06-06T23:19:32.299-04:00Reporting Fraudulent Use of CardsAll MasterCard member banks must report accurately and completely the fraudulent use of MasterCard cards to the System to Avoid Fraud Effectively (SAFE) at least once a month and within 60 days from the date of the transaction, or 30 days from the date of cardholder notification. If there are no fraudulent transactions to report during the month, member banks must submit a Fraud Negative Report (FDN) Record when transmitting their transactions to SAFE or use the Report No Fraud feature of SAFE OnLine.<br />
<br />
<b>Reporting by the Issuer</b><br />
<br />
MasterCard issuers must submit all fraudulent transactions on its MasterCard accounts to SAFE on a monthly basis. For the benefit of all members, MasterCard analyzes the data and produces statistics relating to the fraudulent use of MasterCard accounts and all chargebacks that originate from transactions using accounts with a fraud status.<br />
<br />
An issuer must report fraudulent transactions even if it recovered losses through chargebacks, compliance cases, restitution, insurance, or any other means.<br />
<br />
<b>Reporting by the Acquirer</b><br />
<br />
An acquirer receiving a transaction that cannot be identified by a MasterCard BIN or member ID is liable for that transaction. If it is determined that the transaction is a fraudulent or counterfeit MasterCard transaction, the acquirer must notify, in writing, the Security and Risk Management Department of such an occurrence. This notification must include all mandatory information as described in the Security Systems Specifications manual.<br />
<br />
<script type="text/javascript">
<!-- addthis_pub = 'Merchant Account'; addthis_brand = 'Merchant Account'; addthis_options = 'favorites, email, digg, delicious, myspace, facebook, google, live, more'; // -->
</script><a href="http://www.addthis.com/bookmark.php" title="Bookmark and Share"><img alt="" border="0" height="16" src="http://s9.addthis.com/button1-bm.gif" width="125" /></a><script src="http://s7.addthis.com/js/152/addthis_widget.js" type="text/javascript">
</script>msshttp://www.blogger.com/profile/02682453100579738680noreply@blogger.com0tag:blogger.com,1999:blog-8887473741874669103.post-53680677732966193552009-12-04T19:05:00.003-05:002012-06-06T23:20:01.819-04:00MasterCard Rewards for Capturing a CardThe acquirer may pay the merchant reward for capturing a MasterCard card in accordance with local practices. The acquirer must follow these Standards when paying a reward:
<br />
<ul>
<li>Pay no less than $50 to the merchant capturing a card listed on the Electronic Warning Bulletin file or in the Warning Notice.</li>
<li>Pay the merchant $100, if a merchant initiates an authorization call because of a suspicious transaction or captures a card not listed in the Electronic Warning Bulletin file or in the Warning Notice.</li>
<li>Pay a reward to a financial institution for the capture of another issuer's card if it is the acquirer's practice to pay its tellers rewards for picking up its own cards. The amount of the reward should be the same amount paid for the capture of the acquirer's own cards.</li>
<li>Charge the issuer for reimbursement of the reward paid upon dispatching each captured card. The Fee Collection / 1740 message with an IPM message reason code (data element 25) equal to 7601 will settle the reward.</li>
</ul>
<b>Reward Amounts</b>
<br />
<br />
The acquirer should follow these guidelines for determining reward amounts.
<br />
<br />
<link href="file:///C:%5CUsers%5CMetodi%5CAppData%5CLocal%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_filelist.xml" rel="File-List"></link><link href="file:///C:%5CUsers%5CMetodi%5CAppData%5CLocal%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_themedata.thmx" rel="themeData"></link><link href="file:///C:%5CUsers%5CMetodi%5CAppData%5CLocal%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_colorschememapping.xml" rel="colorSchemeMapping"></link><style>
<!-- /* Font Definitions */ @font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4; mso-font-charset:1; mso-generic-font-family:roman; mso-font-format:other; mso-font-pitch:variable; mso-font-signature:0 0 0 0 0 0;} @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4; mso-font-charset:204; mso-generic-font-family:swiss; mso-font-pitch:variable; mso-font-signature:-1610611985 1073750139 0 0 159 0;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-unhide:no; mso-style-qformat:yes; mso-style-parent:""; margin-top:0in; margin-right:0in; margin-bottom:10.0pt; margin-left:0in; line-height:150%; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:Calibri; mso-fareast-theme-font:minor-latin; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;} .MsoChpDefault {mso-style-type:export-only; mso-default-props:yes; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:Calibri; mso-fareast-theme-font:minor-latin; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;} .MsoPapDefault {mso-style-type:export-only; margin-bottom:10.0pt; line-height:150%;} @page Section1 {size:8.5in 11.0in; margin:70.85pt 70.85pt 70.85pt 70.85pt; mso-header-margin:.5in; mso-footer-margin:.5in; mso-paper-source:0;} div.Section1 {page:Section1;} -->
</style> <br />
<table border="1" cellpadding="0" cellspacing="0" class="MsoTableGrid" style="border-collapse: collapse; border: medium none; margin-left: 5.4pt;"> <tbody>
<tr> <td style="border: 1pt solid black; padding: 0in 5.4pt; width: 177.85pt;" width="237"><div class="MsoNormal" style="line-height: normal; margin-bottom: 0.0001pt;">
<b>IF the capture…<o:p></o:p></b></div>
</td> <td style="border-color: black black black -moz-use-text-color; border-style: solid solid solid none; border-width: 1pt 1pt 1pt medium; padding: 0in 5.4pt; width: 177.85pt;" width="237"><div class="MsoNormal" style="line-height: normal; margin-bottom: 0.0001pt;">
<b>THEN pay this amount…<o:p></o:p></b></div>
</td> </tr>
<tr> <td style="border-color: -moz-use-text-color black black; border-style: none solid solid; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 177.85pt;" width="237"><div class="MsoNormal" style="line-height: normal; margin-bottom: 0.0001pt;">
Resulted from a “Merchant Suspicious” phone call<o:p></o:p></div>
</td> <td style="border-color: -moz-use-text-color black black -moz-use-text-color; border-style: none solid solid none; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 177.85pt;" width="237"><div class="MsoNormal" style="line-height: normal; margin-bottom: 0.0001pt;">
$ 100<o:p></o:p></div>
</td> </tr>
<tr> <td style="border-color: -moz-use-text-color black black; border-style: none solid solid; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 177.85pt;" width="237"><div class="MsoNormal" style="line-height: normal; margin-bottom: 0.0001pt;">
Did not result from a “Merchant Suspicious” phone call<o:p></o:p></div>
</td> <td style="border-color: -moz-use-text-color black black -moz-use-text-color; border-style: none solid solid none; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 177.85pt;" width="237"><div class="MsoNormal" style="line-height: normal; margin-bottom: 0.0001pt;">
$50<o:p></o:p></div>
</td> </tr>
<tr> <td style="border-color: -moz-use-text-color black black; border-style: none solid solid; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 177.85pt;" width="237"><div class="MsoNormal" style="line-height: normal; margin-bottom: 0.0001pt;">
Leads to the capture of additional cards<o:p></o:p></div>
</td> <td style="border-color: -moz-use-text-color black black -moz-use-text-color; border-style: none solid solid none; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 177.85pt;" width="237"><div class="MsoNormal" style="line-height: normal; margin-bottom: 0.0001pt;">
$ 50 for each card captured, with a maximum total of $250 for any one incident<o:p></o:p></div>
</td> </tr>
</tbody></table>
<br />
The recovering member bank may collect an administrative fee of $15 for expenses incurred in processing the captured card. The capturing member may add this fee to the amount of the reward reimbursement or collect the fee independently, using the Fee Collection / 1740 message.
<br />
<br />
<b>Reimbursement of Rewards</b>
<br />
<br />
The following specifications apply to reward reimbursement:
<br />
<ul>
<li>Upon returning the card to the issuer, the acquirer will obtain reimbursement for the reward paid and the $15 fee by processing the Fee Collection / 1740 message.</li>
<li>If an acquirer returns a card to an issuer and a reward is not paid, the acquirer may collect a $15 fee by processing a Fee Collection / 1740 message record.</li>
<li>Upon receipt of the Interchange Card Recovery Form (ICA-6), the issuer should match it to the Fee Collection / 1740 message record based on the acquirer member ID, account number, and recovery date comparisons.</li>
<li>If an exempt member has an electronic reward payment processed, clearing receives the record by an information slip. The transaction is part of the Net Settlement System for settlement purposes.
</li>
</ul>
<script type="text/javascript">
<!-- addthis_pub = 'Merchant Account'; addthis_brand = 'Merchant Account'; addthis_options = 'favorites, email, digg, delicious, myspace, facebook, google, live, more'; // -->
</script><a href="http://www.addthis.com/bookmark.php" title="Bookmark and Share"><img alt="" border="0" height="16" src="http://s9.addthis.com/button1-bm.gif" width="125" /></a><script src="http://s7.addthis.com/js/152/addthis_widget.js" type="text/javascript">
</script>msshttp://www.blogger.com/profile/02682453100579738680noreply@blogger.com0tag:blogger.com,1999:blog-8887473741874669103.post-454346971451767912009-12-02T17:36:00.002-05:002009-12-02T17:54:12.352-05:00Point-of-Sale (POS) Card RetentionAcquirers and merchants are required to recover a card by reasonable and peaceful means if:<br /><ul><li>The card issuer advises the acquirer or merchant to recover the card in response to an authorization request.</li> <li>The Electronic Warning Bulletin file or an effective regional Warning Notice lists the account number.</li></ul>After recovering a card, the merchant must notify its authorization center or its acquirer and receive instructions for returning the card. If mailing the card, the merchant first should cut the card in half through the magnetic stripe.<br /><br /><b>Returning Recovered Cards</b><br /><br />The acquirer must follow these procedures when returning a recovered card to the issuer:<br /><ul><li>If the merchant has not already done so, the acquirer must cut the card in half vertically through the magnetic stripe.</li> <li>The acquirer must forward the recovered card to the issuer within five calendar days of receiving the card along with the first copy (white) of the Interchange Card Recovery Form (ICA-6). The additional copies are file copies for the acquirer's records. A recovered card must be returned to the security contact of the issuer.<br /></li></ul><b>Returning Counterfeit Cards</b><br /><br />The acquirer or merchant must return counterfeit cards to the issuer by following the instructions provided by its authorization center. The following information identifies an issuer:<br /> <ul><li>The issuers bank identification number (BIN) embossed on the front of the card.</li> <li>The member ID imprinted in the Card Source Identification area on the back of the card.</li></ul><!-- AddThis Button BEGIN --><script type="text/javascript"><!-- addthis_pub = 'Merchant Account'; addthis_brand = 'Merchant Account'; addthis_options = 'favorites, email, digg, delicious, myspace, facebook, google, live, more'; // --></script><a title="Bookmark and Share" onclick="return addthis_sendto()" onmouseover="return addthis_open(this, '', '[URL]', '[TITLE]')" onmouseout="addthis_close()" href="http://www.addthis.com/bookmark.php"><img src="http://s9.addthis.com/button1-bm.gif" alt="" border="0" height="16" width="125" /></a><script src="http://s7.addthis.com/js/152/addthis_widget.js" type="text/javascript"></script><br /><!-- AddThis Button END -->msshttp://www.blogger.com/profile/02682453100579738680noreply@blogger.com0tag:blogger.com,1999:blog-8887473741874669103.post-66968513660653108642009-11-16T16:40:00.005-05:002012-06-06T23:20:43.327-04:00Sales Receipt RequirementsBelow is a list of the types of sales receipts discussed in this post:<br />
<ul>
<li>Retail sale.</li>
<li>Credit.</li>
<li>Cash disbursement.</li>
<li>Information.</li>
</ul>
If the merchant uses a manual imprinter, the produced sales receipt is called a formset or slip. If a transaction begins at an electronic terminal, the merchant may substitute a terminal receipt for a formset. Terminal receipts have no prescribed physical specifications but must be numbered sequentially for reference purposes.<br />
<br />
<b>Formset Contents</b><br />
<br />
Each copy of a retail sale, credit, or cash disbursement formset must satisfy minimum statutory and regulatory requirements in the jurisdiction in which the slip originates and any applicable regulations, issued by the U.S. Board of Governors of the Federal Reserve System or other regulatory authorities, and must contain the following:<br />
<ul>
<li>In the case of retail sale and credit slips, a space for the description of goods, services, or other things of value sold by the merchant to the customer and the cost thereof, in sufficient detail to identify the transaction.</li>
<li>Adequate spaces for:<br /><ul>
<li>Customer's signature.</li>
<li>Card imprint and the merchant or bank identification plate imprint.</li>
<li>Date of the transaction.</li>
<li>Authorization number (except on credit slips).</li>
<li>Sales clerk's or teller's initials or department number.</li>
<li>Currency conversion field.</li>
<li>Merchant's signature on credit slips.</li>
<li>Description of the ID supplied by the cardholder on cash disbursements and retail sale slips for certain unique transactions.</li>
</ul>
</li>
<li>A legend clearly identifying the slip as a retail sale, credit, or cash disbursement and identifies the receiving party of each copy.</li>
<li>On the customer copy of the formset, the words (in English, local language, or both): "IMPORTANT—retain this copy for your records," or words to similar effect.</li>
<li>Such other contents as are not inconsistent with these rules.</li>
</ul>
It is recommended that each retail sale, credit, and cash disbursement slip identify the member bank that distributed the slip to the merchant.<br />
<br />
<b>Terminal Receipt Contents</b><br />
<br />
A terminal or other device at a point of sale (POS) must not display magnetic stripe track data other than card account number, expiration date, and cardholder name. Each copy of a POS terminal receipt must contain the following information:<br />
<ul>
<li>Doing Business As (DBA) merchant name, city and state, country, or the point of banking location.</li>
<li>Transaction date.</li>
<li>Card account number.</li>
<li>Transaction amount in the original transaction currency.</li>
<li>Adequate space for the customer's signature (required on merchant copy only).</li>
<li>Authorization approval code (except on credit receipts). Optionally, the acquirer also may print the transaction certificate, the application cryptogram, or both for EMV chip card transactions.</li>
<li>Merchant's signature on credit receipts only.</li>
</ul>
Each receipt must clearly identify the transaction as a retail sale, credit, or cash disbursement.<br />
<br />
<b>Primary Account Number Truncation</b><br />
<br />
ATM acquirers must truncate a minimum of four digits of the Primary Account Number (PAN). PAN truncation is also required for all receipts generated at Cardholder-Activated Terminals (CATs). PAN truncation is permitted for receipts generated at all other points of sale.<br />
<br />
The cardholder receipt generated by point of sale (POS) terminals, whether attended or unattended, must reflect only the last four (4) digits of the PAN. All preceding digits must be replaced with fill characters that are neither blank spaces nor numeric characters, such as "X," "*," or "#."<br />
<br />
<b>Truncation Considerations</b><br />
<br />
Truncating a greater number of digits, when compared to the total number of digits in the PAN, increases the effectiveness of the effort. However, it also increases the confusion and difficulty that cardholders may have reconciling their ATM terminal receipts to their monthly statements. The following practices are recommended:<br />
<ul>
<li>Truncation of the routing BIN alone, while helpful, may not prevent duplication of the PAN. It is possible to observe the card in use in order to obtain issuer identification.</li>
<li>Truncating the check digit and several other digits does not improve PAN security. Absent the check digit, calculation of several missing digits within the PAN, especially if the routing BIN also is truncated, is substantially more complicated and time consuming.</li>
<li>Truncating a small number of digits, when compared to the total number of digits in the PAN, reduces the effectiveness of the effort. It is possible to reconstruct a few missing digits by using a trial-and-error approach.</li>
<li>Truncating a greater number of digits, when compared to the total number of digits in the PAN, increases the effectiveness of the effort.</li>
</ul>
<b>Electronic Signature Capture Technology (ESCT)</b><br />
<br />
An acquirer using Electronic Signature Capture Technology (ESCT) must ensure that:<br />
<ul>
<li>Proper electronic data processing (EDP) controls and security are in place, so that digitized signatures are recreated on a transaction-specific basis. The acquirer may recreate the signature captured for a specific transaction only in response to a retrieval request for the transaction.</li>
<li>Appropriate controls exist over employees with authorized access to digitized signatures maintained in the acquirer or merchant computers. Only employees and agents with a "need to know" should be able to access the stored, electronically captured signatures.</li>
<li>Digitized signatures are not accessed or used against applicable standards and regulations.</li>
</ul>
<script type="text/javascript">
<!-- addthis_pub = 'Merchant Account'; addthis_brand = 'Merchant Account'; addthis_options = 'favorites, email, digg, delicious, myspace, facebook, google, live, more'; // -->
</script><a href="http://www.addthis.com/bookmark.php" title="Bookmark and Share"><img alt="" border="0" height="16" src="http://s9.addthis.com/button1-bm.gif" width="125" /></a><script src="http://s7.addthis.com/js/152/addthis_widget.js" type="text/javascript">
</script>msshttp://www.blogger.com/profile/02682453100579738680noreply@blogger.com0tag:blogger.com,1999:blog-8887473741874669103.post-20178981147349437492009-10-12T11:41:00.011-04:002009-11-10T12:53:02.812-05:00In-flight Commerce Terminals / Level 4 RequirementsThe following requirements apply to In-flight Commerce Terminals / Level 4.
<br /><ol><li><strong>Acquirer / Service Provider requirements and transaction identification specifications:</strong>
<br /><ul><li>Acquiring banks must ensure timely delivery and installation of the IFC Blocked Gaming File to gaming service providers. IFC Blocked Gaming File access is required before every gaming transaction.</li> <li>The acquiring bank must identify in-flight commerce services or merchandise with the most appropriate merchant category code (MCC) in the authorization message and merchant business code (MCC) in First Presentment / 1240 messages. If an airline also acts as the service provider, the acquiring bank may not use an airline MCC but must assign the proper MCC for each type of IFC transaction. The following list of IFC transaction types must be identified with the designated MCC.
<br />
<br /><meta equiv="Content-Type" content="text/html; charset=utf-8"><meta name="ProgId" content="Word.Document"><meta name="Generator" content="Microsoft Word 12"><meta name="Originator" content="Microsoft Word 12"><link rel="File-List" href="file:///C:%5CUsers%5CMetodi%5CAppData%5CLocal%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_filelist.xml"><link rel="themeData" href="file:///C:%5CUsers%5CMetodi%5CAppData%5CLocal%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_themedata.thmx"><link rel="colorSchemeMapping" href="file:///C:%5CUsers%5CMetodi%5CAppData%5CLocal%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_colorschememapping.xml"><!--[if gte mso 9]><xml> <w:worddocument> <w:view>Normal</w:View> <w:zoom>0</w:Zoom> <w:trackmoves/> <w:trackformatting/> <w:punctuationkerning/> <w:validateagainstschemas/> <w:saveifxmlinvalid>false</w:SaveIfXMLInvalid> <w:ignoremixedcontent>false</w:IgnoreMixedContent> <w:alwaysshowplaceholdertext>false</w:AlwaysShowPlaceholderText> <w:donotpromoteqf/> <w:lidthemeother>EN-US</w:LidThemeOther> <w:lidthemeasian>X-NONE</w:LidThemeAsian> <w:lidthemecomplexscript>X-NONE</w:LidThemeComplexScript> <w:compatibility> <w:breakwrappedtables/> <w:snaptogridincell/> <w:wraptextwithpunct/> <w:useasianbreakrules/> <w:dontgrowautofit/> <w:splitpgbreakandparamark/> <w:dontvertaligncellwithsp/> <w:dontbreakconstrainedforcedtables/> <w:dontvertalignintxbx/> <w:word11kerningpairs/> <w:cachedcolbalance/> </w:Compatibility> <w:browserlevel>MicrosoftInternetExplorer4</w:BrowserLevel> <m:mathpr> <m:mathfont val="Cambria Math"> <m:brkbin val="before"> <m:brkbinsub val="--"> <m:smallfrac val="off"> <m:dispdef/> <m:lmargin val="0"> <m:rmargin val="0"> <m:defjc val="centerGroup"> <m:wrapindent val="1440"> <m:intlim val="subSup"> <m:narylim val="undOvr"> </m:mathPr></w:WordDocument> </xml><![endif]--><!--[if gte mso 9]><xml> <w:latentstyles deflockedstate="false" defunhidewhenused="true" defsemihidden="true" defqformat="false" defpriority="99" latentstylecount="267"> <w:lsdexception locked="false" priority="0" semihidden="false" unhidewhenused="false" qformat="true" name="Normal"> <w:lsdexception locked="false" priority="9" semihidden="false" unhidewhenused="false" qformat="true" name="heading 1"> <w:lsdexception locked="false" priority="9" qformat="true" name="heading 2"> <w:lsdexception locked="false" priority="9" qformat="true" name="heading 3"> <w:lsdexception locked="false" priority="9" qformat="true" name="heading 4"> <w:lsdexception locked="false" priority="9" qformat="true" name="heading 5"> <w:lsdexception locked="false" priority="9" qformat="true" name="heading 6"> <w:lsdexception locked="false" priority="9" qformat="true" name="heading 7"> <w:lsdexception locked="false" priority="9" qformat="true" name="heading 8"> <w:lsdexception locked="false" priority="9" qformat="true" name="heading 9"> <w:lsdexception locked="false" priority="39" name="toc 1"> <w:lsdexception locked="false" priority="39" name="toc 2"> <w:lsdexception locked="false" priority="39" name="toc 3"> <w:lsdexception locked="false" priority="39" name="toc 4"> <w:lsdexception locked="false" priority="39" name="toc 5"> <w:lsdexception locked="false" priority="39" name="toc 6"> <w:lsdexception locked="false" priority="39" name="toc 7"> <w:lsdexception locked="false" priority="39" name="toc 8"> <w:lsdexception locked="false" priority="39" name="toc 9"> <w:lsdexception locked="false" priority="35" qformat="true" name="caption"> <w:lsdexception locked="false" priority="10" semihidden="false" unhidewhenused="false" qformat="true" name="Title"> <w:lsdexception locked="false" priority="1" name="Default Paragraph Font"> <w:lsdexception locked="false" priority="11" semihidden="false" unhidewhenused="false" qformat="true" name="Subtitle"> <w:lsdexception locked="false" priority="22" semihidden="false" unhidewhenused="false" qformat="true" name="Strong"> <w:lsdexception locked="false" priority="20" semihidden="false" unhidewhenused="false" qformat="true" name="Emphasis"> <w:lsdexception locked="false" priority="59" semihidden="false" unhidewhenused="false" name="Table Grid"> <w:lsdexception locked="false" unhidewhenused="false" name="Placeholder Text"> <w:lsdexception locked="false" priority="1" semihidden="false" unhidewhenused="false" qformat="true" name="No Spacing"> <w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading"> <w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List"> <w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid"> <w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1"> <w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2"> <w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1"> <w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2"> <w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1"> <w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2"> <w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3"> <w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List"> <w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading"> <w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List"> <w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid"> <w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 1"> <w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 1"> <w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 1"> <w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 1"> <w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 1"> <w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 1"> <w:lsdexception locked="false" unhidewhenused="false" name="Revision"> <w:lsdexception locked="false" priority="34" semihidden="false" unhidewhenused="false" qformat="true" name="List Paragraph"> <w:lsdexception locked="false" priority="29" semihidden="false" unhidewhenused="false" qformat="true" name="Quote"> <w:lsdexception locked="false" priority="30" semihidden="false" unhidewhenused="false" qformat="true" name="Intense Quote"> <w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 1"> <w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 1"> <w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 1"> <w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 1"> <w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 1"> <w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 1"> <w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 1"> <w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 1"> <w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 2"> <w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 2"> <w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 2"> <w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 2"> <w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 2"> <w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 2"> <w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 2"> <w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 2"> <w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 2"> <w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 2"> <w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 2"> <w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 2"> <w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 2"> <w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 2"> <w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 3"> <w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 3"> <w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 3"> <w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 3"> <w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 3"> <w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 3"> <w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 3"> <w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 3"> <w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 3"> <w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 3"> <w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 3"> <w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 3"> <w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 3"> <w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 3"> <w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 4"> <w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 4"> <w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 4"> <w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 4"> <w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 4"> <w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 4"> <w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 4"> <w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 4"> <w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 4"> <w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 4"> <w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 4"> <w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 4"> <w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 4"> <w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 4"> <w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 5"> <w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 5"> <w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 5"> <w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 5"> <w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 5"> <w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 5"> <w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 5"> <w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 5"> <w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 5"> <w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 5"> <w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 5"> <w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 5"> <w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 5"> <w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 5"> <w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 6"> <w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 6"> <w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 6"> <w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 6"> <w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 6"> <w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 6"> <w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 6"> <w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 6"> <w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 6"> <w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 6"> <w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 6"> <w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 6"> <w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 6"> <w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 6"> <w:lsdexception locked="false" priority="19" semihidden="false" unhidewhenused="false" qformat="true" name="Subtle Emphasis"> <w:lsdexception locked="false" priority="21" semihidden="false" unhidewhenused="false" qformat="true" name="Intense Emphasis"> <w:lsdexception locked="false" priority="31" semihidden="false" unhidewhenused="false" qformat="true" name="Subtle Reference"> <w:lsdexception locked="false" priority="32" semihidden="false" unhidewhenused="false" qformat="true" name="Intense Reference"> <w:lsdexception locked="false" priority="33" semihidden="false" unhidewhenused="false" qformat="true" name="Book Title"> <w:lsdexception locked="false" priority="37" name="Bibliography"> <w:lsdexception locked="false" priority="39" qformat="true" name="TOC Heading"> </w:LatentStyles> </xml><![endif]--><style> <!-- /* Font Definitions */ @font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4; mso-font-charset:1; mso-generic-font-family:roman; mso-font-format:other; mso-font-pitch:variable; mso-font-signature:0 0 0 0 0 0;} @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4; mso-font-charset:204; mso-generic-font-family:swiss; mso-font-pitch:variable; mso-font-signature:-1610611985 1073750139 0 0 159 0;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-unhide:no; mso-style-qformat:yes; mso-style-parent:""; margin-top:0in; margin-right:0in; margin-bottom:10.0pt; margin-left:0in; line-height:150%; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:Calibri; mso-fareast-theme-font:minor-latin; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;} .MsoChpDefault {mso-style-type:export-only; mso-default-props:yes; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:Calibri; mso-fareast-theme-font:minor-latin; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;} .MsoPapDefault {mso-style-type:export-only; margin-bottom:10.0pt; line-height:150%;} @page Section1 {size:8.5in 11.0in; margin:70.85pt 70.85pt 70.85pt 70.85pt; mso-header-margin:.5in; mso-footer-margin:.5in; mso-paper-source:0;} div.Section1 {page:Section1;} --> </style><!--[if gte mso 10]> <style> /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-qformat:yes; mso-style-parent:""; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin-top:0in; mso-para-margin-right:0in; mso-para-margin-bottom:10.0pt; mso-para-margin-left:0in; line-height:150%; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:"Times New Roman"; mso-fareast-theme-font:minor-fareast; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin;} table.MsoTableGrid {mso-style-name:"Table Grid"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-priority:59; mso-style-unhide:no; border:solid black 1.0pt; mso-border-themecolor:text1; mso-border-alt:solid black .5pt; mso-border-themecolor:text1; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-border-insideh:.5pt solid black; mso-border-insideh-themecolor:text1; mso-border-insidev:.5pt solid black; mso-border-insidev-themecolor:text1; mso-para-margin:0in; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin;} </style> <![endif]--> <table class="MsoTableGrid" style="border: medium none ; border-collapse: collapse;" border="1" cellpadding="0" cellspacing="0"> <tbody><tr style=""> <td style="border: 1pt solid black; padding: 0in 5.4pt; width: 171.9pt;" valign="top" width="229"> <p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"><b style="">IFC Transaction Type<o:p></o:p></b></p> </td> <td style="border-style: solid solid solid none; border-color: black black black -moz-use-text-color; border-width: 1pt 1pt 1pt medium; padding: 0in 5.4pt; width: 81pt;" valign="top" width="108"> <p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"><b style="">MCC<o:p></o:p></b></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color black black; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 171.9pt;" valign="top" width="229"> <p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;">Catalog card acceptor<o:p></o:p></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color black black -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 81pt;" valign="top" width="108"> <p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;">5964<o:p></o:p></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color black black; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 171.9pt;" valign="top" width="229"> <p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;">Duty-free store<o:p></o:p></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color black black -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 81pt;" valign="top" width="108"> <p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;">5309<o:p></o:p></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color black black; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 171.9pt;" valign="top" width="229"> <p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;">Gaming<o:p></o:p></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color black black -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 81pt;" valign="top" width="108"> <p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;">7995<o:p></o:p></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color black black; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 171.9pt;" valign="top" width="229"> <p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;">Miscellaneous services<o:p></o:p></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color black black -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 81pt;" valign="top" width="108"> <p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;">7299<o:p></o:p></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color black black; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 171.9pt;" valign="top" width="229"> <p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;">Video game<o:p></o:p></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color black black -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 81pt;" valign="top" width="108"> <p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;">7994<o:p></o:p></p> </td> </tr> </tbody></table>
<br /></li> <li>Transactions must be consolidated by MCC, per flight, for each MasterCard cardholder account. "Flight" is defined as one or more segments of a continuous air flight with the same flight number.</li> <li>The acquiring bank must identify the transaction with the most appropriate transaction category code (TCC) in the authorization request message.
<br />
<br /><meta equiv="Content-Type" content="text/html; charset=utf-8"><meta name="ProgId" content="Word.Document"><meta name="Generator" content="Microsoft Word 12"><meta name="Originator" content="Microsoft Word 12"><link rel="File-List" href="file:///C:%5CUsers%5CMetodi%5CAppData%5CLocal%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_filelist.xml"><link rel="themeData" href="file:///C:%5CUsers%5CMetodi%5CAppData%5CLocal%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_themedata.thmx"><link rel="colorSchemeMapping" href="file:///C:%5CUsers%5CMetodi%5CAppData%5CLocal%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_colorschememapping.xml"><!--[if gte mso 9]><xml> <w:worddocument> <w:view>Normal</w:View> <w:zoom>0</w:Zoom> <w:trackmoves/> <w:trackformatting/> <w:punctuationkerning/> <w:validateagainstschemas/> <w:saveifxmlinvalid>false</w:SaveIfXMLInvalid> <w:ignoremixedcontent>false</w:IgnoreMixedContent> <w:alwaysshowplaceholdertext>false</w:AlwaysShowPlaceholderText> <w:donotpromoteqf/> <w:lidthemeother>EN-US</w:LidThemeOther> <w:lidthemeasian>X-NONE</w:LidThemeAsian> <w:lidthemecomplexscript>X-NONE</w:LidThemeComplexScript> <w:compatibility> <w:breakwrappedtables/> <w:snaptogridincell/> <w:wraptextwithpunct/> <w:useasianbreakrules/> <w:dontgrowautofit/> <w:splitpgbreakandparamark/> <w:dontvertaligncellwithsp/> <w:dontbreakconstrainedforcedtables/> <w:dontvertalignintxbx/> <w:word11kerningpairs/> <w:cachedcolbalance/> </w:Compatibility> <w:browserlevel>MicrosoftInternetExplorer4</w:BrowserLevel> <m:mathpr> <m:mathfont val="Cambria Math"> <m:brkbin val="before"> <m:brkbinsub val="--"> <m:smallfrac val="off"> <m:dispdef/> <m:lmargin val="0"> <m:rmargin val="0"> <m:defjc val="centerGroup"> <m:wrapindent val="1440"> <m:intlim val="subSup"> <m:narylim val="undOvr"> </m:mathPr></w:WordDocument> </xml><![endif]--><!--[if gte mso 9]><xml> <w:latentstyles deflockedstate="false" defunhidewhenused="true" defsemihidden="true" defqformat="false" defpriority="99" latentstylecount="267"> <w:lsdexception locked="false" priority="0" semihidden="false" unhidewhenused="false" qformat="true" name="Normal"> <w:lsdexception locked="false" priority="9" semihidden="false" unhidewhenused="false" qformat="true" name="heading 1"> <w:lsdexception locked="false" priority="9" qformat="true" name="heading 2"> <w:lsdexception locked="false" priority="9" qformat="true" name="heading 3"> <w:lsdexception locked="false" priority="9" qformat="true" name="heading 4"> <w:lsdexception locked="false" priority="9" qformat="true" name="heading 5"> <w:lsdexception locked="false" priority="9" qformat="true" name="heading 6"> <w:lsdexception locked="false" priority="9" qformat="true" name="heading 7"> <w:lsdexception locked="false" priority="9" qformat="true" name="heading 8"> <w:lsdexception locked="false" priority="9" qformat="true" name="heading 9"> <w:lsdexception locked="false" priority="39" name="toc 1"> <w:lsdexception locked="false" priority="39" name="toc 2"> <w:lsdexception locked="false" priority="39" name="toc 3"> <w:lsdexception locked="false" priority="39" name="toc 4"> <w:lsdexception locked="false" priority="39" name="toc 5"> <w:lsdexception locked="false" priority="39" name="toc 6"> <w:lsdexception locked="false" priority="39" name="toc 7"> <w:lsdexception locked="false" priority="39" name="toc 8"> <w:lsdexception locked="false" priority="39" name="toc 9"> <w:lsdexception locked="false" priority="35" qformat="true" name="caption"> <w:lsdexception locked="false" priority="10" semihidden="false" unhidewhenused="false" qformat="true" name="Title"> <w:lsdexception locked="false" priority="1" name="Default Paragraph Font"> <w:lsdexception locked="false" priority="11" semihidden="false" unhidewhenused="false" qformat="true" name="Subtitle"> <w:lsdexception locked="false" priority="22" semihidden="false" unhidewhenused="false" qformat="true" name="Strong"> <w:lsdexception locked="false" priority="20" semihidden="false" unhidewhenused="false" qformat="true" name="Emphasis"> <w:lsdexception locked="false" priority="59" semihidden="false" unhidewhenused="false" name="Table Grid"> <w:lsdexception locked="false" unhidewhenused="false" name="Placeholder Text"> <w:lsdexception locked="false" priority="1" semihidden="false" unhidewhenused="false" qformat="true" name="No Spacing"> <w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading"> <w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List"> <w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid"> <w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1"> <w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2"> <w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1"> <w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2"> <w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1"> <w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2"> <w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3"> <w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List"> <w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading"> <w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List"> <w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid"> <w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 1"> <w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 1"> <w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 1"> <w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 1"> <w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 1"> <w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 1"> <w:lsdexception locked="false" unhidewhenused="false" name="Revision"> <w:lsdexception locked="false" priority="34" semihidden="false" unhidewhenused="false" qformat="true" name="List Paragraph"> <w:lsdexception locked="false" priority="29" semihidden="false" unhidewhenused="false" qformat="true" name="Quote"> <w:lsdexception locked="false" priority="30" semihidden="false" unhidewhenused="false" qformat="true" name="Intense Quote"> <w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 1"> <w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 1"> <w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 1"> <w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 1"> <w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 1"> <w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 1"> <w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 1"> <w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 1"> <w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 2"> <w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 2"> <w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 2"> <w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 2"> <w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 2"> <w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 2"> <w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 2"> <w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 2"> <w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 2"> <w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 2"> <w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 2"> <w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 2"> <w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 2"> <w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 2"> <w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 3"> <w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 3"> <w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 3"> <w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 3"> <w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 3"> <w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 3"> <w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 3"> <w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 3"> <w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 3"> <w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 3"> <w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 3"> <w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 3"> <w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 3"> <w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 3"> <w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 4"> <w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 4"> <w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 4"> <w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 4"> <w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 4"> <w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 4"> <w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 4"> <w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 4"> <w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 4"> <w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 4"> <w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 4"> <w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 4"> <w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 4"> <w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 4"> <w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 5"> <w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 5"> <w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 5"> <w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 5"> <w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 5"> <w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 5"> <w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 5"> <w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 5"> <w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 5"> <w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 5"> <w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 5"> <w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 5"> <w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 5"> <w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 5"> <w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 6"> <w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 6"> <w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 6"> <w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 6"> <w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 6"> <w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 6"> <w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 6"> <w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 6"> <w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 6"> <w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 6"> <w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 6"> <w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 6"> <w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 6"> <w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 6"> <w:lsdexception locked="false" priority="19" semihidden="false" unhidewhenused="false" qformat="true" name="Subtle Emphasis"> <w:lsdexception locked="false" priority="21" semihidden="false" unhidewhenused="false" qformat="true" name="Intense Emphasis"> <w:lsdexception locked="false" priority="31" semihidden="false" unhidewhenused="false" qformat="true" name="Subtle Reference"> <w:lsdexception locked="false" priority="32" semihidden="false" unhidewhenused="false" qformat="true" name="Intense Reference"> <w:lsdexception locked="false" priority="33" semihidden="false" unhidewhenused="false" qformat="true" name="Book Title"> <w:lsdexception locked="false" priority="37" name="Bibliography"> <w:lsdexception locked="false" priority="39" qformat="true" name="TOC Heading"> </w:LatentStyles> </xml><![endif]--><style> <!-- /* Font Definitions */ @font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4; mso-font-charset:1; mso-generic-font-family:roman; mso-font-format:other; mso-font-pitch:variable; mso-font-signature:0 0 0 0 0 0;} @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4; mso-font-charset:204; mso-generic-font-family:swiss; mso-font-pitch:variable; mso-font-signature:-1610611985 1073750139 0 0 159 0;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-unhide:no; mso-style-qformat:yes; mso-style-parent:""; margin-top:0in; margin-right:0in; margin-bottom:10.0pt; margin-left:0in; line-height:150%; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:Calibri; mso-fareast-theme-font:minor-latin; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;} .MsoChpDefault {mso-style-type:export-only; mso-default-props:yes; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:Calibri; mso-fareast-theme-font:minor-latin; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;} .MsoPapDefault {mso-style-type:export-only; margin-bottom:10.0pt; line-height:150%;} @page Section1 {size:8.5in 11.0in; margin:70.85pt 70.85pt 70.85pt 70.85pt; mso-header-margin:.5in; mso-footer-margin:.5in; mso-paper-source:0;} div.Section1 {page:Section1;} --> </style><!--[if gte mso 10]> <style> /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-qformat:yes; mso-style-parent:""; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin-top:0in; mso-para-margin-right:0in; mso-para-margin-bottom:10.0pt; mso-para-margin-left:0in; line-height:150%; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:"Times New Roman"; mso-fareast-theme-font:minor-fareast; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin;} table.MsoTableGrid {mso-style-name:"Table Grid"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-priority:59; mso-style-unhide:no; border:solid black 1.0pt; mso-border-themecolor:text1; mso-border-alt:solid black .5pt; mso-border-themecolor:text1; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-border-insideh:.5pt solid black; mso-border-insideh-themecolor:text1; mso-border-insidev:.5pt solid black; mso-border-insidev-themecolor:text1; mso-para-margin:0in; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin;} </style> <![endif]--> <table class="MsoTableGrid" style="border: medium none ; border-collapse: collapse;" border="1" cellpadding="0" cellspacing="0"> <tbody><tr style=""> <td style="border: 1pt solid black; padding: 0in 5.4pt; width: 2.2in;" valign="top" width="211"> <p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"><b style="">IF the IFC transaction is for…<o:p></o:p></b></p> </td> <td style="border-style: solid solid solid none; border-color: black black black -moz-use-text-color; border-width: 1pt 1pt 1pt medium; padding: 0in 5.4pt; width: 2.5in;" valign="top" width="240"> <p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"><b style="">THEN the acquirer must use TCC…<o:p></o:p></b></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color black black; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 2.2in;" valign="top" width="211"> <p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;">Gaming<o:p></o:p></p> </td> <td style="border-style: none solid solid none; padding: 0in 5.4pt; width: 2.5in;" valign="top" width="240"> <p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;">U for Unique Transaction.<o:p></o:p></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color black black; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 2.2in;" valign="top" width="211"> <p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;">Anything other than gaming<o:p></o:p></p> </td> <td style="border-style: none solid solid none; padding: 0in 5.4pt; width: 2.5in;" valign="top" width="240"> <p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;">R for Retail Purchase<o:p></o:p></p> </td> </tr> </tbody></table>
<br /></li> <li>The Merchant Name / Location (DE 43) must include the service provider's name and flight identification. The flight identification must be a recognizable identification of the airline (not necessarily the airline alphabetic International Air Transport Association [IATA] indicator).</li> <li>The city field description should contain the following:
<br />
<br /><meta equiv="Content-Type" content="text/html; charset=utf-8"><meta name="ProgId" content="Word.Document"><meta name="Generator" content="Microsoft Word 12"><meta name="Originator" content="Microsoft Word 12"><link rel="File-List" href="file:///C:%5CUsers%5CMetodi%5CAppData%5CLocal%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_filelist.xml"><link rel="themeData" href="file:///C:%5CUsers%5CMetodi%5CAppData%5CLocal%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_themedata.thmx"><link rel="colorSchemeMapping" href="file:///C:%5CUsers%5CMetodi%5CAppData%5CLocal%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_colorschememapping.xml"><!--[if gte mso 9]><xml> <w:worddocument> <w:view>Normal</w:View> <w:zoom>0</w:Zoom> <w:trackmoves/> <w:trackformatting/> <w:punctuationkerning/> <w:validateagainstschemas/> <w:saveifxmlinvalid>false</w:SaveIfXMLInvalid> <w:ignoremixedcontent>false</w:IgnoreMixedContent> <w:alwaysshowplaceholdertext>false</w:AlwaysShowPlaceholderText> <w:donotpromoteqf/> <w:lidthemeother>EN-US</w:LidThemeOther> <w:lidthemeasian>X-NONE</w:LidThemeAsian> <w:lidthemecomplexscript>X-NONE</w:LidThemeComplexScript> <w:compatibility> <w:breakwrappedtables/> <w:snaptogridincell/> <w:wraptextwithpunct/> <w:useasianbreakrules/> <w:dontgrowautofit/> <w:splitpgbreakandparamark/> <w:dontvertaligncellwithsp/> <w:dontbreakconstrainedforcedtables/> <w:dontvertalignintxbx/> <w:word11kerningpairs/> <w:cachedcolbalance/> </w:Compatibility> <w:browserlevel>MicrosoftInternetExplorer4</w:BrowserLevel> <m:mathpr> <m:mathfont val="Cambria Math"> <m:brkbin val="before"> <m:brkbinsub val="--"> <m:smallfrac val="off"> <m:dispdef/> <m:lmargin val="0"> <m:rmargin val="0"> <m:defjc val="centerGroup"> <m:wrapindent val="1440"> <m:intlim val="subSup"> <m:narylim val="undOvr"> </m:mathPr></w:WordDocument> </xml><![endif]--><!--[if gte mso 9]><xml> <w:latentstyles deflockedstate="false" defunhidewhenused="true" defsemihidden="true" defqformat="false" defpriority="99" latentstylecount="267"> <w:lsdexception locked="false" priority="0" semihidden="false" unhidewhenused="false" qformat="true" name="Normal"> <w:lsdexception locked="false" priority="9" semihidden="false" unhidewhenused="false" qformat="true" name="heading 1"> <w:lsdexception locked="false" priority="9" qformat="true" name="heading 2"> <w:lsdexception locked="false" priority="9" qformat="true" name="heading 3"> <w:lsdexception locked="false" priority="9" qformat="true" name="heading 4"> <w:lsdexception locked="false" priority="9" qformat="true" name="heading 5"> <w:lsdexception locked="false" priority="9" qformat="true" name="heading 6"> <w:lsdexception locked="false" priority="9" qformat="true" name="heading 7"> <w:lsdexception locked="false" priority="9" qformat="true" name="heading 8"> <w:lsdexception locked="false" priority="9" qformat="true" name="heading 9"> <w:lsdexception locked="false" priority="39" name="toc 1"> <w:lsdexception locked="false" priority="39" name="toc 2"> <w:lsdexception locked="false" priority="39" name="toc 3"> <w:lsdexception locked="false" priority="39" name="toc 4"> <w:lsdexception locked="false" priority="39" name="toc 5"> <w:lsdexception locked="false" priority="39" name="toc 6"> <w:lsdexception locked="false" priority="39" name="toc 7"> <w:lsdexception locked="false" priority="39" name="toc 8"> <w:lsdexception locked="false" priority="39" name="toc 9"> <w:lsdexception locked="false" priority="35" qformat="true" name="caption"> <w:lsdexception locked="false" priority="10" semihidden="false" unhidewhenused="false" qformat="true" name="Title"> <w:lsdexception locked="false" priority="1" name="Default Paragraph Font"> <w:lsdexception locked="false" priority="11" semihidden="false" unhidewhenused="false" qformat="true" name="Subtitle"> <w:lsdexception locked="false" priority="22" semihidden="false" unhidewhenused="false" qformat="true" name="Strong"> <w:lsdexception locked="false" priority="20" semihidden="false" unhidewhenused="false" qformat="true" name="Emphasis"> <w:lsdexception locked="false" priority="59" semihidden="false" unhidewhenused="false" name="Table Grid"> <w:lsdexception locked="false" unhidewhenused="false" name="Placeholder Text"> <w:lsdexception locked="false" priority="1" semihidden="false" unhidewhenused="false" qformat="true" name="No Spacing"> <w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading"> <w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List"> <w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid"> <w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1"> <w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2"> <w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1"> <w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2"> <w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1"> <w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2"> <w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3"> <w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List"> <w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading"> <w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List"> <w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid"> <w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 1"> <w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 1"> <w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 1"> <w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 1"> <w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 1"> <w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 1"> <w:lsdexception locked="false" unhidewhenused="false" name="Revision"> <w:lsdexception locked="false" priority="34" semihidden="false" unhidewhenused="false" qformat="true" name="List Paragraph"> <w:lsdexception locked="false" priority="29" semihidden="false" unhidewhenused="false" qformat="true" name="Quote"> <w:lsdexception locked="false" priority="30" semihidden="false" unhidewhenused="false" qformat="true" name="Intense Quote"> <w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 1"> <w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 1"> <w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 1"> <w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 1"> <w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 1"> <w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 1"> <w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 1"> <w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 1"> <w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 2"> <w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 2"> <w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 2"> <w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 2"> <w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 2"> <w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 2"> <w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 2"> <w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 2"> <w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 2"> <w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 2"> <w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 2"> <w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 2"> <w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 2"> <w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 2"> <w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 3"> <w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 3"> <w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 3"> <w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 3"> <w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 3"> <w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 3"> <w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 3"> <w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 3"> <w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 3"> <w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 3"> <w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 3"> <w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 3"> <w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 3"> <w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 3"> <w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 4"> <w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 4"> <w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 4"> <w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 4"> <w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 4"> <w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 4"> <w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 4"> <w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 4"> <w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 4"> <w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 4"> <w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 4"> <w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 4"> <w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 4"> <w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 4"> <w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 5"> <w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 5"> <w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 5"> <w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 5"> <w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 5"> <w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 5"> <w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 5"> <w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 5"> <w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 5"> <w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 5"> <w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 5"> <w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 5"> <w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 5"> <w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 5"> <w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 6"> <w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 6"> <w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 6"> <w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 6"> <w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 6"> <w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 6"> <w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 6"> <w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 6"> <w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 6"> <w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 6"> <w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 6"> <w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 6"> <w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 6"> <w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 6"> <w:lsdexception locked="false" priority="19" semihidden="false" unhidewhenused="false" qformat="true" name="Subtle Emphasis"> <w:lsdexception locked="false" priority="21" semihidden="false" unhidewhenused="false" qformat="true" name="Intense Emphasis"> <w:lsdexception locked="false" priority="31" semihidden="false" unhidewhenused="false" qformat="true" name="Subtle Reference"> <w:lsdexception locked="false" priority="32" semihidden="false" unhidewhenused="false" qformat="true" name="Intense Reference"> <w:lsdexception locked="false" priority="33" semihidden="false" unhidewhenused="false" qformat="true" name="Book Title"> <w:lsdexception locked="false" priority="37" name="Bibliography"> <w:lsdexception locked="false" priority="39" qformat="true" name="TOC Heading"> </w:LatentStyles> </xml><![endif]--><style> <!-- /* Font Definitions */ @font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4; mso-font-charset:1; mso-generic-font-family:roman; mso-font-format:other; mso-font-pitch:variable; mso-font-signature:0 0 0 0 0 0;} @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4; mso-font-charset:204; mso-generic-font-family:swiss; mso-font-pitch:variable; mso-font-signature:-1610611985 1073750139 0 0 159 0;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-unhide:no; mso-style-qformat:yes; mso-style-parent:""; margin-top:0in; margin-right:0in; margin-bottom:10.0pt; margin-left:0in; line-height:150%; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:Calibri; mso-fareast-theme-font:minor-latin; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;} .MsoChpDefault {mso-style-type:export-only; mso-default-props:yes; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:Calibri; mso-fareast-theme-font:minor-latin; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;} .MsoPapDefault {mso-style-type:export-only; margin-bottom:10.0pt; line-height:150%;} @page Section1 {size:8.5in 11.0in; margin:70.85pt 70.85pt 70.85pt 70.85pt; mso-header-margin:.5in; mso-footer-margin:.5in; mso-paper-source:0;} div.Section1 {page:Section1;} --> </style><!--[if gte mso 10]> <style> /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-qformat:yes; mso-style-parent:""; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin-top:0in; mso-para-margin-right:0in; mso-para-margin-bottom:10.0pt; mso-para-margin-left:0in; line-height:150%; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:"Times New Roman"; mso-fareast-theme-font:minor-fareast; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin;} table.MsoTableGrid {mso-style-name:"Table Grid"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-priority:59; mso-style-unhide:no; border:solid black 1.0pt; mso-border-themecolor:text1; mso-border-alt:solid black .5pt; mso-border-themecolor:text1; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-border-insideh:.5pt solid black; mso-border-insideh-themecolor:text1; mso-border-insidev:.5pt solid black; mso-border-insidev-themecolor:text1; mso-para-margin:0in; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin;} </style> <![endif]--> <table class="MsoTableGrid" style="border: medium none ; border-collapse: collapse;" border="1" cellpadding="0" cellspacing="0"> <tbody><tr style=""> <td style="border: 1pt solid black; padding: 0in 5.4pt; width: 2.2in;" valign="top" width="211"> <p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"><b style="">For…<o:p></o:p></b></p> </td> <td style="border-style: solid solid solid none; border-color: black black black -moz-use-text-color; border-width: 1pt 1pt 1pt medium; padding: 0in 5.4pt; width: 2.5in;" valign="top" width="240"> <p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"><b style="">The city field description…<o:p></o:p></b></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color black black; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 2.2in;" valign="top" width="211"> <p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;">Mailed purchases and gaming transactions<o:p></o:p></p> </td> <td style="border-style: none solid solid none; padding: 0in 5.4pt; width: 2.5in;" valign="top" width="240"> <p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;">Must include the service provider’s customer service telephone number.<span style=""> </span>It is not required to be a toll-free number.<o:p></o:p></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color black black; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 2.2in;" valign="top" width="211"> <p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;">All IFC transactions other than mailed purchases and gaming<o:p></o:p></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color black black -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 2.5in;" valign="top" width="240"> <p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;">Optionally may be a customer service telephone number.<o:p></o:p></p> </td> </tr> </tbody></table>
<br /></li> <li>For all IFC transactions except IFC mailed purchase transactions, the transaction date is defined as the date that the flight departs from the originating city. The transaction date for mailed purchases is defined as the shipment date unless otherwise disclosed to the cardholder.</li><li>The acquiring bank must ensure that the service provider provides full disclosure to the cardholder via the video monitor screen prior to the initiation of any IFC transactions, as detailed below. The screen must prompt the cardholder to acknowledge these disclosure terms before initiating transaction. The disclosure must include the following:
<br /> <ul><li>Full identification of the service provider and provision for recourse in terms of cardholder complaints or questions.</li> <li>Notification that transactions will be billed upon the card issuer's approval of the authorization request.</li> <li>For mailed purchases only, any additional shipping or handling charges.</li> <li>Policy on refunds or returns.</li> <li>Provision for a paper receipt.</li>
<br />For IFC gaming transactions, service providers must additionally disclose the following:
<br />
<br /> <li>Maximum winnings ($3,500) and maximum losses ($350).</li> <li>Notification that total net transaction amount (whether a net win or loss) will be applied against the cardholder's account</li> <li>Notification that cardholder must be at least 18 years of age to play.</li> <li>Notification that some card issuers may not allow gaming.</li></ul></li> <li>The acquiring bank must ensure that the service provider is capable of providing an itemized receipt to the cardholder for all IFC transactions and that, at the cardholder's option, the service provider can effect this offer in one of three ways:
<br /> <ul><li>Printing a receipt at the passenger's seat.</li> <li>Printing a receipt from a centralized printer on the plane.</li> <li>Mailing a receipt to the cardholder.</li>
<br />The mailed receipt offer is to be made available via the video monitor and must require the cardholder to input his or her name and address. For IFC gaming transactions the service provider must provide a receipt to the cardholder by one of the first two methods, described above.
<br />
<br />The receipt must contain the following elements:
<br />
<br /> <li>Identification of the passenger's flight, seat number, and date of departure.</li> <li>Itemized transaction detail.</li> <li>Gaming transaction specified as a net win or net loss.</li> <li>The cardholder's account number truncated on the receipt. Acquirers must ensure that transaction receipts provided to cardholders reflect a minimum of four and a maximum of 12 digits of the cardholder account number. The remaining digits are to be truncated, or rendered indeterminable. In all cases, at least four digits must be truncated. It is recommended that the receipt reflect only the last four digits of the primary account number, and that all preceding digits are truncated. It is also recommended that truncated digits are replaced with fill characters such as "X", "*", or "#" and not with blank spaces or numeric characters.</li></ul></li> <li>For IFC terminals, the assurance and demonstration of security of the transmission of authorization and clearing data between the on-board client server and the acquiring bank and the physical controls over hardware and operating software. Encryption of transmitted data is advised.
<br /></li></ul></li><li><strong>Transaction requirements.</strong>
<br /> <ul><li>No maximum transaction amount applies to any IFC transaction, with the exception of IFC gaming transactions.</li><li>An IFC terminal that also is a hybrid terminal is prohibited from performing fallback procedures from chip to magnetic stripe.</li></ul></li><li><strong>Additional requirements for IFC gaming transactions.</strong>
<br /> <ul><li>Net gaming losses cannot exceed $350 per flight per cardholder account. Net payouts to cardholders for gaming wins cannot exceed $3,500 per flight per cardholder account. This must be monitored throughout the flight by the service provider to ensure compliance.</li> <li>A gaming win transaction will result in posting of net winnings (credit) to the cardholder's account. Under no circumstance may winnings be paid in cash or other form of payment.</li> <li>Before participating in IFC gaming activity, the acquiring bank must take all reasonable and necessary steps to ensure that all IFC gaming activity will be effected in full compliance with all applicable laws and regulations.</li></ul></li> <li><strong>Cardholder account number verification - in-flight verification prior to transaction initiation.</strong>
<br /> <ul><li>The acquirer must ensure that the service provider conducts a Mod-10 check digit routine to verify card authenticity.</li> <li>The acquirer must ensure that the service provider confirms that the card account number is a valid one.</li> <li>For IFC gaming transactions, the acquirer must ensure that the cardholder's account number is checked against the IFC Blocked Gaming File. Cardholders whose account numbers are listed on the IFC Blocked Gaming File must be prohibited from initiating any IFC gaming transaction.</li></ul></li><li><strong>Authorization requirements for all IFC transactions.</strong>
<br /> <ul><li>The Authorization Request / 0100 message must include the cardholder-activated terminal level 4 indicator.</li> <li>The acquirer must read and transmit full, unaltered card-read data. An IFC authorization request may not contain a key-entered account number or expiration date.</li> <li>Transactions are either authorized air-to-ground during the transaction or authorized in a delayed batch. All are authorized on a zero floor limit basis.</li> <li>The acquirer must convert all "refer to card issuer" and "capture card" messages received from issuers to "declines."</li></ul></li> <li><strong>Additional authorization requirements for IFC gaming transactions.</strong> All IFC gaming losses authorized post-flight must be submitted for authorization for the net amount. All gaming transactions authorized during the flight will be for the full wager amount ($350 or a lower amount predetermined by the airline and gaming service provider). No gaming wins will be submitted for authorization.</li> <li><strong>Clearing requirements for all IFC transactions.</strong>
<br /> <ul><li>An acquirer is not permitted to submit declined transactions (including those defined in 5.d. above) into clearing.</li> <li>No surcharges or service fees may be assessed on any IFC transaction, including IFC gaming transactions.
<br /> </li></ul></li><li><strong>Additional clearing requirements for IFC gaming transactions.</strong>
<br /> <ul><li>IFC gaming transactions submitted for clearing must be for the net amount that is won or lost.</li> <li>IFC gaming win transactions will be submitted as a credit transaction. Interchange will be paid to issuers by acquirers on gaming win transactions.</li> <li>An acquirer may resubmit a gaming transaction for a different amount within the specified transaction limits if it was previously rejected for exceeding the specified transaction limits $3,500 for wins and $350 for losses.</li></ul></li> <li><strong>Effective date of the IFC blocked gaming file.</strong> Updates to the IFC Blocked Gaming File will be effective on the first and the 15th day of each month. MasterCard must receive account ranges or BINs that issuers choose to list on the next effective updated IFC Blocked Gaming File at least two weeks before the effective date.
<br /></li></ol><!-- AddThis Button BEGIN --><script type="text/javascript"><!-- addthis_pub = 'Merchant Account'; addthis_brand = 'Merchant Account'; addthis_options = 'favorites, email, digg, delicious, myspace, facebook, google, live, more'; // --></script><a title="Bookmark and Share" onclick="return addthis_sendto()" onmouseover="return addthis_open(this, '', '[URL]', '[TITLE]')" onmouseout="addthis_close()" href="http://www.addthis.com/bookmark.php"><img src="http://s9.addthis.com/button1-bm.gif" alt="" border="0" height="16" width="125" /></a><script src="http://s7.addthis.com/js/152/addthis_widget.js" type="text/javascript"></script>
<br /><!-- AddThis Button END -->msshttp://www.blogger.com/profile/02682453100579738680noreply@blogger.com0tag:blogger.com,1999:blog-8887473741874669103.post-83405771855639530582009-09-10T16:37:00.003-04:002012-06-06T23:22:24.152-04:00Cardholder-Activated Terminal Level RequirementsThe following acceptance requirements apply to the specific CAT levels indicated:<br />
<ul>
<li><strong>Automated Dispensing Machines (ADMs) / Level 1.</strong><br /><ol>
<li>The Automated Dispensing Machine (ADM) must accept a personal identification number (PIN) as a substitute for signature, and ensure that all requirements are met in accordance with the published specifications.<br /><ul>
<li>The PIN requirement is contingent upon PIN being adopted as a standard within a country as well as card issuers providing the required PIN. If PIN is not adopted as a standard within a country or supported in accordance with the processing requirements for PIN-based transactions, this level of service is not available.</li>
<li>The PIN authorization must be made via a secured transmission, in accordance with the published specifications.</li>
<li>ADM terminals must be able to support numeric, alpha, or alphanumeric PINs with a minimum length of four digits and a maximum length of six digits.</li>
</ul>
</li>
<li>The acquiring bank may decline a transaction after four attempts and four consecutive negative responses of "invalid PIN" or "invalid transaction" from the network. Optionally, the acquiring bank may allow more than four consecutive PIN entry attempts that each received a negative response at an ADM.</li>
<li>All transactions regardless of amount must be authorized on a zero floor limit basis with full, unaltered card-read data transmitted. All acquiring banks of ADMs must have received one-time CVC / CVV certification.</li>
<li>Card retention at an ADM is not required, however, if the terminal capability is available, the merchant may do so only at the card issuer's specific direction.<br /><ul>
<li>The retained card must be logged and secured under appropriate audit controls.</li>
<li>The retained card must promptly be rendered useless and then returned to the acquiring bank.</li>
</ul>
</li>
<li>"No Cardholder Authorization" (reason code 4837) chargeback rights for this reason code are not available to card issuers for transactions processed at ADMs where a PIN and full, unaltered card-read data are transmitted because PIN is a valid proxy for the cardholder's signature.</li>
<li>An ADM that is also a hybrid terminal may perform fallback procedures unless it is prohibited by a region. Member banks use fallback procedures when a smart card is present at a hybrid terminal and the merchant processes the transaction by using the magnetic stripe or by manually entering the PAN because the merchant cannot process the transaction using smart card technology.</li>
</ol>
</li>
<li><strong>Self-Service Terminal / Level 2.</strong><br /><ol>
<li>Self-Service Terminals do not process PIN. They include (but are not limited to) automated fuel dispensers identified with MCC 5542.</li>
<li>All Self-Service Terminal (SST) devices must comply with the following requirements:<br /><ul>
<li>Zero floor limit for authorization purposes.</li>
<li>Acquiring banks must read and transmit full, unaltered card read data.</li>
</ul>
</li>
<li>The Authorization System will send all transactions identified as Self-Service Terminals in the Authorization Request / 0100 message to the card issuer's host, regardless of Limit-1 parameters.</li>
<li>The maximum transaction amount is $100 or its equivalent.</li>
<li>Chargebacks processed for reason code 4837, "No Cardholder Authorization," for Self-Service Terminal transactions will be allowed only if the card issuer certifies that the account number used in the transaction is fraudulent, as documented in a letter written by the cardholder to the card issuer.In addition, the card issuer must block the account number on the issuer's host until card expiration on or before the Central Site processing date of chargeback reason code 4837, "No Cardholder Authorization." The card issuer also must list the cardholder account number on the Visa and MasterCard Account File with a "capture card" response until card expiration. Card issuers in the Europe region (region D) also must list such accounts on the European Stop List (ESL).<br /><br />Counterfeit transactions occurring at Self-Service Terminals for which the acquiring bank has transmitted the full magnetic stripe data in the authorization request message and for which an authorization was obtained are ineligible for chargeback reason code 4837, "No Cardholder Authorization."</li>
<br />
<li>A U.S. region merchant acquiring automated fuel dispenser transactions at Self-Service Terminals / Level 2 may forward an Authorization Request / 0100 message for $1 if properly identified by MCC 5542 (automated fuel dispenser) and CAT level indicator 2. If authorization is obtained, the acquiring bank is protected from authorization related chargebacks "requested / required authorization not obtained" (reason code 4808), or "exceeds <a href="http://paymentprocessingservices.blogspot.com/2008/07/floor-limit.html" target="_self" title="Floor Limit">floor limit</a>—not authorized and fraudulent transaction" (reason code 4847) for transactions less than or equal to $75. The acquiring bank protection is limited to $75 for transactions that exceed $75, and issuers may charge back only the difference between the transaction amount and the implied $75 limit.</li>
<li>A Self-Service Terminal that also is a hybrid terminal may perform fallback procedures from chip to magnetic stripe unless it is prohibited by a region.</li>
</ol>
</li>
<li><strong>Limited Amount Terminals / Level 3.</strong><br /> <ol>
<li>A Limited Amount Terminal must check the account number against the Electronic Warning Bulletin file if the terminal has such a capacity.</li>
<li>The maximum transaction amount is $40 or its equivalent.</li>
<li>Chargeback rights for reason code 4837, "No Cardholder Authorization," are not available to issuers for properly identified CAT / Level 3 transactions. Chargeback rights for "requested / required authorization not obtained" (reason code 4808), or "exceeds floor limit - not authorized and fraudulent transaction" (reason code 4847) are available if the maximum transaction amount of $40 or its equivalent has been exceeded.</li>
<li>A Limited Amount Terminal that also is a hybrid terminal is prohibited from performing fallback procedures from chip to magnetic stripe.</li>
</ol>
</li>
</ul>
<script type="text/javascript">
<!-- addthis_pub = 'Merchant Account'; addthis_brand = 'Merchant Account'; addthis_options = 'favorites, email, digg, delicious, myspace, facebook, google, live, more'; // -->
</script><a href="http://www.addthis.com/bookmark.php" title="Bookmark and Share"><img alt="" border="0" height="16" src="http://s9.addthis.com/button1-bm.gif" width="125" /></a><script src="http://s7.addthis.com/js/152/addthis_widget.js" type="text/javascript">
</script>msshttp://www.blogger.com/profile/02682453100579738680noreply@blogger.com0tag:blogger.com,1999:blog-8887473741874669103.post-66895359906792780802009-09-09T14:57:00.002-04:002012-06-06T23:23:05.315-04:00General Acceptance Requirements for Cardholder-Activated Terminal (CAT)The following general card acceptance requirements apply to cardholder-activated terminals:<br />
<ul>
<li>All card-not-present transactions initiated by the cardholder where the card number is either captured as a result of reading the card electronically or by using an electronic device (such as a transponder, PC, or mobile phone) must include the proper cardholder-activated terminal (CAT) level indicator in both the authorization message and clearing records. Depending on the CAT level indicator, other specific data is required for authorization and clearing.<br /> <ul>
<li>The Authorization Request / 0100 message must include a valid merchant category code, POS country code, POS postal code, and CAT level indicator (Level 1, 2, 3, 4, 6, or 7).</li>
<li>Messages used at the CAT must communicate to the cardholder, at a minimum, the following:<br /> <ul>
<li>Invalid transaction.</li>
<li>Unable to route.</li>
<li>Invalid PIN—re-enter (Level 1 only).</li>
<li>Capture card (subject to the terminal's ability to retain cards).</li>
</ul>
</li>
<li>The merchant identification number and the CAT level indicator must be present in the First Presentment / 1240, First Chargeback / 1442, Second Presentment / 1240, and Arbitration Chargeback / 1442 messages.</li>
</ul>
</li>
<li>The acquiring bank must ensure that the description of goods or services on the CAT TID is clearly recognizable to the cardholder.</li>
<li>The acquiring bank is responsible for providing requested transaction information documents.</li>
<li>No cardholder-activated terminal may accept a card for the purchase of scrip.</li>
<li>Acquiring banks must ensure that transaction receipts provided to cardholders reflect only the last four digits of the primary account number, and that all preceding digits are truncated. The truncated digits must be replaced with fill characters such as "X," "*," or "#" and not with blank spaces or numeric characters.</li>
</ul>
<script type="text/javascript">
<!-- addthis_pub = 'Merchant Account'; addthis_brand = 'Merchant Account'; addthis_options = 'favorites, email, digg, delicious, myspace, facebook, google, live, more'; // -->
</script><a href="http://www.addthis.com/bookmark.php" title="Bookmark and Share"><img alt="" border="0" height="16" src="http://s9.addthis.com/button1-bm.gif" width="125" /></a><script src="http://s7.addthis.com/js/152/addthis_widget.js" type="text/javascript">
</script>msshttp://www.blogger.com/profile/02682453100579738680noreply@blogger.com0tag:blogger.com,1999:blog-8887473741874669103.post-8339044738280603372009-09-08T17:16:00.000-04:002012-06-06T23:23:33.642-04:00Cardholder-Activated Terminal (CAT)Cardholder-activated terminals (CATs) are typically unattended terminals that accept various payment cards. These terminals are frequently installed at rail ticketing stations, petrol stations, toll roads, parking garages, and other merchant locations. There are four types of cardholder-activated terminals:<br />
<ul>
<li>Automated Dispensing Machines / Level 1.</li>
<li>Self-Service Terminals / Level 2.</li>
<li>Limited Amount Terminals / Level 3.</li>
<li>In-flight Commerce (IFC) Terminals / Level 4.</li>
</ul>
Cardholder-activated terminal requirements specify the maximum allowed dollar amount of transactions as well as authorization, clearing, chargeback, and addendum record requirements and related transaction liability for each cardholder-activated terminal type.<br />
<br />
As CATs are usually unattended, the traditional point-of-sale (POS) acceptance procedures do not apply, such as the merchant's examination of the card to detect irregularities in the logo, hologram, embossed account number, or the security features and the comparison of the cardholder signature to the signature on the sales receipt.<br />
<br />
MasterCard identifies eCommerce transactions using a value of CT6 in Terminal Type (PDS 0023) within First Presentment / 1240, Chargeback / 1442, Second Presentment / 1240, and Arbitration Chargeback / 1442 messages. There are currently no registration requirements established for these types of transactions, however, MasterCard requires acquiring banks to identify eCommerce transactions using a value of CT6 in Terminal Type (PDS 0023). Additionally, member banks can use a CAT level indicator 7 (a value of CT7 in Terminal Type [PDS 0023]) to identify transponder transactions. Acquiring banks may optionally provide a value of CT7 in Terminal Type (PDS 0023) in First Presentment / 1240, First Chargeback / 1442, Second Presentment / 1240, and Arbitration Chargeback / 1442 messages.<br />
<br />
<script type="text/javascript">
<!-- addthis_pub = 'Merchant Account'; addthis_brand = 'Merchant Account'; addthis_options = 'favorites, email, digg, delicious, myspace, facebook, google, live, more'; // -->
</script><a href="http://www.addthis.com/bookmark.php" title="Bookmark and Share"><img alt="" border="0" height="16" src="http://s9.addthis.com/button1-bm.gif" width="125" /></a><script src="http://s7.addthis.com/js/152/addthis_widget.js" type="text/javascript">
</script>msshttp://www.blogger.com/profile/02682453100579738680noreply@blogger.com0tag:blogger.com,1999:blog-8887473741874669103.post-86838721183176873022009-09-04T16:46:00.003-04:002012-06-06T23:23:54.533-04:00Unique Transaction RequirementsUnique transactions are subject to standards governing retail sales transactions except as otherwise provided here.<br />
<ul>
<li>The floor limit for all unique transactions must be zero.</li>
<li>With the exception of truck stop transactions and of card-read transactions where a non-signature <span class="blsp-spelling-error" id="SPELLING_ERROR_0">CVM</span> is used, if a unique transaction is processed in a card-present environment, the cardholder must present a personal identification of the cardholder identical to that required for a cash disbursement as follows:The identification must be an official government document that has not expired and bears the customer's signature (for example, a passport, identification document, or driver's license).<br /><br />Acquiring banks should ensure that their merchants shall, to the extent allowed by applicable law, record on the face of the sales receipt:<br /><ul><br />
<li>A description of the identification.</li>
<li>Any serial number, expiration date, and jurisdiction of issue.</li>
<li>The name of the customer (if not the same as the embossed name).</li>
<li>The address of the customer.</li>
</ul>
<br />Except for card-read transactions where a non-signature <span class="blsp-spelling-error" id="SPELLING_ERROR_1">CVM</span> is used, to ensure that the cardholder's signature compares positively, the signature on the card must be compared to both of the following:<br /><ul><br />
<li>The cardholder's signature on the identification presented.</li>
<li>The cardholder's signature on the merchant receipt.</li>
</ul>
<br />If the identification has a photograph of the cardholder, the merchant must check that the person presenting the card appears to be the same person.</li>
<br />
<li>Authorization requests and clearing messages must identify the transactions as unique.</li>
</ul>
<script type="text/javascript">
<!-- addthis_pub = 'Merchant Account'; addthis_brand = 'Merchant Account'; addthis_options = 'favorites, email, digg, delicious, myspace, facebook, twitter, google, live, more'; // -->
</script><a href="http://www.addthis.com/bookmark.php" title="Bookmark and Share"><img alt="" border="0" height="16" src="http://s9.addthis.com/button1-bm.gif" width="125" /></a><script src="http://s7.addthis.com/js/152/addthis_widget.js" type="text/javascript">
</script>msshttp://www.blogger.com/profile/02682453100579738680noreply@blogger.com0