Account Updater Implementation and Operations Guide

Account Updater Implementation and Operations Guide March 2015 XML Release: 9.4 Document Version: 2.8

Vantiv Account Updater Implementation and Operations Guide XML Release: 9.4 All information whether text or graphics, contained in this manual is confidential and proprietary information of Vantiv, LLC and is provided to you solely for the purpose of assisting you in using a Vantiv, LLC product. All such information is protected by copyright laws and international treaties. No part of this manual may be reproduced or transmitted in any form or by any means, electronic, mechanical or otherwise for any purpose without the express written permission of Vantiv, LLC. The possession, viewing, or use of the information contained in this manual does not transfer any intellectual property rights or grant a license to use this information or any software application referred to herein for any purpose other than that for which it was provided. Information in this manual is presented "as is" and neither Vantiv, LLC or any other party assumes responsibility for typographical errors, technical errors, or other inaccuracies contained in this document. This manual is subject to change without notice and does not represent a commitment on the part Vantiv, LLC or any other party. Vantiv, LLC does not warrant that the information contained herein is accurate or complete. All trademarks are the property of their respective owners and all parties herein have consented to their trademarks appearing in this manual. Any use by you of the trademarks included herein must have express written permission of the respective owner. Copyright 2003-2015, Vantiv, LLC - ALL RIGHTS RESERVED.

About This Guide CONTENTS Intended Audience... vii Revision History...vii Document Structure... viii Documentation Set... viii Typographical Conventions...ix Contact Information...x Chapter 1 Introduction Overview of Account Updater... 2 Account Updater Features and Limitations... 2 Merchant Requirements... 3 Technical Requirements... 4 Account Updater Workflow... 5 Best Practices... 7 Recommended Session File Size... 7 Chapter 2 Testing Your Account Updater XML Before You Begin Certification Testing... 10 Transferring Files via FTP... 11 Submitting a File for Processing via sftp... 11 Retrieving Processed Files via sftp... 11 Testing Account Updater Transactions... 13 After Completing Certification Testing... 26 Chapter 3 Managing Customer Account Data Submitting an Account Updater Request... 28 Account Updater Acknowledgement Response... 29 Monitoring the Progress of Your Account Updater Transactions... 30 Viewing Account Updater Session Data... 30 Retrieving Your Account Updater Completion Results... 32 Retrieving Your Files via FTP... 32 Reviewing Your Account Updater Completion Response File... 33 Reviewing Account Updater Results in the UI... 34 Viewing Account Updater Batch Contents... 34 Browsing Transactions in the Batch Contents Report... 35 Exporting Account Updater Batch Contents to Excel... 36 Viewing Account Updater Info on the Payment Detail Screen... 36 Document Version: 2.8 XML Release: 9.4 iii

Contents Chapter 4 Account Updater LitleXML Examples Account Updater Batch Request... 40 Account Updater Acknowledgement Response... 42 Account Updater Acknowledgement Response Format... 42 Account Updater Acknowledgement Response Codes... 43 Account Updater RFR... 45 Account Updater RFR Request Format... 45 RFR File Processing Response... 47 Account Updater Completion Response... 48 Account Updater Completion Response Format... 48 Account Updater Completion Response Codes... 51 Appendix A LitleXML Account Updater Elements accountupdate... 54 accountupdatefilerequestdata... 55 accountupdateresponse... 56 authentication... 57 batchrequest... 58 batchresponse... 62 bin... 63 card... 64 cardortoken... 65 expdate... 66 litlerequest... 67 litleresponse... 68 litletoken... 69 litletxnid... 70 merchantid... 71 message... 72 number... 73 orderid... 74 originalcard... 75 originaltoken... 76 password... 77 postday... 78 response... 79 responsetime... 80 RFRRequest... 81 RFRResponse... 82 token... 83 type... 84 iv Document Version: 2.8 XML Release: 9.4

Contents updatedcard... 85 updatedtoken... 86 user... 87 Document Version: 2.8 XML Release: 9.4 v

Contents vi Document Version: 2.8 XML Release: 9.4

ABOUT THIS GUIDE This guide explains how to implement and use Account Updater, an optional product from Vantiv, LLC. Intended Audience This guide is intended for technical personnel who will be implementing Account Updater and operations personnel who will be monitoring Account Updater transactions on a merchant s payment processing system. Revision History This document has been revised as follows: TABLE 1 Document Revision History Version Description of Change Location 1.0 Initial Release N/A 1.1 Changed the test data Account Number for Item 10 in Table 2-1 Also, fixed some autonumbering issues. 1.2 Updated to latest template. restructured XML information and examples. Also, minor changes and typos fixed. 2.0 Updated with info about Account Updater for tokenized merchants. 2.1 Update document to include Account Updater for Discover cards. Table 2-1 on page 13 All All All 2.2 Clarify registration requirements for Discover Chapter 1 2.3 Added <bin> element to <originaltoken> and <updatedtoken> elements Chapter 4 and Appendix A 2.4 Revamp all Certification Tests. Chapter 2 Document Version: 2.8 XML Release: 9.4 vii

About This Guide Document Structure TABLE 1 Document Revision History Version Description of Change Location 2.5 Rebrand document. All 2.6 Corrected desciption of id attribute in batchresponse file Appendix A 2.7 Change to the recommended number of transactions in a Session/Batch file. 2.8 Modified several sections to remove references to file submission via HTTP Post and TCP/IP. Chapter 1 Chapters 1, 2, and 3 Document Structure This guide contains the following sections: Chapter 1, "Introduction" This chapter provides an overview of the Account Updater feature and explains how to plan for a smooth Account Updater implementation. Chapter 2, "Testing Your Account Updater XML" This chapter provides information concerning the testing and certification process used to verify your Account Updater XML templates and qualify you for use of the feature. Chapter 3, "Managing Customer Account Data" This chapter explains how to use Account Updater. Chapter 4, "Account Updater LitleXML Examples" This chapter provides information concerning the structure of the LitleXML transactions used for Account Updater, as well as XML examples of requests and responses. Appendix A, "LitleXML Account Updater Elements" This appendix provides definition of the various LitleXML elements used in Account Updater transaction. viii Document Version: 2.8 XML Release: 9.4

Documentation Set About This Guide Documentation Set For information concerning any Vantiv product/service, please refer to the appropriate manual from the following list: Vantiv iq Reporting and AnalyticsUser Guide Vantiv LitleXML Reference Guide Vantiv Chargeback API Reference Guide Vantiv Chargeback Process Guide Vantiv PayPal Integration Guide Vantiv PayPal Credit Integration Guide Vantiv PayFac API Reference Guide Vantiv PayFac Portal User Guide Vantiv PayPage Integration Guide Vantiv LitleXML Differences Guide Vantiv Scheduled Secure Reports Reference Guide Vantiv Chargeback XML and Support Documentation API Reference Guide (Legacy) Typographical Conventions Table 2 describes the conventions used in this guide. TABLE 2 Convention... Typographical Conventions Meaning Vertical ellipsis points in an example mean that information not directly related to the example has been omitted.... Horizontal ellipsis points in statements or commands mean that parts of the statement or command not directly related to the example have been omitted. < > Angle brackets are used in the following situations: user-supplied values (variables) XML elements [ ] Brackets enclose optional clauses from which you can choose one or more option. bold text Bold text indicates emphasis. Document Version: 2.8 XML Release: 9.4 ix

About This Guide Typographical Conventions TABLE 2 Convention Typographical Conventions Meaning Italicized text blue text Italic type in text indicates a term defined in the text, the glossary, or in both locations. Blue text indicates a hypertext link. x Document Version: 2.8 XML Release: 9.4

Contact Information About This Guide Contact Information This section provides contact information for organizations within Vantiv, LLC. Implementation - For certification and technical issues concerning your implementation of LitleXML. You can call your assigned Implementation Consultant or e-mail to the address below. Implementation Department Contact Information E-mail Cases Hours Available implementation@litle.com Monday Friday, 8:30 a.m. 5:30 p.m. EST Chargebacks - For business-related issues, including questions regarding financial transactions and documentation regarding chargeback cases, contact the Chargebacks Department. Chargebacks Department Contact Information Telephone 978-275-6500 (option 4) E-mail Cases chargebackdocs@litle.com Fax Cases 978-970-3517 Hours Available Monday Friday, 8:30 a.m. 5:30 p.m. EST Technical Publications - For questions or comments about this document, please address your feedback to the Technical Publications Department. All comments are welcome. Technical Publications Contact Information E-mail Tech Pubs@litle.com Document Version: 2.8 XML Release: 9.4 xi

About This Guide Contact Information xii Document Version: 2.8 XML Release: 9.4

1 INTRODUCTION Account Updater is an optional product that allows you to request and receive updated information concerning MasterCard, Visa, and Discover cardholder accounts. This product is used most often by merchants who offer a recurring billing payment plan for their customers. This chapter contains the following sections: Overview of Account Updater Merchant Requirements Technical Requirements Account Updater Workflow Best Practices Document Version: 2.8 XML Release: 9.4 1

Introduction Overview of Account Updater 1.1 Overview of Account Updater The primary users of the Account Updater service are merchants that engage in recurring billing scenarios. This type of billing includes subscription services, membership fees, multi-payment programs, and various preferred customer programs. If you engage in this type of billing, it is inevitable that you receive some percentage of authorization failures each billing period due to changed account information. Normally, someone in your organization would then contact the cardholder to obtain updated information and re-submit the transaction. This ties-up your resources, causes additional expenses, and runs the risk of the cardholder ending the service. Using Account Updater, you can submit a request (a minimum of five days in advance is recommended) for changed card information about the cardholders approaching their billing date. This same process applies if you are a tokenized merchant, except that you would typically supply the token instead of the card number. Each cardholder for which you receive updated information saves you money, time and (potentially) business. NOTE: Since you only pay for matches, you may wish to make requests for larger numbers of cardholders rather than only those approaching their billing date. As a best practice, Vantiv recommends that you cycle through your cardholder database at least twice per year. 1.1.1 Account Updater Features and Limitations Account Updater enables you to receive updated credit card information without having to contact each customer individually. The feature provides updates for the following information: New account number and/or new expiration date (or new token if applicable) Information about accounts transitioning from Visa to MasterCard and vice versa due to bank portfolio migration scenarios. Account closed notification Contact customer notification Account Updater is available for Visa, MasterCard, and Discover payment cards. Other payment types do not participate in this program. Also, Account Updater does not support change of address or AVS updates. NOTE: If you are a tokenized merchant and submit credit card information, the system returns updated credit card information. The system does not register the card and return a token for Account Updater transactions. If you submit a token, the system returns a token. 2 Document Version: 2.8 XML Release: 9.4

