<?xml version='1.0' encoding='UTF-8'?><?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?><feed xmlns='http://www.w3.org/2005/Atom' xmlns:openSearch='http://a9.com/-/spec/opensearchrss/1.0/' xmlns:georss='http://www.georss.org/georss' xmlns:gd='http://schemas.google.com/g/2005' xmlns:thr='http://purl.org/syndication/thread/1.0'><id>tag:blogger.com,1999:blog-8887473741874669103</id><updated>2012-01-16T02:34:53.547-05:00</updated><category term='credit card processing'/><category term='payment gateway'/><category term='Authorize.Net'/><category term='take credit cards'/><category term='merchant account'/><category term='accept credit cards'/><title type='text'>Merchant Account</title><subtitle type='html'>A blog about merchant accounts and credit card processing.</subtitle><link rel='http://schemas.google.com/g/2005#feed' type='application/atom+xml' href='http://merchantaccountprocessing.blogspot.com/feeds/posts/default'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default?max-results=100'/><link rel='alternate' type='text/html' href='http://merchantaccountprocessing.blogspot.com/'/><link rel='hub' href='http://pubsubhubbub.appspot.com/'/><link rel='next' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default?start-index=101&amp;max-results=100'/><author><name>mss</name><uri>http://www.blogger.com/profile/02682453100579738680</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><generator version='7.00' uri='http://www.blogger.com'>Blogger</generator><openSearch:totalResults>229</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>100</openSearch:itemsPerPage><entry><id>tag:blogger.com,1999:blog-8887473741874669103.post-2152315588902563386</id><published>2011-07-27T17:26:00.004-04:00</published><updated>2011-07-27T17:58:42.715-04:00</updated><title type='text'>E-Commerce Merchant Account Chargeback Requests</title><content type='html'>&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://blog.unibullmerchantservices.org/2011/07/merchant-credit-card-account-chargeback.html"&gt;&lt;img style="float:right; margin:0 0 10px 10px;cursor:pointer; cursor:hand;width: 300px; height: 210px;" src="http://1.bp.blogspot.com/-Ym_ta6c7Gpo/TjCJ4tGQ3RI/AAAAAAAAARg/Ez_cuiE4LPA/s320/E-Commerce%2BMerchant%2BAccount%2BChargeback%2BRequests.jpg" border="0" alt="E-Commerce Merchant Account Chargeback Requests" title="E-Commerce Merchant Account Chargeback Requests" id="BLOGGER_PHOTO_ID_5634154741112036626" /&gt;&lt;/a&gt;A &lt;a href="http://blog.unibulmerchantservices.com/chargeback-resources"&gt;chargeback&lt;/a&gt;, 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 &lt;a href="https://www.unibulmerchantservices.com/ecommerce-merchant-account"&gt;e-commerce merchant account&lt;/a&gt; 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 &lt;a href="https://www.unibulmerchantservices.com/credit-card-processing"&gt;credit card processing&lt;/a&gt; procedures.&lt;br /&gt;&lt;br /&gt;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.&lt;br /&gt;&lt;br /&gt;Each chargeback request needs to contain the following pieces of information:&lt;div&gt;&lt;ul&gt;&lt;li&gt;&lt;/li&gt;&lt;li&gt;Details of any correspondence between the customer and the retailer documenting the authenticity of the chargeback request; or&lt;/li&gt;&lt;li&gt;Sufficient evidence supporting the dispute.&lt;/li&gt;&lt;/ul&gt;Additionally required information regarding some types of transactions may include the following:&lt;/div&gt;&lt;div&gt;&lt;div&gt;&lt;ul&gt;&lt;li&gt;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);&lt;/li&gt;&lt;li&gt;Assignment of claim by a consumer that received a refund; and&lt;/li&gt;&lt;li&gt;Other documentation that may be requested by the processor.&lt;/li&gt;&lt;/ul&gt;&lt;div&gt;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.&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;&lt;div&gt;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.&lt;/div&gt;&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8887473741874669103-2152315588902563386?l=merchantaccountprocessing.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://merchantaccountprocessing.blogspot.com/feeds/2152315588902563386/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2011/07/e-commerce-merchant-account-chargeback.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/2152315588902563386'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/2152315588902563386'/><link rel='alternate' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2011/07/e-commerce-merchant-account-chargeback.html' title='E-Commerce Merchant Account Chargeback Requests'/><author><name>mss</name><uri>http://www.blogger.com/profile/02682453100579738680</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://1.bp.blogspot.com/-Ym_ta6c7Gpo/TjCJ4tGQ3RI/AAAAAAAAARg/Ez_cuiE4LPA/s72-c/E-Commerce%2BMerchant%2BAccount%2BChargeback%2BRequests.jpg' height='72' width='72'/><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8887473741874669103.post-2906832304944977849</id><published>2011-07-20T12:38:00.003-04:00</published><updated>2011-07-20T13:07:56.319-04:00</updated><title type='text'>Merchant Payment Account Easy Payment Service</title><content type='html'>&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://blog.unibulmerchantservices.org/2011/07/e-commerce-credit-card-processing-banks.html"&gt;&lt;img style="float:right; margin:0 0 10px 10px;cursor:pointer; cursor:hand;width: 300px; height: 193px;" src="http://2.bp.blogspot.com/-he1ppPhmwcM/TicLKbQvt4I/AAAAAAAAAPM/9fY9ZRJO_go/s320/Merchant%2BPayment%2BAccount%2BEasy%2BPayment%2BService.jpg" border="0" alt="Merchant Payment Account Easy Payment Service" title="Merchant Payment Account Easy Payment Service" id="BLOGGER_PHOTO_ID_5631482132794685314" /&gt;&lt;/a&gt;Visa's Easy Payment Service (VEPS) for &lt;a href="https://www.unibulmerchantservices.com/merchant-payment-account"&gt;merchant payment account&lt;/a&gt; users enables face-to-face retailers from more than 98 percent of Merchant Category Codes (MCCs) to &lt;a href="https://www.unibulmerchantservices.com/accept-credit-cards"&gt;accept credit cards&lt;/a&gt; and other bank cards without the need for a signature and only need to print out a receipt upon a request from the customer.&lt;br /&gt;&lt;br /&gt;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.&lt;br /&gt;&lt;br /&gt;&lt;h3&gt;&lt;b&gt;Merchant Payment Account Easy Payment Service Advantages&lt;/b&gt;&lt;/h3&gt;&lt;br /&gt;For qualifying payments, the VEPS program:&lt;div&gt;&lt;ul&gt;&lt;li&gt;Eliminates the need for card acceptors to obtain a signature.&lt;/li&gt;&lt;li&gt;Eliminates the &lt;a href="http://blog.unibulmerchantservices.com/best-practices-for-credit-card-transaction-receipts"&gt;transaction receipt&lt;/a&gt; requirement, unless specifically requested by the cardholder.&lt;/li&gt;&lt;li&gt;Eliminates the necessity for retailers to store sales  receipts and bans issuers from placing retrieval requests.&lt;/li&gt;&lt;li&gt;Provides strong chargeback protection against fraudulent transactions and for the receipt requirement.&lt;/li&gt;&lt;/ul&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;/div&gt;&lt;h3&gt;Which Transactions Qualify&lt;/h3&gt;&lt;br /&gt;Transactions qualify for the VEPS service if they comply with all of the following criteria:&lt;div&gt;&lt;ul&gt;&lt;li&gt;The transaction takes place at a qualified merchant payment account user.&lt;/li&gt;&lt;li&gt;It is a purchase (as opposed to credit) transactions with a valid card.&lt;/li&gt;&lt;li&gt;It is a card-present environment (for amounts of $25 and lower) or unattended environment ( for $15 and under).&lt;/li&gt;&lt;li&gt;Payments are authorized.&lt;/li&gt;&lt;li&gt;Applies to all MCCs except those explicitly excluded (list is provided below).&lt;/li&gt;&lt;li&gt;All card types are eligible, including  magnetic-stripe, chip-and-PIN and proximity payments.&lt;/li&gt;&lt;li&gt;The POS device must read and transmit unaltered magnetic-stripe, chip, or contactless payment information.&lt;/li&gt;&lt;li&gt;The information must be transmitted in the authorization message.&lt;/li&gt;&lt;/ul&gt;&lt;/div&gt;&lt;h3&gt;Unqualified Merchants&lt;/h3&gt;&lt;br /&gt;The following business types are not qualified for VEPS:&lt;div&gt;&lt;ul&gt;&lt;li&gt;Wire Transfer Money Orders.&lt;/li&gt;&lt;li&gt;Insurance Services.&lt;/li&gt;&lt;li&gt;Automated Fuel Dispensers.&lt;/li&gt;&lt;li&gt;Travel Related Arrangement Services.&lt;/li&gt;&lt;li&gt;Catalog Merchants.&lt;/li&gt;&lt;li&gt;Combination Catalog and Retail Merchants.&lt;/li&gt;&lt;li&gt;Outbound and Inbound Telemarketing Merchants.&lt;/li&gt;&lt;li&gt;Continuity / Subscription Merchants.&lt;/li&gt;&lt;li&gt;Manual and Automated Cash Disbursements.&lt;/li&gt;&lt;li&gt;Financial Institutions - Merchandise and Services.&lt;/li&gt;&lt;li&gt;Betting, including Lottery Tickets, Casino Gaming Chips, Off-Track Betting, and Wagers at Race Tracks.&lt;/li&gt;&lt;li&gt;Intra-Government Purchases.&lt;/li&gt;&lt;li&gt;International Automated Referral Service.&lt;/li&gt;&lt;li&gt;GCAS Emergency Services.&lt;/li&gt;&lt;li&gt;Intra-Company Purchases.&lt;/li&gt;&lt;/ul&gt;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.&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8887473741874669103-2906832304944977849?l=merchantaccountprocessing.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://merchantaccountprocessing.blogspot.com/feeds/2906832304944977849/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2011/07/merchant-payment-account-easy-payment.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/2906832304944977849'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/2906832304944977849'/><link rel='alternate' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2011/07/merchant-payment-account-easy-payment.html' title='Merchant Payment Account Easy Payment Service'/><author><name>mss</name><uri>http://www.blogger.com/profile/02682453100579738680</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://2.bp.blogspot.com/-he1ppPhmwcM/TicLKbQvt4I/AAAAAAAAAPM/9fY9ZRJO_go/s72-c/Merchant%2BPayment%2BAccount%2BEasy%2BPayment%2BService.jpg' height='72' width='72'/><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8887473741874669103.post-8274812002311383305</id><published>2011-07-12T17:18:00.003-04:00</published><updated>2011-07-12T17:56:14.972-04:00</updated><title type='text'>Bank Merchant Services Interchange</title><content type='html'>&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://blog.unibullmerchantservices.com/2011/07/credit-card-processing-companies.html"&gt;&lt;img style="float:right; margin:0 0 10px 10px;cursor:pointer; cursor:hand;width: 300px; height: 225px;" src="http://4.bp.blogspot.com/-Y9M_IYwKRX0/ThzCugrXDJI/AAAAAAAAAO0/xrPRGWEsJHY/s320/Bank%2BMerchant%2BServices%2BInterchange.jpg" border="0" alt="Bank Merchant Services Interchange" title="Bank Merchant Services Interchange" id="BLOGGER_PHOTO_ID_5628587738607848594" /&gt;&lt;/a&gt;&lt;a href="https://www.unibulmerchantservices.com/bank-merchant-services"&gt;Bank merchant services&lt;/a&gt; interchange provides incentives for banks to issue credit cards and for businesses to accept them. It is a fee that is paid by the retailer's bank (the acquirer or processor) to the customer's bank (the card issuer) and is designed to compensate the latter for the risks and costs it takes to manage its cardholder accounts. These include the finance costs for the interest-free period that lasts from the time a customer makes a sale to when he pays his bill, as well as for credit losses, fraud prevention and processing costs.&lt;br /&gt;&lt;br /&gt;Setting the various &lt;a href="http://blog.unibulmerchantservices.com/the-issue-with-interchange-fees"&gt;interchange fees&lt;/a&gt; necessitates achieving a careful balance. If they are set too high, the bank merchant services user' desire for accepting bank cards will diminish. If interchange fees are set too low, on the other hand, the issuers' desire to continue issuing cards and maintaining cardholder accounts will decrease and so will the use of cards.&lt;br /&gt;&lt;br /&gt;MasterCard and Visa periodically re-examine interchange fees to make sure that the rates provide to everyone involved: the merchants, the issuers and the cardholders. Each Association keeps dozens of different interchange rates that account for the differences between the various card programs, like e-commerce, gas stations or restaurants.&lt;br /&gt;&lt;br /&gt;The discount rate that merchants pay when they &lt;a href="https://www.unibulmerchantservices.com/accept-credit-cards"&gt;accept credit cards&lt;/a&gt; is typically a small percentage of the cost of the products or services the retailer pays its bank when a card is used. It includes the interchange fee and is negotiated between the retailer and its bank. The Associations are not parties to these negotiations.&lt;br /&gt;&lt;br /&gt;The Associations operate networks that facilitate the communications among four separate parties:&lt;ul&gt;&lt;li&gt;The issuer markets and issues bank cards to customers and provides credit to cardholders from when a purchase is made until a payment is due.&lt;/li&gt;&lt;li&gt;The cardholder uses the bank card to buy merchandise and services at millions of locations around the globe.&lt;/li&gt;&lt;li&gt;The bank merchant services user accepts bank cards for the payment of products and services.&lt;/li&gt;&lt;li&gt;The acquirer contracts with retailers and provides them with bank card acceptance and processing services.&lt;/li&gt;&lt;/ul&gt;By contrast, three-party systems, like Discover, charge discount rates that are often higher than the ones for accepting Visa and MasterCard cards. As three-party system providers act as both issuers and processors, they do not have to set interchange rates. They can use the fees collected directly from retailers to cover the costs for the issuing of the cards.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8887473741874669103-8274812002311383305?l=merchantaccountprocessing.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://merchantaccountprocessing.blogspot.com/feeds/8274812002311383305/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2011/07/bank-merchant-services-interchange.html#comment-form' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/8274812002311383305'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/8274812002311383305'/><link rel='alternate' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2011/07/bank-merchant-services-interchange.html' title='Bank Merchant Services Interchange'/><author><name>mss</name><uri>http://www.blogger.com/profile/02682453100579738680</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://4.bp.blogspot.com/-Y9M_IYwKRX0/ThzCugrXDJI/AAAAAAAAAO0/xrPRGWEsJHY/s72-c/Bank%2BMerchant%2BServices%2BInterchange.jpg' height='72' width='72'/><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8887473741874669103.post-6089553654666698580</id><published>2011-07-06T17:00:00.004-04:00</published><updated>2011-07-06T17:31:26.909-04:00</updated><title type='text'>Merchant Bank Account Fraud Liability</title><content type='html'>&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://blog.unibullmerchantservices.com/2011/06/procedures-to-be-followed-to-accept.html"&gt;&lt;img style="float:right; margin:0 0 10px 10px;cursor:pointer; cursor:hand;width: 300px; height: 179px;" src="http://4.bp.blogspot.com/-B9ytB9hHpbU/ThTTlPN1q_I/AAAAAAAAAOc/ZXvQsWh0CO8/s320/Merchant%2BBank%2BAccount%2BFraud%2BLiability.png" border="0" alt="Merchant Bank Account Fraud Liability" title="Merchant Bank Account Fraud Liability" id="BLOGGER_PHOTO_ID_5626354471185787890" /&gt;&lt;/a&gt;To replace the current data compromise recovery compliance process with one that minimizes retailers' exposure while it is cost-efficient and equitable for all involved parties, &lt;a href="https://www.unibulmerchantservices.com/merchant-bank-account"&gt;merchant bank account&lt;/a&gt; providers have developed the Account Data Compromise Recovery (ADCR) process.&lt;br /&gt;&lt;br /&gt;ADCR is used predominantly for mag-stripe data that have been discovered or suspected to be compromised. It caps counterfeit fraud liability for &lt;a href="https://www.unibulmerchantservices.com/credit-card-processing-companies"&gt;credit card processing companies&lt;/a&gt; to a time frame that is limited at 13 months, whereas the current process where data exposure risk can extend up to the date of expiration of the compromised cards. Moreover, ADCR enables the partial recovery of some expenses incurred by issuers.&lt;br /&gt;&lt;br /&gt;Under the ADCR rules, merchant bank account providers first determines the processor's mag-stripe read fraud liability resulting from inadequate data storage by estimating the amount of the counterfeit fraud that would have resulted in the system for the duration of the 13-month event window if the &lt;a href="http://blog.unibulmerchantservices.com/how-to-manage-a-credit-card-data-breach"&gt;data breach&lt;/a&gt; had never occured. This base-line sets the expected level of fraud for which a processor is not liable. The merchant bank account provider then deducts the baseline from the final confirmed amount of mag- stripe read counterfeit fraud that took place during the event window. This gives you the so-called "incremental fraud" assessment of the processor's liability. This is the fraud loss that exceeds the normal level and is so attributable to the mag-stripe exposure. Moreover, any card number that was in a previous mag-stripe exposure event within the previous 12 months is excluded.&lt;br /&gt;&lt;br /&gt;Issuers enrolled in the ADCR procedure can recoup $1 per account involved in the compromise to cover some of their operating expenses, such as the re-issuing of the cards and the higher volume of incoming customer service calls. Any card number involved in a previous mag-stripe exposure event within the past 12 months is excluded.&lt;br /&gt;&lt;br /&gt;Merchant bank account providers are only liable for up to 80 percent of the entire number of card accounts involved in a magnetic-stripe information type of compromise. The other 20 percent is the approximate share of accounts that will require some or no work by the issuing institutions. Put another way, these are account numbers that have expired or were closed, reissued, or blocked before the time they appeared on the fraud alert.&lt;br /&gt;&lt;br /&gt;The Visa Compromised Account Management System (CAMS) provides a secure and effective way for merchant bank account providers, retailers, law enforcement entities, and issuing banks to communicate compromised and stolen or card account data to and from the Associations through an encrypted site.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8887473741874669103-6089553654666698580?l=merchantaccountprocessing.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://merchantaccountprocessing.blogspot.com/feeds/6089553654666698580/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2011/07/merchant-bank-account-fraud-liability.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/6089553654666698580'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/6089553654666698580'/><link rel='alternate' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2011/07/merchant-bank-account-fraud-liability.html' title='Merchant Bank Account Fraud Liability'/><author><name>mss</name><uri>http://www.blogger.com/profile/02682453100579738680</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://4.bp.blogspot.com/-B9ytB9hHpbU/ThTTlPN1q_I/AAAAAAAAAOc/ZXvQsWh0CO8/s72-c/Merchant%2BBank%2BAccount%2BFraud%2BLiability.png' height='72' width='72'/><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8887473741874669103.post-1153442068204283721</id><published>2011-06-29T16:50:00.002-04:00</published><updated>2011-06-29T17:19:41.652-04:00</updated><title type='text'>Novus Credit Card Processing Easy Payment Transactions</title><content type='html'>&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://blog.unibullmerchantservices.net/2011/06/e-commerce-merchant-account-fraud.html"&gt;&lt;img style="float:right; margin:0 0 10px 10px;cursor:pointer; cursor:hand;width: 300px; height: 225px;" src="http://2.bp.blogspot.com/-ZPeKhkI6170/TguWsz2hX7I/AAAAAAAAAOE/ASeqoWTx-V8/s320/Novus%2BCredit%2BCard%2BProcessing%2BEasy%2BPayment%2BTransactions.jpg" border="0" alt="Novus Credit Card Processing Easy Payment Transactions" title="Novus Credit Card Processing Easy Payment Transactions" id="BLOGGER_PHOTO_ID_5623754256279494578" /&gt;&lt;/a&gt;Sales of $25 or less represent a substantial ratio of all customer spending. The &lt;a href="https://www.unibulmerchantservices.com/novus-credit-card-processing"&gt;Novus credit card processing&lt;/a&gt; Easy Payment Service (EPS) assists in delivering a greater efficiency and convenience to both retailers and consumers.&lt;br /&gt;&lt;br /&gt;The EPS program gives face-to-face retailers the opportunity to &lt;a href="https://www.unibulmerchantservices.com/take-credit-cards"&gt;take credit cards&lt;/a&gt; issued in any given country for sales without asking for a cardholder signature or PIN and not even issuing a &lt;a href="http://blog.unibulmerchantservices.com/best-practices-for-credit-card-transaction-receipts"&gt;transaction receipt&lt;/a&gt; unless explicitly requested by the consumer. This program can potentially increase the speed at the point-of-sale, improve customer satisfaction and provide operating efficiencies for the Novus credit card processing account user. It can build customer loyalty by assisting cardholders use their bank cards securely, quickly and easily.&lt;br /&gt;&lt;br /&gt;&lt;h3&gt;&lt;b&gt;Novus Credit Card Processing EPS Requirements&lt;/b&gt;&lt;/h3&gt;&lt;br /&gt;Sales qualify for the EPS program if they adhere to the following criteria:&lt;ul&gt;&lt;li&gt;Value is lower than or equal to the specific country's transaction limit.&lt;/li&gt;&lt;li&gt;Face-to-face setting.&lt;/li&gt;&lt;li&gt;Authorized.&lt;/li&gt;&lt;li&gt;Applies to all Merchant Category Codes (MCCs), with the exclusion of those specifically listed by the Associations.&lt;/li&gt;&lt;li&gt;The POS terminal must read and transmit the entire magnetic stripe data, unaltered chip-and-PIN data, or unaltered contactless&lt;br /&gt;data.&lt;/li&gt;&lt;/ul&gt;&lt;br /&gt;&lt;h3&gt;EPS Qualifications&lt;/h3&gt;&lt;br /&gt;The following types of transactions do not qualify for the EPS program:&lt;ul&gt;&lt;li&gt;Fallback transactions.&lt;/li&gt;&lt;li&gt;Card funding transactions.&lt;/li&gt;&lt;li&gt;Cash-back payments.&lt;/li&gt;&lt;li&gt;Manual cash disbursement items.&lt;/li&gt;&lt;li&gt;Quasi-cash items.&lt;/li&gt;&lt;li&gt;Prepaid loads.&lt;/li&gt;&lt;li&gt;Payments where Dynamic Currency Conversion is used.&lt;/li&gt;&lt;/ul&gt;The following MCC codes are excluded from the Novus credit card processing Easy Payment Service Program:&lt;ul&gt;&lt;li&gt;4829 - Wire Transfer Money Orders.&lt;/li&gt;&lt;li&gt;5542 - Automated Fuel Dispensers.&lt;/li&gt;&lt;li&gt;5960 - Insurance Services.&lt;/li&gt;&lt;li&gt;5962 - Travel Related Arrangement Services.&lt;/li&gt;&lt;li&gt;5964 - Catalog Merchants.&lt;/li&gt;&lt;li&gt;5965 - Combination Catalog and Retail Merchants.&lt;/li&gt;&lt;li&gt;5966 - Outbound Telemarketing Merchants.&lt;/li&gt;&lt;li&gt;5967 - Inbound Telemarketing Merchants.&lt;/li&gt;&lt;li&gt;5968 - Continuity/Subscription Merchants.&lt;/li&gt;&lt;li&gt;5969 - Direct Marketers (Not elsewhere classified).&lt;/li&gt;&lt;li&gt;6010 - Financial Institutions - Manual Cash Disbursements.&lt;/li&gt;&lt;li&gt;6011 - Financial Institutions - Automated Cash Disbursements.&lt;/li&gt;&lt;li&gt;7995 - Betting, including Lottery Tickets, Casino Gaming Chips, Off-Track Betting, and Wagers at Race Tracks.&lt;/li&gt;&lt;li&gt;9405 - Intra-Government Purchases (Government only).&lt;/li&gt;&lt;li&gt;9700 - International Automated Referral Service (Visa use only).&lt;/li&gt;&lt;li&gt;9701 - Visa Credential Server (Visa use only).&lt;/li&gt;&lt;li&gt;9702 - GCAS Emergency Services (Visa use only).&lt;/li&gt;&lt;li&gt;9751 - UK Supermarkets - Electronic Hot File (Region use only).&lt;/li&gt;&lt;li&gt;9752 - UK Petrol Stations - Electronic Hot File (Region use only).&lt;/li&gt;&lt;li&gt;9950 - Intra-Company Purchases.&lt;/li&gt;&lt;/ul&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8887473741874669103-1153442068204283721?l=merchantaccountprocessing.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://merchantaccountprocessing.blogspot.com/feeds/1153442068204283721/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2011/06/novus-credit-card-processing-easy.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/1153442068204283721'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/1153442068204283721'/><link rel='alternate' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2011/06/novus-credit-card-processing-easy.html' title='Novus Credit Card Processing Easy Payment Transactions'/><author><name>mss</name><uri>http://www.blogger.com/profile/02682453100579738680</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://2.bp.blogspot.com/-ZPeKhkI6170/TguWsz2hX7I/AAAAAAAAAOE/ASeqoWTx-V8/s72-c/Novus%2BCredit%2BCard%2BProcessing%2BEasy%2BPayment%2BTransactions.jpg' height='72' width='72'/><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8887473741874669103.post-8810898692689391256</id><published>2011-06-23T19:42:00.004-04:00</published><updated>2011-06-23T20:05:40.848-04:00</updated><title type='text'>American Credit Card Processing Chargeback Remedies</title><content type='html'>&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://blog.unibullmerchantservices.com/2011/06/accept-credit-card-transactions-for-pin.html"&gt;&lt;img style="float:right; margin:0 0 10px 10px;cursor:pointer; cursor:hand;width: 300px; height: 200px;" src="http://1.bp.blogspot.com/-P1mMd6iYYU4/TgPUdSW6RbI/AAAAAAAAAN0/ZrOf9t_Rq0E/s320/American%2BCredit%2BCard%2BProcessing%2BChargeback%2BRemedies.jpg" border="0" alt="American Credit Card Processing Chargeback Remedies" title="American Credit Card Processing Chargeback Remedies" id="BLOGGER_PHOTO_ID_5621570359497737650" /&gt;&lt;/a&gt;Even when an &lt;a href="https://www.unibulmerchantservices.com/american-credit-card-processing"&gt;American credit card processing&lt;/a&gt; account user receives a chargeback, it could still be able to get it resolved it without losing the sale. It will have to provide its &lt;a href="https://www.unibulmerchantservices.com/merchant-processing-services"&gt;merchant processing services&lt;/a&gt; provider with additional information about the sale or the actions it has already taken related to it. For instance, it could receive a chargeback due to the customer claiming that a refund has not been issued for a returned item. It may be able to resolve the dispute by offering proof that it had issued the refund on a specific date. These data should be sent to the &lt;a href="http://blog.unibulmerchantservices.com/how-to-select-a-merchant-account-provider"&gt;merchant account provider&lt;/a&gt; in a timely fashion.&lt;br /&gt;&lt;br /&gt;The most important thing in this and similar instances is to always send to the acquiring bank as much data as possible to help it cure the chargeback. With adequate  information, the acquirer may be able to resubmit, or "re-present," the sale to the card issuer for payment.&lt;br /&gt;&lt;br /&gt;Timeliness is also crucial when American credit card processing account holders attempt to cure a chargeback. Each step in the chargeback process has a pre-defined time frame, within which action needs to be taken. If the retailer or its acquiring bank does not respond to the request during the specified time frame, which can vary depending on the acquiring bank the merchant will not be able to cure the chargeback.&lt;br /&gt;&lt;br /&gt;Even though most chargebacks are resolved without the retailer losing the sale, some of them cannot be remedied. In such instance, accepting the chargeback may be the best option, saving the merchant the time and expense of needlessly fighting it.&lt;br /&gt;&lt;br /&gt;Card-not-present American credit card processing account holders should be familiar with the chargeback re-presentment rights that are associated with the use of the Address Verification Service (AVS), the card security codes, and with the option to provide solid information. More to the point, the acquiring bank can re-present a charged-back transaction if:&lt;ul&gt;&lt;li&gt;The retailer received an AVS positive match and if the billing and shipping addresses are identical.&lt;/li&gt;&lt;li&gt;The retailer submitted an AVS or security code request and received a "U" response code. These response codes mean that the card issuer is not available or does not support AVS or security codes.&lt;/li&gt;&lt;/ul&gt;Verified by Visa participating retailers are protected by their acquiring bank from receiving some fraud-related chargebacks. If merchants are not participating in Verified by Visa at the present time, they can contact their processor for details on enrolling.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8887473741874669103-8810898692689391256?l=merchantaccountprocessing.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://merchantaccountprocessing.blogspot.com/feeds/8810898692689391256/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2011/06/american-credit-card-processing.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/8810898692689391256'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/8810898692689391256'/><link rel='alternate' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2011/06/american-credit-card-processing.html' title='American Credit Card Processing Chargeback Remedies'/><author><name>mss</name><uri>http://www.blogger.com/profile/02682453100579738680</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://1.bp.blogspot.com/-P1mMd6iYYU4/TgPUdSW6RbI/AAAAAAAAAN0/ZrOf9t_Rq0E/s72-c/American%2BCredit%2BCard%2BProcessing%2BChargeback%2BRemedies.jpg' height='72' width='72'/><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8887473741874669103.post-8406677382005684370</id><published>2011-06-17T16:29:00.004-04:00</published><updated>2011-06-17T16:34:26.490-04:00</updated><title type='text'>Merchant Credit Card Account Basics</title><content type='html'>&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://blog.unibullmerchantservices.net/2011/06/accept-credit-cards-over-phone-with.html"&gt;&lt;img style="float:right; margin:0 0 10px 10px;cursor:pointer; cursor:hand;width: 300px; height: 180px;" src="http://3.bp.blogspot.com/-jwU18049rto/Tfu58qqXAeI/AAAAAAAAANc/wj7kCzJu4XU/s320/Merchant%2BCredit%2BCard%2BAccount%2BBasics.jpg" border="0" alt="Merchant Credit Card Account Basics" title="Merchant Credit Card Account Basics" id="BLOGGER_PHOTO_ID_5619289411970073058" /&gt;&lt;/a&gt;&lt;br /&gt;When &lt;a href="https//www.unibulmerchantservices.com/processing-credit-cards"&gt;processing credit cards&lt;/a&gt;, there are several participants in an average transaction:&lt;ul&gt;&lt;li&gt;Cardholder. A cardholder is an individual to whom a card has been issued or someone who is authorized to use the card. During a transaction, the cardholder offers the card or its account number for payment in exchange for products or services.&lt;/li&gt;&lt;li&gt;&lt;a href="https://www.unibulmerchantservices.com/merchant-credit-card-account"&gt;Merchant credit card account&lt;/a&gt; user. This is a commercial or non profit entity or an individual that, according to a &lt;a href="http://blog.unibulmerchantservices.com/6-reasons-why-visa-can-terminate-your-merchant-agreement"&gt;merchant processing agreement&lt;/a&gt; is authorized to accept bank cards and access terminals when properly presented.&lt;/li&gt;&lt;li&gt;Acquirer. An acquirer (processor) is a licensed Visa and MasterCard member bank that acquires the information relating to a transaction from the merchant credit card account user and submits that information for authorization. The processor also provides clearing and settlement functions to exchange funds between the retailer and the issuer.&lt;/li&gt;&lt;li&gt;Card issuer. An issuer is a licensed Visa and MasterCard member bank that issues bank cards or access POS terminal to consumers. Issuers are responsible for approving or rejecting authorization requests. The issuer also manages their cardholders' accounts and facilitates clearing and settlement to exchange funds between the cardholder and the processor.&lt;/li&gt;&lt;/ul&gt;&lt;h3&gt;Transaction Authorization&lt;/h3&gt;&lt;br /&gt;Each authorization request generates an authorization response that directs the processor or the merchant credit card account user on how to proceed with the payment. The response is usually a code that suggests the action that the retailer should take.&lt;br /&gt;&lt;br /&gt;If the processor is available, the authorization request's response message will include a 2-digit response code. This code tells the acquirer and merchant credit card account user what action should be taken (approve, reject, refer to card issuer, pick up card, or valid).&lt;br /&gt;&lt;br /&gt;&lt;h3&gt;Transaction Clearing&lt;/h3&gt;&lt;br /&gt;Processors and issuers perform clearing to exchange payment data. From the information provided during the clearing process, the Associations' systems calculate the amounts for settlement. Member banks and acquirers contracting with merchant credit card account users to accept cards are required to perform clearing to exchange payment data.&lt;br /&gt;&lt;br /&gt;&lt;h3&gt;Settlement&lt;/h3&gt;&lt;br /&gt;Settlement is the process through which the money is actually exchanged. The funds are calculated as the net equivalent of the amount derived at the clearing. This money is exchanged every day between processors and issuers for the net amount of the cleared transactions. The Associations calculate in reconciliation currency the net positions of each processor and issuer that participate in the clearing process and facilitate the following two settlement functions:&lt;ul&gt;&lt;li&gt;Exchanging advisements.&lt;/li&gt;&lt;li&gt;Transferring money (when applicable).&lt;/li&gt;&lt;/ul&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8887473741874669103-8406677382005684370?l=merchantaccountprocessing.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://merchantaccountprocessing.blogspot.com/feeds/8406677382005684370/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2011/06/merchant-credit-card-account-basics.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/8406677382005684370'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/8406677382005684370'/><link rel='alternate' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2011/06/merchant-credit-card-account-basics.html' title='Merchant Credit Card Account Basics'/><author><name>mss</name><uri>http://www.blogger.com/profile/02682453100579738680</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://3.bp.blogspot.com/-jwU18049rto/Tfu58qqXAeI/AAAAAAAAANc/wj7kCzJu4XU/s72-c/Merchant%2BCredit%2BCard%2BAccount%2BBasics.jpg' height='72' width='72'/><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8887473741874669103.post-7998963961675607511</id><published>2011-06-14T17:51:00.002-04:00</published><updated>2011-06-14T18:15:11.578-04:00</updated><title type='text'>Verified by Visa E-Commerce Credit Card Processing</title><content type='html'>&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://blog.unibulmerchantservices.com/what-every-merchant-needs-to-know-about-transaction-authorizations"&gt;&lt;img style="float:right; margin:0 0 10px 10px;cursor:pointer; cursor:hand;width: 300px; height: 200px;" src="http://2.bp.blogspot.com/-Rp1pjayns1E/TffdOeWHFCI/AAAAAAAAAMs/TpA09oYjZAo/s320/Verified%2Bby%2BVisa%2BE-Commerce%2BCredit%2BCard%2BProcessing.jpg" border="0" alt="Verified by Visa E-Commerce Credit Card Processing" title="Verified by Visa E-Commerce Credit Card Processing" id="BLOGGER_PHOTO_ID_5618202300901692450" /&gt;&lt;/a&gt;&lt;a href="http://blog.unibulmerchantservices.com/verified-by-visa"&gt;Verified by Visa&lt;/a&gt; offers cardholder authentication for merchants using &lt;a href="https://www.unibulmerchantservices.com/ecommerce-credit-card-processing"&gt;e-commerce credit card processing&lt;/a&gt; services. VbV is based on the so-called 3-D Secure protocol and verifies the genuineness of cardholders. It enables consumers to choose a password with their card issuer, and then use it to validate themselves while making a purchase online. This helps make sure that their account number cannot be fraudulently used at an e-commerce website.&lt;br /&gt;&lt;br /&gt;&lt;h3&gt;Verified by Visa E-Commerce Credit Card Processing Activation&lt;/h3&gt;&lt;br /&gt;To use VbV, consumers must initially activate their existing card with the Verified by Visa system. There are several ways they can do this:&lt;br /&gt;&lt;ul&gt;&lt;li&gt;Card issuers usually offer an online activation site.&lt;/li&gt;&lt;li&gt;Visa, the card issuers, and participating &lt;a href="https://www.unibulmerchantservices.com"&gt;merchant account&lt;/a&gt; users can display an "Activation Anytime" banners or buttons that allow consumers to activate their bank card.&lt;/li&gt;&lt;li&gt;Customers can also activate cards during the shopping process, where available.&lt;/li&gt;&lt;/ul&gt;If the customer elects to activate while shopping, he or she gives information to their issuer for identification purposes. The consumer then selects a password. On future sales at participating e-commerce merchants, the consumer's VbV password will be required at checkout, limiting the potential for fraudulent use of the card.&lt;br /&gt;&lt;br /&gt;Once VbV is activated, a customer's card is automatically identified when used for e-commerce credit card processing at participating web stores. The customer is asked for her password; the password is validated; and then the sale is completed. If the password is not validated, the cardholder is not confirmed, and an error message is displayed and the transaction must not be completed.&lt;br /&gt;&lt;br /&gt;&lt;h3&gt;VbV Processing Cycle&lt;/h3&gt;&lt;br /&gt;Verified by Visa retailers need to:&lt;br /&gt;&lt;ul&gt;&lt;li&gt;Add the VbV logo on their home, security information, and checkout pages to promote secure and reliable web shopping. Use one of the following two approaches:&lt;ul&gt;&lt;li&gt;Activation Anytime - This is the approach that will guide consumers directly to an  page where they can activate their bank cards for the VbV service without leaving the retailer's site.&lt;/li&gt;&lt;li&gt;Learn More - This approach routes customers to a service description page (on the merchant's site) where they can educate themselves about VbV and activate their cards for the service.&lt;/li&gt;&lt;/ul&gt;&lt;/li&gt;&lt;li&gt;Add a pre-authentication notice on the checkout page to tell customers that they may be offered to activate their card for VbV.&lt;/li&gt;&lt;li&gt;Complete the VbV authentication process. Offer the authentication information in the authorization request as requested.&lt;/li&gt;&lt;li&gt;If VbV authentication fails, request payment by other means.&lt;/li&gt;&lt;/ul&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8887473741874669103-7998963961675607511?l=merchantaccountprocessing.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://merchantaccountprocessing.blogspot.com/feeds/7998963961675607511/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2011/06/verified-by-visa-e-commerce-credit-card.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/7998963961675607511'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/7998963961675607511'/><link rel='alternate' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2011/06/verified-by-visa-e-commerce-credit-card.html' title='Verified by Visa E-Commerce Credit Card Processing'/><author><name>mss</name><uri>http://www.blogger.com/profile/02682453100579738680</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://2.bp.blogspot.com/-Rp1pjayns1E/TffdOeWHFCI/AAAAAAAAAMs/TpA09oYjZAo/s72-c/Verified%2Bby%2BVisa%2BE-Commerce%2BCredit%2BCard%2BProcessing.jpg' height='72' width='72'/><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8887473741874669103.post-9207610711403603113</id><published>2011-06-09T17:36:00.002-04:00</published><updated>2011-06-09T18:03:31.506-04:00</updated><title type='text'>Processing Credit Cards at Fixed Transaction Fees</title><content type='html'>&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://blog.unibulmerchantservices.com/outdated-mag-stripe-technology-helps-credit-card-fraudsters"&gt;&lt;img style="float:right; margin:0 0 10px 10px;cursor:pointer; cursor:hand;width: 200px; height: 300px;" src="http://2.bp.blogspot.com/-u581AwIp7SM/TfFDCS1x29I/AAAAAAAAAMU/MmfQMO9zwF4/s320/Processing%2BCredit%2BCards%2Bat%2BFixed%2BTransaction%2BFees.jpg" border="0" alt="Processing Credit Cards at Fixed Transaction Fees" title="Processing Credit Cards at Fixed Transaction Fees" id="BLOGGER_PHOTO_ID_5616343917003922386" /&gt;&lt;/a&gt;&lt;a href="https://www.unibulmerchantservices.com/processing-credit-cards"&gt;Processing credit cards&lt;/a&gt; at fixed types of bundled percentage discount fee agreements have the problem of frequently tacking on a fixed per-transaction fee assessed by the &lt;a href="http://blog.unibulmerchantservices.com/how-to-select-a-merchant-account-provider"&gt;merchant account provider&lt;/a&gt; on each transaction. These charges can range quite widely from just pennies to amounts higher $0.25 per item.&lt;br /&gt;&lt;br /&gt;This type of fee must not be confused with the per-item part of the interchange rate for processing credit cards, which is covered by bundled discount rate. The acquirer might add on an additional per-item fee resulting in a total fee to the merchant of, say 3.25 percent + $0.25. This may look like an interchange fee, but the actual Interchange - which also features both a percentage and per-transaction fee – is going to be much lower! The $0.25 per-transaction fee goes directly to the acquirer as an additional fee. If the &lt;a href="https://www.unibulmerchantservices.com"&gt;merchant account&lt;/a&gt; user feels this is confusing, well, it is. This kind of pricing model is unfortunately widely used by acquirers processing credit cards, and is among the leading reasons why retailers look for payment acceptance audits.&lt;br /&gt;&lt;br /&gt;The actual cost of this per-transaction fee is in fact proportional to the cost of the item being sold. So the lower the average sale's amount, the bigger the actual cost in terms of an actual percentage. This may not be a problem for many retailers processing credit cards. Per Visa regulations, the average sale's amount of the four major card brands (Visa, MasterCard, American Express and Discover) weighted to account for market share is about $80 or so. If the client is a merchant with a low average ticket amount, however, this per item fee can pile up rather quickly. For example, the $0.25 per-transaction fee used above would cause the fee on a $10.00 item to rise by 2.5 percent, raising the overall fee to 5.75 percent. This represents an overall increase of 77 percent over the base 3.25 bundled discount rate. on the other hand, this low-average-ticket-amount retailer has an advantage over the average merchant when it comes to the absolute cost that is associated with the base 3.25 percent bundled discount. The $10 retailer will pay $0.325 in base discount, while the $80 one will pay $2.60.&lt;br /&gt;&lt;br /&gt;Retailers processing credit cards also need to be aware of other per-item charges, such as the authorization fees, as they also can lead to an increase in the overall cost of processing a payment. So, what a sophisticated, knowledgeable retailer has learned is that discount rates, fixed per-transaction fees, and interchange all have a deep correlation to the average ticket amount. Understanding the importance of these elements usually contributes to better pricing, sales and marketing decisions.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8887473741874669103-9207610711403603113?l=merchantaccountprocessing.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://merchantaccountprocessing.blogspot.com/feeds/9207610711403603113/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2011/06/processing-credit-cards-at-fixed.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/9207610711403603113'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/9207610711403603113'/><link rel='alternate' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2011/06/processing-credit-cards-at-fixed.html' title='Processing Credit Cards at Fixed Transaction Fees'/><author><name>mss</name><uri>http://www.blogger.com/profile/02682453100579738680</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://2.bp.blogspot.com/-u581AwIp7SM/TfFDCS1x29I/AAAAAAAAAMU/MmfQMO9zwF4/s72-c/Processing%2BCredit%2BCards%2Bat%2BFixed%2BTransaction%2BFees.jpg' height='72' width='72'/><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8887473741874669103.post-692346925000719069</id><published>2011-06-07T16:25:00.003-04:00</published><updated>2011-06-07T17:00:45.049-04:00</updated><title type='text'>Chargeback Policies of Credit Card Processing Companies</title><content type='html'>&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://blog.unibulmerchantservices.com/how-to-use-the-address-verification-service-avs"&gt;&lt;img style="float:right; margin:0 0 10px 10px;cursor:pointer; cursor:hand;width: 300px; height: 182px;" src="http://3.bp.blogspot.com/-TE2H2ttlyOs/Te6RGk7IYFI/AAAAAAAAAL8/9ci1WnVl-uY/s320/Chargeback%2BPolicies%2Bof%2BCredit%2BCard%2BProcessing%2BCompanies.jpg" border="0" alt="Chargeback Policies of Credit Card Processing Companies" title="Chargeback Policies of Credit Card Processing Companies" id="BLOGGER_PHOTO_ID_5615585327554519122" /&gt;&lt;/a&gt;The &lt;a href="https://www.unibulmerchantservices.com/credit-card-processing-companies"&gt;credit card processing companies&lt;/a&gt; monitor the number of disputes and chargebacks at all of their merchants and locations. If the number of disputes and / or chargebacks at a merchant or location is considered excessive, they may take action to limit their exposure.&lt;br /&gt;&lt;br /&gt;Credit card processing companies typically chargeback by deducting, withholding, recouping from, or otherwise offsetting against their payments to a merchant or debiting the retailer's bank account, or they may inform the &lt;a href="https://www.unibulmerchantservices.com"&gt;merchant account&lt;/a&gt; user of its obligation to pay them, which it is required to do immediately and fully.&lt;br /&gt;&lt;br /&gt;&lt;h3&gt;Chargeback Reasons&lt;/h3&gt;&lt;br /&gt;The most typical reasons for chargebacks include:&lt;br /&gt;&lt;ul&gt;&lt;li&gt;A refund has not been issued when the customer expected it would be.&lt;/li&gt;&lt;li&gt;Merchandise that was ordered was never received.&lt;/li&gt;&lt;li&gt;A service was not provided as expected.&lt;/li&gt;&lt;li&gt;The customer did not participate in the purchase, which was fraudulent.&lt;/li&gt;&lt;li&gt;Missing or questionable customer signature.&lt;/li&gt;&lt;li&gt;&lt;a href="http://blog.unibulmerchantservices.com/how-to-manage-chargebacks-resulting-from-processing-transactions-for-which-authorization-was-declined"&gt;Transaction was processed after the authorization request was declined&lt;/a&gt;.&lt;/li&gt;&lt;li&gt;Expired card.&lt;/li&gt;&lt;li&gt;Processing errors.&lt;/li&gt;&lt;/ul&gt;&lt;br /&gt;&lt;h3&gt;Chargeback Programs&lt;/h3&gt;&lt;br /&gt;Chargebacks can be initiated because the retailer is in one of the chargeback programs listed below. The credit card processing companies can place the retailer in any of these programs upon signing the merchant agreement, or at any time during its term.&lt;ul&gt;&lt;li&gt;Immediate chargeback program.&lt;/li&gt;&lt;li&gt;Partial immediate chargeback program.&lt;/li&gt;&lt;li&gt;Fraud full recourse program.&lt;/li&gt;&lt;/ul&gt;&lt;br /&gt;&lt;h3&gt;Chargeback Reversals&lt;/h3&gt;&lt;br /&gt;Merchants can request a chargeback reversal if it was applied in error. In order for the credit card processing companies to consider the request, the retailer is required to:&lt;ul&gt;&lt;li&gt;Have responded to the original information inquiry within the specified time frame.&lt;/li&gt;&lt;li&gt;Request the chargeback reversal within twenty days from the date of the chargeback, and&lt;/li&gt;&lt;li&gt;Provide all relevant supporting documentation to substantiate the error.&lt;/li&gt;&lt;/ul&gt;If the chargeback is applied under any of the above mentioned chargeback programs,the chargeback reversal may only be requested if the retailer proves that a refund was already issued to the customer for the amount of the disputed sale.&lt;br /&gt;&lt;br /&gt;&lt;h3&gt;How to Receive Inquiries and Chargebacks&lt;/h3&gt;&lt;br /&gt;The credit card companies have a wide array of options for the exchange of transaction information with retailers. In addition to the old-fashioned paper by mail method, retailers could be able to receive and reply to information inquiries and chargebacks using various web-based tools, which are usually issuers' preferred method of handling customer disputes and chargebacks.&lt;br /&gt;&lt;br /&gt;&lt;h3&gt;How to Respond to Chargebacks&lt;/h3&gt;&lt;br /&gt;Merchants can respond to information inquiries via online tools, fax and mail depending on how they receive the copy request.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8887473741874669103-692346925000719069?l=merchantaccountprocessing.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://merchantaccountprocessing.blogspot.com/feeds/692346925000719069/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2011/06/chargeback-policies-of-credit-card.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/692346925000719069'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/692346925000719069'/><link rel='alternate' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2011/06/chargeback-policies-of-credit-card.html' title='Chargeback Policies of Credit Card Processing Companies'/><author><name>mss</name><uri>http://www.blogger.com/profile/02682453100579738680</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://3.bp.blogspot.com/-TE2H2ttlyOs/Te6RGk7IYFI/AAAAAAAAAL8/9ci1WnVl-uY/s72-c/Chargeback%2BPolicies%2Bof%2BCredit%2BCard%2BProcessing%2BCompanies.jpg' height='72' width='72'/><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8887473741874669103.post-3779606236763506509</id><published>2011-06-02T12:35:00.004-04:00</published><updated>2011-06-02T13:03:14.298-04:00</updated><title type='text'>Credit Card Payment Processing Life Cycles</title><content type='html'>&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://2.bp.blogspot.com/-jn3LIMkoH-I/TefCPZ6LiPI/AAAAAAAAALg/qGFmAx3sj3E/s1600/Credit%2BCard%2BPayment%2BProcessing%2BLife%2BCycles.png"&gt;&lt;img style="float:right; margin:0 0 10px 10px;cursor:pointer; cursor:hand;width: 300px; height: 225px;" src="http://2.bp.blogspot.com/-jn3LIMkoH-I/TefCPZ6LiPI/AAAAAAAAALg/qGFmAx3sj3E/s320/Credit%2BCard%2BPayment%2BProcessing%2BLife%2BCycles.png" alt="Credit Card Payment Processing Life Cycles" title="Credit Card Payment Processing Life Cycles" id="BLOGGER_PHOTO_ID_5613669030449350898" border="0" /&gt;&lt;/a&gt;The following chain of interactions illustrates the &lt;a href="https://www.unibulmerchantservices.com/credit-card-payment-processing"&gt;credit card payment processing&lt;/a&gt; life cycle for MasterCard and Visa transactions, both in card-present and in card-not-present environment. Processing interactions and activities can vary slightly for any given retailer, merchant bank, or card issuer, based on factors including card and transaction type, as well as the type of &lt;a href="https://www.unibulmerchantservices.com/payment-processing"&gt;payment processing&lt;/a&gt; system used.&lt;br /&gt;&lt;br /&gt;&lt;h3&gt;Credit Card Payment Processing Life Cycles&lt;/h3&gt;&lt;br /&gt;Following are the stages of the bank card transaction process:&lt;br /&gt;&lt;ol&gt;&lt;li&gt;The customer presents a bank card for payment for purchases. In a card-not-present environment, the consumer provides the retailer with the card number, expiration date, billing address, and &lt;a href="http://blog.unibulmerchantservices.com/how-to-use-the-credit-card-security-codes"&gt;card security code&lt;/a&gt;.&lt;/li&gt;&lt;li&gt;The retailer swipes the card, key-enters the transaction amount, and submits an authorization request to the acquiring bank. For card-not-present settings, the account number and other data may be digitally-entered.&lt;/li&gt;&lt;li&gt;The acquiring bank electronically routes the authorization request on to MasterCard's or Visa's payment system.&lt;/li&gt;&lt;li&gt;The Association (Visa or MasterCard) routes on the request to the issuer.&lt;/li&gt;&lt;li&gt;The issuer approves or rejects the transaction authorization.&lt;/li&gt;&lt;li&gt;The Association routes the issuer's authorization response to the acquiring bank.&lt;/li&gt;&lt;li&gt;The acquirer forwards the response to the retailer.&lt;/li&gt;&lt;li&gt;The retailer receives the authorization decision and completes the payment accordingly.&lt;/li&gt;&lt;li&gt;The retailer deposits the sale's receipt with the acquiring bank.&lt;/li&gt;&lt;li&gt;The acquirer funds the retailer's account and electronically sends the transaction to Visa or MasterCard for settlement.&lt;/li&gt;&lt;li&gt;At this point the Association either:&lt;ul&gt;&lt;li&gt;Facilitates the settlement or&lt;/li&gt;&lt;li&gt;Pays the acquiring bank and debits the issuer's account, then immediately sends the transaction to the issuer.&lt;/li&gt;&lt;/ul&gt;&lt;/li&gt;&lt;li&gt;The card issuer now:&lt;ul&gt;&lt;li&gt;Posts the payment to the cardholder's account and&lt;/li&gt;&lt;li&gt;Sends the monthly credit card statement to their customer.&lt;/li&gt;&lt;/ul&gt;&lt;/li&gt;&lt;li&gt;The cardholder receives the statement and makes a payment.&lt;/li&gt;&lt;/ol&gt;Retailers or their agents that collect, save, process, or transmit transaction information are not permitted to store sensitive authentication data (contained in the card's magnetic stripe or chip). Card security codes (CVV2, CVC 2 and CID), or PIN Verification Value (PVV), even in cases when it is encrypted. Once an authorization is processed and a decision is received, whether an approval or rejection, such information must no longer be on file. The only details of the magnetic stripe that are allowed to be stored are customer name, 16-digit account number, and expiration date. This requirement applies to both face-to-face and non-face-to-face types of operations.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8887473741874669103-3779606236763506509?l=merchantaccountprocessing.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://merchantaccountprocessing.blogspot.com/feeds/3779606236763506509/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2011/06/credit-card-payment-processing-life.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/3779606236763506509'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/3779606236763506509'/><link rel='alternate' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2011/06/credit-card-payment-processing-life.html' title='Credit Card Payment Processing Life Cycles'/><author><name>mss</name><uri>http://www.blogger.com/profile/02682453100579738680</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://2.bp.blogspot.com/-jn3LIMkoH-I/TefCPZ6LiPI/AAAAAAAAALg/qGFmAx3sj3E/s72-c/Credit%2BCard%2BPayment%2BProcessing%2BLife%2BCycles.png' height='72' width='72'/><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8887473741874669103.post-3716571256562785779</id><published>2011-05-30T17:47:00.002-04:00</published><updated>2011-05-30T18:14:12.122-04:00</updated><title type='text'>Best Practices to Accept Credit Cards Over the Phone</title><content type='html'>&lt;a href="http://4.bp.blogspot.com/-asUMI5bHe3w/TeQWoLxBM7I/AAAAAAAAALI/lNa0dUDP8XA/s1600/Best%2BPractices%2Bto%2BAccept%2BCredit%2BCards%2BOver%2Bthe%2BPhone.jpg" onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}"&gt;&lt;img style="float:right; margin:0 0 10px 10px;cursor:pointer; cursor:hand;width: 300px; height: 212px;" src="http://4.bp.blogspot.com/-asUMI5bHe3w/TeQWoLxBM7I/AAAAAAAAALI/lNa0dUDP8XA/s320/Best%2BPractices%2Bto%2BAccept%2BCredit%2BCards%2BOver%2Bthe%2BPhone.jpg" border="0" alt="Best Practices to Accept Credit Cards Over the Phone" title="Best Practices to Accept Credit Cards Over the Phone" id="BLOGGER_PHOTO_ID_5612635915219448754" /&gt;&lt;/a&gt;Industry regulations state that merchants are permitted to &lt;a href="https://www.unibulmerchantservices.com/accept-credit-cards-over-the-phone"&gt;accept credit cards over the phone&lt;/a&gt; or in the mail, provided they follow the procedures disclosed in this article for the processing of such card transactions. First of all, it should be understood that the &lt;a href="http://blog.unibulmerchantservices.com/credit-card-processing-floor-limit"&gt;floor limit&lt;/a&gt; of all telephone and transactions is zero and retailers are required to obtain authorization approvals for each one such sale. Retailers need to also document the card transaction and send the sale data to the credit card company or association as described below. Additionally, for each merchant, the transaction form will indicate if their payment programs are primarily telephone and or mail order (MO / TO) sales.&lt;br /&gt;&lt;br /&gt;&lt;h3&gt;Validating Cardholder Identity&lt;/h3&gt;&lt;br /&gt;For each mail or telephone order card transaction, the retailer should verify the address of the cardholder associated with the card account and validate the location for shipping with the customer by using the address verification service (AVS) procedures.&lt;br /&gt;&lt;br /&gt;&lt;h3&gt;Documenting Payment Card Transactions&lt;/h3&gt;&lt;br /&gt;When they accept credit cards over the phone or by mail, retailers need to obtain the following data from their customer for each sale:&lt;br /&gt;&lt;ul&gt;&lt;li&gt;Customer name.&lt;/li&gt;&lt;li&gt;Customer's 16-digit card number.&lt;/li&gt;&lt;li&gt;Card' "good-through" date.&lt;/li&gt;&lt;li&gt;Customer's shipping address.&lt;/li&gt;&lt;/ul&gt;The merchant must keep all such information, together with the delivery date, for the document retention period that is stated in the &lt;a href="https://www.unibulmerchantservices.com/merchant-processing-services"&gt;merchant processing&lt;/a&gt; agreement. Retailers need to communicate the expected date of shipping to the consumer at the time of each telephone order being placed and then upon request by the consumer or the issuer.&lt;br /&gt;&lt;br /&gt;&lt;h3&gt;Communication of Transaction Information&lt;/h3&gt;&lt;br /&gt;When you accept credit cards over the phone are required to communicate the transaction information to their processing provider each day in the form and format that is specified. All transaction information needs to be communicated to the processor through an electronic means of transmittal. The retailer is not allowed to transmit transaction information to the acquirer for items or services purchased by a customer until the product or services have been delivered or furnished to the consumer or at the very least have been shipped. The retailer is allowed, however, to accept a card for a deposit on a sale of item or services and the merchant is permitted to communicate the transaction data pertaining to such a deposit before the time of shipment or delivery of the item or services bought in such a sale.&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;You will need to follow the above guidelines for all of your phone sales and you will be sure to do itright every time and prevent customer disputes and chargebacks.&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8887473741874669103-3716571256562785779?l=merchantaccountprocessing.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://merchantaccountprocessing.blogspot.com/feeds/3716571256562785779/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2011/05/best-practices-to-accept-credit-cards.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/3716571256562785779'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/3716571256562785779'/><link rel='alternate' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2011/05/best-practices-to-accept-credit-cards.html' title='Best Practices to Accept Credit Cards Over the Phone'/><author><name>mss</name><uri>http://www.blogger.com/profile/02682453100579738680</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://4.bp.blogspot.com/-asUMI5bHe3w/TeQWoLxBM7I/AAAAAAAAALI/lNa0dUDP8XA/s72-c/Best%2BPractices%2Bto%2BAccept%2BCredit%2BCards%2BOver%2Bthe%2BPhone.jpg' height='72' width='72'/><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8887473741874669103.post-7935280169844698933</id><published>2011-05-20T19:44:00.002-04:00</published><updated>2011-05-20T20:13:00.819-04:00</updated><title type='text'>Recurring Non-Profit Credit Card Processing Basics</title><content type='html'>&lt;a href="http://3.bp.blogspot.com/-Sa2ACEFHayA/TdcDdXz8o_I/AAAAAAAAAKw/ZvuQ3ELNexw/s1600/Recurring%2BNon-Profit%2BCredit%2BCard%2BProcessing%2BBasics.jpg" onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}"&gt;&lt;img style="float:right; margin:0 0 10px 10px;cursor:pointer; cursor:hand;width: 300px; height: 194px;" src="http://3.bp.blogspot.com/-Sa2ACEFHayA/TdcDdXz8o_I/AAAAAAAAAKw/ZvuQ3ELNexw/s320/Recurring%2BNon-Profit%2BCredit%2BCard%2BProcessing%2BBasics.jpg" border="0" alt="Recurring Non-Profit Credit Card Processing Basics" title="Recurring Non-Profit Credit Card Processing Basics" id="BLOGGER_PHOTO_ID_5608955664056230898" /&gt;&lt;/a&gt;If non-profits &lt;a href="https://www.unibulmerchantservices.com/take-credit-cards"&gt;take credit cards&lt;/a&gt; for donations on a recurring or installment basis, they have to be compliant with all appropriate rules for the processing of each individual card installment. A recurring or installment type of plan is defined as an obligation that could be for a variable or fixed amount, that is agreed to by a customer and paid for with a chain of payments over certain time period.&lt;br /&gt;&lt;br /&gt;&lt;h3&gt;Recurring Non-Profit Credit Card Processing Requirements&lt;/h3&gt;&lt;br /&gt;&lt;a href="https://www.unibulmerchantservices.com/non-profit-credit-card-processing"&gt;Non-profit credit card processing&lt;/a&gt; must comply with a series of requirements for amounts billed to a single card account in relation to a recurring or installment sales arrangement. If a non-profit entity fails to achieve compliance with any one of these rules, or if a donor submits a dispute at any given time over any installment of a recurring plan for the merchandise or services that the non-profit has agreed to perform in connection with it, the issuing bank can, if it decides, charge back the amount of the installment, as well as any preceding installment.&lt;br /&gt;&lt;br /&gt;&lt;h3&gt;Installment Authorization Approval&lt;/h3&gt;&lt;br /&gt;Non-profits must obtain an individual authorization approval from the card issuer for each one of the installments billed to a card in relation to a recurring or installment arrangement and the retailer must get this approval before depositing the transaction data with the processor. If the issuing institution authorizes a given installment, this should not be seen as an insurance that any other installments would be either approved or paid.&lt;br /&gt;&lt;br /&gt;&lt;h3&gt;Consumer Approval&lt;/h3&gt;&lt;br /&gt;The retailer must obtain the consumer's approval for each recurring installment. Keep in mind that a verbal termination request is all that is required from the cardholder to cancel a recurring plan. The consumer's approval should provide all of the following information:&lt;br /&gt;&lt;ul&gt;&lt;li&gt;Consumer's name, billing address and card number.&lt;/li&gt;&lt;li&gt;The amount of each single installment, unless it changes.&lt;/li&gt;&lt;li&gt;Time frame or frequency of the payment installments.&lt;/li&gt;&lt;li&gt;Length of time for which the consumer authorizes the card acceptor to bill installments to his card account.&lt;/li&gt;&lt;li&gt;The non-profit entity's &lt;a href="http://blog.unibulmerchantservices.com/merchant-account-resources"&gt;merchant account&lt;/a&gt; number with the processor.&lt;/li&gt;&lt;li&gt;Card's date of expiration.&lt;/li&gt;&lt;li&gt;Installment's single amount.&lt;/li&gt;&lt;/ul&gt;&lt;h3&gt;Recurring Non-Profit Credit Card Processing Rules for Submission of Transaction Data&lt;/h3&gt;&lt;br /&gt;The payment information that the non-profit entity sends to the processor must be in compliance with the acquirer's requirements. If the merchant agreement is canceled, the non-profit must not submit information for installment types of payments that are payable after the termination's effective date. If a consumer who agreed to an installment plan gets his card terminated, the non-profit should not submit sales information for it as well.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8887473741874669103-7935280169844698933?l=merchantaccountprocessing.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://merchantaccountprocessing.blogspot.com/feeds/7935280169844698933/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2011/05/recurring-non-profit-credit-card.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/7935280169844698933'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/7935280169844698933'/><link rel='alternate' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2011/05/recurring-non-profit-credit-card.html' title='Recurring Non-Profit Credit Card Processing Basics'/><author><name>mss</name><uri>http://www.blogger.com/profile/02682453100579738680</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://3.bp.blogspot.com/-Sa2ACEFHayA/TdcDdXz8o_I/AAAAAAAAAKw/ZvuQ3ELNexw/s72-c/Recurring%2BNon-Profit%2BCredit%2BCard%2BProcessing%2BBasics.jpg' height='72' width='72'/><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8887473741874669103.post-4982915783721249056</id><published>2011-05-18T18:44:00.003-04:00</published><updated>2011-05-18T19:13:46.841-04:00</updated><title type='text'>How to Accept Credit Cards Online and In Person</title><content type='html'>&lt;a href="http://blog.unibulmerchantservices.com/are-australians-the-new-americans-in-credit-card-spending" onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}"&gt;&lt;img style="float:right; margin:0 0 10px 10px;cursor:pointer; cursor:hand;width: 300px; height: 200px;" src="http://1.bp.blogspot.com/-ilR0Sr8aA_8/TdRSYeelmVI/AAAAAAAAAKQ/J7uzC7e_1vk/s320/How%2Bto%2BAccept%2BCredit%2BCards%2BOnline%2Band%2BIn%2BPerson.jpg" border="0" alt="How to Accept Credit Cards Online and In Person" title="How to Accept Credit Cards Online and In Person" id="BLOGGER_PHOTO_ID_5608198016434805074" /&gt;&lt;/a&gt;&lt;a href="https://www.unibulmerchantservices.com/payment-processing"&gt;Payment processing&lt;/a&gt; has to be done in compliance with a set of requirements established by the bank card networks and companies that are mandatory for all merchants, operating both in card-present and card-not-present environment. Listed below are the main guidelines on how to &lt;a href="https://www.unibulmerchantservices.com/accept-credit-cards-online"&gt;accept credit cards online&lt;/a&gt; and in person that retailers need to adhere to.&lt;br /&gt;&lt;br /&gt;&lt;h3&gt;Card "Good Through" Date&lt;/h3&gt;&lt;br /&gt;Retailers need to always inspect the "good through" date on the front of the offered card. You can accept credit cards online and in person if the current date is prior to the expiration date listed on the card. If the card has passed the "good through" date, the merchant is not permitted to take it for payment and is required to contact its &lt;a href="https://www.unibulmerchantservices.com/"&gt;merchant account&lt;/a&gt; provider's authorization center.&lt;br /&gt;&lt;br /&gt;&lt;h3&gt;Card Signature&lt;/h3&gt;&lt;br /&gt;The retailer has to always validate that the customer has signed the bank card where required on its back and verify that the consumer's name as signed is the same as the one printed on the face of it.&lt;br /&gt;&lt;br /&gt;If the offered card has not been signed, the card acceptor will need to ask for two ID documents, of which one must display a photograph of the consumer (a driver's license would answer perfectly). Whenever the merchant has verified that the person offering the card is actually the valid cardholder, the consumer will have to be requested to provide a signature where needed.&lt;br /&gt;&lt;br /&gt;&lt;h3&gt;Approval of Transaction Authorizations&lt;/h3&gt;&lt;br /&gt;If the retailer does not accept credit cards online but in person, it will need to route the full data taken from the magnetic stripe, together with its &lt;a href="http://blog.unibulmerchantservices.com/transaction-authorization-resources"&gt;transaction authorization&lt;/a&gt; request through a swipe of the payment card through the processing terminal. If the POS machine is unable read the data from the magnetic stripe and the merchant has to resort to manually entering the transaction details in order to ask for authorization, the retailer needs to also obtain a physical imprint of the front of the card as evidence that it was available during the interaction. If, however, the card acceptor is unable to obtain a physical imprint for some transaction or other, the issuing bank will be able to charge back the transaction free of recourse.&lt;br /&gt;&lt;br /&gt;Whenever the processing machine is not able to communicate with the processing bank's electronic authorization system, the card acceptor is required to request one by calling its acquirer's voice authorization center.&lt;br /&gt;&lt;br /&gt;For payments for items or services that are delivered or offered or also for payments made back to the retailer in excess than 30 days past the date on which the order was placed, the merchant is required to request an authorization approval both when the order is made and then additionally immediately prior to the item being shipped the services provided to the consumer.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8887473741874669103-4982915783721249056?l=merchantaccountprocessing.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://merchantaccountprocessing.blogspot.com/feeds/4982915783721249056/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2011/05/how-to-accept-credit-cards-online-and.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/4982915783721249056'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/4982915783721249056'/><link rel='alternate' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2011/05/how-to-accept-credit-cards-online-and.html' title='How to Accept Credit Cards Online and In Person'/><author><name>mss</name><uri>http://www.blogger.com/profile/02682453100579738680</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://1.bp.blogspot.com/-ilR0Sr8aA_8/TdRSYeelmVI/AAAAAAAAAKQ/J7uzC7e_1vk/s72-c/How%2Bto%2BAccept%2BCredit%2BCards%2BOnline%2Band%2BIn%2BPerson.jpg' height='72' width='72'/><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8887473741874669103.post-6284897839971898870</id><published>2011-05-13T17:00:00.003-04:00</published><updated>2011-05-13T17:35:56.761-04:00</updated><title type='text'>How to Accept Credit Card Transactions</title><content type='html'>&lt;a href="http://4.bp.blogspot.com/-vJP6hVog5Lc/Tc2kJpjSB0I/AAAAAAAAAJ4/Ou6cjS-ki9E/s1600/How%2Bto%2BAccept%2BCredit%2BCard%2BTransactions.jpg" onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}"&gt;&lt;img style="float:right; margin:0 0 10px 10px;cursor:pointer; cursor:hand;width: 300px; height: 228px;" src="http://4.bp.blogspot.com/-vJP6hVog5Lc/Tc2kJpjSB0I/AAAAAAAAAJ4/Ou6cjS-ki9E/s320/How%2Bto%2BAccept%2BCredit%2BCard%2BTransactions.jpg" border="0" alt="How to Accept Credit Card Transactions" how="" to="" accept="" credit="" card="" id="BLOGGER_PHOTO_ID_5606317596825749314" /&gt;&lt;/a&gt;When you accept credit card transactions, there are multiple interactions occurring among multiple participants. There are three basic processes that make up each transaction:&lt;br /&gt;&lt;ol&gt;&lt;li&gt;Authorization is the process through which card issuers either approve or decline each individual bank card transaction.&lt;/li&gt;&lt;li&gt;Clearing and settlement are the processes that involve the electronic exchange of transactions between acquiring banks and issuers as follows:&lt;/li&gt;&lt;ul&gt;&lt;li&gt;Transaction data is exchanged between the acquiring banks and the issuers for posting to the cardholders' statements.&lt;/li&gt;&lt;li&gt;The payment for each transaction is processed from the issuers to the acquiring banks to be later credited to the card acceptors' account.&lt;/li&gt;&lt;/ul&gt;&lt;/ol&gt;The following article will review how merchants &lt;a href="https://www.unibulmerchantservices.com/accept-credit-card-transactions"&gt;accept credit card transactions&lt;/a&gt; in both face-to-face and non-face-to-face environments. &lt;a href="https://www.unibulmerchantservices.com/payment-processing"&gt;Payment processing&lt;/a&gt; occurrences and activities can possibly vary insignificantly for any one card acceptor, processing bank, or card issuer, depending on card type or transaction environment, as well as the POS system used.&lt;br /&gt;&lt;br /&gt;&lt;h3&gt;How to Accept Credit Card Transactions: Transaction Authorization&lt;/h3&gt;&lt;br /&gt;Here is the credit card transaction authorization process:&lt;br /&gt;&lt;ol&gt;&lt;li&gt;The customer offers a bank card to pay for an item. For non-face-to-face transactions, the customer gives the retailer he account number, address, expiration date and &lt;a href="http://blog.unibulmerchantservices.com/how-to-use-the-credit-card-security-codes"&gt;card security code&lt;/a&gt;.&lt;/li&gt;&lt;li&gt;The card acceptor swipes the card, keys in the dollar amount, and routes an authorization request to the processing bank. For non-face-to-face payments, the account number and the other data can be digitally entered online or key-entered.&lt;/li&gt;&lt;li&gt;The acquiring (processing) bank routes the authorization request on to MasterCard or Visa (the Association).&lt;/li&gt;&lt;li&gt;The Association sends the request on to the card issuer.&lt;/li&gt;&lt;li&gt;The issuer authorizes or declines the transaction.&lt;/li&gt;&lt;li&gt;The Association routes the card issuer's authorization decision to the acquiring bank.&lt;/li&gt;&lt;li&gt;The acquirer sends the response on to the card acceptor.&lt;/li&gt;&lt;li&gt;The card acceptor receives the authorization decision and finalizes the payment accordingly.&lt;/li&gt;&lt;/ol&gt;&lt;br /&gt;&lt;h3&gt;How to Accept Credit Card Transactions: Clearing and Settlement&lt;/h3&gt;&lt;br /&gt;For authorized transactions the payment process goes as follows:&lt;br /&gt;&lt;ol&gt;&lt;li&gt;The card acceptor deposits the payment receipt with the acquiring bank.&lt;/li&gt;&lt;li&gt;The acquirer credits the card acceptor's account and then submits the transaction to the Association for settlement.&lt;/li&gt;&lt;li&gt;The Association facilitates the settlement, pays the acquiring bank and simultaneously debits the card issuer's account. Only then does it send the payment receipt to the card issuer.&lt;/li&gt;&lt;li&gt;The issuer posts the payment to the cardholder's account and issues the monthly statement.&lt;/li&gt;&lt;li&gt;The cardholder gets the statement and makes the payment.&lt;/li&gt;&lt;/ol&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8887473741874669103-6284897839971898870?l=merchantaccountprocessing.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://merchantaccountprocessing.blogspot.com/feeds/6284897839971898870/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2011/05/how-to-accept-credit-card-transactions.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/6284897839971898870'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/6284897839971898870'/><link rel='alternate' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2011/05/how-to-accept-credit-card-transactions.html' title='How to Accept Credit Card Transactions'/><author><name>mss</name><uri>http://www.blogger.com/profile/02682453100579738680</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://4.bp.blogspot.com/-vJP6hVog5Lc/Tc2kJpjSB0I/AAAAAAAAAJ4/Ou6cjS-ki9E/s72-c/How%2Bto%2BAccept%2BCredit%2BCard%2BTransactions.jpg' height='72' width='72'/><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8887473741874669103.post-743555898976249120</id><published>2011-05-06T11:46:00.002-04:00</published><updated>2011-05-06T12:23:43.672-04:00</updated><title type='text'>Merchant Account Services Data Compromise Management</title><content type='html'>&lt;a href="http://4.bp.blogspot.com/-V39DbTQA7RM/TcQgewzq9GI/AAAAAAAAAJM/uYhlgG9uSkQ/s1600/Merchant%2BAccount%2BServices%2BData%2BCompromise%2BManagement.jpg" onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}"&gt;&lt;img style="float:right; margin:0 0 10px 10px;cursor:pointer; cursor:hand;width: 300px; height: 199px;" src="http://4.bp.blogspot.com/-V39DbTQA7RM/TcQgewzq9GI/AAAAAAAAAJM/uYhlgG9uSkQ/s320/Merchant%2BAccount%2BServices%2BData%2BCompromise%2BManagement.jpg" border="0" alt="Merchant Account Services Data Compromise Management" title="Merchant Account Services Data Compromise Management" id="BLOGGER_PHOTO_ID_5603639549225530466" /&gt;&lt;/a&gt;&lt;a href="https://www.unibulmerchantservices.com/merchant-account-services"&gt;Merchant account services&lt;/a&gt; data compromise event (ADC) is an instance that results, in some way or other, in the unallowed access to personal card account information. A potential ADC event is an instance that may lead to, in some way or other, to the unpermitted access to card account data.&lt;br /&gt;&lt;br /&gt;Data security failings in an online &lt;a href="https://www.unibulmerchantservices.com/payment-processing"&gt;payment processing&lt;/a&gt; setting does not necessarily have to be known. Still, there can be indications of an information security breach, unallowed access, or probable signs  of misuse of data within the credit card processing setting that may be indicating an ADC occurrence or a potential ADC event. The list below shows a few such events:&lt;br /&gt;&lt;ul&gt;&lt;li&gt;Internet connections from an internet protocol (IP) address that is not business-related or an inbound internet connection coming from locations that have no sort of business relationship to the potentially affected business or an outbound web connection to a not business-related IP address or country or both.&lt;/li&gt;&lt;li&gt;Access from an unidentified or a not active user's ID or inordinate user activity.&lt;/li&gt;&lt;li&gt;Discovering of malware, suspicious programs or files in an environment, or unusual action or volume in the processing systems.&lt;/li&gt;&lt;li&gt;SQL suspicious action on web-facing systems.&lt;/li&gt;&lt;li&gt;Point-of-sale (POS) devices and ATM machines displaying indications of tampering.&lt;/li&gt;&lt;li&gt;Key-logging activities discovered.&lt;/li&gt;&lt;li&gt;Card-skimming devices discovered.&lt;/li&gt;&lt;li&gt;Lost or stolen &lt;a href="http://blog.unibulmerchantservices.com/credit-card-sales-receipt-processing"&gt;sales receipts&lt;/a&gt;.&lt;/li&gt;&lt;li&gt;Lost or stolen payment card information.&lt;/li&gt;&lt;li&gt;Lost or stolen  PCs, laptops, hard drives, or any other electronic machines that store bank card data.&lt;/li&gt;&lt;li&gt;Files featuring bank account information mistakenly communicated to an unauthorized party.&lt;/li&gt;&lt;/ul&gt;If any action related to any of the above features is found, it is necessary to immediately begin an investigation.&lt;br /&gt;&lt;br /&gt;Once the ADC occurrence is reported, the requesting party has to monitor the ADC reporting activity form status codes. If the respective Credit Card Association gets a report of a potential ADC occurrence or an ADC event, it can validate the data shared by the affected bank via the ADC Reporting Form. When possible, the Card Network will cooperate with the processing banks of record to make sure there is compliance with the rules.&lt;br /&gt;&lt;br /&gt;Registered bank users from the respective acquiring bank need to access the ADC Reporting Form over the web within no more than five days of the received e-mail by using the step-by-step process below:&lt;br /&gt;&lt;ul&gt;&lt;li&gt;Logging in.&lt;/li&gt;&lt;li&gt;Navigate to "My Products" in the "Products" drop-down list.&lt;/li&gt;&lt;li&gt;Choose "Association Alerts."&lt;/li&gt;&lt;li&gt;Select "Yes" in the "Security Warning" option box. The "Association Alerts" disclaimer page will open up.&lt;/li&gt;&lt;li&gt;Examine the disclaimer, and then select "Agree" if you agree to the terms.&lt;/li&gt;&lt;li&gt;From the list on the the "Association Alerts" page, choose "ADC Summary."&lt;/li&gt;&lt;li&gt;From the "ADC Summary" section, choose the number that is the same as the one in the e-mail notification.&lt;/li&gt;&lt;li&gt;Choose the "Section B" tab and populate the data fields requesting the processing bank's contact information.&lt;/li&gt;&lt;li&gt;Select "Save."&lt;/li&gt;&lt;/ul&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8887473741874669103-743555898976249120?l=merchantaccountprocessing.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://merchantaccountprocessing.blogspot.com/feeds/743555898976249120/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2011/05/merchant-account-services-data.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/743555898976249120'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/743555898976249120'/><link rel='alternate' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2011/05/merchant-account-services-data.html' title='Merchant Account Services Data Compromise Management'/><author><name>mss</name><uri>http://www.blogger.com/profile/02682453100579738680</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://4.bp.blogspot.com/-V39DbTQA7RM/TcQgewzq9GI/AAAAAAAAAJM/uYhlgG9uSkQ/s72-c/Merchant%2BAccount%2BServices%2BData%2BCompromise%2BManagement.jpg' height='72' width='72'/><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8887473741874669103.post-3599142288259953209</id><published>2011-05-03T12:15:00.004-04:00</published><updated>2011-05-13T16:59:01.787-04:00</updated><title type='text'>Credit Card Merchant Account Partial Authorizations</title><content type='html'>&lt;a href="http://blog.unibulmerchantservices.com" onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}"&gt;&lt;img style="float:right; margin:0 0 10px 10px;cursor:pointer; cursor:hand;width: 300px; height: 257px;" src="http://blog.unibulmerchantservices.com/wp-content/uploads/2011/05/PayPal-Most-Trusted-Mobile-Payments-Brand.png" border="0" alt="Credit Card Merchant Account Partial Authorizations" title="Credit Card Merchant Account Partial Authorizations" id="BLOGGER_PHOTO_ID_5602530366041013218" /&gt;&lt;/a&gt;Any time the available balance on a cardholder's debit or prepaid card account is lower than the transaction's amount, partial authorizations enable &lt;a href="https://www.unibulmerchantservices.com/credit-card-merchant-account"&gt;credit card merchant account&lt;/a&gt; holders to complete a sale by taking the remaining available balance on the originally presented card, plus another form of payment, such as cash or yet another card. This type of transaction is called a "split tender" sale.&lt;br /&gt;&lt;br /&gt;Whenever a prepaid payment card that is also used as a gift card or an incentive type of card, the available balance will be communicated by default to the merchant's point-of-sale (POS) device where it may be printed out on the &lt;a href="http://blog.unibulmerchantservices.com/credit-card-sales-receipt-processing"&gt;sales receipt&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt;&lt;h3&gt;How Credit Card Merchant Account Partial Authorizations Work&lt;/h3&gt;&lt;br /&gt;Following is the step-by-step process of managing a partial authorization request:&lt;br /&gt;&lt;ol&gt;&lt;li&gt;The cardholder's debit or prepaid card's available balance is lower than the sale's amount.&lt;/li&gt;&lt;li&gt;The merchant submits a &lt;a href="https://www.unibulmerchantservices.com/credit-card-processing"&gt;credit card processing&lt;/a&gt; authorization request for the entire transaction's amount (not adding the tip, though) with an indicator for a Partial authorization.&lt;/li&gt;&lt;li&gt;Because of the insufficient balance, the card's issuer will send a partial authorization approval back to the merchant.&lt;/li&gt;&lt;li&gt;The merchant's POS device identifies the received response code and subtracts the partially approved amount from the entire sale's amount. Bear in mind that if there is a full service setting, the POS machine prints out two receipts - one displaying the partial authorization sale's amount (not including a tip line), and another one showing the residual amount due and the tip line to indicate that the amount is still due.&lt;/li&gt;&lt;li&gt;The customer pays the balance due of the transaction's amount using another form of payment.&lt;/li&gt;&lt;li&gt;The transaction is finalized and a receipt is printed out, showing the split tender amounts. If, as it is with a Balance Return response, the available card balance is also indicated, however it can be formatted as displayed below to keep cardholder privacy:&lt;ul&gt;&lt;li&gt;If the indicated account balance is less than $200, the POS device prints the exact balance on the receipt (i.e., "Balance Remaining: ($69.37").&lt;/li&gt;&lt;li&gt;If the displayed remaining account balance is higher than $200, the POS device prints a "Confirmed" indication, rather than the outstanding dollar amounts (that is, "Balance Remaining: Confirmed").&lt;/li&gt;&lt;/ul&gt;&lt;/li&gt;&lt;/ol&gt;&lt;br /&gt;&lt;h3&gt;Protect Your Credit Card Merchant Account from Fraud&lt;/h3&gt;&lt;br /&gt;While requesting the transaction authorization and waiting for the response, use the time to inspect the card's security features. Any sign of tampering with the card may indicate that you are handling a counterfeit card.&lt;br /&gt;&lt;br /&gt;If you receive an authorization approval response, yet still suspect possible fraud, you may have to make a &lt;a href="http://blog.unibulmerchantservices.com/code-10-call"&gt;Code 10 call&lt;/a&gt; to your processor. You will then be routed to the card issuer's own authorization center and one of their representatives will ask you a series of questions to validate the transaction. Then she will instruct you on how to proceed with the transaction.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8887473741874669103-3599142288259953209?l=merchantaccountprocessing.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://merchantaccountprocessing.blogspot.com/feeds/3599142288259953209/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2011/05/credit-card-merchant-account-partial.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/3599142288259953209'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/3599142288259953209'/><link rel='alternate' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2011/05/credit-card-merchant-account-partial.html' title='Credit Card Merchant Account Partial Authorizations'/><author><name>mss</name><uri>http://www.blogger.com/profile/02682453100579738680</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8887473741874669103.post-2860540535887964919</id><published>2011-04-28T15:35:00.002-04:00</published><updated>2011-04-28T16:05:22.913-04:00</updated><title type='text'>High Risk Merchant Account Visa Chargeback Management</title><content type='html'>&lt;a href="http://4.bp.blogspot.com/-1tyU0J0sdTg/TbnIbBFAeiI/AAAAAAAAAIc/FA3hFT6ZiN4/s1600/High%2BRisk%2BMerchant%2BAccount%2BVisa%2BChargeback%2BManagement.jpg" onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}"&gt;&lt;img style="float:right; margin:0 0 10px 10px;cursor:pointer; cursor:hand;width: 300px; height: 193px;" src="http://4.bp.blogspot.com/-1tyU0J0sdTg/TbnIbBFAeiI/AAAAAAAAAIc/FA3hFT6ZiN4/s320/High%2BRisk%2BMerchant%2BAccount%2BVisa%2BChargeback%2BManagement.jpg" border="0" alt="High Risk Merchant Account Visa Chargeback Management" title="High Risk Merchant Account Visa Chargeback Management" id="BLOGGER_PHOTO_ID_5600727978083383842" /&gt;&lt;/a&gt;Each Credit Card Association (Visa and MasterCard), as well as Discover and American Express, have designed and implemented their very own &lt;a href="https://www.unibulmerchantservices.com/high-risk-merchant-account"&gt;high risk merchant account&lt;/a&gt; programs for monitoring and handling of the chargeback ratios of the card acceptors processing their cards.&lt;br /&gt;&lt;br /&gt;Visa, for example, monitors the chargeback rates of all commercial and non-profit entities processing their cards on a monthly basis and informs the affected acquiring banks (also known as processing or merchant banks or simply an acquirer) any time one of its merchants reaches or goes above the level of excessive chargeback rates. Visa views a chargeback ratio of one percent or more as excessive.&lt;br /&gt;&lt;br /&gt;Whenever it is notified of a retailer with an excessive chargeback ratio, acquiring banks are mandated to take strong actions in order to lower the business' chargeback level. Exactly how this is achieved will depend on the mutual interaction among a number of factors, including the business type, processing amounts, geographic location, and other high risk merchant account factors. Often retailers are mandated to provide their sales staff with additional training on &lt;a href="https://www.unibulmerchantservices.com/payment-processing"&gt;payment processing&lt;/a&gt; procedures. Retailers can also be requested to work with their &lt;a href="http://blog.unibulmerchantservices.com/how-to-select-a-processing-bank-for-your-e-commerce-business"&gt;processing banks&lt;/a&gt; to devise and implement a convincing chargeback-minimizing plan.&lt;br /&gt;&lt;br /&gt;Visa can assess severe penalties on acquiring banks that are not able to decrease their retailers' excessive chargeback ratios. Visa has devised two different chargeback management programs:&lt;ul&gt;&lt;li&gt;Merchant Chargeback Monitoring Program (MCMP). MCMP keeps track of chargeback levels for all merchant banks and retailers on a monthly basis. If a retailer exceeds excessive chargeback rates, Visa contact the affected merchant bank in writing. MCMP is applicable to all high risk merchant account users who have more than 100 total monthly transactions, including sales, credits, etc., over 100 chargebacks, and an overall chargeback-to-sales rate of 1 percent or greater. The initial notification for an excessive chargeback level for a given retailer is viewed as a warning. Visa charges fines only if corrective actions are not provided within a pre-determined period of time to get the chargeback level back to lower rates.&lt;/li&gt;&lt;li&gt;High-Risk Chargeback Monitoring Program (HRCMP). HRCMP is precisely developed to minimize excessive chargeback ratios by high-risk merchant account holders. Such retailers include ticket brokers, timeshare advertising services, travel agents, tour operators, pyramid or multi-level marketing distribution, outbound telemarketing merchants, payment facilitators, internet payment services, etc. HRCMP is applicable to all high-risk merchant account holders with more than 100 total transactions per month, including sales, refunds, etc., greater than 100 chargebacks, and a total chargeback-to-transaction ratio of 1 percent or higher. Unlike the MCMP, under the HRCMP, there is no warning period and fees of $100 per sale are imposed right after a retailer has been caught with an excessive chargeback ratio.&lt;/li&gt;&lt;/ul&gt;Visa additionally monitors international sales and chargeback ratios through its Global Merchant Chargeback Monitoring Program (GMCMP).&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8887473741874669103-2860540535887964919?l=merchantaccountprocessing.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://merchantaccountprocessing.blogspot.com/feeds/2860540535887964919/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2011/04/high-risk-merchant-account-visa.html#comment-form' title='3 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/2860540535887964919'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/2860540535887964919'/><link rel='alternate' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2011/04/high-risk-merchant-account-visa.html' title='High Risk Merchant Account Visa Chargeback Management'/><author><name>mss</name><uri>http://www.blogger.com/profile/02682453100579738680</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://4.bp.blogspot.com/-1tyU0J0sdTg/TbnIbBFAeiI/AAAAAAAAAIc/FA3hFT6ZiN4/s72-c/High%2BRisk%2BMerchant%2BAccount%2BVisa%2BChargeback%2BManagement.jpg' height='72' width='72'/><thr:total>3</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8887473741874669103.post-3764300052835224830</id><published>2011-04-26T12:31:00.002-04:00</published><updated>2011-04-26T12:52:58.575-04:00</updated><title type='text'>Wireless Payment Processing Services Platforms</title><content type='html'>&lt;a href="http://2.bp.blogspot.com/-e2S6IEWoUkk/Tbb4VbkMnAI/AAAAAAAAAIE/dorKHki1Kdw/s1600/Wireless%2BPayment%2BProcessing%2BServices%2BPlatforms.jpg" onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}"&gt;&lt;img style="float:right; margin:0 0 10px 10px;cursor:pointer; cursor:hand;width: 300px; height: 200px;" src="http://2.bp.blogspot.com/-e2S6IEWoUkk/Tbb4VbkMnAI/AAAAAAAAAIE/dorKHki1Kdw/s320/Wireless%2BPayment%2BProcessing%2BServices%2BPlatforms.jpg" border="0" alt="Wireless Payment Processing Services Platforms" title="Wireless Payment Processing Services Platforms" id="BLOGGER_PHOTO_ID_5599936233742310402" /&gt;&lt;/a&gt;As their name implies, wireless &lt;a href="https://www.unibulmerchantservices.com/payment-processing-services"&gt;payment processing services&lt;/a&gt; platforms enable businesses and non-profit organization to &lt;a href="https://www.unibulmerchantservices.com/accept-credit-cards"&gt;accept credit cards&lt;/a&gt; and other forms of electronic money on wireless devices, enabling the processing of payments at locations outside of stores and offices. Depending on the kind of wireless payment processing service, the wireless terminals will be operating on either short- or long-range signal networks to transmit the transaction data collected by the device from the bank card’s magnetic stripe.&lt;br /&gt;&lt;br /&gt;There are two primary groups of wireless payment processing services:&lt;div&gt;&lt;ul&gt;&lt;li&gt;Long-range wireless payment processing. Long-range mobile platforms utilize the same wireless networks that mobile phone carriers use for transmitting their customers' voice and data exchanges. This type of service is available everywhere the network's signal can be caught. It is the best solution for card acceptors that often accept credit cards at their customers' places of operation or at industry conferences and similar kinds of events.&lt;/li&gt;&lt;li&gt;Short-range wireless payment processing. Short-range mobile devices utilize the same wireless services that cordless phones use. The wireless processing terminal can be used within a radius of a few hundred feet from the location of its base unit that is connected to a phone land line. The short-range wireless payment processing services is ideal for card acceptors with limited wireless requirements, that is businesses who need &lt;a href="http://blog.unibulmerchantservices.com/credit-card-processing-resources"&gt;credit card processing&lt;/a&gt; capabilities at various locations all over their premises.&lt;/li&gt;&lt;/ul&gt;There are many great advantages to using wireless solutions for processing credit card payments, including:&lt;/div&gt;&lt;div&gt;&lt;ul&gt;&lt;li&gt;Alternative card acceptance options. A wireless payment processing service enables businesses to quickly accept card payments at trade shows, industry gatherings or on their customers' own premises.&lt;/li&gt;&lt;li&gt;Improved fraud detection. With a mobile terminal the cardholder remains in physical possession of the card throughout the transaction, thus minimizing the probability of a fraudulent activity taking place.&lt;/li&gt;&lt;li&gt;Limited processing costs. As mobile transactions are accepted in the safer card-present setting, they typically receive the lowest processing rates available.&lt;/li&gt;&lt;/ul&gt;There are also a few disadvantages of using wireless payment processing platforms that card acceptors need to be aware of:&lt;br /&gt;&lt;ul&gt;&lt;li&gt;High terminal cost. The cost of wireless terminals is much higher than that of regular point-of-sale (POS) machines and can be the biggest factor in your decision, especially if your card acceptance volumes are low.&lt;/li&gt;&lt;li&gt;Carrier signal presence. Usually listed as the number one drawback, carrier signal presence is constantly being improved. Card acceptors will have to check the availability and strength of the network that your prospective processor is using in the particular area you will be working at prior to setting up a wireless payment processing account.&lt;/li&gt;&lt;/ul&gt;&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8887473741874669103-3764300052835224830?l=merchantaccountprocessing.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://merchantaccountprocessing.blogspot.com/feeds/3764300052835224830/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2011/04/wireless-payment-processing-services.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/3764300052835224830'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/3764300052835224830'/><link rel='alternate' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2011/04/wireless-payment-processing-services.html' title='Wireless Payment Processing Services Platforms'/><author><name>mss</name><uri>http://www.blogger.com/profile/02682453100579738680</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://2.bp.blogspot.com/-e2S6IEWoUkk/Tbb4VbkMnAI/AAAAAAAAAIE/dorKHki1Kdw/s72-c/Wireless%2BPayment%2BProcessing%2BServices%2BPlatforms.jpg' height='72' width='72'/><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8887473741874669103.post-2750299506817054751</id><published>2011-04-21T18:11:00.003-04:00</published><updated>2011-04-21T18:32:16.862-04:00</updated><title type='text'>Managing Invalid Chargebacks with an E-Commerce Merchant Account</title><content type='html'>&lt;a href="http://2.bp.blogspot.com/-Y2K9XtbELX4/TbCwWTduM2I/AAAAAAAAAHk/AJlzjTmE_48/s1600/Managing%2BInvalid%2BChargebacks%2Bwith%2Ban%2BE-Commerce%2BMerchant%2BAccount.jpg" onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}"&gt;&lt;img style="float:right; margin:0 0 10px 10px;cursor:pointer; cursor:hand;width: 300px; height: 199px;" src="http://2.bp.blogspot.com/-Y2K9XtbELX4/TbCwWTduM2I/AAAAAAAAAHk/AJlzjTmE_48/s320/Managing%2BInvalid%2BChargebacks%2Bwith%2Ban%2BE-Commerce%2BMerchant%2BAccount.jpg" border="0" alt="Managing Invalid Chargebacks with an E-Commerce Merchant Account" title="Managing Invalid Chargebacks with an E-Commerce Merchant Account" id="BLOGGER_PHOTO_ID_5598168234050073442" /&gt;&lt;/a&gt;Charged-back sales are bad business for everyone involved in the process and the Credit Card Networks of Visa and MasterCard have set up sophisticated chargeback verification systems that greatly reduce chargeback rates and greatly improve the chargeback process. These procedures can also help limit frivolous customer disputes and especially invalid chargebacks, limiting their negative impact on the business' bottom line in the process.&lt;br /&gt;&lt;br /&gt;&lt;h3&gt;Managing Invalid Chargebacks with an ECommerce Merchant Account&lt;/h3&gt;&lt;br /&gt;Whenever Visa or MasterCard detect an invalid chargeback, they immediately return it to the card's issuer that initiated it, and the business and its &lt;a href="https://www.unibulmerchantservices.com/ecommerce-merchant-account"&gt;e-commerce merchant account&lt;/a&gt; provider will never see it. Most of these providers have also set up systems that regularly review exception items, enabling them to resolve problems before a chargeback is initiated. Together, these systems make sure that the chargebacks that businesses receive are valid or that these that get through can only be resolved by the merchant.&lt;br /&gt;&lt;br /&gt;At the same time, even though chargeback validation systems are becoming ever more sophisticated and reliable, there is always a chance that an invalid chargeback will find its way around the system and into your &lt;a href="http://blog.unibulmerchantservices.com/credit-card-transaction-processing-basics"&gt;transaction processing&lt;/a&gt; statement. In addition, a chargeback may get through the validation systems, as it meets the e-commerce merchant account provider's requirements, and still be invalid. In such cases you need to follow through as fast as possible and re-present your supporting evidence (e.g. sales receipt, invoices, etc.) to your&lt;a href="https://www.unibulmerchantservices.com/online-payment-processing"&gt; online payment processing&lt;/a&gt; provider as a proof that the sale was valid.&lt;br /&gt;&lt;br /&gt;Invalid chargebacks simply cannot be entirely eliminated but you can substantially minimize their number by implementing and following through with a set of best practices for credit card acceptance. The way you accept and process credit card orders and other types of electronic payments must be compliant with Visa and MasterCard regulations that were set up precisely to help you limit chargebacks and downgrades (the process of processing non-compliant payments at rates that are much higher than your headline rate).&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;If the rate of invalid chargebacks is consistently high, even though you have expended all these efforts to limit them and you have received help from your e-commerce merchant account provider, it may just be possible that your processor lacks the expertise to resolve the issue and your best course of action may be to move to another service provider. Make sure that you do your due diligence when evaluating the different prospects and consider all sides of their service. Contact businesses that are currently using your prospective processing provider's platform and try to gauge their rate of satisfaction. Bear in mind that the right processor can save you money and help grow your business.&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8887473741874669103-2750299506817054751?l=merchantaccountprocessing.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://merchantaccountprocessing.blogspot.com/feeds/2750299506817054751/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2011/04/managing-invalid-chargebacks-with-e.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/2750299506817054751'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/2750299506817054751'/><link rel='alternate' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2011/04/managing-invalid-chargebacks-with-e.html' title='Managing Invalid Chargebacks with an E-Commerce Merchant Account'/><author><name>mss</name><uri>http://www.blogger.com/profile/02682453100579738680</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://2.bp.blogspot.com/-Y2K9XtbELX4/TbCwWTduM2I/AAAAAAAAAHk/AJlzjTmE_48/s72-c/Managing%2BInvalid%2BChargebacks%2Bwith%2Ban%2BE-Commerce%2BMerchant%2BAccount.jpg' height='72' width='72'/><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8887473741874669103.post-7787974719279188813</id><published>2011-04-19T15:31:00.002-04:00</published><updated>2011-04-19T16:24:58.416-04:00</updated><title type='text'>Online Payment Processing Fraud Prevention</title><content type='html'>&lt;a href="http://4.bp.blogspot.com/-5AEHL54Y1p0/Ta3vgmra5fI/AAAAAAAAAHM/lrl6nBSIWfA/s1600/Online%2BPayment%2BProcessing%2BFraud%2BPrevention.jpg" onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}"&gt;&lt;img style="float:right; margin:0 0 10px 10px;cursor:pointer; cursor:hand;width: 300px; height: 228px;" src="http://4.bp.blogspot.com/-5AEHL54Y1p0/Ta3vgmra5fI/AAAAAAAAAHM/lrl6nBSIWfA/s320/Online%2BPayment%2BProcessing%2BFraud%2BPrevention.jpg" border="0" alt="Online Payment Processing Fraud Prevention" title="Online Payment Processing Fraud Prevention" id="BLOGGER_PHOTO_ID_5597393255308912114" /&gt;&lt;/a&gt;Regular readers know full well that, as far as &lt;a href="http://blog.unibulmerchantservices.com/fraud-prevention-resources"&gt;fraud prevention&lt;/a&gt; goes, card-not-present transactions are much more challenging in that they are very different from the ones that businesses operating in a face-to-face setting face. Because &lt;a href="https://www.unibulmerchantservices.com/online-payment-processing"&gt;online payment processing&lt;/a&gt; is by definition done in the virtual world, the business never gets to see and examine either the card or the customer.&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;There are, however, a great number of services and best practices that, if implemented consistently and followed scrupulously, will help direct marketing merchant account users and their e-commerce counterparts limit fraud and improve their bottom line.&lt;br /&gt;&lt;br /&gt;&lt;h3&gt;Online Payment Processing Fraud Prevention Guidelines&lt;/h3&gt;&lt;br /&gt;&lt;br /&gt;If you &lt;a href="https://www.unibulmerchantservices.com/accept-credit-cards"&gt;accept credit cards&lt;/a&gt; in a non-face-to-face environment, implement the following&lt;br /&gt;suggestions when processing each of your transactions:&lt;br /&gt;&lt;ul&gt;&lt;li&gt;Obtain authorization approvals for all transactions. The floor limit for all non-face-to-face transactions is zero and that means that you need to receive an authorization approval for every single one of them, regardless of the transaction amount.&lt;/li&gt;&lt;li&gt;Get the expiration date. Always have your customer to provide her card's expiration date. This is used as a way to verify that the customer is in a physical possession of her card during the time of the transaction.&lt;/li&gt;&lt;li&gt;Get the card security code. Card security codes are the 3- (for MasterCard, Visa and Discover cards) and 4-digit (for American Express cards) non-embossed codes on the back (for MasterCard, Visa and Discover) or the front of a bank card (for American Express). Having the card security code in a non-face-to-face transaction is another and very powerful way to validate that your customer is in physical possession of her card. Keep in mind that you should never save the card security codes anywhere in your system. It is forbidden by the Credit Card Networks and violators, if caught, will be assessed steep fines.&lt;/li&gt;&lt;li&gt;Use the Address Verification Service (AVS). The (AVS) enables card acceptors to validate the authenticity of the billing address that a customer has provided at the checkout. It does that by sending the provided address, through the Credit Card Networks, to the card's issuer. The issuer then compares the submitted address to the one it has on file for its own cardholder and responds by issuing a response code that details the result of its investigation.&lt;/li&gt;&lt;/ul&gt;Implementing the above mentioned fraud prevention services and procedures will help minimize fraud and limit chargebacks. Contact your online payment processing provider if you need additional information or help.&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8887473741874669103-7787974719279188813?l=merchantaccountprocessing.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://merchantaccountprocessing.blogspot.com/feeds/7787974719279188813/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2011/04/online-payment-processing-fraud.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/7787974719279188813'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/7787974719279188813'/><link rel='alternate' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2011/04/online-payment-processing-fraud.html' title='Online Payment Processing Fraud Prevention'/><author><name>mss</name><uri>http://www.blogger.com/profile/02682453100579738680</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://4.bp.blogspot.com/-5AEHL54Y1p0/Ta3vgmra5fI/AAAAAAAAAHM/lrl6nBSIWfA/s72-c/Online%2BPayment%2BProcessing%2BFraud%2BPrevention.jpg' height='72' width='72'/><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8887473741874669103.post-5549997070453133756</id><published>2011-04-15T17:58:00.004-04:00</published><updated>2011-04-15T18:45:55.450-04:00</updated><title type='text'>How to Accept Online Payments with AVS</title><content type='html'>&lt;a href="http://1.bp.blogspot.com/-607v3BOxumY/TajEzswsccI/AAAAAAAAAG0/Q-ZwlU478KQ/s1600/How%2Bto%2BAccept%2BOnline%2BPayments%2Bwith%2BAVS.jpg" onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}"&gt;&lt;img style="float:right; margin:0 0 10px 10px;cursor:pointer; cursor:hand;width: 300px; height: 200px;" src="http://1.bp.blogspot.com/-607v3BOxumY/TajEzswsccI/AAAAAAAAAG0/Q-ZwlU478KQ/s320/How%2Bto%2BAccept%2BOnline%2BPayments%2Bwith%2BAVS.jpg" border="0" alt="How to Accept Online Payments with AVS" title="How to Accept Online Payments with AVS" id="BLOGGER_PHOTO_ID_5595938929475613122" /&gt;&lt;/a&gt;AVS (&lt;a href="http://blog.unibulmerchantservices.com/using-the-address-verification-service-avs"&gt;Address Verification Service&lt;/a&gt;) is a widely utilized fraud prevention tool that enables merchants to &lt;a href="https://www.unibulmerchantservices.com/accept-online-payments"&gt;accept online payments&lt;/a&gt; in a way that enables them to verify the billing address provided by the customer by matching it to the one on file with the card issuer.&lt;br /&gt;&lt;br /&gt;&lt;h3&gt;How Accept Online Payments with AVS&lt;/h3&gt;&lt;br /&gt;Using the AVS is very simple, provided your &lt;a href="https://www.unibulmerchantservices.com/interchange-plus-credit-card-processing"&gt;credit card processing&lt;/a&gt; company has set up the service  for your company. First ask that the consumer provides his billing address and submit the data, along with the other needed payment data, to your acquirer for authorization approval. If you support AVS, the cardholder's address will be sent on to the  issuer for verification. The issuer will then compare it to the one it has on file for its own cardholder and will respond by routing back an AVS Response Code.&lt;br /&gt;&lt;br /&gt;AVS and transaction authorization are processed simultaneously and, within just a few seconds, the retailer will receive the two results.&lt;br /&gt;&lt;br /&gt;&lt;h3&gt;AVS Responses and Explanation&lt;/h3&gt;&lt;br /&gt;&lt;br /&gt;&lt;table border="1" cellpadding="0" cellspacing="0"&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td valign="top" width="145"&gt;&lt;p align="center"&gt;&lt;strong&gt;AVS Response Code&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;td valign="top" width="493"&gt;&lt;p align="center"&gt;&lt;strong&gt;Explanation&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td valign="top" width="145"&gt;X - Exact Match&lt;/td&gt;&lt;td valign="top" width="493"&gt;The address and the 9-digit ZIP match. So if all other fraud results raise no suspicion, just process the transaction.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td valign="top" width="145"&gt;Y - Match&lt;/td&gt;&lt;td valign="top" width="493"&gt;The address and the 5-digit ZIP match. Again follow the instructions above.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td valign="top" width="145"&gt;A - Partial Match&lt;/td&gt;&lt;td valign="top" width="493"&gt;The address is the same, but the ZIP is not. This is a sign of a possible fraud. You may want to do some additional investigation before reaching a decision.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td valign="top" width="145"&gt;Z - Partial Match&lt;/td&gt;&lt;td valign="top" width="493"&gt;The ZIP matches, but the address does not. This is again a sign of a possible fraud, so just follow the instructions stated above.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td valign="top" width="145"&gt;N - No Match&lt;/td&gt;&lt;td valign="top" width="493"&gt;Neither the address nor the ZIP are the same. This is a solid sign of possible fraud. You will have to take additional verification steps.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td valign="top" width="145"&gt;U - Unavailable&lt;/td&gt;&lt;td valign="top" width="493"&gt;The issuer's verification system is not reachable and the address cannot be verified. You will need to make a decision without the AVS result.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td valign="top" width="145"&gt;R - Retry&lt;/td&gt;&lt;td valign="top" width="493"&gt;The issuer's system is unresponsive. You need to try again later.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td valign="top" width="145"&gt;U - no AVS Support&lt;/td&gt;&lt;td valign="top" width="493"&gt;If the issuer does not support AVS, you will need to reach a decision on whether to go forward with the transaction or not based on the other data you have available.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td valign="top" width="145"&gt;G - Global&lt;/td&gt;&lt;td valign="top" width="493"&gt;The address is not in the U.S. where the AVS service cannot be used. You will have to take additional steps to verify the legitimacy of the transaction, provided you accept payments from abroad.&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;br /&gt;Remember that if a payment was authorized and the AVS Response Code was "U" (no AVS support) and the transaction is charged back to you, your processor can re-present it again. In the U.S. issuers are required to support AVS or else they simply lose their right to fraud-related chargebacks for virtual transactions.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8887473741874669103-5549997070453133756?l=merchantaccountprocessing.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://merchantaccountprocessing.blogspot.com/feeds/5549997070453133756/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2011/04/how-to-accept-online-payments-with-avs.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/5549997070453133756'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/5549997070453133756'/><link rel='alternate' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2011/04/how-to-accept-online-payments-with-avs.html' title='How to Accept Online Payments with AVS'/><author><name>mss</name><uri>http://www.blogger.com/profile/02682453100579738680</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://1.bp.blogspot.com/-607v3BOxumY/TajEzswsccI/AAAAAAAAAG0/Q-ZwlU478KQ/s72-c/How%2Bto%2BAccept%2BOnline%2BPayments%2Bwith%2BAVS.jpg' height='72' width='72'/><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8887473741874669103.post-432446891014216879</id><published>2011-04-12T17:08:00.002-04:00</published><updated>2011-04-12T17:35:29.494-04:00</updated><title type='text'>Basic Facts about Payment Gateways</title><content type='html'>&lt;a href="http://1.bp.blogspot.com/-mfASjjrtkzE/TaTFib3d-hI/AAAAAAAAAGc/3ZQT8My3_GE/s1600/Basic%2BFacts%2Babout%2BPayment%2BGateways.png" onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}"&gt;&lt;img style="float:right; margin:0 0 10px 10px;cursor:pointer; cursor:hand;width: 300px; height: 225px;" src="http://1.bp.blogspot.com/-mfASjjrtkzE/TaTFib3d-hI/AAAAAAAAAGc/3ZQT8My3_GE/s320/Basic%2BFacts%2Babout%2BPayment%2BGateways.png" border="0" alt="Basic Facts about Payment Gateways" title="Basic Facts about Payment Gateways" id="BLOGGER_PHOTO_ID_5594813832487631378" /&gt;&lt;/a&gt;I have seen a ton of inquiries coming into our company's mail box over the past few weeks that convinced me that I need to offer a refresher on the basics of &lt;a href="https://www.unibulmerchantservices.com/payment-gateway"&gt;payment gateways&lt;/a&gt;. This article will detail what they are and do and go over the payment process.&lt;br /&gt;&lt;br /&gt;&lt;h3&gt;Payment Gateway Basics?&lt;/h3&gt;&lt;br /&gt;Payment gateway is an internet-based service that transmits payment information from an e-commerce website to a processing bank. In short, it is the internet equivalent of the brick-and-mortar point-of-sale machines that is used by physical retailers in face-to-face payment processing settings. The so collected data are encrypted to make sure that the sensitive data is transmitted in a secure fashion.&lt;br /&gt;&lt;br /&gt;&lt;h3&gt;Payment Gateway Transaction Process&lt;/h3&gt;&lt;br /&gt;Payment gateways connect the website's shopping cart (you need to have a shopping cart) with the acquirer's back-end system. The payment stages are as follows:&lt;br /&gt;&lt;ol&gt;&lt;li&gt;A visitor on your website places an order on an &lt;a href="http://blog.unibulmerchantservices.com/13-must-have-e-commerce-website-features"&gt;e-commerce website&lt;/a&gt; and provides his or her credit card account information.&lt;/li&gt;&lt;li&gt;The payment details is encrypted using a service called secure socket layer (SSL) and forwarded on to the merchant's server.&lt;/li&gt;&lt;li&gt;The payment gateway now collects the payment information and, after yet another SSL encryption, sends it on to the &lt;a href="https://www.unibulmerchantservices.com/flat-rate-merchant-account"&gt;merchant account&lt;/a&gt; company's server.&lt;/li&gt;&lt;li&gt;The acquiring bank at this point forwards the payment information to Visa or MasterCard.&lt;/li&gt;&lt;li&gt;If the consumer has used a Discover or an American Express credit card, the card issuer also serves as a processing bank and makes a decision on whether or not to approve authorization of the payment and then sends its response back to the merchant.&lt;/li&gt;&lt;li&gt;The Credit Card Network (Visa or MasterCard) sends the payment data on to the card issuer.&lt;/li&gt;&lt;li&gt;The card issuer either approves or declines authorization of the payment and routes its response via a code (using the exact same channel) back to the acquiring bank. The authorization responses for declined transactions also offer details for the reason the transaction did not get authorized.&lt;/li&gt;&lt;li&gt;The acquiring bank now routes the response code (again through the payment gateway) to the e-commerce website where it is shown to the cardholder.&lt;br /&gt;&lt;/li&gt;&lt;/ol&gt;The process may sound complicated, but in its entirety, from submitting the payment to receiving the response code, only takes seconds.&lt;br /&gt;&lt;br /&gt;The merchant now provides the service or ships the product and then deposits the payment. It is incredibly important that transactions do not get settled prior to the merchandise being shipped. If your customer sees the amount on her statement or payment activity log (now accessible online in virtually real time), prior to receiving the item, the sale may be disputed, setting in motion a chargeback process.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8887473741874669103-432446891014216879?l=merchantaccountprocessing.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://merchantaccountprocessing.blogspot.com/feeds/432446891014216879/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2011/04/basic-facts-about-payment-gateways.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/432446891014216879'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/432446891014216879'/><link rel='alternate' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2011/04/basic-facts-about-payment-gateways.html' title='Basic Facts about Payment Gateways'/><author><name>mss</name><uri>http://www.blogger.com/profile/02682453100579738680</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://1.bp.blogspot.com/-mfASjjrtkzE/TaTFib3d-hI/AAAAAAAAAGc/3ZQT8My3_GE/s72-c/Basic%2BFacts%2Babout%2BPayment%2BGateways.png' height='72' width='72'/><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8887473741874669103.post-5140719725541115214</id><published>2011-04-06T16:23:00.002-04:00</published><updated>2011-04-06T16:43:57.340-04:00</updated><title type='text'>Online Credit Card Payment Processing Set-up Cost</title><content type='html'>&lt;a href="http://4.bp.blogspot.com/-WXmAmPUJccY/TZzQeG5V9fI/AAAAAAAAAGE/9oFYkihLwhg/s1600/Online%2BCredit%2BCard%2BPayment%2BProcessing%2BSet-up%2BCost.jpg" onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}"&gt;&lt;img style="float:right; margin:0 0 10px 10px;cursor:pointer; cursor:hand;width: 300px; height: 212px;" src="http://4.bp.blogspot.com/-WXmAmPUJccY/TZzQeG5V9fI/AAAAAAAAAGE/9oFYkihLwhg/s320/Online%2BCredit%2BCard%2BPayment%2BProcessing%2BSet-up%2BCost.jpg" border="0" alt="Online Credit Card Payment Processing Set-up Cost" title="Online Credit Card Payment Processing Set-up Cost" id="BLOGGER_PHOTO_ID_5592574052953093618" /&gt;&lt;/a&gt;In order to set up an &lt;a href="https://www.unibulmerchantservices.com/online-credit-card-payment-processing"&gt;online credit card payment processing&lt;/a&gt; service, a business needs the following:&lt;div&gt;&lt;ul&gt;&lt;li&gt;An up-and-running website with a valid SSL certificate to encrypt sensitive account data.&lt;/li&gt;&lt;li&gt;A shopping cart to enable customers to organize their shopping selection.&lt;/li&gt;&lt;li&gt;An e-commerce &lt;a href="http://blog.unibulmerchantservices.com/payment-gateway-1"&gt;payment gateway&lt;/a&gt; - the online equivalent of a physical credit card machine that facilitates the transmission of data between the website and the acquiring bank, quickly and safely.&lt;/li&gt;&lt;/ul&gt;The first two items should be supplied by your website designer. The  payment gateway service should be offered and set up by the online credit card payment processing provider. The merchant should not be charged for any application or set up fees. There will most likely be a monthly gateway fee for the gateway that should not be in excess of $15 a month. There is another service fee that the card acceptor will be charged on a monthly basis and it goes by different names. Whatever it may be called, the merchant should not be paying more than $15 for it.&lt;br /&gt;&lt;br /&gt;Also the merchant should not be asked to pay anything until the service is actually set up and usable. The biggest consideration, however, as far as fees are concerned, should be the &lt;a href="https://www.unibulmerchantservices.com/credit-card-processing"&gt;credit card processing&lt;/a&gt; rates. The merchant should carefully examine the pricing proposals prior to making any decision on which  service provider to choose. I would advise that the card acceptor contacts at least a dozen different processing providers and request a detailed pricing proposal from each one of them. The online credit card payment processing cost is made up of several components and the merchant needs to know precisely how much it will be paying for each one of them. Following below is a list of the most typical fees and charges associated with a web-based &lt;a href="https://www.unibulmerchantservices.com/free-authorize-net-merchant-account"&gt;merchant account&lt;/a&gt;:&lt;/div&gt;&lt;div&gt;&lt;ul&gt;&lt;li&gt;Discount rate - the fee a merchant is charged by its processor for accepting card transactions.&lt;/li&gt;&lt;li&gt;Authorization fee - a "per-transaction" fee.&lt;/li&gt;&lt;li&gt;Application and set up fee.&lt;/li&gt;&lt;li&gt;Monthly statement fee.&lt;/li&gt;&lt;li&gt;Support fee.&lt;/li&gt;&lt;li&gt;Payment gateway fee - unique to the online credit card payment processing accounts.&lt;/li&gt;&lt;/ul&gt;If the merchant sees any other fees in the pricing proposal, it will most likely be best to look elsewhere for a processor. Moreover, when evaluating a new pricing proposal, each prospective acquirer should provide a comparison table on how its fees stack up against the competition. Remember, you have plenty of choices, so don't rush into a decision, although that is precisely what the processor will want you to do.&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8887473741874669103-5140719725541115214?l=merchantaccountprocessing.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://merchantaccountprocessing.blogspot.com/feeds/5140719725541115214/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2011/04/online-credit-card-payment-processing.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/5140719725541115214'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/5140719725541115214'/><link rel='alternate' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2011/04/online-credit-card-payment-processing.html' title='Online Credit Card Payment Processing Set-up Cost'/><author><name>mss</name><uri>http://www.blogger.com/profile/02682453100579738680</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://4.bp.blogspot.com/-WXmAmPUJccY/TZzQeG5V9fI/AAAAAAAAAGE/9oFYkihLwhg/s72-c/Online%2BCredit%2BCard%2BPayment%2BProcessing%2BSet-up%2BCost.jpg' height='72' width='72'/><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8887473741874669103.post-7396924688330766249</id><published>2011-04-01T16:04:00.002-04:00</published><updated>2011-04-01T16:29:22.528-04:00</updated><title type='text'>Requirements for Merchant Processing Services Providers</title><content type='html'>&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://4.bp.blogspot.com/-s752Wh4soSE/TZY1j0KEEBI/AAAAAAAAAFs/DeYPxzNFhLQ/s1600/Requirements%2Bfor%2BMerchant%2BProcessing%2BServices%2BProviders.jpg"&gt;&lt;img style="float:right; margin:0 0 10px 10px;cursor:pointer; cursor:hand;width: 281px; height: 300px;" src="http://4.bp.blogspot.com/-s752Wh4soSE/TZY1j0KEEBI/AAAAAAAAAFs/DeYPxzNFhLQ/s320/Requirements%2Bfor%2BMerchant%2BProcessing%2BServices%2BProviders.jpg" border="0" alt="Requirements for Merchant Processing Services Providers" title="Requirements for Merchant Processing Services Providers" id="BLOGGER_PHOTO_ID_5590714876839596050" /&gt;&lt;/a&gt;&lt;a href="https://www.unibulmerchantservices.com/merchant-processing-services"&gt;Merchant processing services&lt;/a&gt; providers allow for-profit and non-commercial institutions to &lt;a href="https://www.unibulmerchantservices.com/take-credit-cards"&gt;take credit cards&lt;/a&gt;, debit cards, checks and other methods of payment online, over the phone or in person. Whatever the card acceptance circumstances, a &lt;a href="https://www.unibulmerchantservices.com/interchange-plus-credit-card-processing"&gt;credit card processing&lt;/a&gt; service is needed to facilitate the process.&lt;br /&gt;&lt;br /&gt;&lt;h3&gt;How Do you Become a Merchant Processing Services Provider&lt;/h3&gt;&lt;br /&gt;In order for an company to become a merchant processing services provider, it first has to be licensed by the Credit Card Associations of &lt;a href="http://blog.unibulmerchantservices.com/u-s-credit-card-spending-jumps-visa-and-mastercard-profits-follow"&gt;Visa and MasterCard&lt;/a&gt;. The registration process involves an examination of the credit files of both the applicant organization and its owners, a review of the business and marketing plans of the applicant. If the application is approved, the applicants are charges registration fees currently at $5,000 for each Association.&lt;br /&gt;&lt;br /&gt;&lt;h3&gt;Why Don't Banks Do That&lt;/h3&gt;&lt;br /&gt;Well, actually some banks do offer merchant merchant processing services directly to the end clients. They are all members of MasterCard and Visa and can do that. However, they prefer contracting with third parties and focusing instead on what they do best: moving money around. By outsourcing the job, the bank assumes the role of a sponsor of the third party entity throughout the application process with the Associations.&lt;br /&gt;&lt;br /&gt;&amp;gt;Merchant processing services providers are known in the industry as Independent Sales Organizations (ISOs) when they are registered by Visa and as Member Service Providers (MSPs) when they are registered by MasterCard. Typically, businesses apply at the same time for the two licenses, using the same sponsor bank.&lt;br /&gt;&lt;br /&gt;&lt;h3&gt;ISO / MSP Relationship with the Processing Bank&lt;/h3&gt;&lt;br /&gt;Upon approval of the application, the sponsor bank becomes a "processing bank" for the newly fledged ISO / MSP. That means that the bank processes the sales and credit transactions generated by the merchants, signed up by its merchant processing services provider. Moreover, the processor is also responsible for the funding of the transaction amounts to the merchant, once it has subtracted its own processing fees as well as the interchange fees charged by the issuers of the cards. At the same time the &lt;a href="http://blog.unibulmerchantservices.com/how-to-select-a-processing-bank-for-your-e-commerce-business"&gt;processing bank&lt;/a&gt; sends a payment request, through the Associations, to the card issuer.&lt;br /&gt;&lt;br /&gt;ISOs and MSPs are mandated to prominently identify the name of their processing bank (or banks in some cases) on all of their marketing materials, including all website pages. ISOs / MSPs typically display this statement in the footer of their websites, which makes it clearly visible from all pages.&lt;br /&gt;&lt;br /&gt;Once registered, merchant processing services providers can contract with their own sales agents to look for merchants. These sales agents can only promote themselves as representatives of their ISO / MSP.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8887473741874669103-7396924688330766249?l=merchantaccountprocessing.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://merchantaccountprocessing.blogspot.com/feeds/7396924688330766249/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2011/04/requirements-for-merchant-processing.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/7396924688330766249'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/7396924688330766249'/><link rel='alternate' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2011/04/requirements-for-merchant-processing.html' title='Requirements for Merchant Processing Services Providers'/><author><name>mss</name><uri>http://www.blogger.com/profile/02682453100579738680</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://4.bp.blogspot.com/-s752Wh4soSE/TZY1j0KEEBI/AAAAAAAAAFs/DeYPxzNFhLQ/s72-c/Requirements%2Bfor%2BMerchant%2BProcessing%2BServices%2BProviders.jpg' height='72' width='72'/><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8887473741874669103.post-6943887361205111619</id><published>2011-03-29T16:49:00.003-04:00</published><updated>2011-03-29T17:49:24.769-04:00</updated><title type='text'>Merchant Credit Card Processing Fees for Online Merchants</title><content type='html'>&lt;a href="http://2.bp.blogspot.com/-JantgVZVVHc/TZJTu9Mmx_I/AAAAAAAAAFM/WTQF3jr1HQI/s1600/Merchant%2BCredit%2BCard%2BProcessing%2BFees%2Bfor%2BOnline%2BMerchants.jpg" onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}"&gt;&lt;img style="float:right; margin:0 0 10px 10px;cursor:pointer; cursor:hand;width: 300px; height: 221px;" src="http://2.bp.blogspot.com/-JantgVZVVHc/TZJTu9Mmx_I/AAAAAAAAAFM/WTQF3jr1HQI/s320/Merchant%2BCredit%2BCard%2BProcessing%2BFees%2Bfor%2BOnline%2BMerchants.jpg" border="0" alt="Merchant Credit Card Processing Fees for Online Merchants" title="Merchant Credit Card Processing Fees for Online Merchants" id="BLOGGER_PHOTO_ID_5589622153686730738" /&gt;&lt;/a&gt;Internet businesses pay higher processing rates for their &lt;a href="https://www.unibulmerchantservices.com/merchant-credit-card-processing"&gt;merchant credit card processing&lt;/a&gt; services than physical retailers. This is a fact that I suspect will come as no surprise to you. The reason for the discrepancy is that card-present transactions are far more probable to lead to customer disputes than card-present ones. This is bad because customer disputes all too often result in chargebacks, which are incredibly costly for both the merchant and the &lt;a href="https://www.unibulmerchantservices.com/flat-rate-merchant-account"&gt;merchant account&lt;/a&gt; provider.&lt;br /&gt;&lt;br /&gt;&lt;h3&gt;Why Are Chargebacks Bad?&lt;/h3&gt;&lt;br /&gt;The problem is that if chargeback rates are allowed to go over 1% of the total transaction number, the &lt;a href="https://www.unibulmerchantservices.com/interchange-plus-credit-card-processing"&gt;credit card processing&lt;/a&gt; service will be suspended by the Credit Card Associations. Or that is what the rule says. In practice, however, the processor will suspend the account well before the ratio comes anywhere close to 1%, because it too will be fined by the Visa and MasterCard, if it exceeds it.&lt;br /&gt;&lt;br /&gt;So you can see that the excessive rates that card-not-present transactions are processed at are in effect an insurance against future chargebacks.&lt;br /&gt;&lt;br /&gt;&lt;h3&gt;Card-not-Present Fee Guidelines&lt;/h3&gt;&lt;br /&gt;Listed below are the various fees that make up the total processing cost for &lt;a href="http://blog.unibulmerchantservices.com/2-services-to-help-e-commerce-merchants-authenticate-shoppers"&gt;e-commerce merchants&lt;/a&gt;, as well as our suggestions for what would be reasonable to agree to for each one of them:&lt;br /&gt;&lt;ul&gt;&lt;li&gt;&lt;strong&gt;Discount rate.&lt;/strong&gt; E-commerce processing fees have fallen drastically over the pastdecade and you should not be paying anything more than 2.14% for credit and 1.94% for debit card transactions for regular consumer types of cards. Special types of cards, e.g. business-to-business, commercial, purchase, etc., are usually processed at higher rates. However, much of that would depend on the pricing structure used by your service provider. Some acquirers, for instance, will provide you one rate for credit and debit cards. The problem here is that debit interchange rates are much lower, so in such cases you would be overcharged. A better choice would be the cost-plus pricing model, where your acquirer's fees will be added directly to the interchange fees, so ensuring that no transaction costs you more than it should.&lt;br /&gt;&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Per-item fee.&lt;/strong&gt; You should not be charged more than $0.30 per transaction.&lt;br /&gt;&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Application processing and service set-up fees.&lt;/strong&gt; You should not be agreeing to any such fees!&lt;br /&gt;&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Payment gateway set-up and monthly fees.&lt;/strong&gt; E-commerce payment gateways are tools that connect e-commerce websites with the payment processor's back-end systems and transmit payment data between them. The most widely used gateway is Authorize.Net. You could be able to have it set up at no charge and your monthly fee should never be above $20.&lt;br /&gt;&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Monthly maintenance fee.&lt;/strong&gt; This fee can have a variety of names, but whatever it is, you should not be paying anything more than $10, preferably $0.&lt;br /&gt;&lt;/li&gt;&lt;li&gt;&lt;strong&gt;PCI fee.&lt;/strong&gt; This fee could be charged monthly or annually. Usually it is in the range of $99 - $199 a year.&lt;br /&gt;&lt;/li&gt;&lt;/ul&gt;You should always evaluate your pricing model as a whole, taking into account all of its components, rather than basing your decision on how much a particular service costs.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8887473741874669103-6943887361205111619?l=merchantaccountprocessing.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://merchantaccountprocessing.blogspot.com/feeds/6943887361205111619/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2011/03/merchant-credit-card-processing-fees.html#comment-form' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/6943887361205111619'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/6943887361205111619'/><link rel='alternate' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2011/03/merchant-credit-card-processing-fees.html' title='Merchant Credit Card Processing Fees for Online Merchants'/><author><name>mss</name><uri>http://www.blogger.com/profile/02682453100579738680</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://2.bp.blogspot.com/-JantgVZVVHc/TZJTu9Mmx_I/AAAAAAAAAFM/WTQF3jr1HQI/s72-c/Merchant%2BCredit%2BCard%2BProcessing%2BFees%2Bfor%2BOnline%2BMerchants.jpg' height='72' width='72'/><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8887473741874669103.post-6848875363802167821</id><published>2011-03-25T15:40:00.002-04:00</published><updated>2011-03-25T16:05:08.676-04:00</updated><title type='text'>Credit Card Services for Cruise Lines</title><content type='html'>&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://3.bp.blogspot.com/-_UQ_kizVqHQ/TYz1XIdsM-I/AAAAAAAAAE0/KTNo_s5T2g4/s1600/Credit%2BCard%2BServices%2Bfor%2BCruise%2BLines.jpg"&gt;&lt;img style="float:right; margin:0 0 10px 10px;cursor:pointer; cursor:hand;width: 300px; height: 240px;" src="http://3.bp.blogspot.com/-_UQ_kizVqHQ/TYz1XIdsM-I/AAAAAAAAAE0/KTNo_s5T2g4/s320/Credit%2BCard%2BServices%2Bfor%2BCruise%2BLines.jpg" border="0" alt="Credit Card Services for Cruise Lines" title="Credit Card Services for Cruise Lines" id="BLOGGER_PHOTO_ID_5588111015417754594" /&gt;&lt;/a&gt;Managers of cruise line businesses need to follow &lt;a href="https://www.unibulmerchantservices.com/credit-card-services"&gt;credit card services&lt;/a&gt; procedures that are somewhat different from these required of most other cad acceptors that &lt;a href="https://www.unibulmerchantservices.com/take-credit-cards"&gt;take credit cards&lt;/a&gt; in retail stores or other traditional types of settings.&lt;br /&gt;&lt;br /&gt;In this short post I will examine the best practices that you should implement each time you accept a card payment to help you achieve the lowest possible processing rates:&lt;br /&gt;&lt;ol&gt;&lt;li&gt;&lt;b&gt;Get an authorization approval for any on-board charges that were not originally authorized.&lt;/b&gt; To obtain an additional &lt;a href="http://blog.unibulmerchantservices.com/transaction-authorization-resources"&gt;transaction authorization&lt;/a&gt; approval from the card issuer for the amount that your customer has incurred on board of the cruise liner:&lt;br /&gt;&lt;ol&gt;&lt;li&gt;Implement regular authorization procedures to get an approval for the additional amount.&lt;/li&gt;&lt;li&gt;If your authorization request is declined by the issuer, do not push the payment through, but instead ask your customer for another method of payment.&lt;/li&gt;&lt;/ol&gt;&lt;/li&gt;&lt;li&gt;&lt;b&gt;If the additional authorization request was not approved, only submit for settlement the amount that is already approved.&lt;/b&gt; The following best practices for transaction settlement will help you minimize customer dispute and chargeback rates, which will lower your processing costs and potential losses from declined authorizations. In particular, you will need to:&lt;br /&gt;&lt;ol&gt;&lt;li&gt;Only settle the approved authorization amount, leaving out any of the on-board charges, for which authorization from the issuer has not received.&lt;/li&gt;&lt;li&gt;Ask your customer that he provides a different form of payment for the rejected additional amount.&lt;/li&gt;&lt;/ol&gt;&lt;/li&gt;&lt;li&gt;&lt;b&gt;If the amount of the initially approved authorization is bigger than the real final cost of the service, submit an authorization reversal for the overcharge.&lt;/b&gt; To finalize the settlement and to ensure that you do not overcharge your customer, you will have to issue an authorization reversal for the excessive amount.&lt;/li&gt;&lt;li&gt;&lt;b&gt;How to use the final authorization and the 15% rules.&lt;/b&gt; At the check-out at the end of the cruise, transaction authorization is only needed in the following instances:&lt;br /&gt;&lt;ol&gt;&lt;li&gt;If, for one reason or other, you did not obtain an authorization approval at the beginning. If that is the case, authorize the whole transaction amount.&lt;/li&gt;&lt;li&gt;You did get an authorization approval initially, but the final amount is bigger than the initially authorized amount. It is here that you will need to use the 15% rule to see if you need to request an additional authorization approval. Here is a step-by-step guide on how this is to be done:&lt;br /&gt;&lt;ol&gt;&lt;li&gt;Begin by adding 15% to the initially authorized amount.&lt;/li&gt;&lt;li&gt;Compare the sum you received above to the final transaction amount.&lt;/li&gt;&lt;li&gt;If the final transaction amount is bigger than the sum you received, you will have to request an authorization approval for the difference.&lt;/li&gt;&lt;/ol&gt;&lt;/li&gt;&lt;/ol&gt;&lt;/li&gt;&lt;li&gt;&lt;b&gt;Disclose and obtain acceptance of all terms and conditions of the sale.&lt;/b&gt; It is really critical that visitors to your website fully understand the terms and conditions of the sale, prior to placing an order. In particular, these details will have to be disclosed:&lt;br /&gt;&lt;ol&gt;&lt;li&gt;The total sale's amount, with all booking fees and other charges.&lt;/li&gt;&lt;li&gt;How these additional charges will be posted on your customer's monthly card statement.&lt;/li&gt;&lt;li&gt;When and how these charges will be applied.&lt;/li&gt;&lt;br /&gt;&lt;/ol&gt;Now that you have disclosed your terms and conditions, you need to get the consumer to agree to them, before taking her to the checkout to complete the transaction.&lt;br /&gt;&lt;/li&gt;&lt;/ol&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8887473741874669103-6848875363802167821?l=merchantaccountprocessing.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://merchantaccountprocessing.blogspot.com/feeds/6848875363802167821/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2011/03/credit-card-services-for-cruise-lines.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/6848875363802167821'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/6848875363802167821'/><link rel='alternate' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2011/03/credit-card-services-for-cruise-lines.html' title='Credit Card Services for Cruise Lines'/><author><name>mss</name><uri>http://www.blogger.com/profile/02682453100579738680</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://3.bp.blogspot.com/-_UQ_kizVqHQ/TYz1XIdsM-I/AAAAAAAAAE0/KTNo_s5T2g4/s72-c/Credit%2BCard%2BServices%2Bfor%2BCruise%2BLines.jpg' height='72' width='72'/><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8887473741874669103.post-393456990384909190</id><published>2011-03-21T16:59:00.002-04:00</published><updated>2011-03-21T17:31:04.288-04:00</updated><title type='text'>How to Take Credit Cards At Hotels</title><content type='html'>&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://3.bp.blogspot.com/-aEb_YNWzfHM/TYfDfVhcgEI/AAAAAAAAAEc/SfXZ5rc-JXE/s1600/How%2Bto%2BTake%2BCredit%2BCards%2BAt%2BHotels.jpg"&gt;&lt;img style="float:right; margin:0 0 10px 10px;cursor:pointer; cursor:hand;width: 300px; height: 300px;" src="http://3.bp.blogspot.com/-aEb_YNWzfHM/TYfDfVhcgEI/AAAAAAAAAEc/SfXZ5rc-JXE/s320/How%2Bto%2BTake%2BCredit%2BCards%2BAt%2BHotels.jpg" border="0" alt="How to Take Credit Cards At Hotels" title="How to Take Credit Cards At Hotels" id="BLOGGER_PHOTO_ID_5586648805897175106" /&gt;&lt;/a&gt;Credit card acceptance at hotels, motels and other lodging types of businesses is done differently than it is at most other businesses. The are specific rules on how to &lt;a href="https://www.unibulmerchantservices.com/take-credit-cards"&gt;take credit cards&lt;/a&gt; that need to be followed. Hotel managers and owners will have to be familiar with these rules and able to implement them into their &lt;a href="https://www.unibulmerchantservices.com/credit-card-processing"&gt;credit card processing&lt;/a&gt; procedures.&lt;br /&gt;&lt;br /&gt;The reason for these peculiarities is that credit card processing at hotels and motels follows a slightly different path than transactions at other types of businesses. In this article I will offer a step-by-step guide on exactly how to do it:&lt;br /&gt;&lt;ol&gt;&lt;li&gt;Often a customer will extend her stay. When that happens or, if additional charges have been incurred, there will be a need to obtain an additional authorization approval for the difference, not for the total final amount. Keep in mind that you have already received an authorization approval for the original amount and there is no need to do it again. Following are the guidelines on how to do this:&lt;br /&gt;&lt;ol&gt;&lt;li&gt;Keep in mind that  for the additional amount you will need to follow your standard &lt;span style="text-decoration: underline;"&gt;&lt;/span&gt;&lt;a href="https://www.unibulmerchantservices.com/accept-credit-cards"&gt;transaction authorization&lt;/a&gt; process for obtaining an approval.&lt;/li&gt;&lt;li&gt;Sometimes your authorization request for the additional amount will be rejected. When that happens, do not submit the payment for settlement. Instead ask that your customer provides an alternative form of payment (another card, check, etc.) for the additional charges.&lt;/li&gt;&lt;/ol&gt;&lt;/li&gt;&lt;li&gt;If you have not received an authorization approval for the additional amount, only deposit for settlement the originally authorized amount.  If the authorization request for the additional amount was declined, you should:&lt;ol&gt;&lt;li&gt;Only settle the amount that was originally authorized, without including any amount for which authorization was rejected.&lt;/li&gt;&lt;li&gt;Immediately call your customer and demand an alternative form of payment for the amount for which authorization was declined.&lt;/li&gt;&lt;/ol&gt;&lt;/li&gt;&lt;li&gt;Request an authorization reversal if the originally authorized amount is greater than the final cost of your service. In such cases, you will have to request an authorization reversal for the balance between the originally authorized amount and the actual cost of the hotel stay.&lt;/li&gt;&lt;li&gt;Understand and use the final authorization and the fifteen percent rules. Be advised that at check out, authorization approval is required in the following circumstances:&lt;br /&gt;&lt;ol&gt;&lt;li&gt;You did not obtain an initial authorization. If that is the case, issue an authorization request for the total amount.&lt;/li&gt;&lt;li&gt;You did obtain an authorization approval originally, but the final amount is greater than the authorized one. Whenever this is the case, use the fifteen percent rule to estimate whether or not an additional authorization approval is needed. Here is how to do this:&lt;br /&gt;&lt;ol&gt;&lt;li&gt;Add fifteen percent to the already authorized amount.&lt;/li&gt;&lt;li&gt;Compare the so-received total to the final transaction amount.&lt;/li&gt;&lt;li&gt;If the final transaction amount is greater than the newly calculated total, you need to request an authorization approval for the difference between the initially authorized amount and the final transaction amount.&lt;/li&gt;&lt;/ol&gt;&lt;/li&gt;&lt;/ol&gt;&lt;/li&gt;&lt;li&gt;Require that your customers accept the terms and conditions of the sale. You need to inform your customers what all of the terms and conditions of the sale are prior to them completing a reservation for a hotel room. More particularly, you need to disclose the following details:&lt;ol&gt;&lt;li&gt;Your business' cancellation policy.&lt;/li&gt;&lt;li&gt;Whether or not a "no-show" charge will be applied to the total amount or will be charged individually.&lt;/li&gt;&lt;li&gt;When the "no show" fee will be charged, if applicable.&lt;/li&gt;&lt;li&gt;The way your hotel's name will be shown on your customer's monthly credit card statement. &lt;/li&gt;&lt;/ol&gt;&lt;br /&gt;The full disclosure of these terms will help limit customer inquiries and disputes which will, in turn, minimize chargebacks. This should be a primary goal for you, as chargebacks are extremely costly and time consuming.&lt;br /&gt;&lt;br /&gt;For best results, require that your customers accept the above-mentioned terms and conditions of the sale by clicking on an "Accept," "Agree" or another button to that effect under the disclosure statement on your website.&lt;/li&gt;&lt;/ol&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8887473741874669103-393456990384909190?l=merchantaccountprocessing.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://merchantaccountprocessing.blogspot.com/feeds/393456990384909190/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2011/03/how-to-take-credit-cards-at-hotels.html#comment-form' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/393456990384909190'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/393456990384909190'/><link rel='alternate' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2011/03/how-to-take-credit-cards-at-hotels.html' title='How to Take Credit Cards At Hotels'/><author><name>mss</name><uri>http://www.blogger.com/profile/02682453100579738680</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://3.bp.blogspot.com/-aEb_YNWzfHM/TYfDfVhcgEI/AAAAAAAAAEc/SfXZ5rc-JXE/s72-c/How%2Bto%2BTake%2BCredit%2BCards%2BAt%2BHotels.jpg' height='72' width='72'/><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8887473741874669103.post-6214963897463688816</id><published>2011-03-17T18:50:00.008-04:00</published><updated>2011-03-18T23:20:12.159-04:00</updated><title type='text'>Interchange-Plus Credit Card Processing Pricing</title><content type='html'>&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://1.bp.blogspot.com/-6QLtHLSB-Gc/TYKR0d_3HvI/AAAAAAAAAEE/nbzkzLL9LY0/s1600/Interchange-Plus%2BCredit%2BCard%2BProcessing%2BPricing.jpg"&gt;&lt;img style="float:right; margin:0 0 10px 10px;cursor:pointer; cursor:hand;width: 300px; height: 193px;" src="http://1.bp.blogspot.com/-6QLtHLSB-Gc/TYKR0d_3HvI/AAAAAAAAAEE/nbzkzLL9LY0/s320/Interchange-Plus%2BCredit%2BCard%2BProcessing%2BPricing.jpg" border="0" alt="Interchange-Plus Credit Card Processing Pricing" title="Interchange-Plus Credit Card Processing Pricing" id="BLOGGER_PHOTO_ID_5585186818484543218" /&gt;&lt;/a&gt;&lt;a href="https://www.unibulmerchantservices.com/"&gt;UniBul Merchant Services&lt;/a&gt; has just added interchange-plus pricing to its line-up of pricing models.  The new pricing structure will be available to merchants &lt;a href="https://www.unibulmerchantservices.com/accept-credit-and-debit-cards"&gt;accepting credit and debit cards&lt;/a&gt; in both face-to-face and card-not-present setting.&lt;div&gt;&lt;br /&gt;Most businesses place pricing at the very top of their lists of priorities when selecting a &lt;a href="http://blog.unibulmerchantservices.com/"&gt;credit card processing&lt;/a&gt; provider. It is understandable and anyway most of us do exactly the same when selecting service providers. Nevertheless, offering low pricing is the only way a payment processor can be competitive and it is the reason UniBul Merchant Services has designed an &lt;a href="https://www.unibulmerchantservices.com/interchange-plus-credit-card-processing"&gt;interchange-plus credit card processing&lt;/a&gt; model. It works by adding UniBul's own cost to the interchange fee charged by Visa and MasterCard for each card transaction. By ensuring that its mark-up is as low as possible, UniBul guarantees that merchants get the lowest possible processing rate.&lt;/div&gt;&lt;div&gt;&lt;br /&gt;UniBul Merchant Services' new interchange-plus pricing model comes with no fixed monthly fees. Here is a list of the applicable rates and fees:&lt;br /&gt;&lt;ul&gt;&lt;li&gt;Application fee - $0.&lt;/li&gt;&lt;li&gt;Merchant account set-up fee - $0.&lt;/li&gt;&lt;li&gt;Equipment set-up or reprogramming fee - $0.&lt;/li&gt;&lt;li&gt;Authorize.Net gateway set-up fee - $0.&lt;/li&gt;&lt;li&gt;Authorize.Net gateway monthly fee - $0.&lt;/li&gt;&lt;li&gt;Monthly statement fee - $0.&lt;/li&gt;&lt;li&gt;Visa / MasterCard discount rate – 0.25% + $0.15 above interchange cost.&lt;/li&gt;&lt;/ul&gt;The merchant's processing rate is the sum of whatever the processor (e.g. UniBul Merchant Services) charges and what Visa or MasterCard charge. With the interchange-plus credit card processing model, the rate the processor charges is exactly the same for all types of cards, which ensures that the merchant does not get arbitrarily overcharged for transactions that may otherwise have been classified as "mid-" or "non-qualified." The total processing cost will vary by transaction, because the fees charged by Visa and MasterCard vary by card type.&lt;/div&gt;&lt;div&gt;&lt;br /&gt;Other service benefits include:&lt;/div&gt;&lt;div&gt;&lt;ul&gt;&lt;li&gt;Fast application decision.&lt;/li&gt;&lt;li&gt;Full pricing disclosure prior to any contract agreement.&lt;/li&gt;&lt;li&gt;Acceptance of all major cards.&lt;/li&gt;&lt;li&gt;PayPal, Google Checkout, Amazon Payments, eChecks and eBillme third party payment options.&lt;/li&gt;&lt;li&gt;Daily ACH deposits into the merchant's checking account.&lt;/li&gt;&lt;li&gt;Risk management services to limit fraud exposure.&lt;/li&gt;&lt;li&gt;Web-based client center for complete account management.&lt;/li&gt;&lt;li&gt;US-based merchant support.&lt;/li&gt;&lt;/ul&gt;"This is the best interchange-plus pricing model in the industry and it guarantees lowest total cost of accepting credit cards," says Greg Stanski, VP of Sales for UniBul Merchant Services "When comparing pricing models, merchants need to estimate the total processing costs. Lower headline fees may be advertised on other websites, but you will get hit with set-up fees , additional fees for accepting rewards cards and corporate cards (the so-called mid-qualified and non-qualified fees), etc.," he added.&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8887473741874669103-6214963897463688816?l=merchantaccountprocessing.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://merchantaccountprocessing.blogspot.com/feeds/6214963897463688816/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2011/03/interchange-plus-credit-card-processing.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/6214963897463688816'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/6214963897463688816'/><link rel='alternate' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2011/03/interchange-plus-credit-card-processing.html' title='Interchange-Plus Credit Card Processing Pricing'/><author><name>mss</name><uri>http://www.blogger.com/profile/02682453100579738680</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://1.bp.blogspot.com/-6QLtHLSB-Gc/TYKR0d_3HvI/AAAAAAAAAEE/nbzkzLL9LY0/s72-c/Interchange-Plus%2BCredit%2BCard%2BProcessing%2BPricing.jpg' height='72' width='72'/><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8887473741874669103.post-4967838139797162886</id><published>2011-03-14T18:57:00.003-04:00</published><updated>2011-03-15T19:11:14.250-04:00</updated><title type='text'>Non-Acceptable Businesses for Credit Card Merchant Services</title><content type='html'>&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://1.bp.blogspot.com/-ujEvpMLrx-Q/TX6kj0AVl-I/AAAAAAAAADk/1MPnNBGqQ2I/s1600/Non-Acceptable%2BBusinesses%2Bfor%2BCredit%2BCard%2BMerchant%2BServices.jpg"&gt;&lt;img style="float:right; margin:0 0 10px 10px;cursor:pointer; cursor:hand;width: 202px; height: 300px;" src="http://1.bp.blogspot.com/-ujEvpMLrx-Q/TX6kj0AVl-I/AAAAAAAAADk/1MPnNBGqQ2I/s320/Non-Acceptable%2BBusinesses%2Bfor%2BCredit%2BCard%2BMerchant%2BServices.jpg" border="0" alt="Non-Acceptable Businesses for Credit Card Merchant Services" title="Non-Acceptable Businesses for Credit Card Merchant Services" id="BLOGGER_PHOTO_ID_5584081523148429282" /&gt;&lt;/a&gt;There are quite a few business types that are restricted or outright barred from setting up &lt;a href="https://www.unibulmerchantservices.com/credit-card-merchant-services"&gt;credit card merchant services&lt;/a&gt; in the U.S. The ultimate decision on exactly what business categories are included in these "black lists" are made by the &lt;a href="https://www.unibulmerchantservices.com/payment-processing"&gt;payment processing&lt;/a&gt; providers, although the Credit Card Associations of Visa and MasterCard certainly play a role in the process. These lists are periodically updated and certain types may be included or excluded.&lt;br /&gt;&lt;br /&gt;The single biggest factor taken into account by the processors when determining whether or not a particular type of business should be allowed to set up a US-based &lt;a href="http://blog.unibulmerchantservices.com/merchant-account-resources"&gt;merchant account&lt;/a&gt; is the risk of generating chargebacks. Historical data show that in some industries the chargeback risk is simply too high. It should be said that, even when credit card merchant services are set up, chargeback levels are monitored on a continuous basis and, if they go over one percent of the total transaction count for any single month, the business will be categorized as excessive chargeback merchant (ECM) and subjected to heavy additional requirements. Businesses that can't fix their chargeback issue within three consecutive months lose their  processing accounts altogether.&lt;br /&gt;&lt;br /&gt;Following is a sample of business types for which credit card merchant services will be rejected, however remember that each processor makes their own list.&lt;br /&gt;&lt;ul&gt;&lt;li&gt;Advanced payments greater than 1 year.&lt;/li&gt;&lt;li&gt;Airlines.&lt;/li&gt;&lt;li&gt;Any merchant engaged in illegal products or activities.&lt;/li&gt;&lt;li&gt;Bidding fee auctions.&lt;/li&gt;&lt;li&gt;Business / investment types operating as "get-rich-quick" schemes.&lt;/li&gt;&lt;li&gt;Adult oriented products or services (all media types: internet, telephone, printed material etc.).&lt;/li&gt;&lt;li&gt;Cash advances (except regulated financial institutions).&lt;/li&gt;&lt;li&gt;Internet and mail order / telephone order (MO / TO) pharmacies (where the fulfillment of the prescription is performed with an online or telephone consultation, without a physical visit with a physician).&lt;/li&gt;&lt;li&gt;Charities without proof of 501( C ) (3) status.&lt;/li&gt;&lt;li&gt;Check cashing establishments.&lt;/li&gt;&lt;li&gt;Collection agencies or any other entities engaged in the collection of past due receivables.&lt;/li&gt;&lt;li&gt;Companion or escort services.&lt;/li&gt;&lt;li&gt; Internet or MO / TO firearm or weapons sales (including ammunition).&lt;/li&gt;&lt;li&gt;Credit card protection or identity theft service.&lt;/li&gt;&lt;li&gt;Internet or MO / TO cigarette tobacco sales.&lt;/li&gt;&lt;li&gt;Occult services or materials.&lt;/li&gt;&lt;li&gt;Internet gambling.&lt;/li&gt;&lt;li&gt;Credit repair or restoration services.&lt;/li&gt;&lt;li&gt;Currency exchanges.&lt;/li&gt;&lt;li&gt;Any types of lotteries or raffles.&lt;/li&gt;&lt;li&gt;Sports forecasting services or odds making.&lt;/li&gt;&lt;li&gt;Extended warranty companies.&lt;/li&gt;&lt;li&gt;Foreclosure protection and guarantees.&lt;/li&gt;&lt;li&gt;Herbal smoking blends and herbal incense.&lt;/li&gt;&lt;li&gt;Lifetime subscriptions for any product or service.&lt;/li&gt;&lt;/ul&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8887473741874669103-4967838139797162886?l=merchantaccountprocessing.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://merchantaccountprocessing.blogspot.com/feeds/4967838139797162886/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2011/03/non-acceptable-businesses-for-credit.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/4967838139797162886'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/4967838139797162886'/><link rel='alternate' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2011/03/non-acceptable-businesses-for-credit.html' title='Non-Acceptable Businesses for Credit Card Merchant Services'/><author><name>mss</name><uri>http://www.blogger.com/profile/02682453100579738680</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://1.bp.blogspot.com/-ujEvpMLrx-Q/TX6kj0AVl-I/AAAAAAAAADk/1MPnNBGqQ2I/s72-c/Non-Acceptable%2BBusinesses%2Bfor%2BCredit%2BCard%2BMerchant%2BServices.jpg' height='72' width='72'/><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8887473741874669103.post-6826803563710938853</id><published>2011-03-10T16:08:00.004-05:00</published><updated>2011-03-14T19:30:13.775-04:00</updated><title type='text'>Essential Facts About Credit Card Processing Floor Limits</title><content type='html'>&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://4.bp.blogspot.com/-MGYKJjZbO_A/TX6k8A1HtII/AAAAAAAAADs/CNdC8gsGizw/s1600/Essential%2BFacts%2BAbout%2BCredit%2BCard%2BProcessing%2BFloor%2BLimits.jpg"&gt;&lt;img style="float:right; margin:0 0 10px 10px;cursor:pointer; cursor:hand;width: 300px; height: 212px;" src="http://4.bp.blogspot.com/-MGYKJjZbO_A/TX6k8A1HtII/AAAAAAAAADs/CNdC8gsGizw/s320/Essential%2BFacts%2BAbout%2BCredit%2BCard%2BProcessing%2BFloor%2BLimits.jpg" border="0" alt="Essential Facts About Credit Card Processing Floor Limits" title="Essential Facts About Credit Card Processing Floor Limits" id="BLOGGER_PHOTO_ID_5584081938907903106" /&gt;&lt;/a&gt;Floor limit is the threshold above which all credit card payments must receive an authorization approval from the issuer before being processed. Floor limits vary from one card acceptor to another and are specified in the &lt;a href="https://www.unibulmerchantservices.com/credit-card-processing"&gt;credit card processing&lt;/a&gt; agreement.&lt;br /&gt;&lt;br /&gt;E-commerce and MO / TO businesses, as well as all others &lt;a href="https://www.unibulmerchantservices.com/accept-credit-cards"&gt;accepting credit card&lt;/a&gt; payments in a non-face-to-face setting, have a zero floor limit, which means that all of their transactions must be authorized, whatever the payment amount. All card-present transactions, including payments at cardholder-activated terminals (CATs), like the ones at your gas, bus or train stations, typically have a floor limit.&lt;br /&gt;&lt;br /&gt;So if a convenience store's floor limit is $50.00, all purchases of $49.99 or less will not have to be authorized, while transactions of $50.00 or more will need to obtain one. &lt;a href="http://blog.unibulmerchantservices.com/transaction-authorization-resources"&gt;Transaction authorization&lt;/a&gt; is the process through which the issuer of the card approves or declines a transaction, after comparing the provided information to what it has on file for its cardholder.&lt;br /&gt;&lt;br /&gt;In a card-present setting, the authorization is requested automatically after the cardholder swipes his card through the store's point-of-sale (POS) machine. In a card-not-present environment, the authorization is again requested automatically, after the card account's information is provided on a website or over the telephone.  Either way, once the transaction information is submitted, it is sent to the card issuer via Visa's or MasterCard's payment systems and then the issuer's decision is sent back to the merchant through the same channel.&lt;br /&gt;&lt;br /&gt;There was a time when floor limits had a much bigger importance than they have today. Years ago the card acceptor had to request an authorization approval for any transaction amount that was over a pre-defined level. Back then credit card processing involved the taking of a physical imprint of the card and the authorization process required a personal review of the transaction, which made the process both time consuming and expensive. Today card acceptors have at their disposal electronic authorization systems that make the process a very simple and inexpensive one. Once a transaction is authorized, the merchant gets an additional, and very powerful, protection against fraud.&lt;br /&gt;&lt;br /&gt;Yet, even today, the concept of a floor limit gets discussed every now and again.  For example, if a card acceptor is unable to connect to the credit card processing provider's authorization system, she will not be able to obtain an electronic authorization and will have no protection against fraud or a customer dispute, both of which can very easily deteriorate into a chargeback. At the same time, if the payment amount is lower than the floor limit, an authorization is not necessary. If, however, the amount exceeds the floor limit, the card acceptor must request an authorization approval for the transaction and should do this by making a telephone call to the processor's voice authorization center and obtaining a "voice authorization." You should only do that as a last resort, because voice authorizations circumvent the processor's system and leave you unprotected against chargebacks. If you have to do it, you should take the card's imprint on the transaction receipt.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8887473741874669103-6826803563710938853?l=merchantaccountprocessing.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://merchantaccountprocessing.blogspot.com/feeds/6826803563710938853/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2011/03/essential-facts-about-credit-card.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/6826803563710938853'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/6826803563710938853'/><link rel='alternate' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2011/03/essential-facts-about-credit-card.html' title='Essential Facts About Credit Card Processing Floor Limits'/><author><name>mss</name><uri>http://www.blogger.com/profile/02682453100579738680</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://4.bp.blogspot.com/-MGYKJjZbO_A/TX6k8A1HtII/AAAAAAAAADs/CNdC8gsGizw/s72-c/Essential%2BFacts%2BAbout%2BCredit%2BCard%2BProcessing%2BFloor%2BLimits.jpg' height='72' width='72'/><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8887473741874669103.post-3923883859380441151</id><published>2011-03-06T19:36:00.002-05:00</published><updated>2011-03-06T20:09:59.712-05:00</updated><title type='text'>Merchant Account Application Requirements</title><content type='html'>&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://4.bp.blogspot.com/-HKD4apw51EY/TXQwRaVUTgI/AAAAAAAAACs/HibxKYm-a6k/s1600/Merchant%2BAccount%2BApplication%2BRequirements.bmp"&gt;&lt;img style="float:right; margin:0 0 10px 10px;cursor:pointer; cursor:hand;width: 300px; height: 223px;" src="http://4.bp.blogspot.com/-HKD4apw51EY/TXQwRaVUTgI/AAAAAAAAACs/HibxKYm-a6k/s320/Merchant%2BAccount%2BApplication%2BRequirements.bmp" border="0" alt="Merchant Account Application Requirements" title="Merchant Account Application Requirements" id="BLOGGER_PHOTO_ID_5581138913903529474" /&gt;&lt;/a&gt;Applying for a &lt;a href="https://www.unibulmerchantservices.com/"&gt;merchant account&lt;/a&gt; is not exactly a straightforward process. In order to understand why this is so, you will have to first understand this type of service is.&lt;br /&gt;&lt;br /&gt;Merchant account is seen by &lt;a href="http://blog.unibulmerchantservices.com/how-to-select-a-processing-bank-for-your-e-commerce-business"&gt;processing banks&lt;/a&gt; as a form of line of credit they extend to a card acceptor. The reason is that, when you &lt;a href="https://www.unibulmerchantservices.com/accept-credit-cards"&gt;accept credit cards&lt;/a&gt; for payment, your processor pays you before it gets paid. So there is a certain risk involved that they have to account for.&lt;br /&gt;&lt;br /&gt;To achieve that, the application process is set up to establish the credit worthiness of both the business n and its owners. Listed below are the documents that you will have to provide to your processor:&lt;ul&gt;&lt;li&gt;Merchant processing agreement. It collects details about your business and its owner, including the addresses (business and personal), SSN, tax ID (if applicable), telephone number, email address, etc.&lt;/li&gt;&lt;li&gt;Personal guarantee. Unless you are running a publicly listed corporations or a non-profit, the personal guarantee is a must.&lt;/li&gt;&lt;li&gt;Articles of Organization. LLCs and all types of corporations must provide their legal papers, as well as their DBA names. You cannot open a merchant account under your personal name.&lt;/li&gt;&lt;li&gt;Business permit or license. If required by your state or municipality, you will have to provide one of these documents.&lt;/li&gt;&lt;li&gt;Financial statements. Most existing businesses are required to provide financials for the latest two years. The same requirement applies to their principal owners.&lt;/li&gt;&lt;li&gt;Monthly statements with the current processor. If the business is presently accepting electronic payments and is looking for a new service provider, it will be asked to provide the three latest statements.&lt;/li&gt;&lt;li&gt;Voided business check. A copy of  a voided permanent business check is needed, so that the processor knows where to make deposits. If the permanent checks are not yet available, a bank letter can substitute.&lt;/li&gt;&lt;/ul&gt;So the list of requirements for merchant account applicants is quite long, as you can see and it has to be said that this is its short version. The person reviewing the documents may request additional paperwork if what they have is not sufficient to make a decision.&lt;br /&gt;&lt;br /&gt;When they have all the information they need, the processors try to establish first of all whether or not the business is a legitimate entity and that its principals have a good credit history, without major issues. Additionally, however, processors try to precisely pinpoint the industry where the business operates. Certain industries are considered higher risk than others and require deeper examination, while other industries are banned from merchant account services altogether.&lt;br /&gt;&lt;br /&gt;It is always a good idea to check your prospective processor's credit policies before applying to avoid potential unpleasant surprises.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8887473741874669103-3923883859380441151?l=merchantaccountprocessing.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://merchantaccountprocessing.blogspot.com/feeds/3923883859380441151/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2011/03/merchant-account-application.html#comment-form' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/3923883859380441151'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/3923883859380441151'/><link rel='alternate' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2011/03/merchant-account-application.html' title='Merchant Account Application Requirements'/><author><name>mss</name><uri>http://www.blogger.com/profile/02682453100579738680</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://4.bp.blogspot.com/-HKD4apw51EY/TXQwRaVUTgI/AAAAAAAAACs/HibxKYm-a6k/s72-c/Merchant%2BAccount%2BApplication%2BRequirements.bmp' height='72' width='72'/><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8887473741874669103.post-9104551831147471419</id><published>2011-03-01T22:56:00.005-05:00</published><updated>2011-03-03T18:22:57.453-05:00</updated><title type='text'>Payment Processing when the POS Terminal is Down</title><content type='html'>&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://3.bp.blogspot.com/-e533-2eHV2g/TXAiaAJ0xuI/AAAAAAAAACE/PwPn1ANlQaI/s1600/Payment%2BProcessing%2Bwhen%2Bthe%2BPOS%2BTerminal%2Bis%2BDown.jpg"&gt;&lt;img style="float:right; margin:0 0 10px 10px;cursor:pointer; cursor:hand;width: 300px; height: 207px;" src="http://3.bp.blogspot.com/-e533-2eHV2g/TXAiaAJ0xuI/AAAAAAAAACE/PwPn1ANlQaI/s320/Payment%2BProcessing%2Bwhen%2Bthe%2BPOS%2BTerminal%2Bis%2BDown.jpg" border="0" title="Payment Processing when the POS Terminal is Down" alt="Payment Processing when the POS Terminal is Down" id="BLOGGER_PHOTO_ID_5579997768425195234" /&gt;&lt;/a&gt;In a face-to-face setting you should always try to complete a swiped transaction. It reduces the probability of a fraudulent  transaction taking place and it gives you the best processing rate. The card's magnetic stripe is read and the information is sent to your &lt;a href="https://www.unibulmerchantservices.com/payment-processing"&gt;payment processing&lt;/a&gt; bank for authorization.&lt;br /&gt;&lt;br /&gt;You are responsible for making sure that the  transaction is valid and are required to examine the card for signs of alteration and to verify the  cardholder's signature by comparing it to the one on the  sales receipt.&lt;br /&gt;&lt;br /&gt;But what do you do if the terminal cannot read the card? You still must be able to &lt;a href="https://www.unibulmerchantservices.com/accept-credit-cards"&gt;accept credit card&lt;/a&gt; payments, right? Yes and I will show you how to do it.&lt;div&gt;&lt;br /&gt;&lt;h3&gt;Why Is the Card Unreadable?&lt;/h3&gt;&lt;br /&gt;It actually happens quite often that the credit card machine will be unable to read the magnetic stripe. There can be several reasons for that, including the following:&lt;br /&gt;&lt;ul&gt; &lt;li style="FONT-WEIGHT: bold"&gt;The POS terminal is malfunctioning.&lt;/li&gt; &lt;li style="FONT-WEIGHT: bold"&gt;The customer is swiping the card improperly.&lt;/li&gt; &lt;li&gt;&lt;span style="FONT-WEIGHT: bold"&gt;The  magnetic stripe is damaged  or demagnetized.&lt;/span&gt; If that is the case you should not jump to the conclusion that a &lt;a href="http://blog.unibulmerchantservices.com/how-to-manage-chargebacks-resulting-from-multiple-fraudulent-transactions"&gt;fraudulent transaction&lt;/a&gt; is being attempted. Yes, that is definitely possibility, but it can also happen by accident. I have seen a Starbucks barista deal with the problem by wrapping the card into a plastic bag and successfully swiping it. I don't necessarily advertise it, but it worked.&lt;/li&gt;&lt;/ul&gt;&lt;h3&gt;Payment Processing When the Terminal is Down&lt;/h3&gt;&lt;br /&gt;So when the credit card machine cannot read the card, for whatever reason, follow these guidelines:&lt;br /&gt;&lt;ul&gt; &lt;li&gt;&lt;b&gt;Make sure the terminal functions properly&lt;/b&gt;. Check the connection and all other signs that a fully functional POS terminal normally displays.&lt;/li&gt;&lt;li&gt;&lt;b&gt;Make sure the card is swiped correctly&lt;/b&gt;. Verify that the customer swipes her card the right way and in the right direction.&lt;/li&gt; &lt;li&gt;&lt;b&gt;Examine the card&lt;/b&gt;. If the machine is in order and the card is being swiped correctly, the problem must be with the card itself, so check for signs of alteration.&lt;/li&gt;&lt;li style="text-align: left;"&gt;&lt;b&gt;If the card is altered, do not complete the transaction.&lt;/b&gt; Instead return the card to your customer and request an alternative payment form.&lt;/li&gt;&lt;li style="text-align: left;"&gt;&lt;b&gt;If there are no signs of alteration, key-enter the information&lt;/b&gt;. Sometimes you will have to pay a higher price for accepting payments and this is just such an occasion.&lt;/li&gt; &lt;li&gt;&lt;b&gt;Take an imprint of the card.&lt;/b&gt; Take the card's imprint for all key-entered and voice authorized transactions and place it on the front of the card as a proof that the card was  present when the payment was made.&lt;/li&gt;&lt;/ul&gt;That's it. Again, key-entering transaction information should be your last resort, so always exhaust all other possibilities before doing it.&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8887473741874669103-9104551831147471419?l=merchantaccountprocessing.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://merchantaccountprocessing.blogspot.com/feeds/9104551831147471419/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2011/03/payment-processing-when-pos-terminal-is.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/9104551831147471419'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/9104551831147471419'/><link rel='alternate' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2011/03/payment-processing-when-pos-terminal-is.html' title='Payment Processing when the POS Terminal is Down'/><author><name>mss</name><uri>http://www.blogger.com/profile/02682453100579738680</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://3.bp.blogspot.com/-e533-2eHV2g/TXAiaAJ0xuI/AAAAAAAAACE/PwPn1ANlQaI/s72-c/Payment%2BProcessing%2Bwhen%2Bthe%2BPOS%2BTerminal%2Bis%2BDown.jpg' height='72' width='72'/><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8887473741874669103.post-5717483376104814107</id><published>2011-03-01T16:48:00.002-05:00</published><updated>2011-03-01T17:19:56.189-05:00</updated><title type='text'>Flat Rate Merchant Account Pricing</title><content type='html'>&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://4.bp.blogspot.com/-Gzz-LHhpc3M/TW1wizm9GjI/AAAAAAAAAB8/40InONPktfQ/s1600/Flat%2BRate%2BMerchant%2BAccount%2BPricing.jpg"&gt;&lt;img style="float:right; margin:0 0 10px 10px;cursor:pointer; cursor:hand;width: 300px; height: 201px;" src="http://4.bp.blogspot.com/-Gzz-LHhpc3M/TW1wizm9GjI/AAAAAAAAAB8/40InONPktfQ/s320/Flat%2BRate%2BMerchant%2BAccount%2BPricing.jpg" border="0" title="Flat Rate Merchant Account Pricing" alt="Flat Rate Merchant Account Pricing" id="BLOGGER_PHOTO_ID_5579239256653371954" /&gt;&lt;/a&gt;At &lt;a href="https://www.unibulmerchantservices.com/" mce_href="https://www.unibulmerchantservices.com/"&gt;UniBul Merchant Services&lt;/a&gt; we have been offering a &lt;a href="https://www.unibulmerchantservices.com/flat-rate-merchant-account" mce_href="https://www.unibulmerchantservices.com/flat-rate-merchant-account"&gt;flat rate merchant account&lt;/a&gt; pricing model to all of our applicants for several months now and I wanted to share our reasons for creating it in the first place and to offer a brief overview of how it compares to its most prominent alternatives: the tiered and the pass-through pricing structures.&lt;br /&gt;&lt;br /&gt;&lt;h3&gt;Why did We Create the Flat Rate Merchant Account Pricing?&lt;/h3&gt;&lt;br /&gt;&lt;br /&gt;The biggest challenge that we've had to overcome ever since we started offering &lt;a href="https://www.unibulmerchantservices.com/merchant-processing-services"&gt;merchant processing services&lt;/a&gt; to U.S.-based businesses and non-profit organizations years ago has been coming up with a pricing structure that is at the same time simple, so that all applicants could immediately understand how it worked, and cost-efficient, so that it would save them money. Easier said than done.&lt;br /&gt;&lt;br /&gt;Let me explain what I mean. The dominant pricing models, which we still support and provide to merchants who insist on having their accounts based on one of them, are either cost-efficient or simple, but not a combination of the two. The reasons are many and complex and we have discuss them at length in other articles.&lt;br /&gt;&lt;br /&gt;The flat rate merchant account pricing, however, solved our predicament, much to our merchants' satisfaction.&lt;br /&gt;&lt;br /&gt;&lt;h3&gt;How Does Flat Rate Merchant Accounts Work?&lt;/h3&gt;&lt;br /&gt;&lt;br /&gt;There are several variations of the flat rate pricing, but I will focus here on our own model, not least because it is the one I am familiar with the most. In any case, our competitors will be best suited to review the types of flat rate pricing structures they offer.&lt;br /&gt;&lt;br /&gt;So here it is and it is as simple, as it gets. We give you one flat rate to be applied to all of your transactions, irrespective of the type of card used or any other factors. So no more no-qualified rates, as all of your transactions become in effect qualified. Additionally, we have eliminated the authorization fees.&lt;br /&gt;&lt;br /&gt;&lt;h3&gt;How Does the Flat Rate Pricing Compare to the Other Models?&lt;/h3&gt;&lt;br /&gt;&lt;br /&gt;This is exactly the question you should ask and, as it happens, the answer is incredibly easy to get. I will show you how you can estimate your costs if we provided your &lt;a href="http://blog.unibulmerchantservices.com/"&gt;merchant services&lt;/a&gt;, so that you can compare them to your current provider's total fees.&lt;br /&gt;&lt;br /&gt;All right, let's say that in March you processed a grand total of $50,000 on 500 card transactions and your flat rate was 2.20% + $0.30 per transaction, which is exactly how much we would have charged you. In this case your total cost is ($50,000 x 2.20%) + (500 x $0.30) = $1,100 + $150 = $1,250. So if we did your processing your effective processing rate for March would have been: [($1,250 / $50,000) x 100] = 2.50%.&lt;br /&gt;&lt;br /&gt;Now you can compare it to the total amount you paid to your current processor. As I said, simple.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8887473741874669103-5717483376104814107?l=merchantaccountprocessing.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://merchantaccountprocessing.blogspot.com/feeds/5717483376104814107/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2011/03/flat-rate-merchant-account-pricing.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/5717483376104814107'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/5717483376104814107'/><link rel='alternate' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2011/03/flat-rate-merchant-account-pricing.html' title='Flat Rate Merchant Account Pricing'/><author><name>mss</name><uri>http://www.blogger.com/profile/02682453100579738680</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://4.bp.blogspot.com/-Gzz-LHhpc3M/TW1wizm9GjI/AAAAAAAAAB8/40InONPktfQ/s72-c/Flat%2BRate%2BMerchant%2BAccount%2BPricing.jpg' height='72' width='72'/><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8887473741874669103.post-5040219466156623583</id><published>2011-02-25T16:59:00.004-05:00</published><updated>2011-02-25T18:24:58.667-05:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='take credit cards'/><category scheme='http://www.blogger.com/atom/ns#' term='accept credit cards'/><title type='text'>Best Practices to Accept Credit Cards Face-to-Face</title><content type='html'>&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://2.bp.blogspot.com/-aPRXRwo1sEE/TWg6DsNZpRI/AAAAAAAAAB0/j-hwtArSSQg/s1600/New%2BFinancial%2BRegulations%2Bto%2BCost%2BCredit%2BCard%2BCompanies%2B%252425B%2Bper%2BYear.jpg"&gt;&lt;img style="float:right; margin:0 0 10px 10px;cursor:pointer; cursor:hand;width: 300px; height: 227px;" src="http://2.bp.blogspot.com/-aPRXRwo1sEE/TWg6DsNZpRI/AAAAAAAAAB0/j-hwtArSSQg/s320/New%2BFinancial%2BRegulations%2Bto%2BCost%2BCredit%2BCard%2BCompanies%2B%252425B%2Bper%2BYear.jpg" border="0" alt="Best Practices to Accept Credit Cards Face-to-Face" title="Best Practices to Accept Credit Cards Face-to-Face" id="BLOGGER_PHOTO_ID_5577771973579744530" /&gt;&lt;/a&gt;Cards are considered accepted in a face-to-face setting when the card and the cardholder are both physically available during the transaction. Card acceptors that &lt;a href="https://www.unibulmerchantservices.com/accept-credit-cards"&gt;accept credit cards&lt;/a&gt; face-to-face include grocery stores,  restaurants, coffee shops, etc.&lt;br /&gt;&lt;br /&gt;The credit card associations also consider payments made at unattended terminals, such as gas stations, as face-to-face. In such settings the card acceptor never actually has possession of the card, it is still swiped through a physical machine which is sufficient to qualify.&lt;br /&gt;&lt;br /&gt;Card-present payments are less plagued by fraud than non-face-to-face ones, because the card acceptor has much more tools at her disposal to validate the legitimacy of the card and cardholder. What is more, retailers are required to ensure, to the best of their ability, that all transactions are valid.&lt;br /&gt;&lt;br /&gt;To achieve that goal, card acceptors should to develop procedures for processing face-to-face payments and provide sufficient training to the staff operating the terminals. Listed below are our suggestions for the card acceptance procedures that you need to incorporate into your &lt;a href="https://www.unibulmerchantservices.com/payment-processing"&gt;payment processing&lt;/a&gt; manual.&lt;br /&gt;&lt;br /&gt;Follow these steps and you will be in compliance with Visa and MasterCard regulations:&lt;br /&gt;&lt;ol&gt;&lt;li&gt;&lt;b&gt;Card swiping.&lt;/b&gt; First, swipe the card through the terminal. Then &lt;a href="https://www.unibulmerchantservices.com/take-credit-cards"&gt;take the credit card&lt;/a&gt; from your customer.&lt;/li&gt;&lt;li&gt;&lt;b&gt;Verify the card's authenticity.&lt;/b&gt; Examine the card and ensure that it has not been changed in any way.&lt;/li&gt;&lt;li&gt;&lt;b&gt;Get the customer's signature.&lt;/b&gt; If the transaction is authorized, obtain a signature from your customer on the sales receipt.&lt;/li&gt;&lt;li&gt;&lt;b&gt;Verify the signature.&lt;/b&gt; Compare the signature your customer just made to the one on the card and ensure that they match.&lt;/li&gt;&lt;li&gt;&lt;b&gt;Return the card.&lt;/b&gt; Once you are satisfied with the validity of the card and the authenticity of your customer, return the card and a copy of the sales receipt to complete the transaction.&lt;/li&gt;&lt;/ol&gt;If you have grounds to doubt that either the card or the cardholder may not be genuine, make a Code 10 call to your processor's authorization center and you will be instructed on how to proceed.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8887473741874669103-5040219466156623583?l=merchantaccountprocessing.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://merchantaccountprocessing.blogspot.com/feeds/5040219466156623583/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2011/02/best-practices-to-accept-credit-cards.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/5040219466156623583'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/5040219466156623583'/><link rel='alternate' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2011/02/best-practices-to-accept-credit-cards.html' title='Best Practices to Accept Credit Cards Face-to-Face'/><author><name>mss</name><uri>http://www.blogger.com/profile/02682453100579738680</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://2.bp.blogspot.com/-aPRXRwo1sEE/TWg6DsNZpRI/AAAAAAAAAB0/j-hwtArSSQg/s72-c/New%2BFinancial%2BRegulations%2Bto%2BCost%2BCredit%2BCard%2BCompanies%2B%252425B%2Bper%2BYear.jpg' height='72' width='72'/><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8887473741874669103.post-5086249363005590014</id><published>2011-02-24T18:12:00.003-05:00</published><updated>2011-02-24T19:27:55.858-05:00</updated><title type='text'>What Is Virtual Terminal and How Much It Costs</title><content type='html'>&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://3.bp.blogspot.com/-suwmPFzZgj0/TWb3X9Rvf1I/AAAAAAAAABs/exHXjfG2Elc/s1600/What%2BEverybody%2BNeeds%2Bto%2BKnow%2BAbout%2BE-Commerce%2BRisk%2BManagement.jpg"&gt;&lt;img style="float:right; margin:0 0 10px 10px;cursor:pointer; cursor:hand;width: 300px; height: 224px;" src="http://3.bp.blogspot.com/-suwmPFzZgj0/TWb3X9Rvf1I/AAAAAAAAABs/exHXjfG2Elc/s320/What%2BEverybody%2BNeeds%2Bto%2BKnow%2BAbout%2BE-Commerce%2BRisk%2BManagement.jpg" border="0" alt="What Is Virtual Terminal and How Much It Costs" Title="What Is Virtual Terminal and How Much It Costs" id="BLOGGER_PHOTO_ID_5577417179502968658" /&gt;&lt;/a&gt;&lt;div&gt;All of us have made credit card payments in a card-present setting and know how it works. You just swipe a credit card through the &lt;a href="https://www.unibulmerchantservices.com/credit-card-processing"&gt;credit card processing&lt;/a&gt; machine; it reads the information stored in the card’s mag-stripe and the data are then transmitted to the card issuer, who would either authorize or decline the transaction. That's it. Now, what happens if your customer Makes the order over the telephone and wants to make a payment the same way? Well, that’s when you need the virtual terminal.&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;&lt;h3&gt;What Exactly is Virtual Terminal?&lt;/h3&gt;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;&lt;a href="https://www.unibulmerchantservices.com/virtual-terminal-credit-card-processing"&gt;Virtual terminal&lt;/a&gt; is the web-based version of the physical credit card machine. Both do the exact same things, which are to collect the payment information, encrypt it and transmit it securely between the merchant and their processing bank. The only difference is that, Instead of reading the cardholder's account data from the card's mag-stripe, the virtual terminal collects it from a payment form, which is filled out by the merchant in a browser. The best thing about virtual terminals is that they can be accessed from anywhere web access is available, from a computer or a smart phone.&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;If you have ever paid any of your utilities bills online, you would have used a virtual terminal. The only difference between paying your own utility bill and processing someone else’s payment is in the first instance you are doing it for yourself, while in the latter the payment is coming from your customer’s credit card account.&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;There are virtual terminals that can be set up to enable you to accept ACH payments, in addition to bank cards. You should not take it for granted, though, and if you need ACH processing, make sure that you ask your prospective processor if they support it.&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;&lt;h3&gt;How to Process Recurring Payment Plans?&lt;/h3&gt;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;Some merchants' business operations involve the charging of fees for products or services that are delivered over time. For example, an auto insurance plan typically involves regular monthly payments of the same amount that are charged on a pre-arranged schedule. These are called &lt;a href="http://blog.unibulmerchantservices.com/managing-risk-in-recurring-payment-plans"&gt;recurring payment plans&lt;/a&gt; and in theory can last indefinitely, until the service is canceled by the customer. Similarly, a payment plan can be agreed-on for the purchase of, say a refrigerator. In such cases both the payment amounts and the number of payments will be pre-defined and the plan will be automatically discontinued when the last payment is made. These are called &lt;a href="http://blog.unibulmerchantservices.com/how-to-manage-installment-payment-plans"&gt;installment payment plans&lt;/a&gt;.&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;Virtual terminals provide the best platform for setting up recurring and installment payment plans. It enables you to store your customer information securely on your processing bank’s server. Then you can use the built-in managed billing service to manage your payment plans.&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;&lt;h3&gt;How Much Do Virtual Terminals Cost?&lt;/h3&gt;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;Ideally, your pricing plan to &lt;a href="https://www.unibulmerchantservices.com/accept-credit-cards"&gt;accept credit cards&lt;/a&gt; would be based on the &lt;a href="https://www.unibulmerchantservices.com/flat-rate-merchant-account"&gt;flat rate merchant account&lt;/a&gt; pricing. You should try to get the &lt;a href="https://www.unibulmerchantservices.com/"&gt;merchant account&lt;/a&gt; together with the virtual terminal and the payment gateway (there are offers out there for a &lt;a href="https://www.unibulmerchantservices.com/free-authorize-net-merchant-account"&gt;free Authorize.Net merchant account&lt;/a&gt;). Your cost will vary by vendor and processor, but there are certain parameters you can use for guidance.&lt;/div&gt;&lt;div&gt;&lt;ul&gt;&lt;li&gt;&lt;b&gt;Set-up cost.&lt;/b&gt; Some processors may ask you for a set-up fee, but you should stay away from them. You can easily find a vendor who would set it up for free.&lt;/li&gt;&lt;li&gt;&lt;b&gt;Monthly fee.&lt;/b&gt; Your monthly fee can be anything from $10 to $30. Don't pay more than that, because all virtual terminals do the same thing; there is is no need to be going overboard.&lt;/li&gt;&lt;li&gt;&lt;b&gt;Authorization fee.&lt;/b&gt; Your authorization fees should not exceed $0.10 per transaction.&lt;/li&gt;&lt;/ul&gt;&lt;/div&gt;&lt;div&gt;In addition to these fees you will have your merchant account fees. As I suggested above, your best option would be to get your services as a package, which typically guarantees a discount.&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8887473741874669103-5086249363005590014?l=merchantaccountprocessing.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://merchantaccountprocessing.blogspot.com/feeds/5086249363005590014/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2011/02/what-is-virtual-terminal-and-how-much.html#comment-form' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/5086249363005590014'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/5086249363005590014'/><link rel='alternate' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2011/02/what-is-virtual-terminal-and-how-much.html' title='What Is Virtual Terminal and How Much It Costs'/><author><name>mss</name><uri>http://www.blogger.com/profile/02682453100579738680</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://3.bp.blogspot.com/-suwmPFzZgj0/TWb3X9Rvf1I/AAAAAAAAABs/exHXjfG2Elc/s72-c/What%2BEverybody%2BNeeds%2Bto%2BKnow%2BAbout%2BE-Commerce%2BRisk%2BManagement.jpg' height='72' width='72'/><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8887473741874669103.post-195481591761331188</id><published>2011-02-23T23:07:00.003-05:00</published><updated>2011-02-23T23:19:08.275-05:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='payment gateway'/><category scheme='http://www.blogger.com/atom/ns#' term='merchant account'/><category scheme='http://www.blogger.com/atom/ns#' term='Authorize.Net'/><title type='text'>Authorize.Net Payment Gateway and Merchant Account</title><content type='html'>&lt;img style="float:right; margin:0 0 10px 10px;cursor:pointer; cursor:hand;width: 320px; height: 212px;" src="http://4.bp.blogspot.com/-U8O0hLsotdo/TWXbxWH_bFI/AAAAAAAAABk/nOtolR6zr6k/s320/Credit_Card_Payment_Processing.jpg" border="0" title="Authorize.Net Payment Gateway and Merchant Account" alt="Authorize.Net Payment Gateway and Merchant Account" id="BLOGGER_PHOTO_ID_5577105354367396946" /&gt;&lt;span class="Apple-style-span" style="font-size: 12px; "&gt;&lt;p&gt;&lt;span class="Apple-style-span"&gt;&lt;a href="https://www.unibulmerchantservices.com/" mce_href="https://www.unibulmerchantservices.com/"&gt;UniBul Merchant Services&lt;/a&gt;&lt;span mce_style="font-weight: normal;" style="font-weight: normal; "&gt; offers payment acceptance solutions mostly to e-commerce and MO / TO merchants and we are fielding a never-ending stream of inquiries about &lt;a href="https://www.unibulmerchantservices.com/payment-gateway" mce_href="https://www.unibulmerchantservices.com/payment-gateway"&gt;payment gateways&lt;/a&gt; and &lt;a href="https://www.unibulmerchantservices.com/virtual-terminal-credit-card-processing" mce_href="https://www.unibulmerchantservices.com/virtual-terminal-credit-card-processing"&gt;virtual terminals&lt;/a&gt;. There is little doubt that our &lt;/span&gt;&lt;a href="https://www.unibulmerchantservices.com/free-authorize-net-merchant-account" mce_href="https://www.unibulmerchantservices.com/free-authorize-net-merchant-account"&gt;free Authorize.Net merchant account&lt;/a&gt;&lt;span mce_style="font-weight: normal;" style="font-weight: normal; "&gt; is a substantial reason why there is so much interest. One thing we learn from these inquiries is that there often is a great deal of misunderstanding about the role a payment gateway plays in the credit card processing cycle. I will try to shed some light on the subject with this post.&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;&lt;p&gt;&lt;span mce_style="font-weight: normal;" style="font-weight: normal; "&gt;&lt;br /&gt;&lt;/span&gt;&lt;/p&gt;&lt;p&gt;&lt;span mce_style="font-weight: normal;" style="font-weight: normal; "&gt;&lt;/span&gt;&lt;/p&gt;&lt;h3&gt;Authorize.Net Payment Gateway Essentials&lt;/h3&gt;&lt;p&gt;&lt;span mce_style="font-weight: normal;"&gt;&lt;/span&gt;&lt;/p&gt;&lt;p style="font-weight: normal; "&gt;&lt;span mce_style="font-weight: normal;"&gt;&lt;br /&gt;&lt;/span&gt;&lt;/p&gt;&lt;p&gt;&lt;span mce_style="font-weight: normal;"&gt;Think of a &lt;a href="http://blog.unibulmerchantservices.com/payment-gateway-1" mce_href="http://blog.unibulmerchantservices.com/payment-gateway-1"&gt;payment gateway&lt;/a&gt;&lt;span style="font-weight: normal; "&gt; as a service for collecting and transmitting information, which is exactly what a point of sale (POS) &lt;/span&gt;&lt;a href="https://www.unibulmerchantservices.com/credit-card-processing" mce_href="https://www.unibulmerchantservices.com/credit-card-processing"&gt;credit card processing&lt;/a&gt; machine does. Authorize.Net provides the link between your &lt;a href="http://blog.unibulmerchantservices.com/13-must-have-e-commerce-website-features" mce_href="http://blog.unibulmerchantservices.com/13-must-have-e-commerce-website-features" target="_self" title="13 Must Have E-Commerce Website Features" style="font-weight: normal; "&gt;e-commerce website&lt;/a&gt; and the processing bank that set up your &lt;a href="https://www.unibulmerchantservices.com/accept-credit-cards"&gt;credit card acceptance&lt;/a&gt; service.&lt;/span&gt;&lt;/p&gt;&lt;p style="font-weight: normal; "&gt;&lt;span mce_style="font-weight: normal;"&gt;Of course there are differences between the functions performed by a POS terminal and a payment gateway and the most prominent one is that the former gathers the payment data directly from the customer's card by "reading" the card's mag-stripe. Authorize.Net, by contrast, collects the data that the customer has key-entered into the checkout's payment form. Still, this is a quite minor technical detail.&lt;/span&gt;&lt;/p&gt;&lt;p style="font-weight: normal; "&gt;&lt;span mce_style="font-weight: normal;"&gt;Once the transaction data is collected, both the payment gateway and the POS machine encrypt it before transmittal to the processor for protection against hackers. The &lt;a href="http://blog.unibulmerchantservices.com/how-to-select-a-processing-bank-for-your-e-commerce-business" mce_href="http://blog.unibulmerchantservices.com/how-to-select-a-processing-bank-for-your-e-commerce-business"&gt;processing bank&lt;/a&gt; communicates the transaction data with the card issuing bank, which approves or declines the transaction and sends its response back to the website through the same channel.&lt;/span&gt;&lt;/p&gt;&lt;p style="font-weight: normal; "&gt;&lt;span mce_style="font-weight: normal;"&gt;&lt;br /&gt;&lt;/span&gt;&lt;/p&gt;&lt;h3&gt;Authorize.Net Payment Gateway Cost&lt;/h3&gt;&lt;p style="font-weight: normal; "&gt;&lt;span mce_style="font-weight: normal;"&gt;&lt;br /&gt;&lt;/span&gt;&lt;/p&gt;&lt;p style="font-weight: normal; "&gt;&lt;span mce_style="font-weight: normal;"&gt;There are variations from one vendor to another, but the pricing should be within a certain range. Authorize.Net usually costs about $20 per month, although it could be as little as $10 or less. There could also be a set-up fee of up to $100 and there will certainly be an authorization fee, typically of $0.10 per transaction (which incidentally is how Authorize.Net makes its money).&lt;/span&gt;&lt;/p&gt;&lt;p style="font-weight: normal; "&gt;&lt;span mce_style="font-weight: normal;"&gt;One very important thing you need to understand is that the Authorize.Net fees are completely independent from the merchant account fees. So when evaluating pricing proposals, you must scrutinize the whole package, including the merchant account fees. Don't be misled by incredibly low headline rates. You know what they say, if it looks too good to be true, it probably is. Authorize.Net, as well as all other payment gateways and merchant accounts are certainly no exception to this rule.&lt;/span&gt;&lt;/p&gt;&lt;p style="font-weight: normal; "&gt;&lt;span mce_style="font-weight: normal;"&gt;By the way, check out &lt;a href="http://mashable.com/twitterlists/user/UniBul" mce_href="http://mashable.com/twitterlists/user/UniBul"&gt;UniBul's Twitter lists on Mashable&lt;/a&gt;.&lt;/span&gt;&lt;/p&gt;&lt;p style="font-family: Verdana, Arial, Helvetica, sans-serif; "&gt;&lt;/p&gt;&lt;/span&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8887473741874669103-195481591761331188?l=merchantaccountprocessing.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://merchantaccountprocessing.blogspot.com/feeds/195481591761331188/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2011/02/authorizenet-payment-gateway-and.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/195481591761331188'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/195481591761331188'/><link rel='alternate' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2011/02/authorizenet-payment-gateway-and.html' title='Authorize.Net Payment Gateway and Merchant Account'/><author><name>mss</name><uri>http://www.blogger.com/profile/02682453100579738680</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://4.bp.blogspot.com/-U8O0hLsotdo/TWXbxWH_bFI/AAAAAAAAABk/nOtolR6zr6k/s72-c/Credit_Card_Payment_Processing.jpg' height='72' width='72'/><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8887473741874669103.post-3511750705963796358</id><published>2011-02-23T22:45:00.006-05:00</published><updated>2011-02-23T23:05:14.921-05:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='merchant account'/><category scheme='http://www.blogger.com/atom/ns#' term='credit card processing'/><category scheme='http://www.blogger.com/atom/ns#' term='accept credit cards'/><title type='text'>Merchant Account Basic Facts</title><content type='html'>&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://4.bp.blogspot.com/-b0TxhjdEWxo/TWXXzqh2nZI/AAAAAAAAABc/g2MKInGPUsI/s1600/1130Bucks-NPSL-blog480.jpg"&gt;&lt;img style="float:right; margin:0 0 10px 10px;cursor:pointer; cursor:hand;width: 320px; height: 218px;" src="http://4.bp.blogspot.com/-b0TxhjdEWxo/TWXXzqh2nZI/AAAAAAAAABc/g2MKInGPUsI/s320/1130Bucks-NPSL-blog480.jpg" border="0" alt="Merchant Account Basic Facts" title="Merchant Account Basic Facts" id="BLOGGER_PHOTO_ID_5577100996157808018" /&gt;&lt;/a&gt;&lt;span class="Apple-style-span" style="font-size: 12px; "&gt;&lt;div class="module_intro"&gt;&lt;h3&gt;What Is a Merchant Account?&lt;/h3&gt;&lt;/div&gt;&lt;div class="module_intro"&gt;&lt;br /&gt;&lt;/div&gt;&lt;div class="module_intro"&gt;&lt;a href="https://www.unibulmerchantservices.com/"&gt;Merchant account&lt;/a&gt; is a type of financial service that a processing bank provides to an organization that needs to &lt;a href="https://www.unibulmerchantservices.com/accept-credit-cards"&gt;accept credit cards&lt;/a&gt; for payments. It represents a form of line of credit that the bank &lt;span id="IL_AD4" class="IL_AD"&gt;extends&lt;/span&gt; to the card acceptor enabling the latter to accept the card brands that are specified in the processing agreement.&lt;br /&gt;&lt;br /&gt;Typically, merchants are enabled to accept Visa, &lt;span id="IL_AD1" class="IL_AD"&gt;MasterCard&lt;/span&gt;, Discover, American Express credit and debit cards and at least the major European and Japanese card brands.&lt;/div&gt;&lt;div class="module_intro"&gt;&lt;br /&gt;&lt;/div&gt;&lt;div class="module_intro"&gt;&lt;h3&gt;How Merchant Accounts Work&lt;/h3&gt;&lt;span class="Apple-style-span" style="font-size: 12px; font-weight: normal; "&gt;&lt;br /&gt;&lt;/span&gt;&lt;span class="Apple-style-span" style="font-size: 12px; font-weight: normal; "&gt;When a merchant accepts a card for payment, either through a point-of-sale (POS) terminal or on an &lt;a href="http://blog.unibulmerchantservices.com/13-must-have-e-commerce-website-features"&gt;e-commerce website&lt;/a&gt;, it is transmitted to the processing bank. The bank then pays the merchant the transaction amount, minus the interchange fees and the processing costs, and submits a payment request to the card issuer. The issuer then pays the processing 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 transaction cycle.&lt;/span&gt;&lt;div&gt;&lt;span class="Apple-style-span" style="font-size: 12px; font-weight: normal; "&gt;&lt;br /&gt;&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="module_intro"&gt;&lt;h3&gt;Types of Merchant Accounts&lt;/h3&gt;&lt;span class="Apple-style-span" style="font-size: 12px; font-weight: normal; "&gt;&lt;br /&gt;&lt;/span&gt;&lt;span class="Apple-style-span" style="font-size: 12px; font-weight: normal; "&gt;There are a number of different merchant account types but the most widely used are:&lt;/span&gt;&lt;/div&gt;&lt;div class="module_intro"&gt;&lt;ul&gt;&lt;li&gt;&lt;strong&gt;Card-Present Merchant Accounts.&lt;/strong&gt; This type of &lt;a href="https://www.unibulmerchantservices.com/credit-card-processing" mce_href="https://www.unibulmerchantservices.com/credit-card-processing" target="_blank"&gt;credit card processing&lt;/a&gt; service includes all payment acceptance solutions that use POS terminals to read the account information from the &lt;span id="IL_AD3" class="IL_AD"&gt;magnetic&lt;/span&gt; stripe of a card. 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 &lt;a href="https://www.unibulmerchantservices.com/lower-your-processing-rates" mce_href="https://www.unibulmerchantservices.com/lower-your-processing-rates" target="_blank"&gt;lower processing rates&lt;/a&gt;.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Card-not-Present Merchant Accounts.&lt;/strong&gt; Included in this group are all card payment processing services where the card account information is manually entered into the processing 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:&lt;br /&gt;&lt;/li&gt;&lt;ul&gt;&lt;li&gt;&lt;strong&gt;&lt;a href="http://www.unibulmerchantservices.com/apply-online/ecommerce-merchant-account/" mce_href="http://www.unibulmerchantservices.com/apply-online/ecommerce-merchant-account/" target="_blank" title="eCommerce Merchant Account"&gt;&lt;/a&gt;&lt;a href="https://www.unibulmerchantservices.com/ecommerce-merchant-account" mce_href="https://www.unibulmerchantservices.com/ecommerce-merchant-account" target="_blank"&gt;E-Commerce Merchant Accounts&lt;/a&gt;. &lt;/strong&gt;These &lt;a href="http://blog.unibulmerchantservices.com/" mce_href="http://blog.unibulmerchantservices.com/" target="_blank"&gt;credit card processing&lt;/a&gt; services are used by web-based merchants and enable cardholders 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 &lt;a href="https://www.unibulmerchantservices.com/payment-gateway" mce_href="https://www.unibulmerchantservices.com/payment-gateway" target="_blank"&gt;payment gateway&lt;/a&gt;, to the processing bank.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Mail Order and Telephone Order Merchant Accounts.&lt;/strong&gt; Also known as &lt;a href="https://www.unibulmerchantservices.com/moto-merchant-account" mce_href="https://www.unibulmerchantservices.com/moto-merchant-account" target="_blank"&gt;MO / TO merchant accounts&lt;/a&gt;, 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 processing bank's system.&lt;/li&gt;&lt;/ul&gt;&lt;/ul&gt;&lt;div&gt;Your business may of course need a combination of the above types, which your processor should be able to accommodate.&lt;/div&gt;&lt;/div&gt;&lt;/span&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8887473741874669103-3511750705963796358?l=merchantaccountprocessing.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://merchantaccountprocessing.blogspot.com/feeds/3511750705963796358/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2011/02/merchant-account-basic-facts.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/3511750705963796358'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/3511750705963796358'/><link rel='alternate' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2011/02/merchant-account-basic-facts.html' title='Merchant Account Basic Facts'/><author><name>mss</name><uri>http://www.blogger.com/profile/02682453100579738680</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://4.bp.blogspot.com/-b0TxhjdEWxo/TWXXzqh2nZI/AAAAAAAAABc/g2MKInGPUsI/s72-c/1130Bucks-NPSL-blog480.jpg' height='72' width='72'/><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8887473741874669103.post-621529577359282830</id><published>2010-01-07T18:35:00.004-05:00</published><updated>2011-02-07T00:00:21.690-05:00</updated><title type='text'>Screening New Merchants</title><content type='html'>&lt;a href="http://blog.unibulmerchantservices.com/4-steps-to-screening-merchant-account-applicants"&gt;&lt;img id="BLOGGER_PHOTO_ID_5570807253103533506" style="FLOAT: right; MARGIN: 0px 0px 10px 10px; WIDTH: 320px; CURSOR: hand; HEIGHT: 218px" alt="" src="http://3.bp.blogspot.com/_viwxYiZ0-Bg/TU97rmln3cI/AAAAAAAAABU/XzN38b02GqU/s320/1130Bucks-NPSL-blog480.jpg" border="0" title="4 Steps to Screening Merchant Account Applicants" alt="4 Steps to Screening Merchant Account Applicants"/&gt;&lt;/a&gt;&lt;br /&gt;&lt;div&gt;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:&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;ul&gt;&lt;br /&gt;&lt;br /&gt;&lt;li&gt;Credit check, background investigations, and reference checks of the merchant.&lt;br /&gt;&lt;br /&gt;If the credit check of the merchant raises questions, the acquirer also should conduct a credit check of:&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;ul&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;li&gt;The owner, if the merchant is a sole proprietor; or&lt;/li&gt;&lt;br /&gt;&lt;br /&gt;&lt;li&gt;The partners, if the merchant is a partnership; or&lt;/li&gt;&lt;br /&gt;&lt;br /&gt;&lt;li&gt;The principal shareholders, if the merchant is a corporation.&lt;/li&gt;&lt;/ul&gt;&lt;/li&gt;&lt;br /&gt;&lt;br /&gt;&lt;li&gt;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.&lt;/li&gt;&lt;br /&gt;&lt;br /&gt;&lt;li&gt;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.&lt;/li&gt;&lt;br /&gt;&lt;br /&gt;&lt;li&gt;Investigation of the merchant’s previous merchant agreements.&lt;/li&gt;&lt;/ul&gt;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.&lt;br /&gt;&lt;br /&gt;&lt;!-- AddThis Button BEGIN --&gt;&lt;br /&gt;&lt;br /&gt;&lt;script type="text/javascript"&gt;// &lt;![CDATA[     addthis_pub  = 'Merchant Account';     addthis_brand = 'Merchant Account';     addthis_options = 'favorites, email, digg, delicious, myspace, facebook, google, live, more'; // ]]&gt;&lt;/script&gt;&lt;br /&gt;&lt;br /&gt;&lt;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"&gt;&lt;img height="16" alt="" src="http://s9.addthis.com/button1-bm.gif" width="125" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;&lt;script src="http://s7.addthis.com/js/152/addthis_widget.js" type="text/javascript"&gt;&lt;/script&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;!-- AddThis Button END --&gt;&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8887473741874669103-621529577359282830?l=merchantaccountprocessing.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://merchantaccountprocessing.blogspot.com/feeds/621529577359282830/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2010/01/screening-new-merchants.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/621529577359282830'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/621529577359282830'/><link rel='alternate' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2010/01/screening-new-merchants.html' title='Screening New Merchants'/><author><name>mss</name><uri>http://www.blogger.com/profile/02682453100579738680</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://3.bp.blogspot.com/_viwxYiZ0-Bg/TU97rmln3cI/AAAAAAAAABU/XzN38b02GqU/s72-c/1130Bucks-NPSL-blog480.jpg' height='72' width='72'/><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8887473741874669103.post-8831201897491535720</id><published>2009-12-26T13:16:00.002-05:00</published><updated>2009-12-31T19:06:39.659-05:00</updated><title type='text'>MasterCard Fraud Loss Control Program Standards</title><content type='html'>In 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.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Acquirer Fraud Loss Control Programs&lt;/b&gt;&lt;br /&gt;&lt;br /&gt;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.&lt;br /&gt;&lt;br /&gt;Additionally, acquirers with high fraud levels must:&lt;br /&gt;&lt;ul&gt;&lt;li&gt;Install "read and display" terminals in areas determined to be at high risk for fraud or counterfeit activity, or&lt;br /&gt;&lt;/li&gt;&lt;li&gt;Install EMV chip terminals.&lt;br /&gt;&lt;/li&gt;&lt;/ul&gt;&lt;b&gt;Acquirer Authorization Monitoring Requirements&lt;/b&gt;&lt;br /&gt;&lt;br /&gt;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:&lt;br /&gt;&lt;ul&gt;&lt;li&gt;Number of authorization requests above a threshold set by the acquirer for that merchant.&lt;/li&gt;    &lt;li&gt;Ratio of non-card-read to card-read transactions that is above the threshold set by the acquirer for that merchant.&lt;/li&gt;    &lt;li&gt;PAN key entry ratio that is above threshold set by the acquirer for that merchant.&lt;/li&gt;    &lt;li&gt;Repeated authorization requests for the same amount or the same cardholder account.&lt;/li&gt;    &lt;li&gt;Increased number of authorization requests.&lt;/li&gt;    &lt;li&gt;"Out of pattern" fallback transaction volume.&lt;br /&gt;&lt;/li&gt;&lt;/ul&gt;&lt;b&gt;Acquirer Merchant Deposit Monitoring Requirements&lt;/b&gt;&lt;br /&gt;&lt;br /&gt;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:&lt;br /&gt;&lt;ul&gt;&lt;li&gt;Increases in merchant deposit volume.&lt;/li&gt;&lt;li&gt;Increase in a merchant's average ticket size and number of transactions per deposit.&lt;/li&gt;&lt;li&gt;Change in frequency of deposits.&lt;/li&gt;&lt;li&gt;Frequency of transactions on the same cardholder account, including credit transactions.&lt;/li&gt;&lt;li&gt;Unusual number of credits, or credit dollar volume, exceeding a level of sales dollar volume appropriate to the merchant category.&lt;/li&gt;&lt;li&gt;Large credit transaction amounts, significantly greater than the average ticket size for the merchant's sales.&lt;/li&gt;&lt;li&gt;Credits issued subsequent to the receipt of a chargeback with the same account number and followed by a second presentment.&lt;/li&gt;&lt;li&gt;Credits issued to an account number not used previously at the merchant location.&lt;/li&gt;&lt;/ul&gt;&lt;strong&gt;90-day Rule&lt;/strong&gt;&lt;br /&gt;&lt;br /&gt;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.&lt;br /&gt;&lt;br /&gt;&lt;strong&gt;150% Recommendation&lt;/strong&gt;&lt;br /&gt;&lt;br /&gt;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.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Recommended Additional Acquirer Monitoring&lt;/b&gt;&lt;br /&gt;&lt;br /&gt;MasterCard recommends that acquirers additionally monitor the following parameters:&lt;br /&gt;&lt;ul&gt;&lt;li&gt;Fallback methods.&lt;/li&gt;&lt;li&gt;Credit transactions (such as refunds) and merchant authorization reversals.&lt;/li&gt;&lt;li&gt;Transactions conducted at high-risk merchants.&lt;/li&gt;&lt;li&gt;Personal account number (PAN) key-entry transactions exceeding ratio.&lt;/li&gt;&lt;li&gt;Abnormal hours or seasons.&lt;/li&gt;&lt;li&gt;Inactive merchants.&lt;/li&gt;&lt;li&gt;Transactions with no approval code.&lt;/li&gt;&lt;li&gt;Transactions that were declined.&lt;/li&gt;&lt;li&gt;Inconsistent authorization and clearing data elements for the same transactions.&lt;/li&gt;&lt;/ul&gt;&lt;!-- AddThis Button BEGIN --&gt;&lt;script type="text/javascript"&gt;&lt;!--     addthis_pub  = 'Merchant Account';     addthis_brand = 'Merchant Account';     addthis_options = 'favorites, email, digg, delicious, myspace, facebook, google, live, more'; // --&gt;&lt;/script&gt;&lt;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"&gt;&lt;img src="http://s9.addthis.com/button1-bm.gif" alt="" border="0" height="16" width="125" /&gt;&lt;/a&gt;&lt;script src="http://s7.addthis.com/js/152/addthis_widget.js" type="text/javascript"&gt;&lt;/script&gt;&lt;br /&gt;&lt;!-- AddThis Button END --&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8887473741874669103-8831201897491535720?l=merchantaccountprocessing.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://merchantaccountprocessing.blogspot.com/feeds/8831201897491535720/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2009/12/mastercard-fraud-loss-control-program.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/8831201897491535720'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/8831201897491535720'/><link rel='alternate' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2009/12/mastercard-fraud-loss-control-program.html' title='MasterCard Fraud Loss Control Program Standards'/><author><name>mss</name><uri>http://www.blogger.com/profile/02682453100579738680</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8887473741874669103.post-1344815325613749033</id><published>2009-12-14T19:33:00.001-05:00</published><updated>2009-12-14T19:43:31.792-05:00</updated><title type='text'>Reporting Fraudulent Use of Cards</title><content type='html'>All &lt;a title="MasterCard Merchant Account" href="http://www.unibulmerchantservices.com/mastercard-merchant-account/" target="_self"&gt;MasterCard&lt;/a&gt; member banks must report accurately and completely the fraudulent use of &lt;a title="MasterCard Merchant Services" href="http://www.unibulmerchantservices.com/mastercard-merchant-services" target="_self"&gt;MasterCard&lt;/a&gt; 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.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Reporting by the Issuer&lt;/b&gt;&lt;br /&gt;&lt;br /&gt;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.&lt;br /&gt;&lt;br /&gt;An issuer must report fraudulent transactions even if it recovered losses through chargebacks, compliance cases, restitution, insurance, or any other means.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Reporting by the Acquirer&lt;/b&gt;&lt;br /&gt;&lt;br /&gt;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.&lt;br /&gt;&lt;br /&gt;&lt;!-- AddThis Button BEGIN --&gt;&lt;script type="text/javascript"&gt;&lt;!--     addthis_pub  = 'Merchant Account';     addthis_brand = 'Merchant Account';     addthis_options = 'favorites, email, digg, delicious, myspace, facebook, google, live, more'; // --&gt;&lt;/script&gt;&lt;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"&gt;&lt;img src="http://s9.addthis.com/button1-bm.gif" alt="" border="0" height="16" width="125" /&gt;&lt;/a&gt;&lt;script src="http://s7.addthis.com/js/152/addthis_widget.js" type="text/javascript"&gt;&lt;/script&gt;&lt;br /&gt;&lt;!-- AddThis Button END --&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8887473741874669103-1344815325613749033?l=merchantaccountprocessing.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://merchantaccountprocessing.blogspot.com/feeds/1344815325613749033/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2009/12/reporting-fraudulent-use-of-cards.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/1344815325613749033'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/1344815325613749033'/><link rel='alternate' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2009/12/reporting-fraudulent-use-of-cards.html' title='Reporting Fraudulent Use of Cards'/><author><name>mss</name><uri>http://www.blogger.com/profile/02682453100579738680</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8887473741874669103.post-5368067773296619355</id><published>2009-12-04T19:05:00.003-05:00</published><updated>2009-12-08T16:22:27.592-05:00</updated><title type='text'>MasterCard Rewards for Capturing a Card</title><content type='html'>The acquirer may pay the merchant reward for capturing a &lt;a title="MasterCard Merchant Services" href="http://www.unibulmerchantservices.com/mastercard-merchant-services" target="_self"&gt;MasterCard&lt;/a&gt; card in accordance with local practices. The acquirer must follow these Standards when paying a reward:&lt;br /&gt; &lt;ul&gt;&lt;li&gt;Pay no less than $50 to the merchant capturing a card listed on the Electronic Warning Bulletin file or in the Warning Notice.&lt;/li&gt;    &lt;li&gt;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.&lt;/li&gt;    &lt;li&gt;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.&lt;/li&gt;    &lt;li&gt;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.&lt;/li&gt;&lt;/ul&gt;&lt;b&gt;Reward Amounts&lt;/b&gt;&lt;br /&gt;&lt;br /&gt;The acquirer should follow these guidelines for determining reward amounts.&lt;br /&gt;&lt;br /&gt;&lt;meta equiv="Content-Type" content="text/html; charset=utf-8"&gt;&lt;meta name="ProgId" content="Word.Document"&gt;&lt;meta name="Generator" content="Microsoft Word 12"&gt;&lt;meta name="Originator" content="Microsoft Word 12"&gt;&lt;link rel="File-List" href="file:///C:%5CUsers%5CMetodi%5CAppData%5CLocal%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_filelist.xml"&gt;&lt;link rel="themeData" href="file:///C:%5CUsers%5CMetodi%5CAppData%5CLocal%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_themedata.thmx"&gt;&lt;link rel="colorSchemeMapping" href="file:///C:%5CUsers%5CMetodi%5CAppData%5CLocal%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_colorschememapping.xml"&gt;&lt;!--[if gte mso 9]&gt;&lt;xml&gt;  &lt;w:worddocument&gt;   &lt;w:view&gt;Normal&lt;/w:View&gt;   &lt;w:zoom&gt;0&lt;/w:Zoom&gt;   &lt;w:trackmoves/&gt;   &lt;w:trackformatting/&gt;   &lt;w:punctuationkerning/&gt;   &lt;w:validateagainstschemas/&gt;   &lt;w:saveifxmlinvalid&gt;false&lt;/w:SaveIfXMLInvalid&gt;   &lt;w:ignoremixedcontent&gt;false&lt;/w:IgnoreMixedContent&gt;   &lt;w:alwaysshowplaceholdertext&gt;false&lt;/w:AlwaysShowPlaceholderText&gt;   &lt;w:donotpromoteqf/&gt;   &lt;w:lidthemeother&gt;EN-US&lt;/w:LidThemeOther&gt;   &lt;w:lidthemeasian&gt;X-NONE&lt;/w:LidThemeAsian&gt;   &lt;w:lidthemecomplexscript&gt;X-NONE&lt;/w:LidThemeComplexScript&gt;   &lt;w:compatibility&gt;    &lt;w:breakwrappedtables/&gt;    &lt;w:snaptogridincell/&gt;    &lt;w:wraptextwithpunct/&gt;    &lt;w:useasianbreakrules/&gt;    &lt;w:dontgrowautofit/&gt;    &lt;w:splitpgbreakandparamark/&gt;    &lt;w:dontvertaligncellwithsp/&gt;    &lt;w:dontbreakconstrainedforcedtables/&gt;    &lt;w:dontvertalignintxbx/&gt;    &lt;w:word11kerningpairs/&gt;    &lt;w:cachedcolbalance/&gt;   &lt;/w:Compatibility&gt;   &lt;w:browserlevel&gt;MicrosoftInternetExplorer4&lt;/w:BrowserLevel&gt;   &lt;m:mathpr&gt;    &lt;m:mathfont val="Cambria Math"&gt;    &lt;m:brkbin val="before"&gt;    &lt;m:brkbinsub val="&amp;#45;-"&gt;    &lt;m:smallfrac val="off"&gt;    &lt;m:dispdef/&gt;    &lt;m:lmargin val="0"&gt;    &lt;m:rmargin val="0"&gt;    &lt;m:defjc val="centerGroup"&gt;    &lt;m:wrapindent val="1440"&gt;    &lt;m:intlim val="subSup"&gt;    &lt;m:narylim val="undOvr"&gt;   &lt;/m:mathPr&gt;&lt;/w:WordDocument&gt; &lt;/xml&gt;&lt;![endif]--&gt;&lt;!--[if gte mso 9]&gt;&lt;xml&gt;  &lt;w:latentstyles deflockedstate="false" defunhidewhenused="true" defsemihidden="true" defqformat="false" defpriority="99" latentstylecount="267"&gt;   &lt;w:lsdexception locked="false" priority="0" semihidden="false" unhidewhenused="false" qformat="true" name="Normal"&gt;   &lt;w:lsdexception locked="false" priority="9" semihidden="false" unhidewhenused="false" qformat="true" name="heading 1"&gt;   &lt;w:lsdexception locked="false" priority="9" qformat="true" name="heading 2"&gt;   &lt;w:lsdexception locked="false" priority="9" qformat="true" name="heading 3"&gt;   &lt;w:lsdexception locked="false" priority="9" qformat="true" name="heading 4"&gt;   &lt;w:lsdexception locked="false" priority="9" qformat="true" name="heading 5"&gt;   &lt;w:lsdexception locked="false" priority="9" qformat="true" name="heading 6"&gt;   &lt;w:lsdexception locked="false" priority="9" qformat="true" name="heading 7"&gt;   &lt;w:lsdexception locked="false" priority="9" qformat="true" name="heading 8"&gt;   &lt;w:lsdexception locked="false" priority="9" qformat="true" name="heading 9"&gt;   &lt;w:lsdexception locked="false" priority="39" name="toc 1"&gt;   &lt;w:lsdexception locked="false" priority="39" name="toc 2"&gt;   &lt;w:lsdexception locked="false" priority="39" name="toc 3"&gt;   &lt;w:lsdexception locked="false" priority="39" name="toc 4"&gt;   &lt;w:lsdexception locked="false" priority="39" name="toc 5"&gt;   &lt;w:lsdexception locked="false" priority="39" name="toc 6"&gt;   &lt;w:lsdexception locked="false" priority="39" name="toc 7"&gt;   &lt;w:lsdexception locked="false" priority="39" name="toc 8"&gt;   &lt;w:lsdexception locked="false" priority="39" name="toc 9"&gt;   &lt;w:lsdexception locked="false" priority="35" qformat="true" name="caption"&gt;   &lt;w:lsdexception locked="false" priority="10" semihidden="false" unhidewhenused="false" qformat="true" name="Title"&gt;   &lt;w:lsdexception locked="false" priority="1" name="Default Paragraph Font"&gt;   &lt;w:lsdexception locked="false" priority="11" semihidden="false" unhidewhenused="false" qformat="true" name="Subtitle"&gt;   &lt;w:lsdexception locked="false" priority="22" semihidden="false" unhidewhenused="false" qformat="true" name="Strong"&gt;   &lt;w:lsdexception locked="false" priority="20" semihidden="false" unhidewhenused="false" qformat="true" name="Emphasis"&gt;   &lt;w:lsdexception locked="false" priority="59" semihidden="false" unhidewhenused="false" name="Table Grid"&gt;   &lt;w:lsdexception locked="false" unhidewhenused="false" name="Placeholder Text"&gt;   &lt;w:lsdexception locked="false" priority="1" semihidden="false" unhidewhenused="false" qformat="true" name="No Spacing"&gt;   &lt;w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading"&gt;   &lt;w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List"&gt;   &lt;w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid"&gt;   &lt;w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1"&gt;   &lt;w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2"&gt;   &lt;w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1"&gt;   &lt;w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2"&gt;   &lt;w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1"&gt;   &lt;w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2"&gt;   &lt;w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3"&gt;   &lt;w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List"&gt;   &lt;w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading"&gt;   &lt;w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List"&gt;   &lt;w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid"&gt;   &lt;w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 1"&gt;   &lt;w:lsdexception locked="false" unhidewhenused="false" name="Revision"&gt;   &lt;w:lsdexception locked="false" priority="34" semihidden="false" unhidewhenused="false" qformat="true" name="List Paragraph"&gt;   &lt;w:lsdexception locked="false" priority="29" semihidden="false" unhidewhenused="false" qformat="true" name="Quote"&gt;   &lt;w:lsdexception locked="false" priority="30" semihidden="false" unhidewhenused="false" qformat="true" name="Intense Quote"&gt;   &lt;w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="19" semihidden="false" unhidewhenused="false" qformat="true" name="Subtle Emphasis"&gt;   &lt;w:lsdexception locked="false" priority="21" semihidden="false" unhidewhenused="false" qformat="true" name="Intense Emphasis"&gt;   &lt;w:lsdexception locked="false" priority="31" semihidden="false" unhidewhenused="false" qformat="true" name="Subtle Reference"&gt;   &lt;w:lsdexception locked="false" priority="32" semihidden="false" unhidewhenused="false" qformat="true" name="Intense Reference"&gt;   &lt;w:lsdexception locked="false" priority="33" semihidden="false" unhidewhenused="false" qformat="true" name="Book Title"&gt;   &lt;w:lsdexception locked="false" priority="37" name="Bibliography"&gt;   &lt;w:lsdexception locked="false" priority="39" qformat="true" name="TOC Heading"&gt;  &lt;/w:LatentStyles&gt; &lt;/xml&gt;&lt;![endif]--&gt;&lt;style&gt; &lt;!--  /* 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;} --&gt; &lt;/style&gt;&lt;!--[if gte mso 10]&gt; &lt;style&gt;  /* 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;} &lt;/style&gt; &lt;![endif]--&gt;  &lt;table class="MsoTableGrid" style="border: medium none ; margin-left: 5.4pt; border-collapse: collapse;" border="1" cellpadding="0" cellspacing="0"&gt;  &lt;tbody&gt;&lt;tr style=""&gt;   &lt;td style="border: 1pt solid black; padding: 0in 5.4pt; width: 177.85pt;" width="237"&gt;   &lt;p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"&gt;&lt;b style=""&gt;IF the capture…&lt;o:p&gt;&lt;/o:p&gt;&lt;/b&gt;&lt;/p&gt;   &lt;/td&gt;   &lt;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: 177.85pt;" width="237"&gt;   &lt;p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"&gt;&lt;b style=""&gt;THEN pay this amount…&lt;o:p&gt;&lt;/o:p&gt;&lt;/b&gt;&lt;/p&gt;   &lt;/td&gt;  &lt;/tr&gt;  &lt;tr style=""&gt;   &lt;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: 177.85pt;" width="237"&gt;   &lt;p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"&gt;Resulted from a “Merchant Suspicious” phone call&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt;   &lt;/td&gt;   &lt;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: 177.85pt;" width="237"&gt;   &lt;p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"&gt;$ 100&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt;   &lt;/td&gt;  &lt;/tr&gt;  &lt;tr style=""&gt;   &lt;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: 177.85pt;" width="237"&gt;   &lt;p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"&gt;Did not result from a “Merchant Suspicious” phone call&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt;   &lt;/td&gt;   &lt;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: 177.85pt;" width="237"&gt;   &lt;p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"&gt;$50&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt;   &lt;/td&gt;  &lt;/tr&gt;  &lt;tr style=""&gt;   &lt;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: 177.85pt;" width="237"&gt;   &lt;p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"&gt;Leads to the capture of additional cards&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt;   &lt;/td&gt;   &lt;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: 177.85pt;" width="237"&gt;   &lt;p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"&gt;$ 50 for each card captured, with a maximum total of $250 for any one   incident&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt;   &lt;/td&gt;  &lt;/tr&gt; &lt;/tbody&gt;&lt;/table&gt;&lt;br /&gt;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.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Reimbursement of Rewards&lt;/b&gt;&lt;br /&gt;&lt;br /&gt;The following specifications apply to reward reimbursement:&lt;br /&gt;&lt;ul&gt;&lt;li&gt;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.&lt;/li&gt;	&lt;li&gt;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.&lt;/li&gt;	&lt;li&gt;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.&lt;/li&gt;	&lt;li&gt;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.&lt;br /&gt;&lt;/li&gt;&lt;/ul&gt;&lt;!-- AddThis Button BEGIN --&gt;&lt;script type="text/javascript"&gt;&lt;!--     addthis_pub  = 'Merchant Account';     addthis_brand = 'Merchant Account';     addthis_options = 'favorites, email, digg, delicious, myspace, facebook, google, live, more'; // --&gt;&lt;/script&gt;&lt;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"&gt;&lt;img src="http://s9.addthis.com/button1-bm.gif" alt="" border="0" height="16" width="125" /&gt;&lt;/a&gt;&lt;script src="http://s7.addthis.com/js/152/addthis_widget.js" type="text/javascript"&gt;&lt;/script&gt;&lt;br /&gt;&lt;!-- AddThis Button END --&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8887473741874669103-5368067773296619355?l=merchantaccountprocessing.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://merchantaccountprocessing.blogspot.com/feeds/5368067773296619355/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2009/12/mastercard-rewards-for-capturing-card.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/5368067773296619355'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/5368067773296619355'/><link rel='alternate' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2009/12/mastercard-rewards-for-capturing-card.html' title='MasterCard Rewards for Capturing a Card'/><author><name>mss</name><uri>http://www.blogger.com/profile/02682453100579738680</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8887473741874669103.post-45434697145176791</id><published>2009-12-02T17:36:00.002-05:00</published><updated>2009-12-02T17:54:12.352-05:00</updated><title type='text'>Point-of-Sale (POS) Card Retention</title><content type='html'>Acquirers and merchants are required to recover a card by reasonable and peaceful means if:&lt;br /&gt;&lt;ul&gt;&lt;li&gt;The card issuer advises the acquirer or merchant to recover the card in response to an authorization request.&lt;/li&gt;    &lt;li&gt;The Electronic Warning Bulletin file or an effective regional Warning Notice lists the account number.&lt;/li&gt;&lt;/ul&gt;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.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Returning Recovered Cards&lt;/b&gt;&lt;br /&gt;&lt;br /&gt;The acquirer must follow these procedures when returning a recovered card to the issuer:&lt;br /&gt;&lt;ul&gt;&lt;li&gt;If the merchant has not already done so, the acquirer must cut the card in half vertically through the magnetic stripe.&lt;/li&gt;    &lt;li&gt;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.&lt;br /&gt;&lt;/li&gt;&lt;/ul&gt;&lt;b&gt;Returning Counterfeit Cards&lt;/b&gt;&lt;br /&gt;&lt;br /&gt;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:&lt;br /&gt;   &lt;ul&gt;&lt;li&gt;The issuers bank identification number (BIN) embossed on the front of the card.&lt;/li&gt;    &lt;li&gt;The member ID imprinted in the Card Source Identification area on the back of the card.&lt;/li&gt;&lt;/ul&gt;&lt;!-- AddThis Button BEGIN --&gt;&lt;script type="text/javascript"&gt;&lt;!--     addthis_pub  = 'Merchant Account';     addthis_brand = 'Merchant Account';     addthis_options = 'favorites, email, digg, delicious, myspace, facebook, google, live, more'; // --&gt;&lt;/script&gt;&lt;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"&gt;&lt;img src="http://s9.addthis.com/button1-bm.gif" alt="" border="0" height="16" width="125" /&gt;&lt;/a&gt;&lt;script src="http://s7.addthis.com/js/152/addthis_widget.js" type="text/javascript"&gt;&lt;/script&gt;&lt;br /&gt;&lt;!-- AddThis Button END --&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8887473741874669103-45434697145176791?l=merchantaccountprocessing.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://merchantaccountprocessing.blogspot.com/feeds/45434697145176791/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2009/12/point-of-sale-pos-card-retention.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/45434697145176791'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/45434697145176791'/><link rel='alternate' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2009/12/point-of-sale-pos-card-retention.html' title='Point-of-Sale (POS) Card Retention'/><author><name>mss</name><uri>http://www.blogger.com/profile/02682453100579738680</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8887473741874669103.post-6696851366065310864</id><published>2009-11-16T16:40:00.005-05:00</published><updated>2009-11-28T19:56:50.909-05:00</updated><title type='text'>Sales Receipt Requirements</title><content type='html'>Below is a list of the types of sales receipts discussed in this post:&lt;br /&gt;&lt;ul&gt;&lt;li&gt;Retail sale.&lt;/li&gt; &lt;li&gt;Credit.&lt;/li&gt; &lt;li&gt;Cash disbursement.&lt;/li&gt; &lt;li&gt;Information.&lt;/li&gt;&lt;/ul&gt;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.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Formset Contents&lt;/b&gt;&lt;br /&gt;&lt;br /&gt;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:&lt;br /&gt;&lt;ul&gt;&lt;li&gt;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.&lt;/li&gt; &lt;li&gt;Adequate spaces for:&lt;br /&gt;&lt;ul&gt;&lt;li&gt;Customer's signature.&lt;/li&gt; &lt;li&gt;Card imprint and the merchant or bank identification plate imprint.&lt;/li&gt; &lt;li&gt;Date of the transaction.&lt;/li&gt; &lt;li&gt;Authorization number (except on credit slips).&lt;/li&gt; &lt;li&gt;Sales clerk's or teller's initials or department number.&lt;/li&gt; &lt;li&gt;Currency conversion field.&lt;/li&gt; &lt;li&gt;Merchant's signature on credit slips.&lt;/li&gt; &lt;li&gt;Description of the ID supplied by the cardholder on cash disbursements and retail sale slips for certain unique transactions.&lt;/li&gt;&lt;/ul&gt;&lt;/li&gt; &lt;li&gt;A legend clearly identifying the slip as a retail sale, credit, or cash disbursement and identifies the receiving party of each copy.&lt;/li&gt; &lt;li&gt;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.&lt;/li&gt; &lt;li&gt;Such other contents as are not inconsistent with these rules.&lt;/li&gt;&lt;/ul&gt;It is recommended that each retail sale, credit, and cash disbursement slip identify the member bank that distributed the slip to the merchant.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Terminal Receipt Contents&lt;/b&gt;&lt;br /&gt;&lt;br /&gt;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:&lt;br /&gt;&lt;ul&gt;&lt;li&gt;Doing Business As (DBA) merchant name, city and state, country, or the point of banking location.&lt;/li&gt; &lt;li&gt;Transaction date.&lt;/li&gt; &lt;li&gt;Card account number.&lt;/li&gt; &lt;li&gt;Transaction amount in the original transaction currency.&lt;/li&gt; &lt;li&gt;Adequate space for the customer's signature (required on merchant copy only).&lt;/li&gt; &lt;li&gt;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.&lt;/li&gt; &lt;li&gt;Merchant's signature on credit receipts only.&lt;/li&gt;&lt;/ul&gt;Each receipt must clearly identify the transaction as a retail sale, credit, or cash disbursement.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Primary Account Number Truncation&lt;/b&gt;&lt;br /&gt;&lt;br /&gt;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 &lt;a title="Cardholder-Activated Terminal (CAT)" href="http://merchantaccountprocessing.blogspot.com/2009/09/cardholder-activated-terminal-cat.html" target="_self"&gt;Cardholder-Activated Terminals (CATs)&lt;/a&gt;. PAN truncation is permitted for receipts generated at all other points of sale.&lt;br /&gt;&lt;br /&gt;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 "#."&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Truncation Considerations&lt;/b&gt;&lt;br /&gt;&lt;br /&gt;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:&lt;br /&gt;&lt;ul&gt;&lt;li&gt;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.&lt;/li&gt;&lt;li&gt;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.&lt;/li&gt;&lt;li&gt;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.&lt;/li&gt;&lt;li&gt;Truncating a greater number of digits, when compared to the total number of digits in the PAN, increases the effectiveness of the effort.&lt;/li&gt;&lt;/ul&gt;&lt;b&gt;Electronic Signature Capture Technology (ESCT)&lt;/b&gt;&lt;br /&gt;&lt;br /&gt;An acquirer using Electronic Signature Capture Technology (ESCT) must ensure that:&lt;br /&gt;&lt;ul&gt;&lt;li&gt;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.&lt;/li&gt; &lt;li&gt;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.&lt;/li&gt; &lt;li&gt;Digitized signatures are not accessed or used against applicable standards and regulations.&lt;/li&gt;&lt;/ul&gt;&lt;!-- AddThis Button BEGIN --&gt;&lt;script type="text/javascript"&gt;&lt;!--     addthis_pub  = 'Merchant Account';     addthis_brand = 'Merchant Account';     addthis_options = 'favorites, email, digg, delicious, myspace, facebook, google, live, more'; // --&gt;&lt;/script&gt;&lt;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"&gt;&lt;img src="http://s9.addthis.com/button1-bm.gif" alt="" border="0" height="16" width="125" /&gt;&lt;/a&gt;&lt;script src="http://s7.addthis.com/js/152/addthis_widget.js" type="text/javascript"&gt;&lt;/script&gt;&lt;br /&gt;&lt;!-- AddThis Button END --&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8887473741874669103-6696851366065310864?l=merchantaccountprocessing.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://merchantaccountprocessing.blogspot.com/feeds/6696851366065310864/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2009/11/sales-receipt-requirements.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/6696851366065310864'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/6696851366065310864'/><link rel='alternate' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2009/11/sales-receipt-requirements.html' title='Sales Receipt Requirements'/><author><name>mss</name><uri>http://www.blogger.com/profile/02682453100579738680</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8887473741874669103.post-2017898114734943749</id><published>2009-10-12T11:41:00.011-04:00</published><updated>2009-11-10T12:53:02.812-05:00</updated><title type='text'>In-flight Commerce Terminals / Level 4 Requirements</title><content type='html'>The following requirements apply to In-flight Commerce Terminals / Level 4.&lt;br /&gt;&lt;ol&gt;&lt;li&gt;&lt;strong&gt;Acquirer / Service Provider requirements and transaction identification specifications:&lt;/strong&gt;&lt;br /&gt;&lt;ul&gt;&lt;li&gt;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.&lt;/li&gt;    &lt;li&gt;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.&lt;br /&gt;&lt;br /&gt;&lt;meta equiv="Content-Type" content="text/html; charset=utf-8"&gt;&lt;meta name="ProgId" content="Word.Document"&gt;&lt;meta name="Generator" content="Microsoft Word 12"&gt;&lt;meta name="Originator" content="Microsoft Word 12"&gt;&lt;link rel="File-List" href="file:///C:%5CUsers%5CMetodi%5CAppData%5CLocal%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_filelist.xml"&gt;&lt;link rel="themeData" href="file:///C:%5CUsers%5CMetodi%5CAppData%5CLocal%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_themedata.thmx"&gt;&lt;link rel="colorSchemeMapping" href="file:///C:%5CUsers%5CMetodi%5CAppData%5CLocal%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_colorschememapping.xml"&gt;&lt;!--[if gte mso 9]&gt;&lt;xml&gt;  &lt;w:worddocument&gt;   &lt;w:view&gt;Normal&lt;/w:View&gt;   &lt;w:zoom&gt;0&lt;/w:Zoom&gt;   &lt;w:trackmoves/&gt;   &lt;w:trackformatting/&gt;   &lt;w:punctuationkerning/&gt;   &lt;w:validateagainstschemas/&gt;   &lt;w:saveifxmlinvalid&gt;false&lt;/w:SaveIfXMLInvalid&gt;   &lt;w:ignoremixedcontent&gt;false&lt;/w:IgnoreMixedContent&gt;   &lt;w:alwaysshowplaceholdertext&gt;false&lt;/w:AlwaysShowPlaceholderText&gt;   &lt;w:donotpromoteqf/&gt;   &lt;w:lidthemeother&gt;EN-US&lt;/w:LidThemeOther&gt;   &lt;w:lidthemeasian&gt;X-NONE&lt;/w:LidThemeAsian&gt;   &lt;w:lidthemecomplexscript&gt;X-NONE&lt;/w:LidThemeComplexScript&gt;   &lt;w:compatibility&gt;    &lt;w:breakwrappedtables/&gt;    &lt;w:snaptogridincell/&gt;    &lt;w:wraptextwithpunct/&gt;    &lt;w:useasianbreakrules/&gt;    &lt;w:dontgrowautofit/&gt;    &lt;w:splitpgbreakandparamark/&gt;    &lt;w:dontvertaligncellwithsp/&gt;    &lt;w:dontbreakconstrainedforcedtables/&gt;    &lt;w:dontvertalignintxbx/&gt;    &lt;w:word11kerningpairs/&gt;    &lt;w:cachedcolbalance/&gt;   &lt;/w:Compatibility&gt;   &lt;w:browserlevel&gt;MicrosoftInternetExplorer4&lt;/w:BrowserLevel&gt;   &lt;m:mathpr&gt;    &lt;m:mathfont val="Cambria Math"&gt;    &lt;m:brkbin val="before"&gt;    &lt;m:brkbinsub val="&amp;#45;-"&gt;    &lt;m:smallfrac val="off"&gt;    &lt;m:dispdef/&gt;    &lt;m:lmargin val="0"&gt;    &lt;m:rmargin val="0"&gt;    &lt;m:defjc val="centerGroup"&gt;    &lt;m:wrapindent val="1440"&gt;    &lt;m:intlim val="subSup"&gt;    &lt;m:narylim val="undOvr"&gt;   &lt;/m:mathPr&gt;&lt;/w:WordDocument&gt; &lt;/xml&gt;&lt;![endif]--&gt;&lt;!--[if gte mso 9]&gt;&lt;xml&gt;  &lt;w:latentstyles deflockedstate="false" defunhidewhenused="true" defsemihidden="true" defqformat="false" defpriority="99" latentstylecount="267"&gt;   &lt;w:lsdexception locked="false" priority="0" semihidden="false" unhidewhenused="false" qformat="true" name="Normal"&gt;   &lt;w:lsdexception locked="false" priority="9" semihidden="false" unhidewhenused="false" qformat="true" name="heading 1"&gt;   &lt;w:lsdexception locked="false" priority="9" qformat="true" name="heading 2"&gt;   &lt;w:lsdexception locked="false" priority="9" qformat="true" name="heading 3"&gt;   &lt;w:lsdexception locked="false" priority="9" qformat="true" name="heading 4"&gt;   &lt;w:lsdexception locked="false" priority="9" qformat="true" name="heading 5"&gt;   &lt;w:lsdexception locked="false" priority="9" qformat="true" name="heading 6"&gt;   &lt;w:lsdexception locked="false" priority="9" qformat="true" name="heading 7"&gt;   &lt;w:lsdexception locked="false" priority="9" qformat="true" name="heading 8"&gt;   &lt;w:lsdexception locked="false" priority="9" qformat="true" name="heading 9"&gt;   &lt;w:lsdexception locked="false" priority="39" name="toc 1"&gt;   &lt;w:lsdexception locked="false" priority="39" name="toc 2"&gt;   &lt;w:lsdexception locked="false" priority="39" name="toc 3"&gt;   &lt;w:lsdexception locked="false" priority="39" name="toc 4"&gt;   &lt;w:lsdexception locked="false" priority="39" name="toc 5"&gt;   &lt;w:lsdexception locked="false" priority="39" name="toc 6"&gt;   &lt;w:lsdexception locked="false" priority="39" name="toc 7"&gt;   &lt;w:lsdexception locked="false" priority="39" name="toc 8"&gt;   &lt;w:lsdexception locked="false" priority="39" name="toc 9"&gt;   &lt;w:lsdexception locked="false" priority="35" qformat="true" name="caption"&gt;   &lt;w:lsdexception locked="false" priority="10" semihidden="false" unhidewhenused="false" qformat="true" name="Title"&gt;   &lt;w:lsdexception locked="false" priority="1" name="Default Paragraph Font"&gt;   &lt;w:lsdexception locked="false" priority="11" semihidden="false" unhidewhenused="false" qformat="true" name="Subtitle"&gt;   &lt;w:lsdexception locked="false" priority="22" semihidden="false" unhidewhenused="false" qformat="true" name="Strong"&gt;   &lt;w:lsdexception locked="false" priority="20" semihidden="false" unhidewhenused="false" qformat="true" name="Emphasis"&gt;   &lt;w:lsdexception locked="false" priority="59" semihidden="false" unhidewhenused="false" name="Table Grid"&gt;   &lt;w:lsdexception locked="false" unhidewhenused="false" name="Placeholder Text"&gt;   &lt;w:lsdexception locked="false" priority="1" semihidden="false" unhidewhenused="false" qformat="true" name="No Spacing"&gt;   &lt;w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading"&gt;   &lt;w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List"&gt;   &lt;w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid"&gt;   &lt;w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1"&gt;   &lt;w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2"&gt;   &lt;w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1"&gt;   &lt;w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2"&gt;   &lt;w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1"&gt;   &lt;w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2"&gt;   &lt;w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3"&gt;   &lt;w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List"&gt;   &lt;w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading"&gt;   &lt;w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List"&gt;   &lt;w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid"&gt;   &lt;w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 1"&gt;   &lt;w:lsdexception locked="false" unhidewhenused="false" name="Revision"&gt;   &lt;w:lsdexception locked="false" priority="34" semihidden="false" unhidewhenused="false" qformat="true" name="List Paragraph"&gt;   &lt;w:lsdexception locked="false" priority="29" semihidden="false" unhidewhenused="false" qformat="true" name="Quote"&gt;   &lt;w:lsdexception locked="false" priority="30" semihidden="false" unhidewhenused="false" qformat="true" name="Intense Quote"&gt;   &lt;w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="19" semihidden="false" unhidewhenused="false" qformat="true" name="Subtle Emphasis"&gt;   &lt;w:lsdexception locked="false" priority="21" semihidden="false" unhidewhenused="false" qformat="true" name="Intense Emphasis"&gt;   &lt;w:lsdexception locked="false" priority="31" semihidden="false" unhidewhenused="false" qformat="true" name="Subtle Reference"&gt;   &lt;w:lsdexception locked="false" priority="32" semihidden="false" unhidewhenused="false" qformat="true" name="Intense Reference"&gt;   &lt;w:lsdexception locked="false" priority="33" semihidden="false" unhidewhenused="false" qformat="true" name="Book Title"&gt;   &lt;w:lsdexception locked="false" priority="37" name="Bibliography"&gt;   &lt;w:lsdexception locked="false" priority="39" qformat="true" name="TOC Heading"&gt;  &lt;/w:LatentStyles&gt; &lt;/xml&gt;&lt;![endif]--&gt;&lt;style&gt; &lt;!--  /* 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;} --&gt; &lt;/style&gt;&lt;!--[if gte mso 10]&gt; &lt;style&gt;  /* 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;} &lt;/style&gt; &lt;![endif]--&gt;  &lt;table class="MsoTableGrid" style="border: medium none ; border-collapse: collapse;" border="1" cellpadding="0" cellspacing="0"&gt;  &lt;tbody&gt;&lt;tr style=""&gt;   &lt;td style="border: 1pt solid black; padding: 0in 5.4pt; width: 171.9pt;" valign="top" width="229"&gt;   &lt;p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"&gt;&lt;b style=""&gt;IFC Transaction Type&lt;o:p&gt;&lt;/o:p&gt;&lt;/b&gt;&lt;/p&gt;   &lt;/td&gt;   &lt;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"&gt;   &lt;p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"&gt;&lt;b style=""&gt;MCC&lt;o:p&gt;&lt;/o:p&gt;&lt;/b&gt;&lt;/p&gt;   &lt;/td&gt;  &lt;/tr&gt;  &lt;tr style=""&gt;   &lt;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"&gt;   &lt;p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"&gt;Catalog card acceptor&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt;   &lt;/td&gt;   &lt;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"&gt;   &lt;p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"&gt;5964&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt;   &lt;/td&gt;  &lt;/tr&gt;  &lt;tr style=""&gt;   &lt;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"&gt;   &lt;p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"&gt;Duty-free store&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt;   &lt;/td&gt;   &lt;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"&gt;   &lt;p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"&gt;5309&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt;   &lt;/td&gt;  &lt;/tr&gt;  &lt;tr style=""&gt;   &lt;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"&gt;   &lt;p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"&gt;Gaming&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt;   &lt;/td&gt;   &lt;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"&gt;   &lt;p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"&gt;7995&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt;   &lt;/td&gt;  &lt;/tr&gt;  &lt;tr style=""&gt;   &lt;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"&gt;   &lt;p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"&gt;Miscellaneous services&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt;   &lt;/td&gt;   &lt;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"&gt;   &lt;p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"&gt;7299&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt;   &lt;/td&gt;  &lt;/tr&gt;  &lt;tr style=""&gt;   &lt;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"&gt;   &lt;p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"&gt;Video game&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt;   &lt;/td&gt;   &lt;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"&gt;   &lt;p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"&gt;7994&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt;   &lt;/td&gt;  &lt;/tr&gt; &lt;/tbody&gt;&lt;/table&gt;&lt;br /&gt;&lt;/li&gt;  &lt;li&gt;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.&lt;/li&gt;    &lt;li&gt;The acquiring bank must identify the transaction with the most appropriate transaction category code (TCC) in the authorization request message.&lt;br /&gt;&lt;br /&gt;&lt;meta equiv="Content-Type" content="text/html; charset=utf-8"&gt;&lt;meta name="ProgId" content="Word.Document"&gt;&lt;meta name="Generator" content="Microsoft Word 12"&gt;&lt;meta name="Originator" content="Microsoft Word 12"&gt;&lt;link rel="File-List" href="file:///C:%5CUsers%5CMetodi%5CAppData%5CLocal%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_filelist.xml"&gt;&lt;link rel="themeData" href="file:///C:%5CUsers%5CMetodi%5CAppData%5CLocal%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_themedata.thmx"&gt;&lt;link rel="colorSchemeMapping" href="file:///C:%5CUsers%5CMetodi%5CAppData%5CLocal%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_colorschememapping.xml"&gt;&lt;!--[if gte mso 9]&gt;&lt;xml&gt;  &lt;w:worddocument&gt;   &lt;w:view&gt;Normal&lt;/w:View&gt;   &lt;w:zoom&gt;0&lt;/w:Zoom&gt;   &lt;w:trackmoves/&gt;   &lt;w:trackformatting/&gt;   &lt;w:punctuationkerning/&gt;   &lt;w:validateagainstschemas/&gt;   &lt;w:saveifxmlinvalid&gt;false&lt;/w:SaveIfXMLInvalid&gt;   &lt;w:ignoremixedcontent&gt;false&lt;/w:IgnoreMixedContent&gt;   &lt;w:alwaysshowplaceholdertext&gt;false&lt;/w:AlwaysShowPlaceholderText&gt;   &lt;w:donotpromoteqf/&gt;   &lt;w:lidthemeother&gt;EN-US&lt;/w:LidThemeOther&gt;   &lt;w:lidthemeasian&gt;X-NONE&lt;/w:LidThemeAsian&gt;   &lt;w:lidthemecomplexscript&gt;X-NONE&lt;/w:LidThemeComplexScript&gt;   &lt;w:compatibility&gt;    &lt;w:breakwrappedtables/&gt;    &lt;w:snaptogridincell/&gt;    &lt;w:wraptextwithpunct/&gt;    &lt;w:useasianbreakrules/&gt;    &lt;w:dontgrowautofit/&gt;    &lt;w:splitpgbreakandparamark/&gt;    &lt;w:dontvertaligncellwithsp/&gt;    &lt;w:dontbreakconstrainedforcedtables/&gt;    &lt;w:dontvertalignintxbx/&gt;    &lt;w:word11kerningpairs/&gt;    &lt;w:cachedcolbalance/&gt;   &lt;/w:Compatibility&gt;   &lt;w:browserlevel&gt;MicrosoftInternetExplorer4&lt;/w:BrowserLevel&gt;   &lt;m:mathpr&gt;    &lt;m:mathfont val="Cambria Math"&gt;    &lt;m:brkbin val="before"&gt;    &lt;m:brkbinsub val="&amp;#45;-"&gt;    &lt;m:smallfrac val="off"&gt;    &lt;m:dispdef/&gt;    &lt;m:lmargin val="0"&gt;    &lt;m:rmargin val="0"&gt;    &lt;m:defjc val="centerGroup"&gt;    &lt;m:wrapindent val="1440"&gt;    &lt;m:intlim val="subSup"&gt;    &lt;m:narylim val="undOvr"&gt;   &lt;/m:mathPr&gt;&lt;/w:WordDocument&gt; &lt;/xml&gt;&lt;![endif]--&gt;&lt;!--[if gte mso 9]&gt;&lt;xml&gt;  &lt;w:latentstyles deflockedstate="false" defunhidewhenused="true" defsemihidden="true" defqformat="false" defpriority="99" latentstylecount="267"&gt;   &lt;w:lsdexception locked="false" priority="0" semihidden="false" unhidewhenused="false" qformat="true" name="Normal"&gt;   &lt;w:lsdexception locked="false" priority="9" semihidden="false" unhidewhenused="false" qformat="true" name="heading 1"&gt;   &lt;w:lsdexception locked="false" priority="9" qformat="true" name="heading 2"&gt;   &lt;w:lsdexception locked="false" priority="9" qformat="true" name="heading 3"&gt;   &lt;w:lsdexception locked="false" priority="9" qformat="true" name="heading 4"&gt;   &lt;w:lsdexception locked="false" priority="9" qformat="true" name="heading 5"&gt;   &lt;w:lsdexception locked="false" priority="9" qformat="true" name="heading 6"&gt;   &lt;w:lsdexception locked="false" priority="9" qformat="true" name="heading 7"&gt;   &lt;w:lsdexception locked="false" priority="9" qformat="true" name="heading 8"&gt;   &lt;w:lsdexception locked="false" priority="9" qformat="true" name="heading 9"&gt;   &lt;w:lsdexception locked="false" priority="39" name="toc 1"&gt;   &lt;w:lsdexception locked="false" priority="39" name="toc 2"&gt;   &lt;w:lsdexception locked="false" priority="39" name="toc 3"&gt;   &lt;w:lsdexception locked="false" priority="39" name="toc 4"&gt;   &lt;w:lsdexception locked="false" priority="39" name="toc 5"&gt;   &lt;w:lsdexception locked="false" priority="39" name="toc 6"&gt;   &lt;w:lsdexception locked="false" priority="39" name="toc 7"&gt;   &lt;w:lsdexception locked="false" priority="39" name="toc 8"&gt;   &lt;w:lsdexception locked="false" priority="39" name="toc 9"&gt;   &lt;w:lsdexception locked="false" priority="35" qformat="true" name="caption"&gt;   &lt;w:lsdexception locked="false" priority="10" semihidden="false" unhidewhenused="false" qformat="true" name="Title"&gt;   &lt;w:lsdexception locked="false" priority="1" name="Default Paragraph Font"&gt;   &lt;w:lsdexception locked="false" priority="11" semihidden="false" unhidewhenused="false" qformat="true" name="Subtitle"&gt;   &lt;w:lsdexception locked="false" priority="22" semihidden="false" unhidewhenused="false" qformat="true" name="Strong"&gt;   &lt;w:lsdexception locked="false" priority="20" semihidden="false" unhidewhenused="false" qformat="true" name="Emphasis"&gt;   &lt;w:lsdexception locked="false" priority="59" semihidden="false" unhidewhenused="false" name="Table Grid"&gt;   &lt;w:lsdexception locked="false" unhidewhenused="false" name="Placeholder Text"&gt;   &lt;w:lsdexception locked="false" priority="1" semihidden="false" unhidewhenused="false" qformat="true" name="No Spacing"&gt;   &lt;w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading"&gt;   &lt;w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List"&gt;   &lt;w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid"&gt;   &lt;w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1"&gt;   &lt;w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2"&gt;   &lt;w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1"&gt;   &lt;w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2"&gt;   &lt;w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1"&gt;   &lt;w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2"&gt;   &lt;w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3"&gt;   &lt;w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List"&gt;   &lt;w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading"&gt;   &lt;w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List"&gt;   &lt;w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid"&gt;   &lt;w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 1"&gt;   &lt;w:lsdexception locked="false" unhidewhenused="false" name="Revision"&gt;   &lt;w:lsdexception locked="false" priority="34" semihidden="false" unhidewhenused="false" qformat="true" name="List Paragraph"&gt;   &lt;w:lsdexception locked="false" priority="29" semihidden="false" unhidewhenused="false" qformat="true" name="Quote"&gt;   &lt;w:lsdexception locked="false" priority="30" semihidden="false" unhidewhenused="false" qformat="true" name="Intense Quote"&gt;   &lt;w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="19" semihidden="false" unhidewhenused="false" qformat="true" name="Subtle Emphasis"&gt;   &lt;w:lsdexception locked="false" priority="21" semihidden="false" unhidewhenused="false" qformat="true" name="Intense Emphasis"&gt;   &lt;w:lsdexception locked="false" priority="31" semihidden="false" unhidewhenused="false" qformat="true" name="Subtle Reference"&gt;   &lt;w:lsdexception locked="false" priority="32" semihidden="false" unhidewhenused="false" qformat="true" name="Intense Reference"&gt;   &lt;w:lsdexception locked="false" priority="33" semihidden="false" unhidewhenused="false" qformat="true" name="Book Title"&gt;   &lt;w:lsdexception locked="false" priority="37" name="Bibliography"&gt;   &lt;w:lsdexception locked="false" priority="39" qformat="true" name="TOC Heading"&gt;  &lt;/w:LatentStyles&gt; &lt;/xml&gt;&lt;![endif]--&gt;&lt;style&gt; &lt;!--  /* 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;} --&gt; &lt;/style&gt;&lt;!--[if gte mso 10]&gt; &lt;style&gt;  /* 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;} &lt;/style&gt; &lt;![endif]--&gt;  &lt;table class="MsoTableGrid" style="border: medium none ; border-collapse: collapse;" border="1" cellpadding="0" cellspacing="0"&gt;  &lt;tbody&gt;&lt;tr style=""&gt;   &lt;td style="border: 1pt solid black; padding: 0in 5.4pt; width: 2.2in;" valign="top" width="211"&gt;   &lt;p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"&gt;&lt;b style=""&gt;IF the IFC transaction is for…&lt;o:p&gt;&lt;/o:p&gt;&lt;/b&gt;&lt;/p&gt;   &lt;/td&gt;   &lt;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"&gt;   &lt;p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"&gt;&lt;b style=""&gt;THEN the acquirer must use   TCC…&lt;o:p&gt;&lt;/o:p&gt;&lt;/b&gt;&lt;/p&gt;   &lt;/td&gt;  &lt;/tr&gt;  &lt;tr style=""&gt;   &lt;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"&gt;   &lt;p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"&gt;Gaming&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt;   &lt;/td&gt;   &lt;td style="border-style: none solid solid none; padding: 0in 5.4pt; width: 2.5in;" valign="top" width="240"&gt;   &lt;p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"&gt;U for Unique Transaction.&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt;   &lt;/td&gt;  &lt;/tr&gt;  &lt;tr style=""&gt;   &lt;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"&gt;   &lt;p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"&gt;Anything other than gaming&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt;   &lt;/td&gt;   &lt;td style="border-style: none solid solid none; padding: 0in 5.4pt; width: 2.5in;" valign="top" width="240"&gt;   &lt;p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"&gt;R for Retail Purchase&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt;   &lt;/td&gt;  &lt;/tr&gt; &lt;/tbody&gt;&lt;/table&gt;&lt;br /&gt;&lt;/li&gt;  &lt;li&gt;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).&lt;/li&gt;    &lt;li&gt;The city field description should contain the following:&lt;br /&gt;&lt;br /&gt;&lt;meta equiv="Content-Type" content="text/html; charset=utf-8"&gt;&lt;meta name="ProgId" content="Word.Document"&gt;&lt;meta name="Generator" content="Microsoft Word 12"&gt;&lt;meta name="Originator" content="Microsoft Word 12"&gt;&lt;link rel="File-List" href="file:///C:%5CUsers%5CMetodi%5CAppData%5CLocal%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_filelist.xml"&gt;&lt;link rel="themeData" href="file:///C:%5CUsers%5CMetodi%5CAppData%5CLocal%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_themedata.thmx"&gt;&lt;link rel="colorSchemeMapping" href="file:///C:%5CUsers%5CMetodi%5CAppData%5CLocal%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_colorschememapping.xml"&gt;&lt;!--[if gte mso 9]&gt;&lt;xml&gt;  &lt;w:worddocument&gt;   &lt;w:view&gt;Normal&lt;/w:View&gt;   &lt;w:zoom&gt;0&lt;/w:Zoom&gt;   &lt;w:trackmoves/&gt;   &lt;w:trackformatting/&gt;   &lt;w:punctuationkerning/&gt;   &lt;w:validateagainstschemas/&gt;   &lt;w:saveifxmlinvalid&gt;false&lt;/w:SaveIfXMLInvalid&gt;   &lt;w:ignoremixedcontent&gt;false&lt;/w:IgnoreMixedContent&gt;   &lt;w:alwaysshowplaceholdertext&gt;false&lt;/w:AlwaysShowPlaceholderText&gt;   &lt;w:donotpromoteqf/&gt;   &lt;w:lidthemeother&gt;EN-US&lt;/w:LidThemeOther&gt;   &lt;w:lidthemeasian&gt;X-NONE&lt;/w:LidThemeAsian&gt;   &lt;w:lidthemecomplexscript&gt;X-NONE&lt;/w:LidThemeComplexScript&gt;   &lt;w:compatibility&gt;    &lt;w:breakwrappedtables/&gt;    &lt;w:snaptogridincell/&gt;    &lt;w:wraptextwithpunct/&gt;    &lt;w:useasianbreakrules/&gt;    &lt;w:dontgrowautofit/&gt;    &lt;w:splitpgbreakandparamark/&gt;    &lt;w:dontvertaligncellwithsp/&gt;    &lt;w:dontbreakconstrainedforcedtables/&gt;    &lt;w:dontvertalignintxbx/&gt;    &lt;w:word11kerningpairs/&gt;    &lt;w:cachedcolbalance/&gt;   &lt;/w:Compatibility&gt;   &lt;w:browserlevel&gt;MicrosoftInternetExplorer4&lt;/w:BrowserLevel&gt;   &lt;m:mathpr&gt;    &lt;m:mathfont val="Cambria Math"&gt;    &lt;m:brkbin val="before"&gt;    &lt;m:brkbinsub val="&amp;#45;-"&gt;    &lt;m:smallfrac val="off"&gt;    &lt;m:dispdef/&gt;    &lt;m:lmargin val="0"&gt;    &lt;m:rmargin val="0"&gt;    &lt;m:defjc val="centerGroup"&gt;    &lt;m:wrapindent val="1440"&gt;    &lt;m:intlim val="subSup"&gt;    &lt;m:narylim val="undOvr"&gt;   &lt;/m:mathPr&gt;&lt;/w:WordDocument&gt; &lt;/xml&gt;&lt;![endif]--&gt;&lt;!--[if gte mso 9]&gt;&lt;xml&gt;  &lt;w:latentstyles deflockedstate="false" defunhidewhenused="true" defsemihidden="true" defqformat="false" defpriority="99" latentstylecount="267"&gt;   &lt;w:lsdexception locked="false" priority="0" semihidden="false" unhidewhenused="false" qformat="true" name="Normal"&gt;   &lt;w:lsdexception locked="false" priority="9" semihidden="false" unhidewhenused="false" qformat="true" name="heading 1"&gt;   &lt;w:lsdexception locked="false" priority="9" qformat="true" name="heading 2"&gt;   &lt;w:lsdexception locked="false" priority="9" qformat="true" name="heading 3"&gt;   &lt;w:lsdexception locked="false" priority="9" qformat="true" name="heading 4"&gt;   &lt;w:lsdexception locked="false" priority="9" qformat="true" name="heading 5"&gt;   &lt;w:lsdexception locked="false" priority="9" qformat="true" name="heading 6"&gt;   &lt;w:lsdexception locked="false" priority="9" qformat="true" name="heading 7"&gt;   &lt;w:lsdexception locked="false" priority="9" qformat="true" name="heading 8"&gt;   &lt;w:lsdexception locked="false" priority="9" qformat="true" name="heading 9"&gt;   &lt;w:lsdexception locked="false" priority="39" name="toc 1"&gt;   &lt;w:lsdexception locked="false" priority="39" name="toc 2"&gt;   &lt;w:lsdexception locked="false" priority="39" name="toc 3"&gt;   &lt;w:lsdexception locked="false" priority="39" name="toc 4"&gt;   &lt;w:lsdexception locked="false" priority="39" name="toc 5"&gt;   &lt;w:lsdexception locked="false" priority="39" name="toc 6"&gt;   &lt;w:lsdexception locked="false" priority="39" name="toc 7"&gt;   &lt;w:lsdexception locked="false" priority="39" name="toc 8"&gt;   &lt;w:lsdexception locked="false" priority="39" name="toc 9"&gt;   &lt;w:lsdexception locked="false" priority="35" qformat="true" name="caption"&gt;   &lt;w:lsdexception locked="false" priority="10" semihidden="false" unhidewhenused="false" qformat="true" name="Title"&gt;   &lt;w:lsdexception locked="false" priority="1" name="Default Paragraph Font"&gt;   &lt;w:lsdexception locked="false" priority="11" semihidden="false" unhidewhenused="false" qformat="true" name="Subtitle"&gt;   &lt;w:lsdexception locked="false" priority="22" semihidden="false" unhidewhenused="false" qformat="true" name="Strong"&gt;   &lt;w:lsdexception locked="false" priority="20" semihidden="false" unhidewhenused="false" qformat="true" name="Emphasis"&gt;   &lt;w:lsdexception locked="false" priority="59" semihidden="false" unhidewhenused="false" name="Table Grid"&gt;   &lt;w:lsdexception locked="false" unhidewhenused="false" name="Placeholder Text"&gt;   &lt;w:lsdexception locked="false" priority="1" semihidden="false" unhidewhenused="false" qformat="true" name="No Spacing"&gt;   &lt;w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading"&gt;   &lt;w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List"&gt;   &lt;w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid"&gt;   &lt;w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1"&gt;   &lt;w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2"&gt;   &lt;w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1"&gt;   &lt;w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2"&gt;   &lt;w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1"&gt;   &lt;w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2"&gt;   &lt;w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3"&gt;   &lt;w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List"&gt;   &lt;w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading"&gt;   &lt;w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List"&gt;   &lt;w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid"&gt;   &lt;w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 1"&gt;   &lt;w:lsdexception locked="false" unhidewhenused="false" name="Revision"&gt;   &lt;w:lsdexception locked="false" priority="34" semihidden="false" unhidewhenused="false" qformat="true" name="List Paragraph"&gt;   &lt;w:lsdexception locked="false" priority="29" semihidden="false" unhidewhenused="false" qformat="true" name="Quote"&gt;   &lt;w:lsdexception locked="false" priority="30" semihidden="false" unhidewhenused="false" qformat="true" name="Intense Quote"&gt;   &lt;w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="19" semihidden="false" unhidewhenused="false" qformat="true" name="Subtle Emphasis"&gt;   &lt;w:lsdexception locked="false" priority="21" semihidden="false" unhidewhenused="false" qformat="true" name="Intense Emphasis"&gt;   &lt;w:lsdexception locked="false" priority="31" semihidden="false" unhidewhenused="false" qformat="true" name="Subtle Reference"&gt;   &lt;w:lsdexception locked="false" priority="32" semihidden="false" unhidewhenused="false" qformat="true" name="Intense Reference"&gt;   &lt;w:lsdexception locked="false" priority="33" semihidden="false" unhidewhenused="false" qformat="true" name="Book Title"&gt;   &lt;w:lsdexception locked="false" priority="37" name="Bibliography"&gt;   &lt;w:lsdexception locked="false" priority="39" qformat="true" name="TOC Heading"&gt;  &lt;/w:LatentStyles&gt; &lt;/xml&gt;&lt;![endif]--&gt;&lt;style&gt; &lt;!--  /* 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;} --&gt; &lt;/style&gt;&lt;!--[if gte mso 10]&gt; &lt;style&gt;  /* 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;} &lt;/style&gt; &lt;![endif]--&gt;  &lt;table class="MsoTableGrid" style="border: medium none ; border-collapse: collapse;" border="1" cellpadding="0" cellspacing="0"&gt;  &lt;tbody&gt;&lt;tr style=""&gt;   &lt;td style="border: 1pt solid black; padding: 0in 5.4pt; width: 2.2in;" valign="top" width="211"&gt;   &lt;p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"&gt;&lt;b style=""&gt;For…&lt;o:p&gt;&lt;/o:p&gt;&lt;/b&gt;&lt;/p&gt;   &lt;/td&gt;   &lt;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"&gt;   &lt;p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"&gt;&lt;b style=""&gt;The city field description…&lt;o:p&gt;&lt;/o:p&gt;&lt;/b&gt;&lt;/p&gt;   &lt;/td&gt;  &lt;/tr&gt;  &lt;tr style=""&gt;   &lt;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"&gt;   &lt;p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"&gt;Mailed purchases and gaming transactions&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt;   &lt;/td&gt;   &lt;td style="border-style: none solid solid none; padding: 0in 5.4pt; width: 2.5in;" valign="top" width="240"&gt;   &lt;p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"&gt;Must include the service provider’s customer service telephone   number.&lt;span style=""&gt;  &lt;/span&gt;It is not required to be a   toll-free number.&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt;   &lt;/td&gt;  &lt;/tr&gt;  &lt;tr style=""&gt;   &lt;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"&gt;   &lt;p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"&gt;All IFC transactions other than mailed purchases and gaming&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt;   &lt;/td&gt;   &lt;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"&gt;   &lt;p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"&gt;Optionally may be a customer service telephone number.&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt;   &lt;/td&gt;  &lt;/tr&gt; &lt;/tbody&gt;&lt;/table&gt;&lt;br /&gt;&lt;/li&gt;  &lt;li&gt;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.&lt;/li&gt;&lt;li&gt;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:&lt;br /&gt;	&lt;ul&gt;&lt;li&gt;Full identification of the service provider and provision for recourse in terms of cardholder complaints or questions.&lt;/li&gt;	&lt;li&gt;Notification that transactions will be billed upon the card issuer's approval of the authorization request.&lt;/li&gt;	&lt;li&gt;For mailed purchases only, any additional shipping or handling charges.&lt;/li&gt;	&lt;li&gt;Policy on refunds or returns.&lt;/li&gt;	&lt;li&gt;Provision for a paper receipt.&lt;/li&gt;&lt;br /&gt;For IFC gaming transactions, service providers must additionally disclose the following:&lt;br /&gt;&lt;br /&gt;	&lt;li&gt;Maximum winnings ($3,500) and maximum losses ($350).&lt;/li&gt;	&lt;li&gt;Notification that total net transaction amount (whether a net win or loss) will be applied against the cardholder's account&lt;/li&gt;	&lt;li&gt;Notification that cardholder must be at least 18 years of age to play.&lt;/li&gt;	&lt;li&gt;Notification that some card issuers may not allow gaming.&lt;/li&gt;&lt;/ul&gt;&lt;/li&gt;	&lt;li&gt;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:&lt;br /&gt;	&lt;ul&gt;&lt;li&gt;Printing a receipt at the passenger's seat.&lt;/li&gt;	&lt;li&gt;Printing a receipt from a centralized printer on the plane.&lt;/li&gt;	&lt;li&gt;Mailing a receipt to the cardholder.&lt;/li&gt;&lt;br /&gt;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.&lt;br /&gt;&lt;br /&gt;The receipt must contain the following elements:&lt;br /&gt;&lt;br /&gt;	&lt;li&gt;Identification of the passenger's flight, seat number, and date of departure.&lt;/li&gt;	&lt;li&gt;Itemized transaction detail.&lt;/li&gt;	&lt;li&gt;Gaming transaction specified as a net win or net loss.&lt;/li&gt;	&lt;li&gt;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.&lt;/li&gt;&lt;/ul&gt;&lt;/li&gt;	&lt;li&gt;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.&lt;br /&gt;&lt;/li&gt;&lt;/ul&gt;&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Transaction requirements.&lt;/strong&gt;&lt;br /&gt;	&lt;ul&gt;&lt;li&gt;No maximum transaction amount applies to any IFC transaction, with the exception of IFC gaming transactions.&lt;/li&gt;&lt;li&gt;An IFC terminal that also is a hybrid terminal is prohibited from performing fallback procedures from chip to magnetic stripe.&lt;/li&gt;&lt;/ul&gt;&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Additional requirements for IFC gaming transactions.&lt;/strong&gt;&lt;br /&gt;	&lt;ul&gt;&lt;li&gt;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.&lt;/li&gt;	&lt;li&gt;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.&lt;/li&gt;	&lt;li&gt;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.&lt;/li&gt;&lt;/ul&gt;&lt;/li&gt;	&lt;li&gt;&lt;strong&gt;Cardholder account number verification - in-flight verification prior to transaction initiation.&lt;/strong&gt;&lt;br /&gt;	&lt;ul&gt;&lt;li&gt;The acquirer must ensure that the service provider conducts a Mod-10 check digit routine to verify card authenticity.&lt;/li&gt;	&lt;li&gt;The acquirer must ensure that the service provider confirms that the card account number is a valid one.&lt;/li&gt;	&lt;li&gt;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.&lt;/li&gt;&lt;/ul&gt;&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Authorization requirements for all IFC transactions.&lt;/strong&gt;&lt;br /&gt;	&lt;ul&gt;&lt;li&gt;The Authorization Request / 0100 message must include the cardholder-activated terminal level 4 indicator.&lt;/li&gt;	&lt;li&gt;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.&lt;/li&gt;	&lt;li&gt;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.&lt;/li&gt;	&lt;li&gt;The acquirer must convert all "refer to card issuer" and "capture card" messages received from issuers to "declines."&lt;/li&gt;&lt;/ul&gt;&lt;/li&gt;	&lt;li&gt;&lt;strong&gt;Additional authorization requirements for IFC gaming transactions.&lt;/strong&gt; 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.&lt;/li&gt;	&lt;li&gt;&lt;strong&gt;Clearing requirements for all IFC transactions.&lt;/strong&gt;&lt;br /&gt;	&lt;ul&gt;&lt;li&gt;An acquirer is not permitted to submit declined transactions (including those defined in 5.d. above) into clearing.&lt;/li&gt;	&lt;li&gt;No surcharges or service fees may be assessed on any IFC transaction, including IFC gaming transactions.&lt;br /&gt;	&lt;/li&gt;&lt;/ul&gt;&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Additional clearing requirements for IFC gaming transactions.&lt;/strong&gt;&lt;br /&gt;	&lt;ul&gt;&lt;li&gt;IFC gaming transactions submitted for clearing must be for the net amount that is won or lost.&lt;/li&gt;	&lt;li&gt;IFC gaming win transactions will be submitted as a credit transaction. Interchange will be paid to issuers by acquirers on gaming win transactions.&lt;/li&gt;	&lt;li&gt;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.&lt;/li&gt;&lt;/ul&gt;&lt;/li&gt;	&lt;li&gt;&lt;strong&gt;Effective date of the IFC blocked gaming file.&lt;/strong&gt; 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.&lt;br /&gt;&lt;/li&gt;&lt;/ol&gt;&lt;!-- AddThis Button BEGIN --&gt;&lt;script type="text/javascript"&gt;&lt;!--     addthis_pub  = 'Merchant Account';     addthis_brand = 'Merchant Account';     addthis_options = 'favorites, email, digg, delicious, myspace, facebook, google, live, more'; // --&gt;&lt;/script&gt;&lt;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"&gt;&lt;img src="http://s9.addthis.com/button1-bm.gif" alt="" border="0" height="16" width="125" /&gt;&lt;/a&gt;&lt;script src="http://s7.addthis.com/js/152/addthis_widget.js" type="text/javascript"&gt;&lt;/script&gt;&lt;br /&gt;&lt;!-- AddThis Button END --&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8887473741874669103-2017898114734943749?l=merchantaccountprocessing.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://merchantaccountprocessing.blogspot.com/feeds/2017898114734943749/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2009/10/in-flight-commerce-terminals-level-4.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/2017898114734943749'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/2017898114734943749'/><link rel='alternate' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2009/10/in-flight-commerce-terminals-level-4.html' title='In-flight Commerce Terminals / Level 4 Requirements'/><author><name>mss</name><uri>http://www.blogger.com/profile/02682453100579738680</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8887473741874669103.post-8340577185563953058</id><published>2009-09-10T16:37:00.003-04:00</published><updated>2009-10-06T12:20:33.390-04:00</updated><title type='text'>Cardholder-Activated Terminal Level Requirements</title><content type='html'>The following acceptance requirements apply to the specific CAT levels indicated:&lt;br /&gt;&lt;ul&gt;&lt;li&gt;&lt;strong&gt;Automated Dispensing Machines (ADMs) / Level 1.&lt;/strong&gt;&lt;br /&gt;&lt;ol&gt;&lt;li&gt;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.&lt;br /&gt;&lt;ul&gt;&lt;li&gt;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.&lt;/li&gt;    &lt;li&gt;The PIN &lt;a title="Authorization" href="http://merchantprocessingservices.blogspot.com/2008/11/authorization.html" target="_self"&gt;authorization&lt;/a&gt; must be made via a secured transmission, in accordance with the published specifications.&lt;/li&gt;    &lt;li&gt;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.&lt;/li&gt;&lt;/ul&gt;&lt;/li&gt;    &lt;li&gt;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.&lt;/li&gt;    &lt;li&gt;All transactions regardless of amount must be authorized on a zero &lt;a title="Floor Limit" href="http://paymentprocessingservices.blogspot.com/2008/07/floor-limit.html" target="_self"&gt;floor limit&lt;/a&gt; basis with full, unaltered card-read data transmitted. All acquiring banks of ADMs must have received one-time &lt;a title="CVC2" href="http://merchantprocessingservices.blogspot.com/2008/11/card-verification-code-2-cvc2.html" target="_self"&gt;CVC&lt;/a&gt; / &lt;a title="CVV2" href="http://merchantprocessingservices.blogspot.com/2008/11/card-verification-value-2-cvv2.html" target="_self"&gt;CVV&lt;/a&gt; certification.&lt;/li&gt;    &lt;li&gt;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.&lt;br /&gt;&lt;ul&gt;&lt;li&gt;The retained card must be logged and secured under appropriate audit controls.&lt;/li&gt;    &lt;li&gt;The retained card must promptly be rendered useless and then returned to the acquiring bank.&lt;/li&gt;&lt;/ul&gt;&lt;/li&gt;    &lt;li&gt;"No Cardholder Authorization" (reason code 4837) &lt;a title="Chargeback Manual" href="http://www.unibulmerchantservices.com/chargeback-manual" target="_self"&gt;chargeback&lt;/a&gt; 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.&lt;/li&gt;    &lt;li&gt;An ADM that is also a hybrid terminal may perform fallback procedures unless it is prohibited by a region. &lt;a title="Member" href="http://merchantprocessingservices.blogspot.com/2008/12/member.html" target="_self"&gt;Member&lt;/a&gt; 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.&lt;/li&gt;&lt;/ol&gt;&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Self-Service Terminal / Level 2.&lt;/strong&gt;&lt;br /&gt;&lt;ol&gt;&lt;li&gt;Self-Service Terminals do not process PIN. They include (but are not limited to) automated fuel dispensers identified with MCC 5542.&lt;/li&gt; &lt;li&gt;All Self-Service Terminal (SST) devices must comply with the following requirements:&lt;br /&gt;&lt;ul&gt;&lt;li&gt;Zero floor limit for &lt;a title="Authorization" href="http://merchantprocessingservices.blogspot.com/2008/11/authorization.html" target="_self"&gt;authorization&lt;/a&gt; purposes.&lt;/li&gt; &lt;li&gt;Acquiring banks must read and transmit full, unaltered card read data.&lt;/li&gt;&lt;/ul&gt;&lt;/li&gt; &lt;li&gt;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.&lt;/li&gt; &lt;li&gt;The maximum transaction amount is $100 or its equivalent.&lt;/li&gt; &lt;li&gt;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 &lt;a title="Chargeback" href="http://merchantprocessingservices.blogspot.com/2008/11/chargeback.html" target="_self"&gt;chargeback&lt;/a&gt; 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).&lt;br /&gt;&lt;br /&gt;Counterfeit transactions occurring at Self-Service Terminals for which the acquiring bank has transmitted the full magnetic stripe data in the &lt;a title="Authorization Message" href="http://merchantprocessingservices.blogspot.com/2009/05/authorization-message.html" target="_self"&gt;authorization&lt;/a&gt; request message and for which an &lt;a title="Authorization Code" href="http://merchantprocessingservices.blogspot.com/2009/05/authorization-code.html" target="_self"&gt;authorization&lt;/a&gt; was obtained are ineligible for &lt;a title="Chargeback Manual" href="http://www.unibulmerchantservices.com/chargeback-manual" target="_self"&gt;chargeback&lt;/a&gt; reason code 4837, "No Cardholder Authorization."&lt;/li&gt;&lt;br /&gt;&lt;li&gt;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 &lt;a title="Authorization Response" href="http://merchantprocessingservices.blogspot.com/2009/05/authorization-response.html" target="_self"&gt;authorization&lt;/a&gt; is obtained, the acquiring bank is protected from authorization related &lt;a title="Chargeback Basics" href="http://merchantaccountprocessing.blogspot.com/2008/09/chargeback-basics.html" target="_self"&gt;chargebacks&lt;/a&gt; "requested / required authorization not obtained" (reason code 4808), or "exceeds &lt;a title="Floor Limit" href="http://paymentprocessingservices.blogspot.com/2008/07/floor-limit.html" target="_self"&gt;floor limit&lt;/a&gt;—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.&lt;/li&gt; &lt;li&gt;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.&lt;/li&gt;&lt;/ol&gt;&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Limited Amount Terminals / Level 3.&lt;/strong&gt;&lt;br /&gt; &lt;ol&gt;&lt;li&gt;A Limited Amount Terminal must check the account number against the Electronic Warning Bulletin file if the terminal has such a capacity.&lt;/li&gt; &lt;li&gt;The maximum transaction amount is $40 or its equivalent.&lt;/li&gt; &lt;li&gt;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.&lt;/li&gt; &lt;li&gt;A Limited Amount Terminal that also is a hybrid terminal is prohibited from performing fallback procedures from chip to magnetic stripe.&lt;/li&gt;&lt;/ol&gt;&lt;/li&gt;&lt;/ul&gt;&lt;!-- AddThis Button BEGIN --&gt;&lt;script type="text/javascript"&gt;&lt;!--     addthis_pub  = 'Merchant Account';     addthis_brand = 'Merchant Account';     addthis_options = 'favorites, email, digg, delicious, myspace, facebook, google, live, more'; // --&gt;&lt;/script&gt;&lt;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"&gt;&lt;img src="http://s9.addthis.com/button1-bm.gif" alt="" width="125" border="0" height="16" /&gt;&lt;/a&gt;&lt;script src="http://s7.addthis.com/js/152/addthis_widget.js" type="text/javascript"&gt;&lt;/script&gt;&lt;br /&gt;&lt;!-- AddThis Button END --&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8887473741874669103-8340577185563953058?l=merchantaccountprocessing.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://merchantaccountprocessing.blogspot.com/feeds/8340577185563953058/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2009/09/cardholder-activated-terminal-level.html#comment-form' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/8340577185563953058'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/8340577185563953058'/><link rel='alternate' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2009/09/cardholder-activated-terminal-level.html' title='Cardholder-Activated Terminal Level Requirements'/><author><name>mss</name><uri>http://www.blogger.com/profile/02682453100579738680</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8887473741874669103.post-6689535990679278080</id><published>2009-09-09T14:57:00.002-04:00</published><updated>2009-09-09T15:13:34.756-04:00</updated><title type='text'>General Acceptance Requirements for Cardholder-Activated Terminal (CAT)</title><content type='html'>The following general card acceptance requirements apply to &lt;a title="Cardholder-Activated Terminal (CAT)" href="http://merchantaccountprocessing.blogspot.com/2009/09/cardholder-activated-terminal-cat.html" target="_self"&gt;cardholder-activated terminals&lt;/a&gt;:&lt;br /&gt; &lt;ul&gt;&lt;li&gt;All &lt;a title="Card-Not-Present" href="http://merchantprocessingservices.blogspot.com/2008/11/card-not-present.html" target="_self"&gt;card-not-present&lt;/a&gt; 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 &lt;a title="Authorization Message" href="http://merchantprocessingservices.blogspot.com/2009/05/authorization-message.html" target="_self"&gt;authorization message&lt;/a&gt; and clearing records. Depending on the CAT level indicator, other specific data is required for &lt;a title="Authorization" href="http://merchantprocessingservices.blogspot.com/2008/11/authorization.html" target="_self"&gt;authorization&lt;/a&gt; and clearing.&lt;br /&gt; &lt;ul&gt;&lt;li&gt;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).&lt;/li&gt; &lt;li&gt;Messages used at the CAT must communicate to the cardholder, at a minimum, the following:&lt;br /&gt; &lt;ul&gt;&lt;li&gt;Invalid transaction.&lt;/li&gt; &lt;li&gt;Unable to route.&lt;/li&gt; &lt;li&gt;Invalid PIN—re-enter (Level 1 only).&lt;/li&gt; &lt;li&gt;Capture card (subject to the terminal's ability to retain cards).&lt;/li&gt;&lt;/ul&gt;&lt;/li&gt; &lt;li&gt;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.&lt;/li&gt;&lt;/ul&gt;&lt;/li&gt; &lt;li&gt;The acquiring bank must ensure that the description of goods or services on the CAT TID is clearly recognizable to the cardholder.&lt;/li&gt; &lt;li&gt;The acquiring bank is responsible for providing requested transaction information documents.&lt;/li&gt; &lt;li&gt;No cardholder-activated terminal may accept a card for the purchase of scrip.&lt;/li&gt; &lt;li&gt;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.&lt;/li&gt;&lt;/ul&gt;&lt;!-- AddThis Button BEGIN --&gt;&lt;script type="text/javascript"&gt;&lt;!--     addthis_pub  = 'Merchant Account';     addthis_brand = 'Merchant Account';     addthis_options = 'favorites, email, digg, delicious, myspace, facebook, google, live, more'; // --&gt;&lt;/script&gt;&lt;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"&gt;&lt;img src="http://s9.addthis.com/button1-bm.gif" alt="" width="125" border="0" height="16" /&gt;&lt;/a&gt;&lt;script src="http://s7.addthis.com/js/152/addthis_widget.js" type="text/javascript"&gt;&lt;/script&gt;&lt;br /&gt;&lt;!-- AddThis Button END --&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8887473741874669103-6689535990679278080?l=merchantaccountprocessing.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://merchantaccountprocessing.blogspot.com/feeds/6689535990679278080/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2009/09/general-acceptance-requirements-for.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/6689535990679278080'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/6689535990679278080'/><link rel='alternate' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2009/09/general-acceptance-requirements-for.html' title='General Acceptance Requirements for Cardholder-Activated Terminal (CAT)'/><author><name>mss</name><uri>http://www.blogger.com/profile/02682453100579738680</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8887473741874669103.post-833904473828060337</id><published>2009-09-08T17:16:00.000-04:00</published><updated>2009-09-08T17:17:28.861-04:00</updated><title type='text'>Cardholder-Activated Terminal (CAT)</title><content type='html'>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:&lt;br /&gt;   &lt;ul&gt;&lt;li&gt;Automated Dispensing Machines / Level 1.&lt;/li&gt;    &lt;li&gt;Self-Service Terminals / Level 2.&lt;/li&gt;    &lt;li&gt;Limited Amount Terminals / Level 3.&lt;/li&gt;    &lt;li&gt;In-flight Commerce (IFC) Terminals / Level 4.&lt;/li&gt;&lt;/ul&gt;Cardholder-activated terminal requirements specify the maximum allowed dollar amount of transactions as well as authorization, clearing, &lt;a title="Chargeback Manual" href="http://www.unibulmerchantservices.com/chargeback-manual" target="_self"&gt;chargeback&lt;/a&gt;, and addendum record requirements and related transaction liability for each cardholder-activated terminal type.&lt;br /&gt;&lt;br /&gt;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.&lt;br /&gt;&lt;br /&gt;&lt;a title="MasterCard Merchant Services" href="http://www.unibulmerchantservices.com/mastercard-merchant-services" target="_self"&gt;MasterCard&lt;/a&gt; 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, &lt;a title="MasterCard Merchant Account" href="http://www.unibulmerchantservices.com/mastercard-merchant-account" target="_self"&gt;MasterCard&lt;/a&gt; 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.&lt;br /&gt;&lt;br /&gt;&lt;!-- AddThis Button BEGIN --&gt;&lt;script type="text/javascript"&gt;&lt;!--     addthis_pub  = 'Merchant Account';     addthis_brand = 'Merchant Account';     addthis_options = 'favorites, email, digg, delicious, myspace, facebook, google, live, more'; // --&gt;&lt;/script&gt;&lt;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"&gt;&lt;img src="http://s9.addthis.com/button1-bm.gif" alt="" width="125" border="0" height="16" /&gt;&lt;/a&gt;&lt;script src="http://s7.addthis.com/js/152/addthis_widget.js" type="text/javascript"&gt;&lt;/script&gt;&lt;br /&gt;&lt;!-- AddThis Button END --&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8887473741874669103-833904473828060337?l=merchantaccountprocessing.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://merchantaccountprocessing.blogspot.com/feeds/833904473828060337/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2009/09/cardholder-activated-terminal-cat.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/833904473828060337'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/833904473828060337'/><link rel='alternate' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2009/09/cardholder-activated-terminal-cat.html' title='Cardholder-Activated Terminal (CAT)'/><author><name>mss</name><uri>http://www.blogger.com/profile/02682453100579738680</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8887473741874669103.post-8683872118317687302</id><published>2009-09-04T16:46:00.003-04:00</published><updated>2009-09-04T16:49:41.368-04:00</updated><title type='text'>Unique Transaction Requirements</title><content type='html'>Unique transactions are subject to standards governing retail sales transactions except as otherwise provided here.&lt;br /&gt;   &lt;ul&gt;&lt;li&gt;The &lt;a title="Floor Limit" href="http://paymentprocessingservices.blogspot.com/2008/07/floor-limit.html" target="_self"&gt;floor limit&lt;/a&gt; for all unique transactions must be zero.&lt;/li&gt;    &lt;li&gt;With the exception of truck stop transactions and of card-read transactions where a non-signature &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_0"&gt;CVM&lt;/span&gt; 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).&lt;br /&gt;&lt;br /&gt;Acquiring banks should ensure that their merchants shall, to the extent allowed by applicable law, record on the face of the sales receipt:&lt;br /&gt;&lt;ul&gt;&lt;br /&gt;   &lt;li&gt;A description of the identification.&lt;/li&gt;    &lt;li&gt;Any serial number, expiration date, and jurisdiction of issue.&lt;/li&gt;    &lt;li&gt;The name of the customer (if not the same as the embossed name).&lt;/li&gt;    &lt;li&gt;The address of the customer.&lt;/li&gt;&lt;/ul&gt;&lt;br /&gt;Except for card-read transactions where a non-signature &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_1"&gt;CVM&lt;/span&gt; is used, to ensure that the cardholder's signature compares positively, the signature on the card must be compared to both of the following:&lt;br /&gt;&lt;ul&gt;&lt;br /&gt;   &lt;li&gt;The cardholder's signature on the identification presented.&lt;/li&gt;    &lt;li&gt;The cardholder's signature on the merchant receipt.&lt;/li&gt;&lt;/ul&gt;&lt;br /&gt;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.&lt;/li&gt;&lt;br /&gt;   &lt;li&gt;&lt;a title="Authorization" href="http://merchantprocessingservices.blogspot.com/2008/11/authorization.html" target="_self"&gt;Authorization&lt;/a&gt; requests and clearing messages must identify the transactions as unique.&lt;/li&gt;&lt;/ul&gt;&lt;!-- AddThis Button BEGIN --&gt;&lt;script type="text/javascript"&gt;&lt;!--     addthis_pub  = 'Merchant Account';     addthis_brand = 'Merchant Account';     addthis_options = 'favorites, email, digg, delicious, myspace, facebook, twitter, google, live, more'; // --&gt;&lt;/script&gt;&lt;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"&gt;&lt;img src="http://s9.addthis.com/button1-bm.gif" alt="" width="125" border="0" height="16" /&gt;&lt;/a&gt;&lt;script src="http://s7.addthis.com/js/152/addthis_widget.js" type="text/javascript"&gt;&lt;/script&gt;&lt;br /&gt;&lt;!-- AddThis Button END --&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8887473741874669103-8683872118317687302?l=merchantaccountprocessing.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://merchantaccountprocessing.blogspot.com/feeds/8683872118317687302/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2009/09/unique-transaction-requirements.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/8683872118317687302'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/8683872118317687302'/><link rel='alternate' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2009/09/unique-transaction-requirements.html' title='Unique Transaction Requirements'/><author><name>mss</name><uri>http://www.blogger.com/profile/02682453100579738680</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8887473741874669103.post-7678581623183241318</id><published>2009-09-03T17:51:00.002-04:00</published><updated>2009-09-03T18:00:20.047-04:00</updated><title type='text'>Processing Procedures for Unique Transactions</title><content type='html'>At merchant locations processing unique transactions via a Point of Sale (POS) terminal, acquiring banks must incorporate the following requirement into merchant agreements with gambling merchants and ensure compliance:&lt;br /&gt;&lt;br /&gt;"A merchant must not credit winnings, unspent chips, or other value usable for gambling to a cardholder account."&lt;br /&gt;&lt;br /&gt;Acquiring banks must properly identify all unique transactions in all authorization and clearing messages. In addition, acquirers must ensure that electronic commerce transactions are properly identified in the authorization and clearing messages.&lt;br /&gt;&lt;br /&gt;Acquiring banks must incorporate the following requirements into all merchant agreements with internet casino merchants:&lt;br /&gt; &lt;ul&gt;&lt;li&gt;Internet casino merchants must request that cardholders identify the state or foreign country where they are physically located at the time of the transaction. They must record the response and retain it, along with the cardholder's account number, the transaction amount, and the date. Internet casino merchants must retain this information for a minimum of one year from the transaction date and provide it to the acquirer on request.&lt;/li&gt;   &lt;li&gt;As a condition of having a merchant account, internet casino merchants must post a notice on their websites (in a position such that the notice will be displayed before requesting a card account number, such as a click-through notice) stating that assertions have been made that internet gambling may not be lawful in some jurisdictions, including California, and suggesting that the cardholder check whether internet gambling is lawful under applicable law.&lt;/li&gt;   &lt;li&gt;Internet casino merchants must not sell chips or other value that can be used, directly or indirectly, to gamble other than at a merchant that sells such chips or other value.&lt;/li&gt;   &lt;li&gt;Internet casino merchants must not credit winnings or unspent chips or other value usable for gambling to a cardholder account.&lt;/li&gt;&lt;/ul&gt;&lt;!-- AddThis Button BEGIN --&gt;&lt;script type="text/javascript"&gt;&lt;!--     addthis_pub  = 'Merchant Account';     addthis_brand = 'Merchant Account';     addthis_options = 'favorites, email, digg, delicious, myspace, facebook, twitter, google, live, more'; // --&gt;&lt;/script&gt;&lt;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"&gt;&lt;img src="http://s9.addthis.com/button1-bm.gif" alt="" width="125" border="0" height="16" /&gt;&lt;/a&gt;&lt;script src="http://s7.addthis.com/js/152/addthis_widget.js" type="text/javascript"&gt;&lt;/script&gt;&lt;br /&gt;&lt;!-- AddThis Button END --&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8887473741874669103-7678581623183241318?l=merchantaccountprocessing.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://merchantaccountprocessing.blogspot.com/feeds/7678581623183241318/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2009/09/processing-procedures-for-card-not.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/7678581623183241318'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/7678581623183241318'/><link rel='alternate' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2009/09/processing-procedures-for-card-not.html' title='Processing Procedures for Unique Transactions'/><author><name>mss</name><uri>http://www.blogger.com/profile/02682453100579738680</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8887473741874669103.post-6279292985518484245</id><published>2009-09-02T16:32:00.002-04:00</published><updated>2009-09-02T16:49:06.517-04:00</updated><title type='text'>Advance Resort Deposit</title><content type='html'>If a hotel, motel, or resort is participating in the Advance Resort Deposit service for all cards, the following procedures will apply:&lt;br /&gt;  &lt;ol&gt;&lt;li&gt;If a cardholder calls a participating merchant wishing to make an advance deposit with his or her card, the merchant explains the terms of the reservation, cancellation, and refund policy procedure to the cardholder.&lt;/li&gt;    &lt;li&gt;The merchant takes the cardholder's account number, card expiration date, name, and address and confirms the room rate and location.&lt;/li&gt;    &lt;li&gt;The merchant is required to confirm the status of the card. The &lt;a title="Authorization" href="http://merchantprocessingservices.blogspot.com/2008/11/authorization.html" target="_self"&gt;authorization&lt;/a&gt; procedure is determined by the location (region) of the lodging facility. The applicable procedure follows.&lt;br /&gt;  &lt;ul&gt;&lt;li&gt;If located within the U.S. region, the merchant is required to follow the appropriate &lt;a title="Authorization Response" href="http://merchantprocessingservices.blogspot.com/2009/05/authorization-response.html" target="_self"&gt;authorization&lt;/a&gt; procedures to obtain approval for the transaction. If &lt;a title="Authorization Message" href="http://merchantprocessingservices.blogspot.com/2009/05/authorization-message.html" target="_self"&gt;authorization&lt;/a&gt; is not obtained, the merchant accepts responsibility for the transaction.&lt;/li&gt;    &lt;li&gt;For all regions other than the U.S., the merchant is required to check the Warning Notice. (This may be done subsequent to the phone call.) If the account number is listed in the Warning Notice, the merchant should follow the usual procedures provided by the acquiring bank.&lt;/li&gt;&lt;/ul&gt;&lt;br /&gt;The merchant is required to call for &lt;a title="Authorization Code" href="http://merchantprocessingservices.blogspot.com/2009/05/authorization-code.html" target="_self"&gt;authorization&lt;/a&gt; if the amount of the advance deposit exceeds $50. If the result of the authorization call is denial, the merchant must advise the cardholder.&lt;/li&gt;&lt;br /&gt;  &lt;li&gt;The merchant completes a sales ticket filling in the cardholder's name, card account number, card expiration date, reservation confirmation number, and merchant identification and writes the words "advance deposit" in place of the cardholder's signature. It is recommended that the merchant note on the sales ticket any special terms and conditions regarding its refund policy.&lt;/li&gt;    &lt;li&gt;The merchant mails a letter of confirmation, a copy of the sales ticket, including the reservation confirmation number, and information concerning its cancellation and refund policy to the cardholder at the address previously provided.&lt;/li&gt;    &lt;li&gt;The merchant deposits the sales ticket for the advance deposit in the usual manner. There are no special deposit requirements imposed on the merchant.&lt;/li&gt;    &lt;li&gt;If a cardholder cancels his or her reservation in accordance with the agreed upon procedures, the merchant is obligated to cancel the reservation and issue a credit to the cardholder.&lt;br /&gt;  &lt;ul&gt;&lt;li&gt;The merchant prepares a credit slip in the usual manner for the amount of the previously-submitted advance deposit, writing the words "deposit cancellation" in place of the cardholder's signature on the credit slip.&lt;/li&gt;    &lt;li&gt;The merchant prepares a notice of cancellation issuing a cancellation number to the cardholder.&lt;/li&gt;    &lt;li&gt;The merchant mails a copy of the credit slip and notice of cancellation to the cardholder.&lt;/li&gt;    &lt;li&gt;The merchant records the cancellation number on the slip and deposits the credit slip in the usual manner. There are no special deposit requirements imposed on the merchant.&lt;/li&gt;&lt;/ul&gt;&lt;/li&gt;    &lt;li&gt;If the transaction results in a dispute, and if the account number used to make the deposit is unidentifiable as to a specific card issuer or was fictitious, the bearer of the liability will be the acquiring bank. Where the transaction is identifiable to a specific card issuer but is not identifiable to a specific account number within that institution, the bearer of the liability will again be the acquiring bank.&lt;/li&gt;&lt;/ol&gt;&lt;!-- AddThis Button BEGIN --&gt;&lt;script type="text/javascript"&gt;&lt;!--     addthis_pub  = 'Merchant Account';     addthis_brand = 'Merchant Account';     addthis_options = 'favorites, email, digg, delicious, twitter, myspace, facebook, google, live, more'; // --&gt;&lt;/script&gt; &lt;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"&gt;&lt;img src="http://s9.addthis.com/button1-bm.gif" alt="" width="125" border="0" height="16" /&gt;&lt;/a&gt;&lt;script src="http://s7.addthis.com/js/152/addthis_widget.js" type="text/javascript"&gt;&lt;/script&gt;&lt;br /&gt;&lt;!-- AddThis Button END --&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8887473741874669103-6279292985518484245?l=merchantaccountprocessing.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://merchantaccountprocessing.blogspot.com/feeds/6279292985518484245/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2009/09/advance-resort-deposit.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/6279292985518484245'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/6279292985518484245'/><link rel='alternate' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2009/09/advance-resort-deposit.html' title='Advance Resort Deposit'/><author><name>mss</name><uri>http://www.blogger.com/profile/02682453100579738680</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8887473741874669103.post-3419234984072584770</id><published>2009-08-31T16:51:00.000-04:00</published><updated>2009-08-31T16:53:50.462-04:00</updated><title type='text'>Express Checkout Guidelines</title><content type='html'>If a merchant is participating in the Express Checkout service, the merchant must comply with the following requirements:&lt;br /&gt;   &lt;ol&gt;&lt;li&gt;At the time of check-in, inquire whether the cardholder would like to use the Express Checkout service or routinely provide the necessary form (Express Checkout Authorization Form) in its "welcome package."&lt;/li&gt;    &lt;li&gt;Have the cardholder complete and sign the Express Checkout Authorization Form. It is recommended that the Express Checkout Authorization Form at the very least include the name, address, and phone number of the merchant for the cardholder's name, address, room number, cardholder signature, and account number that may optionally be imprinted. The form should state clearly that the cardholder directs the merchant to charge his or her account number for his or her bill and process his or her sales ticket without a cardholder signature.&lt;/li&gt;    &lt;li&gt;Imprint a sales ticket with the cardholder's account number, and follow its normal &lt;a title="Authorization" href="http://merchantprocessingservices.blogspot.com/2008/11/authorization.html" target="_self"&gt;authorization&lt;/a&gt; procedures. The "pre-authorized order" &lt;a title="Floor Limit" href="http://paymentprocessingservices.blogspot.com/2008/07/floor-limit.html" target="_self"&gt;floor limit&lt;/a&gt; of $50 does not apply.&lt;/li&gt;    &lt;li&gt;On the cardholder's departure the merchant should complete the sales ticket, indicating the total amount of the bill, and print legibly in the space allotted for the customer's signature the words "signature on file - express checkout."&lt;/li&gt;    &lt;li&gt;Process the sales ticket in the usual manner. There are no special deposit requirements imposed on the merchant outlet.&lt;/li&gt;    &lt;li&gt;Mail a copy of the itemized bill, sales ticket, and the Express Checkout Authorization Form to the cardholder at the address noted on the authorization form within three business days after the cardholder checks out.&lt;/li&gt;    &lt;li&gt;Retain and make available to the card issuer all records pertaining to the itemized bill and &lt;a title="Authorization Response" href="http://merchantprocessingservices.blogspot.com/2009/05/authorization-response.html" target="_self"&gt;authorization&lt;/a&gt; requests in the event of a dispute.&lt;/li&gt;&lt;/ol&gt;&lt;!-- AddThis Button BEGIN --&gt;&lt;script type="text/javascript"&gt;&lt;!--     addthis_pub  = 'Merchant Account';     addthis_brand = 'Merchant Account';     addthis_options = 'favorites, email, digg, delicious, twitter, myspace, facebook, google, live, more'; // --&gt;&lt;/script&gt; &lt;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"&gt;&lt;img src="http://s9.addthis.com/button1-bm.gif" alt="" width="125" border="0" height="16" /&gt;&lt;/a&gt;&lt;script src="http://s7.addthis.com/js/152/addthis_widget.js" type="text/javascript"&gt;&lt;/script&gt;&lt;br /&gt;&lt;!-- AddThis Button END --&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8887473741874669103-3419234984072584770?l=merchantaccountprocessing.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://merchantaccountprocessing.blogspot.com/feeds/3419234984072584770/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2009/08/express-checkout-guidelines.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/3419234984072584770'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/3419234984072584770'/><link rel='alternate' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2009/08/express-checkout-guidelines.html' title='Express Checkout Guidelines'/><author><name>mss</name><uri>http://www.blogger.com/profile/02682453100579738680</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8887473741874669103.post-5402509447959973051</id><published>2009-08-28T16:32:00.001-04:00</published><updated>2009-08-28T16:54:05.444-04:00</updated><title type='text'>MasterCard Guaranteed Reservations</title><content type='html'>If a hotel, motel, or resort is participating in the &lt;a title="MasterCard Merchant Account" href="http://www.unibulmerchantservices.com/mastercard-merchant-account/" target="_self"&gt;MasterCard&lt;/a&gt; Guaranteed Reservations service for all &lt;a title="MasterCard Merchant Services" href="http://www.unibulmerchantservices.com/mastercard-merchant-services/" target="_self"&gt;MasterCard&lt;/a&gt; cardholders, the hotel, motel, or resort is obligated to have a room available when the cardholder arrives (until checkout time the next day). The cardholder is obligated to cancel a confirmed reservation before 18:00 at the hotel, motel, or resort (merchant's local time). Failure to do this will allow the hotel, motel, or resort to charge the cardholder a no-show charge equal to one night's lodging. The following procedure will prevail:&lt;br /&gt;   &lt;ol&gt;&lt;li&gt;If a cardholder calls a participating merchant and wants to guarantee a room with his or her card, the reservation clerk explains the terms of the &lt;a title="MasterCard Account Data Compromise Events" href="http://paymentprocessingservices.blogspot.com/2009/08/mastercard-account-data-compromise.html" target="_self"&gt;MasterCard&lt;/a&gt; Guaranteed Reservations service, specifically including the fact that an authorization check will be made at the time of arrival and the cancellation procedure the cardholder must follow to avoid being charged a no show charge equal to one night’s lodging.&lt;/li&gt;    &lt;li&gt;The clerk takes the cardholder's account number, card expiration date, name embossed on the card, and address; confirms the room rate and location; issues the cardholder a reservation confirmation number; and advises the cardholder to retain it. It is recommended that the merchant also confirm that guaranteed reservation in writing, advising the cardholder of his or her confirmation number and cancellation procedures.&lt;/li&gt;    &lt;li&gt;If a cardholder who has guaranteed his or her reservation by use of his or her card calls the merchant to cancel the reservation within the agreed upon period, the hotel, motel, or resort is obligated to cancel the guaranteed reservation and issue the cardholder a cancellation number that is verification that the reservation has been canceled. The cardholder should be advised to retain the cancellation number. It is also recommended that the merchant confirm the cancellation in writing advising the cardholder of the cancellation number.&lt;/li&gt;    &lt;li&gt;If a cardholder who has guaranteed a reservation by use of his or her card arrives within the specified period (until checkout time the next day), the merchant is obligated to provide a room. If the merchant is unable to provide a room, it is obligated to provide at no additional charge a comparable room for one night, transportation to the other lodging and a three-minute domestic or long distance phone call, whichever the cardholder deems necessary to advise of a change of location.&lt;/li&gt;    &lt;li&gt;Before the cardholder's expected arrival, the merchant must prepare a registration card and assign a room number on that card.&lt;/li&gt;    &lt;li&gt;If the cardholder does not cancel and does not stay at the hotel, motel, or resort, the merchant may bill the cardholder for one night's room rate. The following procedure should be followed:&lt;br /&gt;   &lt;ul&gt;&lt;li&gt;The merchant completes a sales ticket filling in the cardholder's name, card account number, expiration date, date of no show, assigned room number and merchant identification, and writes the words "guaranteed reservation / no-show" in place of the cardholder's signature.&lt;/li&gt;    &lt;li&gt;Follow your usual authorization procedures.&lt;/li&gt;    &lt;li&gt;Assuming the account is not on the Warning Notice (or the Electronic Warning Bulletin file in the United States), if under the &lt;a title="Floor Limit" href="http://paymentprocessingservices.blogspot.com/2008/07/floor-limit.html" target="_self"&gt;floor limit&lt;/a&gt;, or &lt;a title="Authorization" href="http://merchantprocessingservices.blogspot.com/2008/11/authorization.html" target="_self"&gt;authorization&lt;/a&gt; has been given, the merchant deposits the no-show charge in the usual manner. There are no special deposit requirements imposed on the merchant outlet.&lt;/li&gt;    &lt;li&gt;The actual no-show registration card, reflecting the assigned room number, must be retained six months from the date the sales ticket is deposited.&lt;/li&gt;&lt;/ul&gt;&lt;/li&gt;    &lt;li&gt;Where the account number used to guarantee the transaction that results in a no show was unidentifiable as to a specific card issuer or was fictitious, the bearer of the liability will be the acquiring bank.&lt;/li&gt;    &lt;li&gt;Where the transaction is identifiable to a specific card issuer but is not identifiable to a specific account number within that institution, the bearer of the liability will be the acquiring bank.&lt;/li&gt;    &lt;li&gt;&lt;a title="MasterCard Data Protection Standards" href="http://paymentprocessingservices.blogspot.com/2009/08/mastercard-data-protection-standards.html" target="_self"&gt;MasterCard&lt;/a&gt; reserves the right to prevent the acquiring bank from allowing a specific hotel, motel, or resort to participate in the &lt;a title="General MasterCard Monitoring Requirements" href="http://paymentprocessingservices.blogspot.com/2009/06/general-mastercard-monitoring.html" target="_self"&gt;MasterCard&lt;/a&gt; Guaranteed Reservations service where the hotel, motel, or resort has been abusing the privilege.&lt;/li&gt;&lt;/ol&gt;&lt;!-- AddThis Button BEGIN --&gt;&lt;script type="text/javascript"&gt;&lt;!--     addthis_pub  = 'Merchant Account';     addthis_brand = 'Merchant Account';     addthis_options = 'favorites, email, digg, delicious, myspace, facebook, twitter, google, live, more'; // --&gt;&lt;/script&gt;&lt;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"&gt;&lt;img src="http://s9.addthis.com/button1-bm.gif" alt="" border="0" height="16" width="125" /&gt;&lt;/a&gt;&lt;script src="http://s7.addthis.com/js/152/addthis_widget.js" type="text/javascript"&gt;&lt;/script&gt;&lt;br /&gt;&lt;!-- AddThis Button END --&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8887473741874669103-5402509447959973051?l=merchantaccountprocessing.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://merchantaccountprocessing.blogspot.com/feeds/5402509447959973051/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2009/08/mastercard-guaranteed-reservations.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/5402509447959973051'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/5402509447959973051'/><link rel='alternate' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2009/08/mastercard-guaranteed-reservations.html' title='MasterCard Guaranteed Reservations'/><author><name>mss</name><uri>http://www.blogger.com/profile/02682453100579738680</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8887473741874669103.post-6481599806621253444</id><published>2009-08-27T16:41:00.001-04:00</published><updated>2009-08-27T16:43:01.256-04:00</updated><title type='text'>Returned Merchandise, Adjustments, Credits and Other Specific Terms of a Transaction</title><content type='html'>The following requirements concern returned merchandise, adjustments, credits and other specific terms of a transaction.&lt;br /&gt;   &lt;ul&gt;&lt;li&gt;&lt;strong&gt;Merchant disclosure of specific transaction terms.&lt;/strong&gt; The merchant may impose specific terms governing a transaction. In the event of a dispute, such specific terms will be given effect, provided that such specific terms were disclosed to and accepted by the cardholder before completion of the transaction. The merchant may impose specific transaction terms by, for example, printing the specific terms on the invoice or sales receipt in close proximity to the cardholder signature line before presenting the invoice or sales receipt to the cardholder for signature. Specific transaction terms also may be disclosed by other means, such as by signage or literature, provided the disclosure is sufficiently prominent and clear so that a reasonable person would be aware of and understand the disclosure before the transaction is completed.Specific transaction terms may include, for example, such words as "Exchange Only," "In-Store Credit Only" or "Original Packaging Required for Returns." Specific terms may address such matters as late delivery, delivery charges, or insurance charges.&lt;/li&gt;    &lt;li&gt;&lt;strong&gt;Returned merchandise and canceled services.&lt;/strong&gt; A merchant is not required to accept returned merchandise or the cancellation of services unless a right of return or cancellation was a condition of the transaction. If the merchant agrees to accept merchandise for return or to cancel services, the merchant must credit the same account used to purchase the merchandise or service.If the merchandise or service is purchased with a card, upon a partial or entire return of merchandise or cancellation of service, or if the merchant agrees to a price adjustment, the merchant may not provide a full or partial refund or adjustment by cash or check or by any means other than by a credit to the card account used to purchase the merchandise or service. The cardholder must be provided a copy of the credit receipt. A cash or check refund is permitted for involuntary refunds by airlines or other carriers or merchants only when required by law.&lt;br /&gt;   &lt;ul&gt;&lt;li&gt;Credit receipt requirements. The credit receipt must contain the following information:&lt;br /&gt;   &lt;ul&gt;&lt;li&gt;The date.&lt;/li&gt;    &lt;li&gt;A description of the returned merchandise, canceled services or adjustment made.&lt;/li&gt;    &lt;li&gt;The amount of the credit.&lt;/li&gt;    &lt;li&gt;The merchant's signature.&lt;/li&gt;&lt;/ul&gt;&lt;/li&gt;&lt;/ul&gt;&lt;/li&gt;&lt;/ul&gt;&lt;!-- AddThis Button BEGIN --&gt;&lt;script type="text/javascript"&gt;&lt;!--     addthis_pub  = 'Merchant Account';     addthis_brand = 'Merchant Account';     addthis_options = 'favorites, email, digg, delicious, twitter, myspace, facebook, google, live, more'; // --&gt;&lt;/script&gt; &lt;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"&gt;&lt;img src="http://s9.addthis.com/button1-bm.gif" alt="" border="0" height="16" width="125" /&gt;&lt;/a&gt;&lt;script src="http://s7.addthis.com/js/152/addthis_widget.js" type="text/javascript"&gt;&lt;/script&gt;&lt;br /&gt;&lt;!-- AddThis Button END --&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8887473741874669103-6481599806621253444?l=merchantaccountprocessing.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://merchantaccountprocessing.blogspot.com/feeds/6481599806621253444/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2009/08/returned-merchandise-adjustments.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/6481599806621253444'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/6481599806621253444'/><link rel='alternate' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2009/08/returned-merchandise-adjustments.html' title='Returned Merchandise, Adjustments, Credits and Other Specific Terms of a Transaction'/><author><name>mss</name><uri>http://www.blogger.com/profile/02682453100579738680</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8887473741874669103.post-6233554722600151444</id><published>2009-08-26T16:27:00.002-04:00</published><updated>2009-08-26T16:47:06.358-04:00</updated><title type='text'>Multiple Sales Receipts and Partial Payment</title><content type='html'>Following are requirements concerning multiple sales receipts and partial payments:&lt;br /&gt;  &lt;ul&gt;&lt;li&gt;&lt;strong&gt;Split tickets are prohibited.&lt;/strong&gt; A merchant is prohibited from using two or more sales receipts, also known as a split ticket, to avoid an &lt;a title="Authorization" href="http://merchantprocessingservices.blogspot.com/2008/11/authorization.html" target="_self"&gt;authorization&lt;/a&gt; request.&lt;/li&gt;   &lt;li&gt;&lt;strong&gt;Include all goods on a single sales receipts.&lt;/strong&gt; All products and services purchased in a single transaction must be included in one total amount on a single sales receipt except in the following instances:&lt;br /&gt;  &lt;ul&gt;&lt;li&gt;Multiple cards are presented. More than one card is presented for payment on a single transaction, and an &lt;a title="Authorization Response" href="http://merchantprocessingservices.blogspot.com/2009/05/authorization-response.html" target="_self"&gt;authorization&lt;/a&gt; is obtained for the portion of the transaction charged to a each card.&lt;/li&gt;   &lt;li&gt;Multiple items are billed. Multiple items are purchased and individually billed to the same account, and an &lt;a title="Authorization Message" href="http://merchantprocessingservices.blogspot.com/2009/05/authorization-message.html" target="_self"&gt;authorization&lt;/a&gt; is obtained for each item purchased.&lt;/li&gt;   &lt;li&gt;Partial payment. A merchant is prohibited from processing a card transaction where only a part of the total amount is included on a single sales receipt except in the following instances:&lt;br /&gt;  &lt;ul&gt;&lt;li&gt;When the cardholder bills a portion of the transaction amount to a card and pays the remaining balance by cash or check.&lt;/li&gt;   &lt;li&gt;When the products or services will be delivered or performed after the transaction date, one sales receipt represents a deposit, and the second sales receipt represents payment of the balance. The second sales receipt is conditioned upon the delivery or performance of the goods or services.&lt;/li&gt;&lt;/ul&gt;&lt;br /&gt;An &lt;a title="Authorization Code" href="http://merchantprocessingservices.blogspot.com/2009/05/authorization-code.html" target="_self"&gt;authorization&lt;/a&gt; must be obtained for the total amount of the transaction if it exceeds the applicable &lt;a title="Floor Limit" href="http://paymentprocessingservices.blogspot.com/2008/07/floor-limit.html" target="_self"&gt;floor limit&lt;/a&gt;. The merchant must note on the sales receipt the words "deposit" or "balance," as appropriate. The sales receipt representing the balance must not be presented until the products or services are delivered or performed.&lt;/li&gt;&lt;/ul&gt;&lt;/li&gt;&lt;/ul&gt;&lt;!-- AddThis Button BEGIN --&gt;&lt;script type="text/javascript"&gt;&lt;!--     addthis_pub  = 'Merchant Account';     addthis_brand = 'Merchant Account';     addthis_options = 'favorites, email, digg, delicious, twitter, myspace, facebook, google, live, more'; // --&gt;&lt;/script&gt; &lt;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"&gt;&lt;img src="http://s9.addthis.com/button1-bm.gif" alt="" border="0" height="16" width="125" /&gt;&lt;/a&gt;&lt;script src="http://s7.addthis.com/js/152/addthis_widget.js" type="text/javascript"&gt;&lt;/script&gt;&lt;br /&gt;&lt;!-- AddThis Button END --&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8887473741874669103-6233554722600151444?l=merchantaccountprocessing.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://merchantaccountprocessing.blogspot.com/feeds/6233554722600151444/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2009/08/multiple-sales-receipts-and-partial.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/6233554722600151444'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/6233554722600151444'/><link rel='alternate' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2009/08/multiple-sales-receipts-and-partial.html' title='Multiple Sales Receipts and Partial Payment'/><author><name>mss</name><uri>http://www.blogger.com/profile/02682453100579738680</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8887473741874669103.post-5342833205274814450</id><published>2009-08-20T16:30:00.004-04:00</published><updated>2009-08-25T18:12:38.508-04:00</updated><title type='text'>Completing the Sales Receipt</title><content type='html'>The following information and requirements are relevant to the completion of the sales receipt:&lt;br /&gt;&lt;ul&gt;&lt;li&gt;&lt;strong&gt;Include all goods on one sales receipt.&lt;/strong&gt; All goods and services purchased in the same transaction must be included on a single sales receipt.&lt;/li&gt;    &lt;li&gt;&lt;strong&gt;Sales receipt information requirements.&lt;/strong&gt; The following information must be included on the sales receipt.&lt;br /&gt;&lt;ul&gt;&lt;li&gt;A description of the goods. A description of the goods and services and their price, including applicable taxes, must be entered on the sales receipt in detail sufficient to identify the transaction. If no currency is identified on the sales receipt, the transaction is considered to have taken place in the currency that is legal tender at the point of interaction. If the merchant offers multiple currencies, then the sales receipt must indicate all of the following information:&lt;br /&gt;&lt;ul&gt;&lt;li&gt;The transaction amount in the merchant's local currency (the goods or services total).&lt;/li&gt;    &lt;li&gt;The converted transaction amount in the currency chosen and agreed to by the cardholder and the merchant (the sale total).&lt;/li&gt;    &lt;li&gt;The currency symbol of each.&lt;/li&gt;    &lt;li&gt;The method by which the currency agreed to by the cardholder was converted from the amount in the merchant's local currency.&lt;/li&gt;&lt;/ul&gt;&lt;/li&gt;    &lt;li&gt;The transaction date. The transaction date must be entered on the sales receipt.&lt;/li&gt;    &lt;li&gt;An imprint of the card. A legible imprint of the card must be made on the sales receipt, or the merchant may electronically record the customer's card information and the merchant location. If a transaction is completed without obtaining a card imprint or electronically derived card information, the merchant must note legibly on the sales receipt sufficient detail to identify the cardholder, the merchant, and the card issuer. This information must include at least the name and address of the merchant, the name or trade name of the card issuer as it appears on the face of the card, the account number, the security code, the expiration date (or dual date), the cardholder name, and any company name.If the transaction is completed without obtaining a card imprint or electronically derived card information, the merchant is considered to have verified the true identity of the customer as the cardholder, unless the merchant obtained and noted on the sales receipt independent evidence of the cardholder's true identity.&lt;br /&gt;&lt;br /&gt;Transactions based on mail orders, telephone orders, preauthorized orders, electronic commerce orders, Guaranteed Reservations and Advanced Resort Deposits may be completed without a card imprint.&lt;/li&gt;    &lt;li&gt;The authorization number. If an authorization is obtained from the card issuer, unless the transaction is an offline chip-read transaction, the authorization number must be entered on the sales receipt. If more than one authorization is obtained over the course of the transaction (as may occur for hotel, motel, or vehicle rental transactions), all authorization numbers, the amounts authorized, and the date of each authorization must be entered on the sales receipt.&lt;/li&gt;    &lt;li&gt;The primary account number. The primary account number (PAN) must be truncated on all cardholder-activated terminal sales receipts. Subject to local and national laws, PAN truncation is permitted on any other sales receipt type. It is recommended that only the last four digits of the PAN are printed on the receipt. Truncated digits should be replaced with fill characters such as "x," "*," or "#," and not with blank spaces or numeric characters.&lt;/li&gt;    &lt;li&gt;Delayed presentment. When the merchant receives approval for delayed presentment, the authorization number and the words "Delayed Presentment" must be noted legibly on the sales receipt.&lt;/li&gt;    &lt;li&gt;Cardholder identification. For unique transactions processed in a face-to-face environment (with the exception of truck stop transactions and card-read transactions where a non-signature CVM is used), the merchant must record on the sales receipt a description of the unexpired, official government document provided as identification by the cardholder, including any serial number, expiration date, jurisdiction of issue, customer name (if not the same name as embossed on the card), and customer address.&lt;/li&gt;    &lt;li&gt;The transaction certificate. The transaction certificate is not required on the sales receipt. However, if the acquiring bank elects to record the receipt of a transaction certificate on the sales receipt, then the merchant must enter the complete transaction certificate on the sales receipt.&lt;/li&gt;    &lt;li&gt;Prohibited information. The sales receipt or any other document must not reflect the following information:&lt;br /&gt;&lt;ul&gt;&lt;li&gt;The PIN, any part of the PIN, or any fill characters representing the PIN.&lt;/li&gt;    &lt;li&gt;The card security code (CVC2, CVV2 or CID), which is indent-printed on the signature panel of the card.&lt;/li&gt;&lt;/ul&gt;&lt;/li&gt;&lt;/ul&gt;&lt;/li&gt;&lt;li&gt;Obtain the cardholder's signature. In a face-to-face environment, the merchant must give the cardholder the option of a signature-based transaction. Unless the cardholder uses a PIN, the cardholder must sign the sales receipt.&lt;br /&gt;&lt;ul&gt;&lt;li&gt;Compare signatures. Unless the cardholder uses a PIN, the merchant must compare the signature on the sales receipt with the signature on the card to determine whether they appear to be the same.&lt;/li&gt; &lt;li&gt;Discrepancy between signatures. If the merchant believes that the signature on the card does not match the signature on the sales receipt, the merchant must contact the acquiring bank for instructions. The signature would not match if the signature panel were signed "John P. Smith" and the sales receipt "Stan Smith" or K. Smith." The signature would be acceptable if signed "John P. Smith," "J. P. Smith" or "John Smith." The signature would be acceptable if a title such as Mr., Mrs., or Dr. is missing or is included.&lt;/li&gt; &lt;li&gt;Signature not required. Transactions based on mail orders, telephone orders, preauthorized orders, electronic commerce orders, Guaranteed Reservations, Advanced Resort Deposits and Express Checkouts may be completed without the cardholder's signature. The merchant must type or legibly print on the signature line of the sales receipt the letters "TO", "MO", "PO", "EC", "Guaranteed Reservation / No Show," "Signature on File – Express Check-out," or "Advance Deposit" as appropriate. The merchant must retain and make available to the acquiring bank upon request the cardholder's written request to the merchant for preauthorization. The merchant must not deliver goods or perform services covered by a preauthorization after receiving notification that the preauthorization is canceled or that the card covered by the preauthorization is not to be honored.&lt;/li&gt;&lt;/ul&gt;&lt;/li&gt; &lt;li&gt;Give the cardholder a copy of the receipt. The merchant must provide the cardholder with a true and completed copy of the sales receipt.&lt;/li&gt;&lt;/ul&gt;&lt;!-- AddThis Button BEGIN --&gt;&lt;script type="text/javascript"&gt;&lt;!--     addthis_pub  = 'Merchant Account';     addthis_brand = 'Merchant Account';     addthis_options = 'favorites, email, digg, delicious, twitter, myspace, facebook, google, live, more'; // --&gt;&lt;/script&gt; &lt;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"&gt;&lt;img src="http://s9.addthis.com/button1-bm.gif" alt="" width="125" border="0" height="16" /&gt;&lt;/a&gt;&lt;script src="http://s7.addthis.com/js/152/addthis_widget.js" type="text/javascript"&gt;&lt;/script&gt;&lt;br /&gt;&lt;!-- AddThis Button END --&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8887473741874669103-5342833205274814450?l=merchantaccountprocessing.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://merchantaccountprocessing.blogspot.com/feeds/5342833205274814450/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2009/08/completing-sales-receipt.html#comment-form' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/5342833205274814450'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/5342833205274814450'/><link rel='alternate' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2009/08/completing-sales-receipt.html' title='Completing the Sales Receipt'/><author><name>mss</name><uri>http://www.blogger.com/profile/02682453100579738680</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8887473741874669103.post-8211023583794833349</id><published>2009-08-18T16:13:00.001-04:00</published><updated>2009-08-18T16:24:12.834-04:00</updated><title type='text'>Obtaining an Authorization when a Tip is Added</title><content type='html'>The following information and requirements are relevant to the merchant's obtaining of an &lt;a title="Authorization" href="http://merchantprocessingservices.blogspot.com/2008/11/authorization.html" target="_self"&gt;authorization&lt;/a&gt; when a tip is added, either before or after the &lt;a title="Authorization Response" href="http://merchantprocessingservices.blogspot.com/2009/05/authorization-response.html" target="_self"&gt;authorization&lt;/a&gt; process.&lt;br /&gt;   &lt;ul&gt;&lt;li&gt;If the transaction amount is below the merchant's &lt;a title="Floor Limit" href="http://paymentprocessingservices.blogspot.com/2008/07/floor-limit.html" target="_self"&gt;floor limit&lt;/a&gt;, and the cardholder adds a tip in an amount less than or equal to 20% of the transaction amount, the merchant is not required to obtain an &lt;a title="Authorization Message" href="http://merchantprocessingservices.blogspot.com/2009/05/authorization-message.html" target="_self"&gt;authorization&lt;/a&gt; even though the total transaction amount may exceed the merchant's floor limit.&lt;/li&gt;    &lt;li&gt;If a merchant obtained an &lt;a title="Authorization Code" href="http://merchantprocessingservices.blogspot.com/2009/05/authorization-code.html" target="_self"&gt;authorization&lt;/a&gt; for a transaction, and the cardholder adds a tip in an amount greater than 20% of the transaction amount, the merchant must obtain an &lt;a title="Voice Authorization" href="http://merchantprocessingservices.blogspot.com/2009/03/voice-authorization.html" target="_self"&gt;authorization&lt;/a&gt; for the additional amount. The card issuer is responsible for the full amount of the transaction.&lt;/li&gt;    &lt;li&gt;If the cardholder adds a tip in an amount greater than 20% of the transaction amount and causes the transaction amount to exceed the merchant's floor limit, the merchant must obtain an &lt;a title="Voice Authorization Center" href="http://merchantprocessingservices.blogspot.com/2009/03/voice-authorization-center.html" target="_self"&gt;authorization&lt;/a&gt; for the total amount of the transaction.&lt;/li&gt;&lt;/ul&gt;&lt;!-- AddThis Button BEGIN --&gt;&lt;script type="text/javascript"&gt;&lt;!--     addthis_pub  = 'Merchant Account';      addthis_brand = 'Merchant Account';      addthis_options = 'favorites, email, digg, delicious, twitter, myspace, facebook, google, live, more'; // --&gt;&lt;/script&gt; &lt;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"&gt;&lt;img src="http://s9.addthis.com/button1-bm.gif" alt="" width="125" border="0" height="16" /&gt;&lt;/a&gt;&lt;script src="http://s7.addthis.com/js/152/addthis_widget.js" type="text/javascript"&gt;&lt;/script&gt;&lt;br /&gt;&lt;!-- AddThis Button END --&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8887473741874669103-8211023583794833349?l=merchantaccountprocessing.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://merchantaccountprocessing.blogspot.com/feeds/8211023583794833349/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2009/08/obtaining-authorization-when-tip-is.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/8211023583794833349'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/8211023583794833349'/><link rel='alternate' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2009/08/obtaining-authorization-when-tip-is.html' title='Obtaining an Authorization when a Tip is Added'/><author><name>mss</name><uri>http://www.blogger.com/profile/02682453100579738680</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8887473741874669103.post-6650227224508520823</id><published>2009-08-17T17:12:00.002-04:00</published><updated>2009-08-18T16:12:56.096-04:00</updated><title type='text'>Completing a Transaction</title><content type='html'>When the transaction is completed (i.e., when customer checks out of the hotel / motel or returns the car) and the final transaction amount is determined, the following will apply:&lt;br /&gt;&lt;ul&gt;&lt;li&gt;If the final transaction amount does not exceed the merchant's &lt;a title="Floor Limit" href="http://paymentprocessingservices.blogspot.com/2008/07/floor-limit.html" target="_self"&gt;floor limit&lt;/a&gt;, the merchant is not required to obtain an &lt;a title="Authorization" href="http://merchantprocessingservices.blogspot.com/2008/11/authorization.html" target="_self"&gt;authorization&lt;/a&gt;, but it must check the account number against the international Warning Notice or the Electronic Warning Bulletin.&lt;/li&gt;  &lt;li&gt;If the final transaction amount does not exceed the merchant's estimated amount by 15%, the merchant is not required to request a secondary &lt;a title="Authorization Response" href="http://merchantprocessingservices.blogspot.com/2009/05/authorization-response.html" target="_self"&gt;authorization&lt;/a&gt;. The initial &lt;a title="Authorization Message" href="http://merchantprocessingservices.blogspot.com/2009/05/authorization-message.html" target="_self"&gt;authorization&lt;/a&gt; guarantees the full amount of the transaction.&lt;/li&gt;  &lt;li&gt;If the final transaction amount exceeds the merchant's estimated amount by 15%, the merchant must request a secondary &lt;a title="Authorization Code" href="http://merchantprocessingservices.blogspot.com/2009/05/authorization-code.html" target="_self"&gt;authorization&lt;/a&gt; on the additional amount.&lt;/li&gt;  &lt;li&gt;If the final transaction amount exceeds the merchant's applicable floor limit, but a previous &lt;a title="Voice Authorization" href="http://merchantprocessingservices.blogspot.com/2009/03/voice-authorization.html" target="_self"&gt;authorization&lt;/a&gt; was not received because the merchant's estimate did not exceed its applicable floor limit, the merchant must obtain an &lt;a title="Voice Authorization Center" href="http://merchantprocessingservices.blogspot.com/2009/03/voice-authorization-center.html" target="_self"&gt;authorization&lt;/a&gt; for the full amount of the transaction.&lt;/li&gt;&lt;/ul&gt;If the card issuer declines a subsequent authorization request, the merchant is guaranteed the cumulative amount of previous authorizations, plus 15%.&lt;br /&gt;&lt;br /&gt;If a pick-up-card response is received in response to a subsequent authorization request, the merchant must pick up the card. The merchant is guaranteed the cumulative amount of the previous authorizations, plus 15%.&lt;br /&gt;&lt;br /&gt;&lt;!-- AddThis Button BEGIN --&gt;&lt;script type="text/javascript"&gt;&lt;!--     addthis_pub  = 'Merchant Account';     addthis_brand = 'Merchant Account';     addthis_options = 'favorites, email, digg, delicious, twitter, myspace, facebook, google, live, more'; // --&gt;&lt;/script&gt; &lt;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"&gt;&lt;img src="http://s9.addthis.com/button1-bm.gif" alt="" width="125" border="0" height="16" /&gt;&lt;/a&gt;&lt;script src="http://s7.addthis.com/js/152/addthis_widget.js" type="text/javascript"&gt;&lt;/script&gt;&lt;br /&gt;&lt;!-- AddThis Button END --&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8887473741874669103-6650227224508520823?l=merchantaccountprocessing.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://merchantaccountprocessing.blogspot.com/feeds/6650227224508520823/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2009/08/completing-transaction.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/6650227224508520823'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/6650227224508520823'/><link rel='alternate' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2009/08/completing-transaction.html' title='Completing a Transaction'/><author><name>mss</name><uri>http://www.blogger.com/profile/02682453100579738680</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8887473741874669103.post-4285503251490221422</id><published>2009-08-14T16:18:00.002-04:00</published><updated>2009-08-14T16:40:33.071-04:00</updated><title type='text'>Obtaining an Authorization for Hotel, Cruise Line, and Car Rental Transactions</title><content type='html'>The following information and requirements are relevant to merchants obtaining &lt;a title="Authorization" href="http://merchantprocessingservices.blogspot.com/2008/11/authorization.html" target="_self"&gt;authorizations&lt;/a&gt; for hotel / motel, cruise line, and car rental transactions.&lt;br /&gt;  &lt;ul&gt;&lt;li&gt;&lt;strong&gt;Authorization procedures.&lt;/strong&gt; Hotel, motel, car rental, and cruise line merchants must comply with the standard &lt;a title="Authorization Code" href="http://merchantprocessingservices.blogspot.com/2009/05/authorization-code.html" target="_self"&gt;authorization&lt;/a&gt; procedures and the requirements set out below.&lt;br /&gt;  &lt;/li&gt;&lt;li&gt;&lt;strong&gt;Initiating the transaction.&lt;/strong&gt; When the transaction is initiated, the merchant must request an &lt;a title="Authorization Message" href="http://merchantprocessingservices.blogspot.com/2009/05/authorization-message.html" target="_self"&gt;authorization&lt;/a&gt; for an estimated transaction amount if the estimate exceeds the applicable &lt;a title="Floor Limit" href="http://paymentprocessingservices.blogspot.com/2008/07/floor-limit.html" target="_self"&gt;floor limit&lt;/a&gt;. The merchant also may request an &lt;a title="Authorization Response" href="http://merchantprocessingservices.blogspot.com/2009/05/authorization-response.html" target="_self"&gt;authorization&lt;/a&gt; for any additional estimated amounts as needed.Merchants engaging in car rental transactions may not include charges representing either:&lt;br /&gt;  &lt;ul&gt;&lt;li&gt;The vehicle insurance deductible amount, or&lt;br /&gt;  &lt;/li&gt;&lt;li&gt;An amount to cover potential damages when the cardholder waives insurance coverage at the time of the rental.&lt;/li&gt;&lt;br /&gt;Car rental merchants must disclose to the cardholder at the time of the rental the amount for which the &lt;a title="Voice Authorization" href="http://merchantprocessingservices.blogspot.com/2009/03/voice-authorization.html" target="_self"&gt;authorization&lt;/a&gt; was obtained.&lt;/ul&gt;&lt;br /&gt;Charges for damages must be processed as a separate transaction. The merchant must provide a reasonable estimate of the cost to repair the damages and obtain agreement from the cardholder. If the cardholder chooses to pay for the repairs using his or her card, the merchant must:&lt;br /&gt;&lt;ul&gt;&lt;br /&gt;  &lt;li&gt;Prepare a specific sales slip with proof of card presence.&lt;br /&gt;  &lt;/li&gt;&lt;li&gt;Provide the estimated amount for repairs indicating that the amount will be adjusted accordingly pursuant to completion of the repairs and submission of the invoice for such repairs.&lt;br /&gt;  &lt;/li&gt;&lt;li&gt;Obtain a signature from the cardholder.&lt;/li&gt;&lt;br /&gt;The final transaction amount may not exceed the merchant's estimated amount by more than 15% (or less, as directed by local ordinances). The merchant must submit a credit if the final cost of repairs is less than the estimated amount on the sales slip and has 30 days from the date of the subsequent transaction related to damages to submit the item into clearing.&lt;/ul&gt;&lt;/li&gt;&lt;/ul&gt;&lt;!-- AddThis Button BEGIN --&gt;&lt;script type="text/javascript"&gt;&lt;!--     addthis_pub  = 'Merchant Account';     addthis_brand = 'Merchant Account';     addthis_options = 'favorites, email, digg, delicious, twitter, myspace, facebook, google, live, more'; // --&gt;&lt;/script&gt; &lt;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"&gt;&lt;img src="http://s9.addthis.com/button1-bm.gif" alt="" border="0" height="16" width="125" /&gt;&lt;/a&gt;&lt;script src="http://s7.addthis.com/js/152/addthis_widget.js" type="text/javascript"&gt;&lt;/script&gt;&lt;br /&gt;&lt;!-- AddThis Button END --&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8887473741874669103-4285503251490221422?l=merchantaccountprocessing.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://merchantaccountprocessing.blogspot.com/feeds/4285503251490221422/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2009/08/obtaining-authorization-for-hotel.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/4285503251490221422'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/4285503251490221422'/><link rel='alternate' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2009/08/obtaining-authorization-for-hotel.html' title='Obtaining an Authorization for Hotel, Cruise Line, and Car Rental Transactions'/><author><name>mss</name><uri>http://www.blogger.com/profile/02682453100579738680</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8887473741874669103.post-1749114192784137303</id><published>2009-08-13T15:45:00.001-04:00</published><updated>2009-08-13T16:25:36.465-04:00</updated><title type='text'>Obtaining an Authorization</title><content type='html'>The following information and requirements are relevant to the merchant's obtaining of an &lt;a title="Authorization" href="http://merchantprocessingservices.blogspot.com/2008/11/authorization.html" target="_self"&gt;authorization&lt;/a&gt;.&lt;br /&gt;   &lt;ul&gt;&lt;li&gt;&lt;strong&gt;Treat all transactions the same.&lt;/strong&gt; With respect to obtaining &lt;a title="Voice Authorization Center" href="http://merchantprocessingservices.blogspot.com/2009/03/voice-authorization-center.html" target="_self"&gt;authorizations&lt;/a&gt; of transactions, the acquiring bank must treat all transactions at a merchant location in the same manner.&lt;br /&gt;   &lt;/li&gt;&lt;li&gt;&lt;strong&gt;Retain the card while obtaining authorization.&lt;/strong&gt; The merchant must use its best efforts, by reasonable and peaceful means, to retain the card while making an &lt;a title="Voice Authorization" href="http://merchantprocessingservices.blogspot.com/2009/03/voice-authorization.html" target="_self"&gt;authorization&lt;/a&gt; request.&lt;br /&gt;   &lt;/li&gt;&lt;li&gt;&lt;strong&gt;When to obtain an authorization.&lt;/strong&gt; The merchant must obtain an &lt;a title="Authorization Code" href="http://merchantprocessingservices.blogspot.com/2009/05/authorization-code.html" target="_self"&gt;authorization&lt;/a&gt; from the card issuer before completing the transaction in the following instances:&lt;br /&gt;   &lt;ul&gt;&lt;li&gt;The transaction amount exceeds the merchant's floor limit or the &lt;a title="Floor Limit" href="http://paymentprocessingservices.blogspot.com/2008/07/floor-limit.html" target="_self"&gt;floor limit&lt;/a&gt; applicable to the transaction.&lt;br /&gt;   &lt;/li&gt;&lt;li&gt;The card is expired or not yet valid.&lt;br /&gt;   &lt;/li&gt;&lt;li&gt;The card is not signed.&lt;br /&gt;   &lt;/li&gt;&lt;li&gt;The merchant wishes to delay presenting the transaction record.&lt;br /&gt;   &lt;/li&gt;&lt;li&gt;The transaction receipt cannot be imprinted although the card is present.&lt;br /&gt;   &lt;/li&gt;&lt;li&gt;The merchant's data processing equipment is unable to read the magnetic stripe or the chip (if one is present) on the card.&lt;br /&gt;   &lt;/li&gt;&lt;li&gt;The account number is listed on the regional Warning Notice.&lt;br /&gt;   &lt;/li&gt;&lt;li&gt;The transaction is a recurring payment and a previous &lt;a title="Authorization Code" href="http://merchantprocessingservices.blogspot.com/2009/05/authorization-code.html" target="_self"&gt;authorization&lt;/a&gt; request was declined.&lt;br /&gt;   &lt;/li&gt;&lt;li&gt;The merchant is suspicious of the transaction for any reason.&lt;br /&gt;   &lt;/li&gt;&lt;/ul&gt;&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Reporting a suspicious transaction.&lt;/strong&gt; To report a suspicious transaction, the merchant must contact the &lt;a title="Authorization Message" href="http://merchantprocessingservices.blogspot.com/2009/05/authorization-message.html" target="_self"&gt;authorization&lt;/a&gt; center, state "This is a &lt;a title="Code 10" href="http://paymentprocessingservices.blogspot.com/search?q=Code+10" target="_self"&gt;Code 10&lt;/a&gt;" and await instructions.In all instances, except where the transaction exceeds the applicable floor limit, the merchant must inform the &lt;a title="Authorization Response" href="http://merchantprocessingservices.blogspot.com/2009/05/authorization-response.html" target="_self"&gt;authorization&lt;/a&gt; center of the reason for the &lt;a title="Transaction Authorization and Presentment Requirements" href="http://merchantaccountprocessing.blogspot.com/2009/08/transaction-authorization-and.html" target="_self"&gt;authorization&lt;/a&gt; request.&lt;br /&gt;   &lt;/li&gt;&lt;li&gt;&lt;strong&gt;Pick-up-card response.&lt;/strong&gt; If a cardholder account is listed on the electronic Warning Bulletin or regional Warning Notice, the merchant must not complete the transaction. The merchant must retain the card by reasonable and peaceful means and notify the &lt;a title="ECommerce Authorization Routing Sequence" href="http://merchantaccountprocessing.blogspot.com/2008/12/ecommerce-authorization-routing.html" target="_self"&gt;authorization&lt;/a&gt; center for further instructions. If the &lt;a title="ECommerce Routing Authorization Requirements" href="http://merchantaccountprocessing.blogspot.com/2008/12/ecommerce-routing-authorization.html" target="_self"&gt;authorization&lt;/a&gt; center cannot be reached, the merchant must retain the card by reasonable and peaceful means until the center can be reached.&lt;br /&gt;&lt;/li&gt;&lt;/ul&gt;&lt;!-- AddThis Button BEGIN --&gt;&lt;script type="text/javascript"&gt;&lt;!--     addthis_pub  = 'Merchant Account';     addthis_brand = 'Merchant Account';     addthis_options = 'favorites, email, digg, delicious, twitter, myspace, facebook, google, live, more'; // --&gt;&lt;/script&gt; &lt;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"&gt;&lt;img src="http://s9.addthis.com/button1-bm.gif" alt="" border="0" height="16" width="125" /&gt;&lt;/a&gt;&lt;script src="http://s7.addthis.com/js/152/addthis_widget.js" type="text/javascript"&gt;&lt;/script&gt;&lt;br /&gt;&lt;!-- AddThis Button END --&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8887473741874669103-1749114192784137303?l=merchantaccountprocessing.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://merchantaccountprocessing.blogspot.com/feeds/1749114192784137303/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2009/08/obtaining-authorization.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/1749114192784137303'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/1749114192784137303'/><link rel='alternate' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2009/08/obtaining-authorization.html' title='Obtaining an Authorization'/><author><name>mss</name><uri>http://www.blogger.com/profile/02682453100579738680</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8887473741874669103.post-6238799950505431851</id><published>2009-08-12T17:21:00.001-04:00</published><updated>2009-08-12T17:40:25.122-04:00</updated><title type='text'>MasterCard Acceptance Procedures for Purchase Transactions</title><content type='html'>The following requirements are relevant to the merchant's acceptance procedures for purchase transactions.&lt;br /&gt;   &lt;ul&gt;&lt;li&gt;&lt;strong&gt;Card must be present.&lt;/strong&gt; A payment card must be presented to the merchant for all transactions except in the case of mail orders, telephone orders, card-not-present unique transactions, eCommerce transactions, and pre-authorized orders.&lt;br /&gt;   &lt;/li&gt;&lt;li&gt;&lt;strong&gt;Determine whether the card is valid.&lt;/strong&gt; The merchant must complete the following steps to determine whether each card presented is a valid payment card:&lt;br /&gt;   &lt;ul&gt;&lt;li&gt;Check the valid date and the expiration date on the face of the card. If the card is expired or not yet valid, the merchant must obtain an authorization from the card issuer.&lt;br /&gt;   &lt;/li&gt;&lt;li&gt;Check the Electronic Warning Bulletin or international Warning Notices. If the account number is listed, the merchant must not complete the transaction without obtaining an authorization from the card issuer.&lt;br /&gt;   &lt;/li&gt;&lt;li&gt;Compare the four-digit truncated account number imprinted in the signature panel with the last four digits of the embossed account number on the face of the card.&lt;br /&gt;   &lt;/li&gt;&lt;li&gt;Unless a hybrid terminal is used, compare the embossed account number on the face of the card with the number displayed or printed from the point of sale (POS) terminal.&lt;br /&gt;   &lt;/li&gt;&lt;li&gt;If a photograph of the cardholder is present on the card, compare the photograph on the card with the person presenting the card.&lt;br /&gt;   &lt;/li&gt;&lt;li&gt;Check that the card is signed.&lt;br /&gt;   &lt;/li&gt;&lt;li&gt;For unique transactions processed in a face-to-face environment (with the exception of truck stop transactions and card-read transactions where a non-signature CVM is used), request personal identification of the cardholder in the form of an unexpired, official government document. Compare the signature on the personal identification with the signature on the card.&lt;br /&gt;   &lt;/li&gt;&lt;/ul&gt;&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Unsigned cards.&lt;/strong&gt; If the card is not signed, the merchant must:&lt;br /&gt;   &lt;ul&gt;&lt;li&gt;Obtain an authorization from the card issuer.&lt;br /&gt;   &lt;/li&gt;&lt;li&gt;Ask the cardholder to provide identification (but not record the cardholder identification information).&lt;br /&gt;   &lt;/li&gt;&lt;li&gt;Require the cardholder to sign the card.&lt;br /&gt;&lt;/li&gt;The merchant must not complete the transaction if the cardholder refuses to sign the card.&lt;/ul&gt;&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Suspicious cards.&lt;/strong&gt; If the merchant believes that there is a discrepancy in the signature, or if the last four digits of the embossed account number do not match the four-digit truncated account number on the signature panel or displayed on the terminal, or if the photographic identification is uncertain, the merchant must contact its acquiring bank for instructions. If any unexpired &lt;a title="MasterCard Merchant Services" href="http://www.unibulmerchantservices.com/mastercard-merchant-services/" target="_self"&gt;MasterCard&lt;/a&gt; card does not have a &lt;a title="MasterCard Merchant Account" href="http://www.unibulmerchantservices.com/mastercard-merchant-account/" target="_self"&gt;MasterCard&lt;/a&gt; hologram on the lower right corner of the card face, the merchant must pick up the card and contact its acquiring bank's &lt;a title="Code 10" href="http://merchantprocessingservices.blogspot.com/2008/11/code-10-call.html" target="_self"&gt;Code 10&lt;/a&gt; operator to advise it of the pick-up and to receive mailing instructions.&lt;br /&gt;&lt;/li&gt;&lt;/ul&gt;&lt;!-- AddThis Button BEGIN --&gt;&lt;script type="text/javascript"&gt;&lt;!--     addthis_pub  = 'Merchant Account';     addthis_brand = 'Merchant Account';     addthis_options = 'favorites, email, digg, delicious, twitter, myspace, facebook, google, live, more'; // --&gt;&lt;/script&gt; &lt;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"&gt;&lt;img src="http://s9.addthis.com/button1-bm.gif" alt="" border="0" height="16" width="125" /&gt;&lt;/a&gt;&lt;script src="http://s7.addthis.com/js/152/addthis_widget.js" type="text/javascript"&gt;&lt;/script&gt;&lt;br /&gt;&lt;!-- AddThis Button END --&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8887473741874669103-6238799950505431851?l=merchantaccountprocessing.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://merchantaccountprocessing.blogspot.com/feeds/6238799950505431851/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2009/08/mastercard-acceptance-procedures-for.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/6238799950505431851'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/6238799950505431851'/><link rel='alternate' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2009/08/mastercard-acceptance-procedures-for.html' title='MasterCard Acceptance Procedures for Purchase Transactions'/><author><name>mss</name><uri>http://www.blogger.com/profile/02682453100579738680</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8887473741874669103.post-5315317829725786667</id><published>2009-08-11T16:17:00.003-04:00</published><updated>2009-08-11T16:50:30.177-04:00</updated><title type='text'>Handling Account, Cardholder, Transaction, and Merchant Information</title><content type='html'>&lt;b&gt;Sale or Exchange of Account and Cardholder Information Prohibited&lt;/b&gt;&lt;br /&gt;&lt;br /&gt;Merchant banks must not sell, purchase, provide, exchange or in any manner disclose card account number information to anyone other than its acquiring bank, to the Credit Card Association, or in response to a government request. This prohibition applies to card imprints, transaction receipts, carbon copies, mailing lists, tapes, or other media obtained as a result of a card transaction.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Fraudulent or Unauthorized Use of Account Information Prohibited&lt;/b&gt;&lt;br /&gt;&lt;br /&gt;A merchant must not request or use card account number information for any purpose that it knows or should have known to be fraudulent or in violation of the card Association's standards, or for any purpose that the cardholder did not authorize.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Account, Cardholder and Transaction Data Must Be Kept Secure&lt;/b&gt;&lt;br /&gt;&lt;br /&gt;Merchants must keep all systems and media containing card account, cardholder, or transaction information (whether physical or electronic) in a secure manner so as to prevent access by, or disclosure to any unauthorized party. Merchants must destroy all media not necessary to retain, in a manner that will render the data unreadable.&lt;br /&gt;&lt;br /&gt;If an account compromise occurs, the following will apply:&lt;br /&gt;  &lt;ul&gt;&lt;li&gt;The merchant must notify its acquiring bank immediately.&lt;br /&gt;  &lt;/li&gt;&lt;li&gt;The acquiring bank must provide the affected Credit Card Association with complete information about the account compromise.&lt;br /&gt;  &lt;/li&gt;&lt;li&gt;If the account compromise results from the merchant's failure to comply with this rule, the acquiring bank promptly must engage a data security firm to assess the vulnerability of the merchant systems and provide the results of such audit (or a forensics examination if required) promptly to the affected Credit Card Association.&lt;br /&gt;  &lt;/li&gt;&lt;li&gt;If the acquiring bank fails to engage promptly the services of a data security firm or fails to promptly provide the findings of the audit, or any forensics examination, the acquiring bank may be assessed a fine by the Credit Card Association.&lt;br /&gt;  &lt;/li&gt;&lt;li&gt;The acquiring bank must cooperate, and ensure that its merchant cooperates, with the investigation and resolution of the account compromise, including any forensic audit or other measure that the Credit Card Association deems necessary.&lt;br /&gt;&lt;/li&gt;&lt;/ul&gt;&lt;b&gt;Account Information Must Not Be Recorded on a Mailer&lt;/b&gt;&lt;br /&gt;&lt;br /&gt;A merchant must not ask a cardholder to record a card account number or other account information on the exterior of any order form or other similar device designed to be mailed.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Merchant Identification&lt;/b&gt;&lt;br /&gt;&lt;br /&gt;A merchant must prominently and unequivocally inform the cardholder of the identity of the merchant at all points of sale so that the cardholder can distinguish the merchant from any other party such as a supplier of goods or services to the merchant.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Data Storage Entity (DSE) Identification&lt;/b&gt;&lt;br /&gt;&lt;br /&gt;The merchant must inform the acquiring bank promptly of the identity of any DSE that engages, or proposes to engage, in the processing, storage, or both of card account data for the merchant, whether directly or indirectly, regardless of the manner or duration of such activities.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Storage of Account, Cardholder, and Transaction Data&lt;/b&gt;&lt;br /&gt;&lt;br /&gt;A merchant and any DSE must not store in any system or in any manner, discretionary card-read data, &lt;a title="CVC2" href="http://merchantprocessingservices.blogspot.com/2008/11/card-verification-code-2-cvc2.html" target="_self"&gt;CVC2&lt;/a&gt; / &lt;a title="CVV2" href="http://merchantprocessingservices.blogspot.com/2008/11/card-verification-value-2-cvv2.html" target="_self"&gt;CVV2&lt;/a&gt; data, PIN data, &lt;a title="Address Verification Service (AVS)" href="http://merchantprocessingservices.blogspot.com/2008/11/address-verification-service-avs.html" target="_self"&gt;Address Verification Service (AVS)&lt;/a&gt; data, or any other prohibited information as set forth in the Credit Card Associations' standards, except during the &lt;a title="Authorization" href="http://merchantprocessingservices.blogspot.com/2008/11/authorization.html" target="_self"&gt;authorization&lt;/a&gt; process for a transaction, that is, from the time an &lt;a title="Authorization Message" href="http://merchantprocessingservices.blogspot.com/2009/05/authorization-message.html" target="_self"&gt;authorization request message&lt;/a&gt; is transmitted and up to the time the &lt;a title="Authorization Response" href="http://merchantprocessingservices.blogspot.com/2009/05/authorization-response.html" target="_self"&gt;authorization request response&lt;/a&gt; message is received. Storage is permitted of only the card account number, expiration date, cardholder name, and service code, in a secure environment to which access is limited, and then only to the extent that this data is required for bona fide purposes and only for the length of time that the data is required for such purposes.&lt;br /&gt;&lt;br /&gt;&lt;!-- AddThis Button BEGIN --&gt;&lt;script type="text/javascript"&gt;&lt;!--     addthis_pub  = 'Merchant Account';     addthis_brand = 'Merchant Account';     addthis_options = 'favorites, email, digg, delicious, twitter, myspace, facebook, google, live, more'; // --&gt;&lt;/script&gt; &lt;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"&gt;&lt;img src="http://s9.addthis.com/button1-bm.gif" alt="" border="0" height="16" width="125" /&gt;&lt;/a&gt;&lt;script src="http://s7.addthis.com/js/152/addthis_widget.js" type="text/javascript"&gt;&lt;/script&gt;&lt;br /&gt;&lt;!-- AddThis Button END --&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8887473741874669103-5315317829725786667?l=merchantaccountprocessing.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://merchantaccountprocessing.blogspot.com/feeds/5315317829725786667/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2009/08/account-cardholder-transaction-and.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/5315317829725786667'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/5315317829725786667'/><link rel='alternate' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2009/08/account-cardholder-transaction-and.html' title='Handling Account, Cardholder, Transaction, and Merchant Information'/><author><name>mss</name><uri>http://www.blogger.com/profile/02682453100579738680</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8887473741874669103.post-3977141904007782862</id><published>2009-08-06T17:18:00.001-04:00</published><updated>2009-08-06T17:26:44.917-04:00</updated><title type='text'>Transaction Authorization and Presentment Requirements</title><content type='html'>&lt;b&gt;Authorizing Transactions&lt;/b&gt;&lt;br /&gt;&lt;br /&gt;When required by the Credit Card Associations' standards or by its acquiring bank, the merchant must obtain an &lt;a title="Authorization" href="http://merchantprocessingservices.blogspot.com/2008/11/authorization.html" target="_self"&gt;authorization&lt;/a&gt; before completing a transaction. Standards concerning &lt;a title="&amp;quot;Call&amp;quot; or &amp;quot;Call Center&amp;quot; Authorization Response" href="http://merchantprocessingservices.blogspot.com/2008/11/call-or-call-center-authorization.html" target="_self"&gt;authorizations&lt;/a&gt; are published annually by the Credit Card Associations.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Presenting Transactions&lt;/b&gt;&lt;br /&gt;&lt;br /&gt;The following standards apply to the presentment of transactions.&lt;br /&gt;   &lt;ul&gt;&lt;li&gt;&lt;strong&gt;Valid and invalid transactions.&lt;/strong&gt; A merchant must present to its acquiring bank only valid transactions between itself and a bona fide cardholder. A merchant must not present transactions that it knows or should have known to be fraudulent or not authorized by the cardholder, or authorized by a cardholder that is in collusion with the merchant for a fraudulent intent. Within the scope of this rule, the merchant is responsible for the actions of its employees.&lt;br /&gt;   &lt;/li&gt;&lt;li&gt;&lt;strong&gt;Present transactions within three business days.&lt;/strong&gt; The merchant must present records of valid transactions to its acquiring bank no later than three bank business days after the date of the transaction, except:&lt;br /&gt;   &lt;ul&gt;&lt;li&gt;The record must not be presented until after the goods are shipped or the services are performed unless, at the time of the transaction, the cardholder agrees to a properly disclosed delayed delivery of the goods or services.&lt;br /&gt;   &lt;/li&gt;&lt;li&gt;When the merchant receives &lt;a title="Authorization Code" href="http://merchantprocessingservices.blogspot.com/2009/05/authorization-code.html" target="_self"&gt;authorization&lt;/a&gt; for a delayed presentment (in which case the words "Delayed Presentment" must be noted on the TID).&lt;br /&gt;   &lt;/li&gt;&lt;li&gt;When the merchant is obligated by law to retain the sales receipt or return it to a buyer upon timely cancellation, in which case the merchant should present the record within 10 business days after the transaction date.&lt;br /&gt;&lt;/li&gt;&lt;/ul&gt;&lt;/li&gt;&lt;/ul&gt;&lt;!-- AddThis Button BEGIN --&gt;&lt;script type="text/javascript"&gt;&lt;!--     addthis_pub  = 'Merchant Account';     addthis_brand = 'Merchant Account';     addthis_options = 'favorites, email, digg, delicious, twitter, myspace, facebook, google, live, more'; // --&gt;&lt;/script&gt; &lt;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"&gt;&lt;img src="http://s9.addthis.com/button1-bm.gif" alt="" width="125" border="0" height="16" /&gt;&lt;/a&gt;&lt;script src="http://s7.addthis.com/js/152/addthis_widget.js" type="text/javascript"&gt;&lt;/script&gt;&lt;br /&gt;&lt;!-- AddThis Button END --&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8887473741874669103-3977141904007782862?l=merchantaccountprocessing.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://merchantaccountprocessing.blogspot.com/feeds/3977141904007782862/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2009/08/transaction-authorization-and.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/3977141904007782862'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/3977141904007782862'/><link rel='alternate' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2009/08/transaction-authorization-and.html' title='Transaction Authorization and Presentment Requirements'/><author><name>mss</name><uri>http://www.blogger.com/profile/02682453100579738680</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8887473741874669103.post-3577344573732972863</id><published>2009-08-05T15:27:00.001-04:00</published><updated>2009-08-05T15:57:36.234-04:00</updated><title type='text'>Prohibited MasterCard Card Acceptance Practices</title><content type='html'>The following card acceptance practices are prohibited by MasterCard:&lt;br /&gt;   &lt;ul&gt;&lt;li&gt;&lt;strong&gt;Discrimination&lt;/strong&gt; A merchant must not engage in any acceptance practice that discriminates against or discourages the use of &lt;a title="MasterCard Merchant Account" href="http://www.unibulmerchantservices.com/mastercard-merchant-account/" target="_self"&gt;MasterCard&lt;/a&gt; cards in favor of any other brand.&lt;br /&gt;   &lt;/li&gt;&lt;li&gt;&lt;strong&gt;Charges to cardholders.&lt;/strong&gt; A merchant must not directly or indirectly require any &lt;a title="MasterCard Merchant Services" href="http://www.unibulmerchantservices.com/mastercard-merchant-services/" target="_self"&gt;MasterCard&lt;/a&gt; cardholder to pay a surcharge or any part of any merchant discount or any contemporaneous finance charge in connection with a &lt;a title="MasterCard Account Data Compromise Events" href="http://paymentprocessingservices.blogspot.com/2009/08/mastercard-account-data-compromise.html" target="_self"&gt;MasterCard&lt;/a&gt; card transaction. A merchant may provide a discount to its customers for cash payments. A merchant is permitted to charge a fee (such as a commission, postage, expedited service or convenience fees, and the like) if the fee is imposed on all like transactions regardless of the form of payment used. The following definitions apply:&lt;br /&gt;   &lt;ul&gt;&lt;li&gt;A surcharge is any fee charged in connection with a &lt;a title="MasterCard Data Protection Standards" href="http://paymentprocessingservices.blogspot.com/2009/08/mastercard-data-protection-standards.html" target="_self"&gt;MasterCard&lt;/a&gt; transaction that is not charged if another payment method is used.&lt;br /&gt;   &lt;/li&gt;&lt;li&gt;The merchant discount fee is the fee the merchant pays to its acquiring bank to acquire transactions.&lt;br /&gt;   &lt;/li&gt;&lt;/ul&gt;&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Minimum / maximum transaction amount prohibited.&lt;/strong&gt; A merchant must not require, or post signs indicating that it requires, a minimum or maximum transaction amount to accept a valid &lt;a title="General MasterCard Monitoring Requirements" href="http://paymentprocessingservices.blogspot.com/2009/06/general-mastercard-monitoring.html" target="_self"&gt;MasterCard&lt;/a&gt; card.&lt;br /&gt;   &lt;/li&gt;&lt;li&gt;&lt;strong&gt;Prohibited transactions.&lt;/strong&gt; A merchant must not submit for payment into interchange, and an acquiring bank must not accept from a merchant for submission into interchange, any transaction:&lt;br /&gt;   &lt;ul&gt;&lt;li&gt;That represents the refinancing or transfer of an existing cardholder obligation that is deemed to be uncollectible.&lt;br /&gt;   &lt;/li&gt;&lt;li&gt;That arises from the dishonor of a cardholder's personal check.&lt;br /&gt;   &lt;/li&gt;&lt;li&gt;That arises from the acceptance of &lt;a title="General MasterCard Registration Requirements" href="http://paymentprocessingservices.blogspot.com/2009/06/general-mastercard-registration.html" target="_self"&gt;MasterCard&lt;/a&gt; cards at terminals that dispense scrip.&lt;br /&gt;   &lt;/li&gt;&lt;/ul&gt;&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Other forms of payment.&lt;/strong&gt; A merchant must not accept any payment from a customer in any other form (for example, cash or check) with respect to a charge for goods or services that are included on a transaction information document (TID) resulting from the use of a &lt;a title="MasterCard Registration Program" href="http://paymentprocessingservices.blogspot.com/2009/06/mastercard-registration-program.html" target="_self"&gt;MasterCard&lt;/a&gt; card.&lt;br /&gt;&lt;/li&gt;&lt;/ul&gt;&lt;!-- AddThis Button BEGIN --&gt;&lt;script type="text/javascript"&gt;&lt;!--     addthis_pub  = 'Merchant Account';     addthis_brand = 'Merchant Account';     addthis_options = 'favorites, email, digg, delicious, twitter, myspace, facebook, google, live, more'; // --&gt;&lt;/script&gt; &lt;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"&gt;&lt;img src="http://s9.addthis.com/button1-bm.gif" alt="" width="125" border="0" height="16" /&gt;&lt;/a&gt;&lt;script src="http://s7.addthis.com/js/152/addthis_widget.js" type="text/javascript"&gt;&lt;/script&gt;&lt;br /&gt;&lt;!-- AddThis Button END --&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8887473741874669103-3577344573732972863?l=merchantaccountprocessing.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://merchantaccountprocessing.blogspot.com/feeds/3577344573732972863/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2009/08/prohibited-mastercard-card-acceptance.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/3577344573732972863'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/3577344573732972863'/><link rel='alternate' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2009/08/prohibited-mastercard-card-acceptance.html' title='Prohibited MasterCard Card Acceptance Practices'/><author><name>mss</name><uri>http://www.blogger.com/profile/02682453100579738680</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8887473741874669103.post-3359633712744947096</id><published>2009-08-04T17:22:00.002-04:00</published><updated>2009-08-04T17:38:34.962-04:00</updated><title type='text'>Honoring Payment Cards</title><content type='html'>Merchants must honor all valid payment cards of the types they have contracted to accept without discrimination when they are properly presented for payment. The merchant must maintain a policy that does not discriminate among customers seeking to make purchases with a payment card. A merchant that does not deal with the public at large (for example, a private club) is considered to comply with this rule if it honors payment cards of cardholders that have purchasing privileges with the merchant.&lt;br /&gt;&lt;br /&gt;A merchant must not refuse to complete a payment card transaction solely because a cardholder who has complied with the conditions for presentment of a card at the point of sale (POS) refuses to provide additional identification information, except as specifically permitted or required by the Associations. A merchant may require additional identification from the cardholder if the information is required to complete the transaction, such as for shipping purposes. A merchant in a country or region that supports use of the &lt;a title="Address Verification Service (AVS)" href="http://merchantprocessingservices.blogspot.com/2008/11/address-verification-service-avs.html" target="_self"&gt;Address Verification Service (AVS)&lt;/a&gt; may require the cardholder's ZIP or postal code to complete a &lt;a title="Cardholder-Activated Terminals" href="http://paymentprocessingservices.blogspot.com/2008/10/cardholder-activated-terminals.html" target="_self"&gt;cardholder-activated terminal&lt;/a&gt; (CAT) transaction, or the cardholder's address and ZIP or postal code to complete a mail order, phone order, or &lt;a title="eCommerce Card Processing Guide" href="http://www.unibulmerchantservices.com/ecommerce-card-processing-guide/" target="_self"&gt;eCommerce&lt;/a&gt; transaction. A merchant must not refuse to complete an electronic commerce transaction using a payment card solely because the cardholder does not have a digital certificate or other secured protocol.&lt;br /&gt;&lt;br /&gt;&lt;!-- AddThis Button BEGIN --&gt;&lt;script type="text/javascript"&gt;&lt;!--     addthis_pub  = 'Merchant Account';     addthis_brand = 'Merchant Account';     addthis_options = 'favorites, email, digg, delicious, twitter, myspace, facebook, google, live, more'; // --&gt;&lt;/script&gt; &lt;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"&gt;&lt;img src="http://s9.addthis.com/button1-bm.gif" alt="" width="125" border="0" height="16" /&gt;&lt;/a&gt;&lt;script src="http://s7.addthis.com/js/152/addthis_widget.js" type="text/javascript"&gt;&lt;/script&gt;&lt;br /&gt;&lt;!-- AddThis Button END --&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8887473741874669103-3359633712744947096?l=merchantaccountprocessing.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://merchantaccountprocessing.blogspot.com/feeds/3359633712744947096/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2009/08/honoring-payment-cards.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/3359633712744947096'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/3359633712744947096'/><link rel='alternate' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2009/08/honoring-payment-cards.html' title='Honoring Payment Cards'/><author><name>mss</name><uri>http://www.blogger.com/profile/02682453100579738680</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8887473741874669103.post-6637754925321372926</id><published>2009-08-02T09:50:00.001-04:00</published><updated>2009-08-02T10:22:38.078-04:00</updated><title type='text'>Merchant Monitoring Requirements</title><content type='html'>&lt;b&gt;Merchant Monitoring&lt;/b&gt;&lt;br /&gt;&lt;br /&gt;Processors must monitor each of their merchants' activity on an ongoing basis to deter fraud or other wrongful activity. At a minimum, processors must monitor their merchants' deposits and authorization activity&lt;br /&gt;&lt;br /&gt;The Credit Card Associations have established certain standards applicable to fraudulent transactions and &lt;a title="Chargeback Manual" href="http://www.unibulmerchantservices.com/chargeback-manual/" target="_self"&gt;chargeback&lt;/a&gt; activity. Processors whose merchants exceed or violate these standards may be subject to fines or other disciplinary action and may be subject to &lt;a title="Chargeback Management" href="http://www.unibulmerchantservices.com/chargeback-management/" target="_self"&gt;chargeback&lt;/a&gt; liability.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Merchant Noncompliance&lt;/b&gt;&lt;br /&gt;&lt;br /&gt;If the Credit Card Associations become aware that any merchant has violated any of the rules governing the acceptance of their cards, the use of their marks, the charges to cardholders, the minimum or maximum transaction amount restrictions or the prohibited transactions, they will notify the acquiring bank of the violation and request that it take action to ensure that the merchant discontinues the practice promptly, and in no more than 10 business days.&lt;br /&gt;&lt;br /&gt;Acquiring banks may be fined if the Associations become aware of such violations. &lt;a title="MasterCard Merchant Account" href="http://www.unibulmerchantservices.com/mastercard-merchant-account/" target="_self"&gt;MasterCard&lt;/a&gt;, for instance, may impose an assessment for noncompliance of up to $100,000 per individual violation, with a maximum aggregate assessment of $500,000 for additional or continuing violations during any consecutive 12-month period.&lt;br /&gt;&lt;br /&gt;If a processor terminates the merchant processing agreement with a merchant because of a violation by the merchant of one or more of the rules referenced above, the member must report the merchant to the &lt;a title="MasterCard Merchant Services" href="http://www.unibulmerchantservices.com/mastercard-merchant-services/" target="_self"&gt;MasterCard&lt;/a&gt; MATCH system within five calendar days of the decision to terminate, regardless of the effective date of the termination. All records of rules violations move with the merchant to any new acquiring bank.&lt;br /&gt;&lt;br /&gt;&lt;!-- AddThis Button BEGIN --&gt;&lt;script type="text/javascript"&gt;&lt;!--     addthis_pub  = 'Merchant Account';     addthis_brand = 'Merchant Account';     addthis_options = 'favorites, email, digg, delicious, twitter, myspace, facebook, google, live, more'; // --&gt;&lt;/script&gt; &lt;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"&gt;&lt;img src="http://s9.addthis.com/button1-bm.gif" alt="" width="125" border="0" height="16" /&gt;&lt;/a&gt;&lt;script src="http://s7.addthis.com/js/152/addthis_widget.js" type="text/javascript"&gt;&lt;/script&gt;&lt;br /&gt;&lt;!-- AddThis Button END --&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8887473741874669103-6637754925321372926?l=merchantaccountprocessing.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://merchantaccountprocessing.blogspot.com/feeds/6637754925321372926/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2009/08/merchant-monitoring-requirements.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/6637754925321372926'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/6637754925321372926'/><link rel='alternate' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2009/08/merchant-monitoring-requirements.html' title='Merchant Monitoring Requirements'/><author><name>mss</name><uri>http://www.blogger.com/profile/02682453100579738680</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8887473741874669103.post-5519237392288330651</id><published>2009-08-01T11:24:00.000-04:00</published><updated>2009-08-01T11:31:57.254-04:00</updated><title type='text'>Acquirer Obligations and Activities</title><content type='html'>&lt;b&gt;Acquiring Transactions&lt;/b&gt;&lt;br /&gt;&lt;br /&gt;Each acquiring bank must acquire all transactions properly presented to it from each of its merchants on such terms as set forth in the merchant agreement between them and under applicable rules and procedures.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Payments to Merchants&lt;/b&gt;&lt;br /&gt;&lt;br /&gt;Each acquiring bank must pay its merchant for all transactions received from the merchant no later than the next business day following the day of receipt. The acquiring bank may delay payment for only as long as it is necessary to determine the legitimacy of the deposit, within local law or banking regulation. Payment must be made by cash, check or credit to an account designated by the merchant. This requirement does not apply to transaction amounts withheld by an acquiring bank, by agreement of the merchant, for chargeback reserve or similar purposes.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Supplying Materials&lt;/b&gt;&lt;br /&gt;&lt;br /&gt;Each acquiring bank must ensure that each of its merchants is provided with all materials necessary to effect card transactions in accordance with applicable rules and regulations and to signify acceptance of the supported brands. These materials may include sales slips, credit slips, terminals, authorization services, acceptance displays, and the like.&lt;br /&gt;&lt;br /&gt;&lt;!-- AddThis Button BEGIN --&gt;&lt;script type="text/javascript"&gt;&lt;!--     addthis_pub  = 'Merchant Account';     addthis_brand = 'Merchant Account';     addthis_options = 'favorites, email, digg, delicious, twitter, myspace, facebook, google, live, more'; // --&gt;&lt;/script&gt; &lt;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"&gt;&lt;img src="http://s9.addthis.com/button1-bm.gif" alt="" width="125" border="0" height="16" /&gt;&lt;/a&gt;&lt;script src="http://s7.addthis.com/js/152/addthis_widget.js" type="text/javascript"&gt;&lt;/script&gt;&lt;br /&gt;&lt;!-- AddThis Button END --&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8887473741874669103-5519237392288330651?l=merchantaccountprocessing.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://merchantaccountprocessing.blogspot.com/feeds/5519237392288330651/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2009/08/acquirer-obligations-and-activities.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/5519237392288330651'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/5519237392288330651'/><link rel='alternate' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2009/08/acquirer-obligations-and-activities.html' title='Acquirer Obligations and Activities'/><author><name>mss</name><uri>http://www.blogger.com/profile/02682453100579738680</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8887473741874669103.post-823114510076164423</id><published>2009-07-31T11:52:00.001-04:00</published><updated>2009-08-01T11:23:19.940-04:00</updated><title type='text'>Processor Requirements for Signing a Merchant</title><content type='html'>&lt;a title="Visa Credit Card Processing" href="http://www.unibulmerchantservices.com/visa-credit-card-processing/" target="_self"&gt;Visa&lt;/a&gt; and &lt;a title="MasterCard Merchant Account" href="http://www.unibulmerchantservices.com/mastercard-merchant-account/" target="_self"&gt;MasterCard&lt;/a&gt; member banks must directly enter into a written merchant processing agreement with each merchant from which they acquire transactions.&lt;br /&gt;&lt;br /&gt;A member bank can only submit into interchange transactions arising in connection with products and services provided by a commercial entity that a cardholder purchases with a payment card, after the commercial entity has entered into a valid merchant processing agreement with the member. This rule applies regardless of whether the ability to use the payment card is explicit or implied, or whether the card is presented directly to the commercial entity, a third-party payment processor, or any other person. A commercial entity is any person that sells goods or services on an ongoing basis and that maintains a physical or virtual presence for the purpose of selling goods or services. This rule does not prohibit a commercial entity from being the recipient of funds that result from a money transfer transaction, provided the transaction is properly identified as such to the card issuer and cardholder with the appropriate merchant category code (MCC) and transaction category code (TCC) in all authorization and clearing records.&lt;br /&gt;&lt;br /&gt;Regardless of whether a member bank uses an &lt;a title="Independent Sales Organization (ISO)" href="http://paymentprocessingservices.blogspot.com/2008/06/what-is-iso.html" target="_self"&gt;Independent Sales Organization (ISO)&lt;/a&gt; or a &lt;a title="Member Service Provider (MSP)" href="http://paymentprocessingservices.blogspot.com/2008/07/what-is-msp.html" target="_self"&gt;Member Service Provider (MSP)&lt;/a&gt;, the member must itself execute a written agreement directly with each merchant. The agreement must reflect the member's primary responsibility for the merchant relationship and must comply with &lt;a title="Visa Merchant Account" href="http://www.unibulmerchantservices.com/visa-merchant-account/" target="_self"&gt;Visa&lt;/a&gt; and &lt;a title="MasterCard Merchant Services" href="http://www.unibulmerchantservices.com/mastercard-merchant-services/" target="_self"&gt;MasterCard&lt;/a&gt; standards and regulations. The merchant agreement can contain other provisions that may be agreed upon between the member bank and the merchant, provided that the provisions do not conflict with &lt;a title="Visa Merchant Services" href="http://www.unibulmerchantservices.com/visa-merchant-services/" target="_self"&gt;Visa&lt;/a&gt; and &lt;a title="General MasterCard Monitoring Requirements" href="http://paymentprocessingservices.blogspot.com/2009/06/general-mastercard-monitoring.html" target="_self"&gt;MasterCard&lt;/a&gt; standards and regulations.&lt;br /&gt;&lt;br /&gt;The member bank is responsible for ensuring that each of its merchants complies with &lt;a title="Accept Visa Credit Cards" href="http://www.unibulmerchantservices.com/accept-visa-credit-cards/" target="_self"&gt;Visa&lt;/a&gt; and &lt;a title="General MasterCard Registration Requirements" href="http://paymentprocessingservices.blogspot.com/2009/06/general-mastercard-registration.html" target="_self"&gt;MasterCard&lt;/a&gt; and regulations, including those applicable to unique transactions, cardholder-activated terminals, and the like, and is responsible for the merchant's failure to do so. The member bears the responsibility for each merchant's compliance and must take appropriate actions to ensure it, such as reviewing the merchant's deposit records and procedures for effecting transactions.&lt;br /&gt;&lt;br /&gt;Before entering into, extending, or renewing a merchant agreement, a member bank must verify that the merchant from which it intends to acquire transactions is a bona fide business and that the transactions will reflect bona fide business between the merchant and the cardholder.&lt;br /&gt;&lt;br /&gt;A member bank must retain all records concerning the investigation of any merchant with which it has entered into a merchant agreement for a minimum of two years after the date the agreement is terminated.&lt;br /&gt;&lt;br /&gt;&lt;!-- AddThis Button BEGIN --&gt;&lt;script type="text/javascript"&gt;&lt;!--     addthis_pub  = 'Merchant Account';     addthis_brand = 'Merchant Account';     addthis_options = 'favorites, email, digg, delicious, twitter, myspace, facebook, google, live, more'; // --&gt;&lt;/script&gt; &lt;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"&gt;&lt;img src="http://s9.addthis.com/button1-bm.gif" alt="" width="125" border="0" height="16" /&gt;&lt;/a&gt;&lt;script src="http://s7.addthis.com/js/152/addthis_widget.js" type="text/javascript"&gt;&lt;/script&gt;&lt;br /&gt;&lt;!-- AddThis Button END --&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8887473741874669103-823114510076164423?l=merchantaccountprocessing.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://merchantaccountprocessing.blogspot.com/feeds/823114510076164423/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2009/07/processor-requirements-for-signing.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/823114510076164423'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/823114510076164423'/><link rel='alternate' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2009/07/processor-requirements-for-signing.html' title='Processor Requirements for Signing a Merchant'/><author><name>mss</name><uri>http://www.blogger.com/profile/02682453100579738680</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8887473741874669103.post-5405841903661834718</id><published>2009-07-30T11:53:00.003-04:00</published><updated>2009-07-31T11:09:17.998-04:00</updated><title type='text'>Credit Card Discounts or Other Benefits at the Point of Sale</title><content type='html'>The Credit card Associations of &lt;a title="Visa Credit Card Processing" href="http://www.unibulmerchantservices.com/visa-credit-card-processing/" target="_self"&gt;Visa&lt;/a&gt; and &lt;a title="MasterCard Merchant Services" href="http://www.unibulmerchantservices.com/mastercard-merchant-services/" target="_self"&gt;MasterCard&lt;/a&gt; do not allow transactions involving their cards to receive a discount or other benefit at the Point of Sale (POS), unless such discount or other POS benefit may be received in transactions involving any valid card of their brand. Moreover, the Credit card Associations prohibit the promotion at the POS of discounts or other POS benefits on transactions executed with a particular card.&lt;br /&gt;&lt;br /&gt;The only discount practices permitted in connection with a particular &lt;a title="Visa Merchant Account" href="http://www.unibulmerchantservices.com/visa-merchant-account/" target="_self"&gt;Visa&lt;/a&gt; or &lt;a title="MasterCard Merchant Account" href="http://www.unibulmerchantservices.com/mastercard-merchant-account/" target="_self"&gt;MasterCard&lt;/a&gt; card are as follows:&lt;br /&gt; &lt;ul&gt;&lt;li&gt;A discount or other point of sale benefit accessed after the transaction has been completed (for example, credit on the billing statement, rebates, and so on).&lt;br /&gt; &lt;/li&gt;&lt;li&gt;A discount or other POS benefit accessed at the time of or after the transaction has been completed by a separate payment method and not by the card (for example, a coupon or voucher).&lt;br /&gt;&lt;/li&gt;&lt;/ul&gt;&lt;!-- AddThis Button BEGIN --&gt;&lt;script type="text/javascript"&gt;&lt;!--     addthis_pub  = 'Merchant Account';     addthis_brand = 'Merchant Account';     addthis_options = 'favorites, email, digg, delicious, twitter, myspace, facebook, google, live, more'; // --&gt;&lt;/script&gt; &lt;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"&gt;&lt;img src="http://s9.addthis.com/button1-bm.gif" alt="" width="125" border="0" height="16" /&gt;&lt;/a&gt;&lt;script src="http://s7.addthis.com/js/152/addthis_widget.js" type="text/javascript"&gt;&lt;/script&gt;&lt;br /&gt;&lt;!-- AddThis Button END --&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8887473741874669103-5405841903661834718?l=merchantaccountprocessing.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://merchantaccountprocessing.blogspot.com/feeds/5405841903661834718/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2009/07/mastercard-discounts-or-other-benefits.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/5405841903661834718'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8887473741874669103/posts/default/5405841903661834718'/><link rel='alternate' type='text/html' href='http://merchantaccountprocessing.blogspot.com/2009/07/mastercard-discounts-or-other-benefits.html' title='Credit Card Discounts or Other Benefits at the Point of Sale'/><author><name>mss</name><uri>http://www.blogger.com/profile/02682453100579738680</uri><email>noreply@blogger.com</email><gd:image r