Merchant Requirements Introduction 1.2 Merchant Requirements In order to use the Vantiv Account Updater feature, you must first apply for membership to the following (not required by Discover for Vantiv acquired merchants): MasterCard Automatic Billing Updater Visa Account Updater Your Account Updater Welcome Kit includes the required application forms. If you have any questions about these forms, contact your Customer Experieice Manager, who can walk you through the application process. Approval from Visa and MasterCard typically takes between 10-15 business days. Normally, merchants are approved without issue; however, you can be declined for a variety of reasons. For example, merchants on a risk mitigation program typically are not accepted. NOTE: Visa does not allow merchants with SIC numbers 5962, 5966, 5967, or 7995 to participate in their Account Updater service. MasterCard has no restrictions against any specific MCC numbers Document Version: 2.8 XML Release: 9.4 3

Introduction Technical Requirements 1.3 Technical Requirements This section lists Vantiv s technical requirements: Supported Data Format - LitleXML format Supported Data Processing - Batch processing Supported Communication Protocols: FTP using PGP or GPG key encryption (Recommended) sftp Certification Testing - You must pass certification testing for Account Updater transactions. For more details about certification testing, see Chapter 2, "Testing Your Account Updater XML". 4 Document Version: 2.8 XML Release: 9.4

Account Updater Workflow Introduction 1.4 Account Updater Workflow As shown in the following illustration, the Account Updater workflow requires several days. For example, if you submit an Account Updater request on Monday (Day Zero), Vantiv accumulates data from the networks Tuesday through Friday (days 1 through 4), and the completed response would be ready on Saturday (day five). Vantiv processes Account Updater files seven days per week. This section provides an overview of the Account Updater lifecycle. FIGURE 1-1 Account Updater Workflow Day Zero You submit a request containing the relevant customer account numbers and expiration dates to verify. Vantiv immediately returns a confirmation file that contains basic validation information as follows: Approved - indicates the data passed validation. Invalid credit card number - indicates that the card data failed a validation. You must correct the issue and resubmit. Document Version: 2.8 XML Release: 9.4 5

Introduction Account Updater Workflow Invalid expiration date - indicates that the date failed validation. You must correct the issue and resubmit. Vantiv forwards all approved Account Updater transactions to the network. Days One Through Four Each day, the network provides available account data to Vantiv. Vantiv displays this information in iq. The merchant can log into iq to monitor the progress of their account updater transactions. Day Five Vantiv creates a completion response file containing updated account information. You retrieve your response file by logging in to your FTP account. After retrieval, review the completion response file and use the data to update your customer data as necessary. 6 Document Version: 2.8 XML Release: 9.4

Best Practices Introduction 1.5 Best Practices The following is list of best practices concerning your use of the Account Updater feature: Vantiv requires using the FTP file protocol (also see Technical Requirements on page 4). Vantiv requires the submition of Account Updater transactions separate from payment transactions. Because of the total time involved in completing the workflow, you should send the Account Updater request at least six days prior to your normal due date for submitting auth/deposits for recurring transactions. Due to constraints imposed by the credit card networks, the end of the business day for Account Updater submissions is 6:00 p.m. If you send an Account Updater request after 6:00 p.m., Vantiv processes it on the following business day. Because of the end-of-day differences noted above, Vantiv recommends that you gather and send your Account Updater information earlier in the day. This action ensures that the Account Updater workflow process begins on the day sent. 1.5.1 Recommended Session File Size Batch processing involves a group of transactions submitted in a single file. A batch is a set of transactions for a single merchant. In the case of a LitleXML Batch the parent or root element is the <litlerequest> element. A single <litlerequest>, referred to as a Session, can contain many batches and each batch can contain multiple transactions. Normally, you send in a single file which has one batch for each merchant. This works well when the overall number of transactions is small. The number of transactions you should submit in any individual Session or Batch depend on a number of factors, including whether or not you are an individual merchant or a presenter submitting transactions for multiple merchants. In general, you should keep the following recommendations and rules in mind when determining the number of transactions you submit in an Session/Batch file: A Batch should not exceed 20,000 transactions. If the number of transaction for a single merchant exceeds 20,000, you should create multiple batches for the same merchant, each batch containing not more than 20,000 transactions. A Batch should not contain only one transaction, unless the merchant has only one transaction for the day. A Session file must never contain more than 9,999 Batches. A Session file must never contain more than 1,000,000 transactions across all Batches. Always allow sufficient time between your submission time and your cut-off time for the processing of the Session. Larger files take longer to process. Document Version: 2.8 XML Release: 9.4 7

Introduction Best Practices 8 Document Version: 2.8 XML Release: 9.4

2 TESTING YOUR ACCOUNT UPDATER XML This chapter provides information enabling you to verify that your Account Updater templates work correctly and will pass Certification Testing. This chapter contains the following topics: Before You Begin Certification Testing Testing Account Updater Transactions After Completing Certification Testing NOTE: Use the reference material found in Appendix 4, Account Updater LitleXML Examples to verify your coding and LitleXML structure. Document Version: 2.8 XML Release: 9.4 9

Testing Your Account Updater XML Before You Begin Certification Testing 2.1 Before You Begin Certification Testing Certification testing is a required phase of implementing the LitleXML format. The Vantiv testing process involves submitting specified data in a request and receiving specific data back in a response. The data in the request must match the format specified in the LitleXML schema. You should use the response messaged returned to you to verify that your systems correctly parse the Account Updater information. Vantiv assigns an Implementation Consultant to assist you. Your Implementation Analyst will provide the following: Process your IP address (required for access to the test server) Provide a username and password for you to use during testing to access the certification environment Assist at resolving issues during the certification process Feel free to call your Implementation Analyst or email implementation@litle.com for assistance. 10 Document Version: 2.8 XML Release: 9.4

Transferring Files via FTP Testing Your Account Updater XML 2.2 Transferring Files via FTP This section describes how to sftp your files. It is divided into the following topics: Submitting a File for Processing via sftp Retrieving Processed Files via sftp NOTE: Before you begin transferring files via FTP, your Inplementation Consultant provides the FTP Host and a username/password for the Vantiv Pre-Live testing environment. 2.2.1 Submitting a File for Processing via sftp IMPORTANT: File naming conventions are crucial to the submission process. Incorrect file names will prevent the file from being processed. 1. On your own system, add the extension.prg (lowercase) to the name of the file you want to submit. For example, you could name the file MerchantName_YYMMDD.prg. Keep in mind the following rules: Spaces are not allowed in the file name The.prg extension must be lower case 2. Open your FTP connection to the Vantiv inbound directory and move your file to the Vantiv directory. 3. After the ftp process completes, change the extension of the transmitted file (in the Vantiv inbound directory) from.prg to.asc (lowercase). The system polls the directory for files with an.asc extension every thirty seconds. When the system encounters files with the proper extension, it retrieves them for processing. 2.2.2 Retrieving Processed Files via sftp Depending on the size of your file, your response should be ready within a few minutes. Batch files containing large number of transactions take longer. For example, a batch of 10,000 transactions may require as long as ten minutes to process. The initial response represents an acknowledgement that we received the transactions and notification that we will deliver them upstream to Visa and/or MasterCard for review. Since we perform validation operations against the credit card number and the expiration date, it is possible that you also receive decline responses containing the appropriate response code. To retrieve response files from the outbound directory: Document Version: 2.8 XML Release: 9.4 11

Testing Your Account Updater XML Transferring Files via FTP NOTE: Vantiv removes response files from the outbound directory after 24 hours. Plan to retrieve your files daily. 1. Open your FTP connection to the Vantiv outbound directory. 2. Locate the response file, which will have the same name as the submitted file. If the response file has a.prg extension, it is still transferring to the outbound directory and is not ready for retrieval. The extension changes to.asc when the transfer to the outbound directory completes. 3. Retrieve the response file. 12 Document Version: 2.8 XML Release: 9.4

Testing Account Updater Transactions Testing Your Account Updater XML 2.3 Testing Account Updater Transactions All merchants who want to use Account Updater transactions must perform these tests. This process takes approximately one hour. To test Account Updater transactions: 1. Submit Account Updater Requests each orderid using the values in the Supplied Data Elements column of Table 2-1. 2. Verify that the response values for the Account Updater Acknowledgement Response match those shown in the Key Response Elements of Table 2-1. Receiving the matching Acknowledgment Response indicates that your Account Updater Request was properly formatted. 3. (Required only for https submissions) Construct and submit an AU RFR (Account Updater Request for Response) using the information in Account Updater RFR on page 45 as a guide. The system returns and RFR response (see RFR File Processing Response on page 47) indicating that your AU RFR was properly formatted. Failure to receive this file may indicate that the RFR was not properly formatted (Also, see Note below). NOTE: Due to a limitation of the Pre-Live AU simulator, if you submit multiple files in the same hour (e.g., 12:00 PM - 12:59 PM), you will not receive an RFR response. 4. The Pre-Live environment constructs an AU Response file every hour for the requests submitted in the previous hour. For example, the response file created at 1:00 PM contains responses for requests submitted between 12:00 PM and 12:59 PM. Verify that the information contained in the response files matches the AU response informations shown in the Key Response Elements of Table 2-1. NOTE: Once you have begun processing in the production environment, a response file will contain Visa, MasterCard, and Discover information. You will receive one completion response file per day per merchantid. Document Version: 2.8 XML Release: 9.4 13

Testing Your Account Updater XML Testing Account Updater Transactions TABLE 2-1 Account Updater Test Data Supplied Data Elements Key Response Elements orderid Element Value Element Value 1 <type> MC 5194560012341234 1216 Acknowledgement Response: 000 Approved AU File Response: 500 The account number was changed. <updatedcard> (parent element) <type> VI 4457010000000009 0116 <originalcard> (parent element) <type> MC 5194560012341234 1216 2 <type> MC 5435101234510196 0716 Acknowledgement Response: 000 Approved AU File Response: 501 The account was closed. <originalcard> (parent element) <type> MC 5435101234510196 0716 14 Document Version: 2.8 XML Release: 9.4

Testing Account Updater Transactions Testing Your Account Updater XML TABLE 2-1 Account Updater Test Data Supplied Data Elements Key Response Elements orderid Element Value Element Value 3 <type> MC 5112010000000003 0216 Acknowledgement Response: 000 Approved AU File Response: 502 The expiration date was changed. <updatedcard> (parent element) <type> MC 5112010000000003 0118 <originalcard> (parent element) <type> MC 5112010000000003 0216 4 <type> MC 5112002200000008 1116 Acknowledgement Response: 000 Approved AU File Response: 506 No changes found 5 <type> MC 5112000200000002 1116 Acknowledgement Response: 000 Approved AU File Response: 505 No match found Document Version: 2.8 XML Release: 9.4 15

Testing Your Account Updater XML Testing Account Updater Transactions TABLE 2-1 Account Updater Test Data Supplied Data Elements Key Response Elements orderid Element Value Element Value 6 <type> MC 5112010140000004 0216 Acknowledgement Response: 000 Approved AU File Response: 503 The issuing bank does not participate in the update program. 7 <type> MC 5112010100000002 0716 Acknowledgement Response: 000 Approved AU File Response: 301 Invalid account number <originalcard> (parent element) <type> MC 5112010100000002 0716 8 <type> MC 5500000254444445 0316 Acknowledgement Response: 000 Approved AU File Response: 301 Invalid account number <originalcard> (parent element) <type> MC 5500000254444445 0316 16 Document Version: 2.8 XML Release: 9.4

Testing Account Updater Transactions Testing Your Account Updater XML TABLE 2-1 Account Updater Test Data Supplied Data Elements Key Response Elements orderid Element Value Element Value 9 <type> MC 5592106621450897 0316 Acknowledgement Response: 000 Approved AU File Response: 320 Invalid expiration date <originalcard> (parent element) <type> MC 5592106621450897 0316 10 <type> MC 5590409551104142 0316 Acknowledgement Response: 000 Approved AU File Response: 191 Merchant is not registered in the update program. <originalcard> (parent element) <type> MC 5590409551104142 0316 11 <type> MC 5112002100000009 0000 Acknowledgement Response: 320 Invalid expiration date 12 <type> MC 5112000400400018 0210 Acknowledgement Response: 301 Invalid account number Document Version: 2.8 XML Release: 9.4 17

Testing Your Account Updater XML Testing Account Updater Transactions TABLE 2-1 Account Updater Test Data Supplied Data Elements Key Response Elements orderid Element Value Element Value 13 <type> VI 4457010000000009 0116 Acknowledgement Response: 000 Approved AU File Response: 500 The account number was changed. <updatedcard> (parent element) <type> MC 5194560012341234 0216 <originalcard> (parent element) <type> VI 4457010000000009 0116 14 <type> VI 4457000900000001 0816 Acknowledgement Response: 000 Approved AU File Response: 501 The account was closed. <originalcard> (parent element) <type> VI 4457000900000001 0816 18 Document Version: 2.8 XML Release: 9.4

Testing Account Updater Transactions Testing Your Account Updater XML TABLE 2-1 Account Updater Test Data Supplied Data Elements Key Response Elements orderid Element Value Element Value 15 <type> VI 4457000300000007 0115 Acknowledgement Response: 000 Approved AU File Response: 502 The expiration date was changed <updatedcard> (parent element) <type> VI 4457000300000007 0118 <originalcard> (parent element) <type> VI 4457000300000007 0115 16 <type> VI 4457010100000008 0616 Acknowledgement Response: 000 Approved AU File Response: 503 The issuing bank does not participate in the updating program. <originalcard> (parent element) <type> VI 4457010100000008 0616 Document Version: 2.8 XML Release: 9.4 19

Testing Your Account Updater XML Testing Account Updater Transactions TABLE 2-1 Account Updater Test Data Supplied Data Elements Key Response Elements orderid Element Value Element Value 17 <type> VI 4457010140000141 0916 Acknowledgement Response: 000 Approved AU File Response: 504 Contact the cardholder for updated information. <originalcard> (parent element) <type> VI 4457010140000141 0916 18 <type> VI 4457010200000247 0816 Acknowledgement Response: 000 Approved AU File Response: 505 No match found <originalcard> (parent element) <type> VI 4457010200000247 0816 20 Document Version: 2.8 XML Release: 9.4

Testing Account Updater Transactions Testing Your Account Updater XML TABLE 2-1 Account Updater Test Data Supplied Data Elements Key Response Elements orderid Element Value Element Value 19 <type> VI 4100200300011001 0516 Acknowledgement Response: 000 Approved AU File Response: 506 No changes found <originalcard> (parent element) <type> VI 4100200300011001 0516 20 <type> VI 4457000400000006 0000 Acknowledgement Response: 320 Invalid expiration date 21 <type> VI 4457000200400008 0210 Acknowledgement Response: 301 Invalid account number Document Version: 2.8 XML Release: 9.4 21

Testing Your Account Updater XML Testing Account Updater Transactions TABLE 2-1 Account Updater Test Data Supplied Data Elements Key Response Elements orderid Element Value Element Value 22 <type> DI 6011010000000003 0316 Acknowledgement Response: 000 Approved AU File Response: 500 The account number was changed <updatedcard> (parent element) <type> DI 6011102010020228 0316 <originalcard> (parent element) <type> DI 6011010000000003 0316 23 <type> DI 6011010100000002 0816 Acknowledgement Response: 000 Approved AU File Response: 501 The account was closed. <originalcard> (parent element) <type> DI 6011010100000002 0816 22 Document Version: 2.8 XML Release: 9.4

Testing Account Updater Transactions Testing Your Account Updater XML TABLE 2-1 Account Updater Test Data Supplied Data Elements Key Response Elements orderid Element Value Element Value 24 <type> DI 6011010140000004 0816 Acknowledgement Response: 000 Approved AU File Response: 502 The expiration date was changed. <updatedcard> (parent element) <type> DI 6011010140000004 0818 <originalcard> (parent element) <type> DI 6011010140000004 0816 25 <type> DI 6500102012345662 0118 Acknowledgement Response: 000 Approved AU File Response: 506 No changes found <originalcard> (parent element) <type> DI 6500102012345662 0118 Document Version: 2.8 XML Release: 9.4 23

Testing Your Account Updater XML Testing Account Updater Transactions TABLE 2-1 Account Updater Test Data Supplied Data Elements Key Response Elements orderid Element Value Element Value 26 <type> DI 6011102067026227 0118 Acknowledgement Response: 000 Approved AU File Response: 500 The account number was changed. <updatedcard> (parent element) <type> DI 6011010000000006 0118 <originalcard> (parent element) <type> DI 6011102067026227 0118 27 <type> DI 6011102087026223 0118 Acknowledgement Response: 000 Approved AU File Response: 504 Contact the cardholder for updated information. <originalcard> (parent element) <type> DI 6011102087026223 0118 28 <type> DI 6011102087026223 0000 Acknowledgement Response: 320 Invalid expiration date 24 Document Version: 2.8 XML Release: 9.4

Testing Account Updater Transactions Testing Your Account Updater XML TABLE 2-1 Account Updater Test Data Supplied Data Elements Key Response Elements orderid Element Value Element Value 29 <type> DI 6011010140000005 1104 Acknowledgement Response: 301 Invalid account number Document Version: 2.8 XML Release: 9.4 25

Testing Your Account Updater XML After Completing Certification Testing 2.4 After Completing Certification Testing After you successfully complete Account Updater certification testing, Vantiv enables the Account Updater service for your use in the production environment. Vantiv provides you with continuing access to the Post-Live test environment for your convenience. You can use this environment to run any additional testing you deem necessary. 26 Document Version: 2.8 XML Release: 9.4

3 MANAGING CUSTOMER ACCOUNT DATA This chapter explains how to use Account Updater. This chapter contains the following section: Submitting an Account Updater Request Monitoring the Progress of Your Account Updater Transactions Viewing Account Updater Session Data Reviewing Your Account Updater Completion Response File Document Version: 2.8 XML Release: 9.4 27

Managing Customer Account Data Submitting an Account Updater Request 3.1 Submitting an Account Updater Request To start the Account Updater process, you submit an Account Updater batch request for the relevant customer accounts. For technical information about the Account Updater batch request, see Account Updater Batch Request on page 40. 28 Document Version: 2.8 XML Release: 9.4

Account Updater Acknowledgement Response Managing Customer Account Data 3.2 Account Updater Acknowledgement Response When Vantiv receives an Account Updater request, the system immediately returns an acknowledgement file to you. This acknowledgement contains basic validation information shown in Table 3-1. If the response file indicates any errors, you must resolve them and submit corrected information in a new Account Updater request. The Response Code value appears in the element. The Response Message value appears in the element. The Resolution column explains how to correct the account error, if necessary. TABLE 3-1 Account Updater Acknowledgment Response Codes Respo nse Code Response Message Resolution 000 Approved Vantiv forwards these accounts to the network (Visa and MasterCard). 301 Invalid Account Number Correct the account number, and resubmit the card data. 320 Invalid Expiration Date Correct the expiration date, and resubmit the card data. NOTES: Vantiv verifies that the submitted card number is Mod 10 compliant. Vantiv verifies that the date does not contain null or 0000 values. The expiration date must be submitted as MMYY. For technical information about the acknowledgment response file, see Account Updater Acknowledgement Response on page 42. Document Version: 2.8 XML Release: 9.4 29

Managing Customer Account Data Monitoring the Progress of Your Account Updater Transactions 3.3 Monitoring the Progress of Your Account Updater Transactions On days two, three, and four Visa and MasterCard each send a file of updated information to Vantiv. This file contains all of the information that Visa and MasterCard has at the time, so this file may not necessarily include information regarding all of the accounts that were submitted. During this interim period, merchants can log into the UI to monitor the progress of their Account Updater transactions as described in the following section. 3.3.1 Viewing Account Updater Session Data The Session Report provides a real-time view of the Account Updater batches you present for processing. To open the Session Report: 1. From the Reporting page, click Session. 2. Select the Date Range you want to display, and click Recalculate. The Session Report displays as shown in Figure 3-1. FIGURE 3-1 Session Report For information about the Session Report, see Table 3-2. TABLE 3-2 Column Session ID Session Report Columns Description A unique number automatically assigned to each session. To view a session, click the hypertext link that identifies the session you want to view. This is a sortable column. Number of Batches Batch ID The number of batch files transmitted during a session. A unique number automatically assigned to each batch within a session. To view details about a batch, click the hypertext link that identifies the session you want to view. 30 Document Version: 2.8 XML Release: 9.4

Monitoring the Progress of Your Account Updater Transactions Managing Customer Account Data TABLE 3-2 Column Session Report Columns (Continued) Description Session Type Defines the type of file submitted. The possible types are: RFR Account Update Response Normal Online POS Status The transmission status of the incoming files, common types are: Processing (teal dot) Complete (green dot) Error -contact Litle & Co. Technical Support Duplicate (yellow dot) - contact Litle & Co. Technical Support Discarded To view the status details about a batch, click the relevant hypertext link in the Status column. Merchant Name Date Started and Date Finished (Elapsed) Total Auths Sales Refunds Acct. Upd. Txns Identifies the organization for which the file was transmitted. If the session included transactions for more than one merchant, the merchant name appears as Multiple. In this case, click the relevant Session ID to view a list of merchants. Sortable column. Shows the Start and Finish timestamps, as well as elapsed time of the file transmission. Defines the total number of transactions in the session (Count) and the total financial value of the transactions in the session (sum of Auths, Sales, and Refunds Amounts). Count and total amount of authorizations processed. Count and total amount of sales processed. Count and total amount of refunds processed. Defines the number of Account Updater transactions in the session. The Amt (Amount column) always appears as N/A. Document Version: 2.8 XML Release: 9.4 31

Managing Customer Account Data Retrieving Your Account Updater Completion Results 3.4 Retrieving Your Account Updater Completion Results When we receive all responses from Visa and MasterCard, the system creates one or more Account Updater completion response files. This typically occurs five days after the initial Account Updater request. NOTE: It is also possible to review the Account Updater completion results by means of the user interface. For more information, see Reviewing Account Updater Results in the UI on page 34. To obtain your Account Updater completion response files: Retrieving Your Files via FTP 3.4.1 Retrieving Your Files via FTP For merchants using FTP, the Account Updater response file will automatically be placed on the merchants' outbound directory. Merchants using FTP merely need to pick up their response files from their FTP directory as described in Retrieving Processed Files via sftp on page 11. Vantiv assigns a name to the response file using the following format: merchantid. mmddyyyy. sessionid.rfr.asc NOTE: Vantiv purges all files in the FTP directory every 24 hours. You should plan to retrieve your files daily. 32 Document Version: 2.8 XML Release: 9.4

Reviewing Your Account Updater Completion Response File Managing Customer Account Data 3.5 Reviewing Your Account Updater Completion Response File The Account Updater completion response code and its associated message specify whether or not an account number has been changed and what type of change occurred, if any. The Response Code value appears in the element. The Response Message value appears in the element. The Resolution column explains how to update the account number, if needed. You should review the completion response file and update your customer data as indicated in the file. For technical information concerning the completion response file, see RFR File Processing Response on page 47. TABLE 3-3 Account Updater Completion Response Codes Response Code Response Message Resolution 191 The merchant is not registered in the update program 500 The account number was changed Escalate this to your Customer Experience Manager. This indicates a set-up problem that must be resolved prior to submitting another request file. Submit the account number returned in the completion response. 501 The account was closed Contact the cardholder for updated information. 502 The expiration date was changed 503 The issuing bank does not participate in the update program. 504 Contact the cardholder for updated information Submit the expiration date returned in the completion response. Submit the original card information Contact the cardholder for updated information. 505 No match found Submit the original card information 506 No changes found Submit the original card information Document Version: 2.8 XML Release: 9.4 33

Managing Customer Account Data Reviewing Account Updater Results in the UI 3.6 Reviewing Account Updater Results in the UI This section contains the following topics: Viewing Account Updater Batch Contents Viewing Account Updater Info on the Payment Detail Screen 3.6.1 Viewing Account Updater Batch Contents The Batch Contents Report displays a list of the customer accounts contained within a batch. To open the Batch Contents Report: 1. From the Reporting page, click Session. 2. Specify the desired Date Range and click Recalculate. The Session Report displays as shown in Figure 3-1. 3. In the Batch ID column, select the desired Batch ID link. The Batch Contents Report displays as shown in Figure 3-2. 4. In the Batch Contents Report, you can: Adjust how many records display, as described in Browsing Transactions in the Batch Contents Report on page 35. Export the batch contents to Excel, as described in Exporting Account Updater Batch Contents to Excel on page 36. View the details of a payment within the batch, as described in Viewing Account Updater Info on the Payment Detail Screen on page 36. FIGURE 3-2 Batch Contents Report 34 Document Version: 2.8 XML Release: 9.4

Reviewing Account Updater Results in the UI Managing Customer Account Data For details of the Batch Contents Report, see Table 3-4. TABLE 3-4 Field Payment ID Batch Contents Fields Description A unique number automatically assigned to each payment within a batch. # Sequential number of the transaction within the batch. Merchant Order Number Transaction Type Merchant-designated identifier for this transaction. All transactions within the batch are Account Updater transactions. Transaction Amount For Account Updater transactions, this field displays 0.00. Payment Type Account Number Response Reason Message The method used for transferring funds from the customer to the merchant. Typical payment types are credit card, debit card, PayPal, and electronic check. The Payment Method is the transaction used. This is a sortable column. The account number associated with the customer s method of payment. Regardless of your permission level, this report shows only the last four digits of the credit card number. This is a sortable column. The transaction response returned by Vantiv. If the transaction was declined, this message will provide a reason. 3.6.1.1 Browsing Transactions in the Batch Contents Report By default, the Batch Contents report displays 200 records per page, but you can modify this behavior as follows: To specify how many records to display per page do the following: 1. In the Items Per Page field, specify how many records to display per page, up to a maximum of 500 records. 2. Click Apply. The page refreshes, displaying the number of records per page that you specified. 3. To browse from page to page, click the arrows next to the page number in the upper right. Document Version: 2.8 XML Release: 9.4 35

Managing Customer Account Data Reviewing Account Updater Results in the UI 3.6.1.2 Exporting Account Updater Batch Contents to Excel To export a report do the following: 1. Click the Export button/link. 2. In the dialog box choose Open the File. The data opens in Excel. The figure below is an example (full width not shown) of the resulting spreadsheet. See Table 3-4 for definitions of the exported columns. FIGURE 3-3 Exported Session Report 3.6.2 Viewing Account Updater Info on the Payment Detail Screen The Payment Detail screen displays the details regarding a specific credit card. To open the Payment Detail screen do the following: 1. From the Reporting page, click Session Report. 2. Select the Date Range you want to display, and click Recalculate. The Session Report displays as shown in Figure 3-1. 3. In the Batch ID column, click the hypertext link that identifies the batch you want to view. The Batch Contents report displays as shown in Figure 3-2. 4. In the Payment ID column, click the link that identifies the payment you want to view. The Payment Detail screen displays as shown in Figure 3-4. 36 Document Version: 2.8 XML Release: 9.4

Reviewing Account Updater Results in the UI Managing Customer Account Data FIGURE 3-4 Payment Details Screen For definitions of the fields displayed in the Payment Details screen, see Table 3-5. TABLE 3-5 Field Payment Detail Screen Description Transaction Data Txn Type Post Day Amount (USD) Account Updater Response The date the merchant sent the Account Updater request. N/A. Total amount of funds sent within the transaction. For Account Updater transactions, this field displays 0.00. Identifying Information Merchant Merchant Order Number Batch ID Payment ID Batch Type Order Source The merchant associated with the customer s account. Merchant-designated identifier for this transaction. A unique number automatically assigned to each batch within a session. A unique number automatically assigned to each customer account within a batch. Account Updater Response N/A. Document Version: 2.8 XML Release: 9.4 37

Managing Customer Account Data Reviewing Account Updater Results in the UI TABLE 3-5 Field Payment Detail Screen (Continued) Description Card Data Card Type Card Number Exp Date The new card type. The new card number. The new expiration date. Response Data Response Reason Message Response Reason Code AVS Message AVS Code Approval Code STIP Card Validation Message Card Validation Code Explains how the account information has been changed, if applicable. For a list of all possible messages, see Table 3-3. The code that corresponds with the Response Reason Message. For a list of all possible codes, see Table 3-3. N/A. Account Updater does not perform address verification. N/A. Account Updater does not perform address verification. N/A. Account Updater does not perform a purchase Authorization. N/A.Account Updater does not perform STIP functionality. N/A. Account Updater does not perform card security code validation. N/A. Account Updater does not perform card security code validation. 38 Document Version: 2.8 XML Release: 9.4

ACCOUNT UPDATER LITLEXML EXAMPLES 4 This chapter contains information and examples concerning the structure of LitleXML transaction messages used by the Account Updater feature. For definitions of the various element, please refer to Appendix A, "LitleXML Account Updater Elements". This appendix contains the following topics: Account Updater Batch Request Account Updater Acknowledgement Response Account Updater RFR RFR File Processing Response Account Updater Completion Response Document Version: 2.8 XML Release: 9.4 39

Account Updater LitleXML Examples Account Updater Batch Request 4.1 Account Updater Batch Request To begin the Account Updater process, you need to submit an Account Updater batch request. As shown in the examples below, the parent element is <litlerequest>. This element has several attributes and contains the <authenticaton> and <batchrequest> child elements. The <batchrequest> element contains the submitted card or token information as children of the <accountupdate> element. Appendix A provides definitions of each element and/or attribute. Example: Account Updater Request XML Structure You must use the following structure when submitting an Account Updater request. As shown, you can submit the request using either card information or token information. <litlerequest version="8.25" xmlns="http://www.litle.com/schema" id="requestid" numbatchrequests="1"> <authentication> <user>username</user> <password>password</password> </authentication> <batchrequest id="batchid" numaccountupdates="2" merchantid="testmerchant01"> <accountupdate reportgroup"merchant01reportgrpoup"> <orderid>order Id</orderId> <card> <type>card Type</type> Card Number</number> Card Expiration Date</expDate> </card> </accountupdate> <accountupdate reportgroup"merchant01reportgrpoup"> <orderid>order Id</orderId> <token> <litletoken>token Number</litleToken> Card Expiration Date</expDate> </token> </accountupdate> </batchrequest> </litlerequest> 40 Document Version: 2.8 XML Release: 9.4

Account Updater Batch Request Account Updater LitleXML Examples Example: Account Updater Batch Request <litlerequest version="8.25" xmlns="http://www.litle.com/schema" id="requestid" numbatchrequests="2"> <authentication> <user>testorg</user> <password>testorgpassword</password> </authentication> <batchrequest id="batchid" numaccountupdates="02" merchantid="testmerchant01"> <accountupdate reportgroup="merch01reportgrp"> <orderid>merch01-0001</orderid> <card> <type>mc</type> 5151102088487202</number> 1110</expDate> </card> </accountupdate> <accountupdate reportgroup="merch01reportgrp"> <orderid>merch01-0003</orderid> <card> <type>vi</type> 4271125020000039</number> 1211</expDate> </card> </accountupdate> </batchrequest> <batchrequest id="batchid" numaccountupdates="01" merchantid="testmerchant02"> <accountupdate reportgroup="merch02reportgrp"> <orderid>merch02-0001</orderid> <token> <litletoken>1712990000047202</litletoken> 1110</expDate> </token> </accountupdate> </batchrequest> </litlerequest> Document Version: 2.8 XML Release: 9.4 41

Account Updater LitleXML Examples Account Updater Acknowledgement Response 4.2 Account Updater Acknowledgement Response This section provides information concerning the format and elements of an Account Updater acknowledgement response. This section contains the following topics: Account Updater Acknowledgement Response Format Account Updater Acknowledgement Response Codes 4.2.1 Account Updater Acknowledgement Response Format When you submit an Account Updater request, Vantiv returns an acknowledgement response. This response confirms that we have received the request and contains validation information concerning the XML syntax of the request, card numbers, and expiration dates. Figure shows a tree structure view of an Account Updater acknowledgement response. Example: Account Updater Acknowledgement Response XML Structure <litleresponse version="8.25" response="0" message="valid Format" litlesessionid="1700000128"> <batchresponse litlebatchid="1700000136" merchantid="testmerchant01"> <accountupdateresponse reportgroup="merchantreportgroup01"> <litletxnid>transaction Id</litleTxnId> <orderid>order Id</orderId> Response Code</response> <responsetime>date and Time in GMT</responseTime> Response Message</message> </accountupdateresponse> </batchresponse> </litleresponse> As shown in the structure above, the parent element is <litleresponse>. This element has several attributes and can contain one or more <batchresponse> child elements. The <batchresponse> element also has several attributes and can contain one or more <accountupdateresponse> child elements. Appendix A provides definitions of each element and/or attribute. Example: Account Updater Acknowledgement Response <litleresponse version="8.25" response="0" message="valid Format" litlesessionid="1700000128"> <batchresponse litlebatchid="1700000136" merchantid="testmerchant01"> <accountupdateresponse reportgroup="merch01reportgrp"> 42 Document Version: 2.8 XML Release: 9.4

Account Updater Acknowledgement Response Account Updater LitleXML Examples <litletxnid>1100000090</litletxnid> <orderid>merch01-0001</orderid> 000</response> <responsetime>2010-04-11t15:44:25</responsetime> Approved</message> </accountupdateresponse> <accountupdateresponse reportgroup="merch01reportgrp"> <litletxnid>1100000108</litletxnid> <orderid>merch01-0002</orderid> 000</response> <responsetime>2010-04-11t15:44:26</responsetime> Approved</message> </accountupdateresponse> </batchresponse> <batchresponse litlebatchid="1700000138" merchantid="testmerchant02"> <accountupdateresponse reportgroup="merch02reportgrp"> <litletxnid>1100000090</litletxnid> <orderid>merch02-0001</orderid> 000</response> <responsetime>2010-04-11t15:44:25</responsetime> Approved</message> </accountupdateresponse> <accountupdateresponse reportgroup="merch02reportgrp"> <litletxnid>1100000108</litletxnid> <orderid>merch02-0002</orderid> 000</response> <responsetime>2010-04-11t15:44:26</responsetime> Approved</message> </accountupdateresponse> </batchresponse> </litleresponse> 4.2.2 Account Updater Acknowledgement Response Codes As explained above, when Vantiv receives an Account Updater request, we immediately return an acknowledgement file to you. If the response file indicates that there are any errors, you must resolve the issues and submit corrected account information in a new Account Updater request. Table 4-1 provides information concerning the possible contents of the and elements. Document Version: 2.8 XML Release: 9.4 43

Account Updater LitleXML Examples Account Updater Acknowledgement Response TABLE 4-1 Account Updater Acknowledgment Response Codes Response Code Response Message Resolution 000 Approved Vantiv forwards these accounts to the network (Visa and MasterCard). 301 Invalid account number The card number is not valid. Correct the account number and resubmit the card data. 320 Invalid Expiration Date The expiration date is not valid. Correct the expiration date and resubmit the card data. 821 Merchant is not authorized for tokens You are not authorized to use tokens. 822 Token was not found The submitted token was not found in the system. Correct the token number and resubmit. 823 Token was Invalid The submitted token failed validation. Correct the token number and resubmit. 899 Generic token use error There is an unspecified token use error; contact Customer Srevice. 44 Document Version: 2.8 XML Release: 9.4

Account Updater RFR Account Updater LitleXML Examples 4.3 Account Updater RFR The Account Updater RFR (request for response) provides an alternate method of retrieving Account Updater response files for merchants not using the FTP. To allow adequate time for processing by the associations, you should submit the RFR five days after submitting the Account Updater request. Regardless of the number of Account Updater request files submitted each day, Vantiv creates one response file per merchant ID per (fiscal) day. As a result, if you have submitted request files for more than one merchant ID, you need to submit an RFR for each one of those merchant IDs. This section explains the format of an Account Updater RFR request. NOTE: If you submit and retrieve your files via FTP, you do not need to submit an RFR. For additional information concerning the retrieval of response files via FTP, see Retrieving Processed Files via sftp on page 11. 4.3.1 Account Updater RFR Request Format This section provides information concerning the required XML structure of a RFR request. The examples below shows a structure view of an Account Updater RFR request and an actual request. Appendix A provides definitions of each element and/or attribute. Example: RFR Request XML Structure <litlerequest version="8.25" xmlns="http://www.litle.com/schema" id="requestid" numbatchrequests="1"> <authentication> <user>username</user> <password>password</password> </authentication> <RFRRequest> <accountupdatefilerequestdata> <merchantid>merchant ID</merchantId> <postday>post date of AU request</postday> </accountupdatefilerequestdata> </RFRRequest> </litlerequest> Document Version: 2.8 XML Release: 9.4 45

Account Updater LitleXML Examples Account Updater RFR Example: Account Updater RFR Request <litlerequest version="8.25" xmlns="http://www.litle.com/schema" id="requestid" numbatchrequests="0"> <authentication> <user>testorg</user> <password>testorgpassword</password> </authentication> <RFRRequest> <accountupdatefilerequestdata> <merchantid>101</merchantid> <postdate>2010-06-10</postdate> </accountupdatefilerequestdata> </RFRRequest> </litlerequest> 46 Document Version: 2.8 XML Release: 9.4

RFR File Processing Response Account Updater LitleXML Examples 4.4 RFR File Processing Response The file is considered to be incomplete until all data pertaining to the file is received by Vantiv. If you submit an RFR request and the Account Update file is not yet complete, Vantiv sends you the following response: Example: Account Updater RFR not ready Response <litleresponse version="8.25"> <RFRResponse response="1" message="the account update file is not ready yet. Please try again later."> </RFRResponse> </litleresponse> If you receive this response, please re-submit the RFR request. Document Version: 2.8 XML Release: 9.4 47

Account Updater LitleXML Examples Account Updater Completion Response 4.5 Account Updater Completion Response When you send an Account Updater RFR request and the response file is complete, Vantiv returns the Account Updater Completion Response, providing you with updated customer account information including reason codes supplied by the network. You can use this information to update your stored customer account information as needed. Typically, Vantiv generates this file five days after the merchant first submits their Account Updater batch request, which is described in Account Updater Batch Request on page 40. This section contains the following topics: Account Updater Completion Response Format Account Updater Completion Response Codes 4.5.1 Account Updater Completion Response Format The examples that follow show a tree structure view of an Account Updater acknowledgement response and an example response. Appendix A provides definitions of each element and/or attribute. NOTE: If there was no change in the submitted card/token information, the system returns the original card or token information, but the response will not contain the updatedcard or updatedtoken child elements. Example: Account Updater Completion Response XML Structure <litleresponse version="8.25" response="0" message="merchant Fiscal Day: 06102010" litlesessionid="1700000128"> <batchresponse litlebatchid="1700000136" merchantid="testmerchant01"> <accountupdateresponse reportgroup="merchantreportgroup01"> <litletxnid>transaction Id</litleTxnId> <orderid>order Id</orderId> Response Code</response> <responsetime>date and Time in GMT</responseTime> Response Message</message> <originalcard> <type>original Card Type</type> Original Card Number</number> Original Expiration Date</expDate> </originalcard> 48 Document Version: 2.8 XML Release: 9.4

Account Updater Completion Response Account Updater LitleXML Examples <updatedcard> <type>new Card Type</type> New Card Number</number> New Expiration Date</expDate> </updatedcard> </accountupdateresponse> <accountupdateresponse reportgroup="merchantreportgroup01"> <litletxnid>transaction Id</litleTxnId> <orderid>order Id</orderId> Response Code</response> <responsetime>date and Time in GMT</responseTime> Response Message</message> <originaltoken> <litletoken>original Token Number</number> Original Expiration Date</expDate> <type>original Card Type</type> <bin>original BIN</bin> </originaltoken> <updatedtoken> <litletoken>new Token Number</number> New Expiration Date</expDate> <type>new Card Type</type> <bin>original BIN</bin> </updatedtoken> </accountupdateresponse> </batchresponse> </litleresponse> Example: Account Updater Completion Response <litleresponse version="8.25" response="0" message="merchant Fiscal Day: 04192010" litlesessionid="1700008089"> <batchresponse litlebatchid="1700008097" merchantid="merchandid"> <accountupdateresponse reportgroup="test"> <litletxnid>1100019298</litletxnid> <orderid>merch01-0001</orderid> 503</response> <responsetime>2009-09-01t10:24:31</responsetime> Document Version: 2.8 XML Release: 9.4 49

Account Updater LitleXML Examples Account Updater Completion Response The issuing bank does not participate in the update program.</message> <originalcard> <type>vi</type> 4841020582907</number> 1210</expDate> </originalcard> </accountupdateresponse> <accountupdateresponse reportgroup="test"> <litletxnid>1100019264</litletxnid> <orderid>merch01-0002</orderid> 502</response> <responsetime>2009-09-01t10:24:31</responsetime> The expiration date was changed</message> <originalcard> <type>vi</type> 4841020582904077</number> 1109</expDate> </originalcard> <updatedcard> <type>vi</type> 4841020582904077</number> 1111</expDate> </updatedcard> </accountupdateresponse> <accountupdateresponse reportgroup="test"> <litletxnid>1100019249</litletxnid> <orderid>merch01-0003</orderid> 500</response> <responsetime>2009-09-01t10:24:31</responsetime> The account number was changed</message> <originalcard> <type>vi</type> 4841102000050004</number> 1109</expDate> </originalcard> <updatedcard> <type>vi</type> 4841102010003209</number> 1112</expDate> </updatedcard> </accountupdateresponse> <accountupdateresponse reportgroup="test"> 50 Document Version: 2.8 XML Release: 9.4

Account Updater Completion Response Account Updater LitleXML Examples <litletxnid>1100019322</litletxnid> <orderid>merch01-0004</orderid> 500</response> <responsetime>2009-09-01t10:24:31</responsetime> The account number was changed</message> <originaltoken> <litletoken>1741102000080001</litletoken> 1110</expDate> <type>vi</type> <bin>484110</bin> </originaltoken> <updatedtoken> <litletoken>1741102000080216</litletoken> 1111</expDate> <type>vi</type> <bin>484111</bin> </updatedtoken> </accountupdateresponse> </batchresponse> </litleresponse> NOTE: The example above shows both card and token response information to illustrate the xml structures. In practice, you would not receive both token and card information in a response. If you are not using the Vault, you receive only card information; if you are using the Vault, you receive only token information. 4.5.2 Account Updater Completion Response Codes The Account Updater completion response code and its associated message specify whether or not an account number has been changed and what type of change occurred, if any. The Response Code value appears in the element. The Response Message value appears in the element. The Resolution column provides a recommended action. Document Version: 2.8 XML Release: 9.4 51

Account Updater LitleXML Examples Account Updater Completion Response TABLE 4-2 Account Updater Completion Response Codes Response Code Response Message Resolution 191 The merchant is not registered in the update program 500 The account number was changed Escalate this to your Customer Experience Manager. This indicates a set-up problem that must be resolved prior to submitting another request file. Submit the account number returned in the completion response. Note: The response may also indicate that both the account number and expiration date changed. 501 The account was closed Contact the cardholder for updated information. 502 The expiration date was changed 503 The issuing bank does not participate in the update program. 504 Contact the cardholder for updated information Submit the expiration date returned in the completion response. The Issuer does not participate in the Account Updater program. Submit original card information. Contact the cardholder for updated information 505 No match found There was no match found in the updated information. Submit the original card information 506 No changes found Submit the original card information 52 Document Version: 2.8 XML Release: 9.4

A LITLEXML ACCOUNT UPDATER ELEMENTS This chapter provides definitions for the elements and attributes used in LitleXML associated with the Account Updater feature. This information is intended to be used in combination with the various LitleXML schema files to assist you as you build the code necessary to submit Account Updater transactions to our transaction processing systems. Each section defines a particular element, its relationship to other elements (parents and children), as well as any attributes associated with the element. For additional information on the structure of LitleXML requests and responses using these elements, as well as XML examples, please refer to Chapter 4, "Account Updater LitleXML Examples". The XML elements defined in this chapter are listed alphabetically. Document Version: 2.8 XML Release: 9.4 53

LitleXML Account Updater Elements accountupdate A.1 accountupdate The accountupdate element is the parent element for all Account Updater request transactions. You can use this only with Batch transactions. Parent Elements: batchrequest Attributes: Attribute Name Type Required? Description id String No A unique identifier assigned by the presenter and mirrored back in the response. minlength = N/A maxlength = 25 customerid String No A value assigned by the merchant to identify the consumer. minlength = N/A maxlength = 50 reportgroup String Yes Required attribute that defines the merchant sub-group in the user interface where this transaction will be displayed. minlength = 1 maxlength = 25 Child Elements: (Required) orderid, cardortoken (allows the substitution of either the card or token elements) 54 Document Version: 2.8 XML Release: 9.4

accountupdatefilerequestdata LitleXML Account Updater Elements A.2 accountupdatefilerequestdata The accountupdatefilerequestdata element is a child of the RFRRequest element, required when requesting the response file for an Account Updater submission. Parent Elements: RFRRequest Attributes: None Child Elements: Required: merchantid Optional: postday Example: accountupdatefilerequestdata Structure <accountupdatefilerequestdata> <merchantid>merchant ID</merchantId> <postday>post Date</postDay> </accountupdatefilerequestdata> Document Version: 2.8 XML Release: 9.4 55

LitleXML Account Updater Elements accountupdateresponse A.3 accountupdateresponse The accountupdaterresponse element is the parent element for all Account Updater responses transactions. You can use this only with Batch transactions. Parent Elements: batchresponse Attributes: Attribute Name Type Required? Description id String No The response returns the same value submitted in the accountupdate transaction. minlength = N/A maxlength = 25 customerid String No The response returns the same value submitted in the accountupdate transaction. minlength = N/A maxlength = 50 reportgroup String Yes The response returns the same value submitted in the accountupdate transaction. minlength = 1 maxlength = 25 Child Elements: (Required) litletxnid, orderid, response, responsetime, message Child Elements: (Optional) originalcard, updatedcard, originaltoken, updatedtoken 56 Document Version: 2.8 XML Release: 9.4

authentication LitleXML Account Updater Elements A.4 authentication The authentication element is a required element of both the litleonlinerequest and the batchrequest elements. It contains child elements used to authenticate that the XML message is from a valid user. Parent Elements: litleonlinerequest, litlerequest Attributes: None Child Elements: Required: user, password Example: authentication Structure <authentication> <user>user Name</user> <password>password</password> </authentication> Document Version: 2.8 XML Release: 9.4 57

LitleXML Account Updater Elements batchrequest A.5 batchrequest This is the root element for all LitleXML Batch requests. Parent Elements: litlerequest Attributes: NOTE: The xxxamount attributes are required if the associated numxxx attribute is included and greater than 0. For example, if numauths=5 and each Authorization is $10.00, then you must include authamount=5000. Attribute Name Type Required? Description id String No A unique string to identify this batchrequest within the system. minlength = N/A maxlength = 50 numauths Integer No Defines the total count of Authorization transactions in the batchrequest. minlength = N/A maxlength = N/A authamount Integer No Defines the total dollar amount of Authorization transactions in the batchrequest. The decimal point is implied. For example, you enter $25.00 as 2500. totaldigits = 10 numauthreversals Integer No Defines the total count of AuthReversal transactions in the batchrequest. minlength = N/A maxlength = N/A authreversalamount Integer No Defines the total dollar amount of AuthReversal transactions in the batchrequest. The decimal point is implied. For example, you enter $25.00 as 2500. totaldigits = 10 numcaptures Integer No Defines the total count of Capture transactions in the batchrequest. minlength = N/A maxlength = N/A 58 Document Version: 2.8 XML Release: 9.4

batchrequest LitleXML Account Updater Elements Attribute Name Type Required? Description captureamount Integer No Defines the total dollar amount of Capture transactions in the batchrequest. The decimal point is implied. For example, you enter $25.00 as 2500. totaldigits = 10 numcredits Integer No Defines the total count of Credit transactions in the batchrequest. minlength = N/A maxlength = N/A creditamount Integer No Defines the total dollar amount of Credit transactions in the batchrequest. The decimal point is implied. For example, you enter $25.00 as 2500. totaldigits = 10 numforcecaptures Integer No Defines the total count of Force Capture transactions in the batchrequest. minlength = N/A maxlength = N/A forcecaptureamount Integer No Defines the total dollar amount of Force Capture transactions in the batchrequest. The decimal point is implied. For example, you enter $25.00 as 2500. totaldigits = 10 numsales Integer No Defines the total count of Sale transactions in the batchrequest. minlength = N/A maxlength = N/A saleamount Integer No Defines the total dollar amount of Sale transactions in the batchrequest. The decimal point is implied. For example, you enter $25.00 as 2500. totaldigits = 10 numemails (not used at this time) emailamount (not used at this time) Integer No Defines the total count of Email Notification transactions in the batchrequest. minlength = N/A maxlength = N/A Integer No Defines the total dollar amount of Email Notification transactions in the batchrequest. The decimal point is implied. For example, you enter $25.00 as 2500. totaldigits = 10 Document Version: 2.8 XML Release: 9.4 59

LitleXML Account Updater Elements batchrequest Attribute Name Type Required? Description numcapturegivenauths Integer No Defines the total count of Capture Given Auth transactions in the batchrequest. minlength = N/A maxlength = N/A capturegivenauthamount Integer No Defines the total dollar amount of Capture Given Auth transactions in the batchrequest. The decimal point is implied. For example, you enter $25.00 as 2500. totaldigits = 10 numechecksales Integer No Defines the total count of Echeck Sale transactions in the batchrequest. minlength = N/A maxlength = N/A echecksaleamount Integer No Defines the total dollar amount of Echeck Sale transactions in the batchrequest. The decimal point is implied. For example, you enter $25.00 as 2500. totaldigits = 10 numecheckcredit Integer No Defines the total count of Echeck Credit transactions in the batchrequest. minlength = N/A maxlength = N/A echeckcreditamount Integer No Defines the total dollar amount of Echeck Credit transactions in the batchrequest. The decimal point is implied. For example, you enter $25.00 as 2500. totaldigits = 10 numecheckverification Integer No Defines the total count of Echeck Verification transactions in the batchrequest. minlength = N/A maxlength = N/A echeckverificationamount Integer No Defines the total dollar amount of Echeck Verification transactions in the batchrequest. The decimal point is implied. For example, you enter $25.00 as 2500. totaldigits = 10 numecheckredeposit Integer No Defines the total count of echeck Redeposit transactions in the batchrequest. minlength = N/A maxlength = N/A numaccountupdates Integer No Defines the total count of Account Update transactions in the batchrequest. minlength = N/A maxlength = N/A 60 Document Version: 2.8 XML Release: 9.4

batchrequest LitleXML Account Updater Elements Attribute Name Type Required? Description numtokenregistrations Integer No Defines the total count of Token Registration transactions in the batchrequest. minlength = N/A maxlength = N/A merchantid String Yes A unique string to identify the merchant within the system. minlength = N/A maxlength = 50 Child Elements: Required: authentication At least one of the following required:accountupdate, authorization, authreversal, capture, capturegivenauth, credit, echecksale, echeckcredit, forcecapture, sale Document Version: 2.8 XML Release: 9.4 61

LitleXML Account Updater Elements batchresponse A.6 batchresponse The batchresponse element is the parent element for information returned to you in response to a batch you submitted for processing. It is a child of a litleresponse element. Parent Elements: litleresponse Attributes: Attribute Name Type Required? Description id String No In the acknowledgement message, the response returns the same value submitted in the batchrequest. This attribute is not returned in the AU completion response message. minlength = N/A maxlength = 25 litlebatchid Long Yes A unique value assigned by us to identify the batch. minlength = N/A maxlength = 19 merchantid String Yes The response returns the same value submitted in the authorization transaction. minlength = 1 maxlength = 50 Child Elements: Required: accountupdateresponse, authorizationresponse, authreversalresponse, captureresponse, capturegivenauthresponse, creditresponse, echeckcreditresponse, echecksaleresponse, forcecaptureresponse, saleresponse 62 Document Version: 2.8 XML Release: 9.4

bin LitleXML Account Updater Elements A.7 bin The bin element provides the 6-digit Bank (or Issuer) Identification Number of the Issuing Bank. The system returns this value in XML responses when issuing new tokens to replace Visa or MasterCard account numbers. For Discover and American Express cards, this element is empty. Type = String; minlength = 0; maxlength = 6 Parent Elements: The bin element is an optional child of each listed parent element. registertokenresponse, tokenresponse, newcardtokeninfo, originalcardtokeninfo, originaltoken, updatedtoken Attributes: None Child Elements: None Document Version: 2.8 XML Release: 9.4 63

LitleXML Account Updater Elements card A.8 card The card element defines payment card information. It is a required element for most transaction types unless the transaction uses an alternate payment method such as PayPal. It contains one or more child elements depending upon whether the transaction is a card-not-present or a card-present (face-to-face) transaction. Parent Elements: accountupdate, authorization, capturegivenauth, credit, forcecapture, sale Attributes: None Child Elements: For card-not-present transactions and Account Update (Required): type, number, expdate For card-present transactions (Required): track For both transactions types (Optional): cardvalidationnum Example: card Structure - Card-Not-Present <card> <type>card Type Abbreviation</type> Account Number</number> Expiration Date</expDate> <cardvalidationnum>card Validation Number</cardValidationNum> </card> Example: card Structure - Card-Present <card> <track>magnetic Stripe Read</track> </card> 64 Document Version: 2.8 XML Release: 9.4

cardortoken LitleXML Account Updater Elements A.9 cardortoken The cardortoken element an abstract that allows the substitution of either the card or token element. You must specify one of the two substitution elements as a child of the accountupdate element. Parent Elements: accountupdate Substitution Options: card, token Document Version: 2.8 XML Release: 9.4 65

LitleXML Account Updater Elements expdate A.10 expdate The expdate element is a child of the card element, which specifies the expiration date of the card and is required for card-not-present transactions. Type = String; minlength = 4; maxlength = 4 Parent Elements: card, token Attributes: None Child Elements: None 66 Document Version: 2.8 XML Release: 9.4

litlerequest LitleXML Account Updater Elements A.11 litlerequest This is the root element for all LitleXML Batch requests. Parent Elements: None Attributes: Attribute Name Type Required? Description version String Yes Defines the LitleXML schema version against which the XML is validated. The current version is 7.3, but you may be using an older version. minlength = N/A maxlength = 10 xmlns String Yes Defines the URI of the schema definition. This is a fixed location and must be specified as: http://www.litle.com/schema. minlength = N/A maxlength = 38 id String No A unique string to identify the session within the system. minlength = N/A maxlength = 25 numbatchrequests Integer Yes Defines the total number of batchrequest children included in the litlerequest. If the litlerequest contains only an RFRRequest, then set this attribute to 0. Child Elements: Required: authentication One of the following required: batchrequest, RFRRequest Document Version: 2.8 XML Release: 9.4 67

LitleXML Account Updater Elements litleresponse A.12 litleresponse This is the root element for all LitleXML Batch responses. Parent Elements: None Attributes: Attribute Name Type Required? Description version String Yes Defines the LitleXML schema version against which the XML is validated. The current version is 7.3, but you may be using an older version. minlength = N/A maxlength = 10 id String No The response returns the same value submitted in the authorization transaction. minlength = N/A maxlength = 25 response String Yes Indicates whether your XML syntax passed validation. Expected values are as follows: 0 - XML validation succeeded. 1 - XML validation failed. See the message attribute for more details. minlength = N/A maxlength = 3 message String Yes XML validation error message. Expected values are as follows: If the response attribute returns 0, the message attribute returns the text Valid Format. If the response attribute returns 1, the message attribute returns an error message that helps you to identify and troubleshoot the syntax problem. minlength = N/A maxlength = 512 litlesessionid Long Yes A unique value assigned by us to identify the session. minlength = N/A maxlength = 19 Child Elements: One of the following required: batchresponse, RFRResponse 68 Document Version: 2.8 XML Release: 9.4

litletoken LitleXML Account Updater Elements A.13 litletoken The litletoken element defines the value of the token. The system returns this value in XML responses when issuing new tokens to replace account numbers. The length of the token is the same as the length of the submitted account number. Type = String; minlength = 13; maxlength = 25 Parent Elements: The litletoken element is an optional child of each listed parent element. registertokenresponse, and tokenresponse, originaltoken, updatedtoken Attributes: None Child Elements: None Document Version: 2.8 XML Release: 9.4 69

LitleXML Account Updater Elements litletxnid A.14 litletxnid The litletxnid element is used to identify transactions in the system. The system returns this element in XML responses. You use it in various requests to reference the original transaction. For example, when you submit a Capture transaction, you include the litletxnid for the associated Authorization. Type = Long; minlength = N/A; maxlength = 19 Parent Elements: This element is a required child of the following: accountupdateresponse, authorizationresponse, authreversalresponse, capture, captureresponse, credit, creditresponse, capturegivenauthresponse, echeckcredit, echeckcreditresponse, echecksaleresponse, forcecapture, forcecaptureresponse, saleresponse, void, voidresponse This element is an optional child of the following: authorization, echecksale, sale Attributes: None Child Elements: None 70 Document Version: 2.8 XML Release: 9.4

merchantid LitleXML Account Updater Elements A.15 merchantid The merchantid element is a child of the accountupdatefilerequestdata element used when you request an Account Update file. This value is a unique string used to identify the merchant within the system. Type = String; minlength = N/A; maxlength = 50 Parent Elements: accountupdatefilerequestdata Attributes: None Child Elements: None NOTE: Several elements use merchantid as an attribute, including batchrequest, batchresponse, and litleonlinerequest. Document Version: 2.8 XML Release: 9.4 71

LitleXML Account Updater Elements message A.16 message The message element contains a brief definition of the response code returned for the transaction. For a complete list of response codes and associated messages, please refer to the Vantiv LitleXML Reference Guide. Type = String; minlength = N/A; maxlength = 512 Parent Elements: accountupdateresponse, authorizationresponse, captureresponse, capturegivenauthresponse, creditresponse, echeckcreditresponse, echecksaleresponse, forcecaptureresponse, saleresponse, voidresponse Attributes: None Child Elements: None 72 Document Version: 2.8 XML Release: 9.4

number LitleXML Account Updater Elements A.17 number The number element is a required child of the card element, used for card-not-present transactions and Account Update transactions. It is also an optional child of the accountinformation element, used in Authorization and Sale responses. It defines the account number associated with the transaction. Type = String; minlength = 13; maxlength = 25 Parent Elements: accountinformation, card Attributes: None Child Elements: None Document Version: 2.8 XML Release: 9.4 73

LitleXML Account Updater Elements orderid A.18 orderid The orderid element defines a merchant-assigned value representing the order in the merchant s system. Type = String; minlength = N/A; maxlength = 25 Parent Elements: accountupdate, accountupdateresponse, authorization, authorizationresponse, captureresponse, credit, creditresponse, capturegivenauth, capturegivenauthresponse, echeckcredit, echeckcreditresponse, echecksale, echecksaleresponse, forcecapture, forcecaptureresponse, sale, saleresponse, registertokenrequest Attributes: None Child Elements: None 74 Document Version: 2.8 XML Release: 9.4

originalcard LitleXML Account Updater Elements A.19 originalcard The originalcard element is an optional child of the accountupdateresponse element, which contains child elements providing the original information for the submitted card. Parent Elements: accountupdateresponse Attributes: None Child Elements: type, number, expdate Example: originalcard Structure <originalcard> <type>card Type</type> Old Account Number</number> Old Expiration Date</expDate> </originalcard> Document Version: 2.8 XML Release: 9.4 75

LitleXML Account Updater Elements originaltoken A.20 originaltoken The originaltoken element is an optional child of the accountupdateresponse element, which contains child elements providing the original information for the submitted token. Parent Elements: accountupdateresponse Attributes: None Child Elements: litletoken, expdate, type, bin Example: originalcard Structure <originaltoken> <litletoken>old Token Number</litleToken> Old Expiration Date</expDate> <type>card Type</type> <bin>card BIN</bin> </originaltoken> 76 Document Version: 2.8 XML Release: 9.4

password LitleXML Account Updater Elements A.21 password The password element is a required child of the authentication element. It is used in combination with the user element to authenticate that the message is from a valid source. Type = String; minlength = N/A; maxlength = 20 Parent Elements: authentication Attributes: None Child Elements: None Document Version: 2.8 XML Release: 9.4 77

LitleXML Account Updater Elements postday A.22 postday The postday element is an optional child of the accountupdatefilerequestdata element that defines the date you submitted the Account Updater request. The format is YYYY-MM-DD. NOTE: This is also the same date that we created the Account Updater acknowledgement file. Type = Date; minlength = N/A; maxlength = 10 Parent Elements: accountupdatefilerequestdata Attributes: None Child Elements: None 78 Document Version: 2.8 XML Release: 9.4

response LitleXML Account Updater Elements A.23 response The response element contains a three digit numeric code which specifies either that the transaction is approved (000 code) or declined. The message element provides a brief definition of the response code. For a complete list of response codes and associated messages, please refer to Appendix Aof the Vantiv LitleXML Reference Guide. Type = String; minlength = N/A; maxlength = 3 Parent Elements: accountupdateresponse, authorizationresponse, authreversalresponse, captureresponse, capturegivenauthresponse, creditresponse, echecksaleresponse, echeckcreditresponse, forcecaptureresponse, registertokenresponse saleresponse, voidresponse Attributes: None Child Elements: None Document Version: 2.8 XML Release: 9.4 79

LitleXML Account Updater Elements responsetime A.24 responsetime The responsetime element provides a date/time stamp of the response. The format of the element is YYYY-MM-DDTHH:MM:SS. For example, 2009-12-21T11:37:04. Type = String; minlength = N/A; maxlength = 19 Parent Elements: accountupdateresponse, authorizationresponse, authreversalresponse, captureresponse, capturegivenauthresponse, creditresponse, echecksaleresponse, echeckcreditresponse, forcecaptureresponse, registertokenresponse saleresponse, voidresponse Attributes: None Child Elements: None 80 Document Version: 2.8 XML Release: 9.4

RFRRequest LitleXML Account Updater Elements A.25 RFRRequest The RFRRequest element is an optional child of a litlerequest element. You can use this type of request in one of two ways. To request a session response from a previously processed litlerequest, include the litlesessionid child. The resulting RFR response will duplicate the original session response associated with the litlesessionid. The session ID returned in the response will be the session ID of the original session. To request an Account Updater completion response file, include the accountupdatefilerequestdata element. If the completion file is ready, it is returned. If the completion file is not ready, you receive an RFRResponse message with the response attribute set to 1 and the message attribute reading, The account Update file is not ready yet. Please try again later. Parent Elements: litlerequest Attributes: None Child Elements: (Choice of) litlesessionid or accountupdatefilerequestdata Example: RFRRequest Structure - Batch <RFRRequest> <litlesessionid>session ID</litleSessionId> </RFRRequest> Example: RFRRequest Structure - Account Updater <RFRRequest> <accountupdatefilerequestdata> <merchantid>merchant ID</merchantId> <postday>post Date</postDay> </accountupdatefilerequestdata> </RFRRequest> Document Version: 2.8 XML Release: 9.4 81

LitleXML Account Updater Elements RFRResponse A.26 RFRResponse The RFRResponse element is an optional child of a litleresponse element returned in response to a RFRRequest. Parent Elements: litleresponse Attributes: Attribute Name Type Required? Description response String Yes The RFR Response Code indicating the result of the RFR request. minlength = N/A maxlength = 3 message String Yes A brief definition of the response code returned for this transaction. minlength = N/A maxlength = 512 Child Elements: None 82 Document Version: 2.8 XML Release: 9.4

token LitleXML Account Updater Elements A.27 token The token element replaces the card element in tokenized transactions and defines the tokenized payment card information. Parent Elements: authorization, capturegivenauth, credit, forcecapture, sale, accountupdate Attributes: None Child Elements: Required: litletoken Optional: expdate, cardvalidationnum Document Version: 2.8 XML Release: 9.4 83

LitleXML Account Updater Elements type A.28 type This type element defines the type of account used in the transaction in terms of card association, card company, Bill Me Later, or PayPal. From an Account Updater perspective, MC, VI, and DI are the only valid enumerations. NOTE: Please refer to the Vantiv LitleXML Reference Guide for information about other uses of the type element. Type = String (Enum); minlength = N/A; maxlength = 2 Parent Elements: accountinformation, originalcard, updatedcard, registertokenresponse, tokenresponse, card, originaltoken, updatedtoken Attributes: None Child Elements: None Enumerations: (Only VI, MC, and DI valid for Account Updater) Enumeration MC VI AX DC DI PP JC BL Description MasterCard Visa American Express Diner s Club Discover PayPal JCB (Japanese Credit Bureau) Bill Me Later (empty) Card type unknown or undefined 84 Document Version: 2.8 XML Release: 9.4

updatedcard LitleXML Account Updater Elements A.29 updatedcard The updatedcard element is an optional child of the accountupdateresponse element, which contains child elements providing the updated information for the submitted card. Parent Elements: accountupdateresponse Attributes: None Child Elements: type, number, expdate Example: originalcard Structure <updatedcard> <type>card Type</type> New Account Number</number> New Expiration Date</expDate> </updatedcard> NOTE: The updatedcard element may also contain the value of N/A for the type, number, and expdate element. Document Version: 2.8 XML Release: 9.4 85

LitleXML Account Updater Elements updatedtoken A.30 updatedtoken The updatedtoken element is an optional child of the accountupdateresponse element, which contains child elements providing the updated information for the submitted token. Parent Elements: accountupdateresponse Attributes: None Child Elements: litletoken, expdate, type, bin Example: originalcard Structure <updatedtoken> <litletoken>new Token Number</litleToken> New Expiration Date</expDate> <type>card Type</type> <bin>card BIN</bin> </updatedtoken> NOTE: The updatedtoken element may also contain the value of N/A for the litletoken, expdate, and type elements. 86 Document Version: 2.8 XML Release: 9.4

user LitleXML Account Updater Elements A.31 user The user element is a required child of the authentication element. It is a unique identifier of the user/merchant used to authenticate that the message is from a valid source. Type = String; minlength = N/A; maxlength = 20 Parent Elements: authentication Attributes: None Child Elements: None Document Version: 2.8 XML Release: 9.4 87

LitleXML Account Updater Elements user 88 Document Version: 2.8 XML Release: 9.4

Index A Account Updater Acknowledge Response format, 42 acknowledgement response, 29 Acknowledgement Response Code, 43 best practices, 7 Completion Response Code, 51 Completion Response format, 48 completion results, 32 features, 2 monitoring progress, 30 request submission, 28 required tests, 13 RFR Request format, 45 viewing Batch contents, 34 workflow, 5 accountupdate, 54 accountupdatefilerequestdata, 55 accountupdaterresponse, 56 authentication, 57 B Batch contents exporting, 36 viewing, 34 batchrequest, 58 batchresponse, 62 bin, 63 C card, 64 cardortoken, 65 completion results retrieving, 32 E expdate, 66 F L file retrieval, 11 file submission, 11 litlerequest, 67 litleresponse, 68 litletoken, 69 litletxnid, 70 M Merchant Requirements, 3 merchantid, 71 message, 72 N number, 73 O orderid, 74 originalcard, 75 P password, 77 postday, 78 R required tests, 13 requirements merchant, 3 technical, 4 response, 79 Response Codes acknowledgement, 43 completion, 51 responsetime, 80 RFRRequest, 81 RFRResponse, 82 FTP Document Version: 2.8 XML Release: 9.4 89

Index S Session Report opening, 30 T Technical Requirements, 4 testing, 13 token, 83 type, 84 RFRRequest, 81 RFRResponse, 82 token, 83 type, 84 updatedcard, 85 updatedtoken, 86 user, 87 U updatedcard, 85 updatedtoken, 86 user, 87 X xml acknowledge response format, 42 completion response format, 48 RFR request format, 45 XML elements accountupdate, 54 accountupdatefilerequestdata, 55 accountupdaterresponse, 56 authentication, 57 batchrequest, 58 batchresponse, 62 bin, 63 card, 64 cardortoken, 65 expdate, 66 litlerequest, 67 litleresponse, 68 litletoken, 69 litletxnid, 70 merchantid, 71 message, 72 number, 73 orderid, 74 originalcard, 75 password, 77 postday, 78 response, 79 responsetime, 80 90 Document Version: 2.8 XML Release: 9.4