Skipjack Integration Guide

Skipjack Integration Guide

2009 Skipjack Financial Services


Table of ContentsAbout this Document ............................................................................................................................. 9Copyright Notice ................................................................................................................................................................. 9 Trademark Notice ............................................................................................................................................................... 9 Interchange Qualifications and Transaction Rates ............................................................................................................. 9 Publication History ............................................................................................................................................................ 10 Documentation Conventions............................................................................................................................................. 12 Definitions of Variable Types ........................................................................................................................................ 13 Permitted Syntax for Variable Fields ............................................................................................................................ 13 Obtaining Additional Information....................................................................................................................................... 13 Obtaining Referenced Documents ............................................................................................................................... 14 Contacting Skipjack Financial Services ............................................................................................................................ 14 Obtaining a Developer Account with Skipjack Financial Services.................................................................................... 14 Obtaining a Merchant Account from a Financial Institution .............................................................................................. 14

Getting Started: Application Development Lifecycle ........................................................................... 15Overview: Recommended Development Process ............................................................................................................ 15 Payment Processors Supported by Skipjack Financial Services ..................................................................................... 16 Payment Processor Information for Canadian Merchant Accounts and Payment Processors ........................................ 17

Connection Types ............................................................................................................................... 18Direct Skipjack API Posts ................................................................................................................................................. 18 Installed API Posts ............................................................................................................................................................ 18 Batch Posts ....................................................................................................................................................................... 18

Level I, II, III Card Data Transaction Overview.................................................................................... 19Level I Transactions .......................................................................................................................................................... 19 Level II Transactions ......................................................................................................................................................... 19 Example of Level II Data Request String ..................................................................................................................... 20 Level III Transactions ........................................................................................................................................................ 20 Example of Level III Data Request String .................................................................................................................... 21

Core & Supplementary Transaction Methods ..................................................................................... 22Core Methods ................................................................................................................................................................... 22 Supplementary Methods ................................................................................................................................................... 22

Authorize and AuthorizeAPI Methods ................................................................................................. 23Authorize ........................................................................................................................................................................... 23 Post-Back Locations for Authorize Method .................................................................................................................. 23 AuthorizeAPI ..................................................................................................................................................................... 23 Transaction Requests for Authorize and AuthorizeAPI .................................................................................................... 23 Details for Submitting Transaction Requests for Authorize and AuthorizeAPI ............................................................ 23 Request Variables for Authorize and AuthorizeAPI Methods....................................................................................... 24 Transaction Examples for Authorize and Authorize API Methods.................................................................................... 38 Request Example 1: Authorize ..................................................................................................................................... 38 Response Example 1: Authorize .................................................................................................................................. 39 Request Example 2: AuthorizeAPI ............................................................................................................................... 39 Response Example 2: AuthorizeAPI ............................................................................................................................ 39 Request Example 3: TSYS Credit Card Balance Inquiry ............................................................................................. 40 Response Example 3: TSYS Credit Card Balance Inquiry .......................................................................................... 40 Response Variables for Authorize and AuthorizeAPI Methods ........................................................................................ 41 Response Variables for Authorize and AuthorizeAPI Methods .................................................................................... 41 Response Variables Returned when ResponseFlags Variable Sent in Transaction Request..................................... 48 szPOSEntryMode Return Variable Values by Position ................................................................................................ 53 Example Using ResponseFlags Request Variables ......................................................................................................... 54 Example 1 ..................................................................................................................................................................... 54 Example 2 ..................................................................................................................................................................... 54 Development Notes for AuthorizeAPI Response Handling .............................................................................................. 55

Page 2



Annotated Examples for Authorize and AuthorizeAPI ......................................................................... 56Assumptions ..................................................................................................................................................................... 56 Example 1: Authorization Successful for a Basic Credit Card Transaction ...................................................................... 56 Interpretation ..................................................................................................................................................................... 56 Example 2: Authorization Decline for a Basic Transaction ............................................................................................... 58 Interpretation ..................................................................................................................................................................... 58 Example 3: Authorization Failure for a Basic Transaction ................................................................................................ 59 Interpretation ..................................................................................................................................................................... 59 Example 4: Authorization Successful with AVS Filtering Off ............................................................................................ 60 Interpretation ..................................................................................................................................................................... 60 Example 5: Authorization Successful with AVS Filtering On ............................................................................................ 61 Interpretation ..................................................................................................................................................................... 61 Example 6: Authorization Failed with AVS Filtering On.................................................................................................... 62 Interpretation ..................................................................................................................................................................... 62 Example 7: Authorization Successful with CVV matching for Visa and MasterCard ....................................................... 63 Interpretation ..................................................................................................................................................................... 63 Example 8: Authorization Failure with CVV not matching for Visa and MasterCard ........................................................ 64 Interpretation ..................................................................................................................................................................... 64 Example 9: Authorization Success with CVV matching for Amex or Discover ................................................................. 65 Interpretation ..................................................................................................................................................................... 65 Example 10: Authorization Failure because of CVV not matching for Amex or Discover ................................................ 66 Interpretation ..................................................................................................................................................................... 66

Get Transaction Status Method .......................................................................................................... 67Description.................................................................................................................................................................... 67 When Used ................................................................................................................................................................... 67 See Also ....................................................................................................................................................................... 67 Transaction Variables for the Get Transaction Status Method ......................................................................................... 67 Details for Submitting Get Transaction Status Method Requests ................................................................................ 67 Request Variables for Get Transaction Status ................................................................................................................. 68 Response Variables for Get Transaction Status .............................................................................................................. 69 Interpreting the Get Transaction Status Response Messages .................................................................................... 69 Examples for Get Transaction Status Method .................................................................................................................. 72 Request Example 1: Get Transaction Status Method specifying szDate..................................................................... 72 Response Example 1: Get Transaction Status specifying szDate ............................................................................... 72 Request Example 2: Get Transaction Status Method specifying szOrderNumber ...................................................... 73 Response Example 2: Get Transaction Status specifying szOrderNumber ................................................................ 73

Change Transaction Status Method.................................................................................................... 74Description.................................................................................................................................................................... 74 When Used ................................................................................................................................................................... 74 Change Status Functionality Matrix.............................................................................................................................. 75 See Also ....................................................................................................................................................................... 76 Details for Submitting Change Transaction Status Method Requests ......................................................................... 76 Transaction Requests for Change Transaction Status Method........................................................................................ 77 Development Notes for Change Transaction Status Method ....................................................................................... 97 Response Variables for the Change Transaction Status Method .................................................................................... 98 Interpreting the Change Transaction Status Response Records ................................................................................. 98 Examples for Change Transaction Status Method ......................................................................................................... 102 Request Example 1: Change Transaction Status: Credit Specifying szOrderNumber (Error)................................ 102 Response Example 1: No Records Found for Order Number (Error) ........................................................................ 102 Request Example 2: Change Transaction Status (Error - Incorrect Amount for Credit) ............................................ 102 Response Example 2: Change Transaction Status (Error- Incorrect Amount for Credit) .......................................... 103 Request Example 3: Change Transaction Status SplitSettle specifying szOrderNumber ...................................... 103 Response Example 3: Change Transaction Status SplitSettle ............................................................................... 103 Request Example 4: Change Transaction Status Credit specifying szOrderNumber ............................................. 103 Response Example 4: Change Transaction Status Credit Error: Status Mismatch ................................................ 103

Page 3



Request Example 5: Change Transaction Status Split Settle specifying szOrderNumber ..................................... 104 Response Example 5: Change Transaction Status Successful: Split Settle........................................................... 104 Request Example 6a and 6b: Change Transaction Status: Authorize ....................................................................... 104 Request Example 7: ChangeStatus:CreditEx ............................................................................................................ 105 Response Example 7: ChangeStatus:CreditEx ......................................................................................................... 105 Request Example 8: Change Transaction Status: AuthorizeAdditionalEx ................................................................. 105 Response Example 8: ChangeStatus: AuthorizeAdditionalEx ................................................................................... 105

Supplemental Transaction Methods.................................................................................................. 106 Recurring Payments Overview.......................................................................................................... 107Description .................................................................................................................................................................. 107 Development Notes about Recurring Payments Transactions .................................................................................. 107 Recurring Payment Methods; ..................................................................................................................................... 108 See Also: .................................................................................................................................................................... 108

Add Recurring Payment Method ....................................................................................................... 109When Used ................................................................................................................................................................. 109 Submitting Requests for Add Recurring Payments .................................................................................................... 109 See Also ..................................................................................................................................................................... 109 Transaction Requests for the Add Recurring Payments Method ................................................................................... 109 Transaction Responses for Add Recurring Payments Method ...................................................................................... 114 Interpreting the Response Records for Add Recurring Payments Method ................................................................ 114 Response Records Variables for Add Recurring Payments Method ......................................................................... 114 Examples for Add Recurring Payments Method............................................................................................................. 115 Request Example 1: Add Recurring Payments Request ........................................................................................... 115 Response Example 1: Add Recurring Payments Records Successful ................................................................... 115 Request Example 2: Add Recurring Payments Request ........................................................................................... 116 Response Example 2: Add Recurring Payments Records Error: Starting Date ..................................................... 116

Edit Recurring Payments Method ..................................................................................................... 117When Used ................................................................................................................................................................. 117 Submitting Requests for Edit Recurring Payments .................................................................................................... 117 See Also ..................................................................................................................................................................... 117 Transaction Requests for Edit Recurring Payments Method ......................................................................................... 117 Transaction Responses for Edit Recurring Payments Method ....................................................................................... 121 Interpreting the Response Records for Edit Recurring Payments Method ................................................................ 121 Response Records (Header Record) Variables for Edit Recurring Payments Method ............................................. 121 Examples for Edit Recurring Payments Method ............................................................................................................. 122 Request Example 1: Edit Recurring Payments Request............................................................................................ 122 Response Example 1: Edit Recurring Payments Success...................................................................................... 122 Request Example 2: Edit Recurring Payments .......................................................................................................... 123 Response Example 2: Edit Recurring Payments Error: Missing szPaymentId ....................................................... 123

Delete Recurring Payment Method ................................................................................................... 124Submitting Requests for Delete Recurring Payment Method..................................................................................... 124 See Also ..................................................................................................................................................................... 124 Transaction Requests for Delete Recurring Payment Method ....................................................................................... 124 Transaction Responses for Delete Recurring Payments Method .................................................................................. 125 Interpreting the Response Records for Delete Recurring Payments Method ............................................................ 125 Response Records (Header Record) Variables for Delete Recurring Payments ...................................................... 126 Examples for Delete Recurring Payment Method .......................................................................................................... 126 Request Example 1: Delete Recurring Payments Request specifying szPaymentId ................................................ 126 Response Example 1: Delete Recurring Payment specifying szPaymentId Successful ........................................ 126 Request Example 2: Delete Recurring Payments Request specifying szTransactionDate ....................................... 127 Response Example 2: Delete Recurring Payment specifying szTransactionDate ................................................. 127 Successful .................................................................................................................................................................. 127 Request Example 3: Delete Recurring Payments Request specifying szTransactionDate ....................................... 127 Response Example 3: Delete a Recurring Payment Error: Failed Deleting............................................................ 127

Page 4



Get Recurring Payment Information Method ..................................................................................... 128Description.................................................................................................................................................................. 128 When Used ................................................................................................................................................................. 128 See Also ..................................................................................................................................................................... 128 Transaction Requests for Get Recurring Payment Information ...................................................................................... 128 Submitting Requests for Get Recurring Payment Information ................................................................................... 128 Transaction Requests for Get Recurring Payments Method .......................................................................................... 128 Transaction Response for Get Recurring Payment Information ..................................................................................... 129 Interpreting the Response Records for Get Recurring Payment Information Method ............................................... 129 Status Records (Header Record) Variables for Get Recurring Payment Information Method................................... 130 Interpreting the Response Records (Data Records) for Get Recurring Payment Information Method ...................... 131 Response Records (Data Records) returned for Get Recurring Payment Method Information Method ................... 131 Examples for Get Recurring Payment Information Method ............................................................................................ 134 Request Example 1: Get Recurring Payments Request specifying szTransactionDate............................................ 134 Response Example 1: Get Recurring Payment Information specifying szTransactionDate ...................................... 134 Request Example 2: Get Recurring Payments Request specifying szPaymentId ..................................................... 135 Response Example 2: Get Recurring Payment Information specifying szPaymentId Success.............................. 135 Request Example 3: Get Recurring Payments Request specifying szPaymentId ..................................................... 135 Response Example 3: Get Recurring Payment Information Error: No Records Found .......................................... 135

Transaction Settlement Methods ...................................................................................................... 136Available Only Though Merchant Services ................................................................................................................ 136 Performed using Batch Settlement API Methods ....................................................................................................... 136

Close Current Open Batch Method ................................................................................................... 137Description.................................................................................................................................................................. 137 When Used ................................................................................................................................................................. 137 See Also ..................................................................................................................................................................... 137 Submitting Requests for the Close Current Open Batch Method .............................................................................. 137 Transaction Request Variables for Close Current Open Batch Method .................................................................... 138 Interpreting the Transaction Responses for the Close Current Open Batch Method ................................................ 138 Request Example 1: Close Current Open Batch Method........................................................................................... 139 Response Example 1: Close Current Open Batch Method Success ...................................................................... 139 Request Example 2: Close Current Open Batch Method........................................................................................... 139 Response Example 2: Close Current Open Batch Method Error (Parameter Missing) .......................................... 140

Get Batch Settlement Status Method ................................................................................................ 141Description.................................................................................................................................................................. 141 When Used ................................................................................................................................................................. 141 Submitting Requests for the Get Batch Settlement Status Method ........................................................................... 141 Transaction Request Variables for the Get Batch Settlement Status Method ............................................................... 142 Transaction Responses for the Get Batch Settlement Status Method ........................................................................... 143 Transaction Responses for the Get Batch Settlement Status Method ....................................................................... 143 Request Example 1: Get Batch Settlement Status Method ....................................................................................... 146 Response Example 1 : Get Batch Settlement Status Method Success .................................................................. 146 Request Example 2: Get Batch Settlement Status Method ....................................................................................... 146 Response Example 2: Get Batch Settlement Status Method Failure ..................................................................... 146

Batch File Methods for Transaction Processing ................................................................................ 147When Used ................................................................................................................................................................. 147 Mechanisms Supported for Batch File Uploads ......................................................................................................... 147 How Batch Upload Files are Processed and Queued ................................................................................................ 147 Enabling Batch File Processing Privileges on a Merchant Account........................................................................... 148 Development and Usage Notes for Batch Uploading Methods .................................................................................. 148 Workflow for Processing Batch Upload Files ............................................................................................................. 148 Transaction Requests for Batch File Uploads ................................................................................................................ 149 Formatting Requirements of Name-Value Pairs by Batch Method Type........................................................................ 150 Formatting Examples by Method Types ......................................................................................................................... 150 Formatting for Batch Authorization Method Request ................................................................................................. 150

Page 5



Formatting for Get Transaction Status Method Request............................................................................................ 151 Formatting for Change Transaction Status Request .................................................................................................. 151 Formatting for Add Recurring Payments Request ..................................................................................................... 151 Formatting for Edit Recurring Payments .................................................................................................................... 152 Formatting for Delete Recurring Payments ................................................................................................................ 152 Transaction Responses for Batch Upload Methods ....................................................................................................... 152

Check Batch File Status Method ....................................................................................................... 153Description.................................................................................................................................................................. 153 When Used ................................................................................................................................................................. 153 See Also ..................................................................................................................................................................... 153 Details for Submitting Transaction Requests for Check Batch File Status Method ................................................... 153 Transaction Requests for Check Batch File Status Method ........................................................................................... 153 Transaction Response for Check Batch File Status Method .......................................................................................... 155 Request Example 1: Check Batch File Status Specifying Date Range ..................................................................... 157 Response Example 1: Check Batch File Status ......................................................................................................... 157

Modify Batch File Status Method ...................................................................................................... 158Description.................................................................................................................................................................. 158 When Used ................................................................................................................................................................. 158 Transaction Requests for Modify Batch File Status Method .......................................................................................... 158 Request Variables for Modify Batch File Status Method ............................................................................................ 158 Transaction Response for Modify Batch File Status Method ......................................................................................... 159 Request Example 1: Modify Batch File Status ........................................................................................................... 160 Response Example 1: Modify Batch File Status Success....................................................................................... 160 Request Example 2: Modify Batch File Status ........................................................................................................... 160 Response Example 2 Modify Batch File Status Error ............................................................................................. 160

Get Batch File Response Method ..................................................................................................... 161Description.................................................................................................................................................................. 161 Request Variables for Get Batch File Response Method ............................................................................................... 161 Transaction Responses for Get Batch File Response Batch Authorize Transactions ................................................ 162 Get Batch File Transaction Response for Batch Authorize Transactions ...................................................................... 162 Response Example 1: Get Batch File Response for Batch Authorization No Errors .............................................. 162 Example 2: Batch Authorization Response String Error ......................................................................................... 162

Echo Utility ........................................................................................................................................ 163When Used ................................................................................................................................................................. 163 Details for Submitting an Echo Utility Request ........................................................................................................... 163 Transaction Requests for the Echo Utility ...................................................................................................................... 163 Transaction Responses for the Echo Utility .................................................................................................................... 164 Response Example: Authorize using the Debugging Utility ....................................................................................... 164

Debugging Utility ............................................................................................................................... 165When Used ................................................................................................................................................................. 165 Details for Submitting a Debugging Utility Request ................................................................................................... 165 Transaction Requests for Debugging Utility ................................................................................................................... 165 Transaction Responses for Debugging Utility ................................................................................................................ 165 Response Example: Authorize using the Debugging Utility ....................................................................................... 165

Authorization Logic and Appropriate Failsafe Mechanisms .............................................................. 166See Also ..................................................................................................................................................................... 168

Scenarios .......................................................................................................................................... 169Scenario 1: Split Authorization Scenario ........................................................................................................................ 169 Scenario 2: Refunds and Voids Scenario ....................................................................................................................... 174 Scenario 3: Recurring Payments Scenario ..................................................................................................................... 176 Scenario 4: Batch Settlement Scenario .......................................................................................................................... 179 Scenario 5: Batch File Upload Scenario ......................................................................................................................... 180 Re-Authorization Scenarios ............................................................................................................................................ 182 Usage Notes Regarding the Following Scenarios:..................................................................................................... 182

Page 6



Scenario 6A Authorize Original Amount, Settle Different Amount............................................................................... 183 Advantages ................................................................................................................................................................. 183 Disadvantages ............................................................................................................................................................ 183 Scenario 6B Authorize Original Amount, Change Status Authorize Additional ........................................................... 185 Advantages ................................................................................................................................................................. 185 Disadvantages ............................................................................................................................................................ 185 Scenario 6C Authorize Original Amount, Change Status: Authorize........................................................................... 188 Advantages ................................................................................................................................................................. 188 Disadvantages ............................................................................................................................................................ 188

Appendix A: Permitted Country Code Values ................................................................................... 190 Appendix B: Address Verification System (AVS) Checking............................................................... 198AVS Filtering within the Skipjack Transaction Network .................................................................................................. 198 Development Notes for AVS and AVS Filtering.............................................................................................................. 199 AVS Codes by Card Type............................................................................................................................................... 200 AVS Response Codes for International and Domestic Credit Cards ............................................................................. 201 AVS Code Handling for International and Domestic Transactions ................................................................................. 201 Use of Canadian Postal Codes in AVS Checks ............................................................................................................. 201

Appendix C: CVV and Interpreting CVV Return Codes ..................................................................... 202How CVV Code Checking is Used in Transactions ........................................................................................................ 202 CVV Code Locations by Card Type ................................................................................................................................ 203 CVV Response Codes for Visa and MasterCard/Eurocard ............................................................................................ 203

Appendix D: Avoiding Duplicate Transactions .................................................................................. 204Development Notes on Avoiding Duplicate Transactions............................................................................................... 204

Appendix E: Configuring Level II Transaction Data........................................................................... 205Development Notes for Level II Data .............................................................................................................................. 205

Appendix F: TSYS PIN-based Debit Transactions Information ......................................................... 206Example Code Snippets ................................................................................................................................................. 207 Request Variables ...................................................................................................................................................... 207 Example Response String .......................................................................................................................................... 208 Response Example: Authorize ................................................................................................................................... 208 Development Notes for the TSYS PIN-based Debit Service .......................................................................................... 208

Appendix G: Blind Credits ................................................................................................................. 209Prerequisites and Requirements for Performing Blind Credits ....................................................................................... 209 szReturnCode Error Messages Associated with Blind Credits ....................................................................................... 210 Blind Credits versus Change Status: Credit ................................................................................................................... 210 Configuring the Skipjack Merchant Account to Permit Blind Credits .............................................................................. 211

Appendix H: Using Trackdata Details in Transactions ...................................................................... 212Recommended Trackdata Hardware .............................................................................................................................. 212 Trackdata Information and Examples ............................................................................................................................. 212 Trackdata Capture, Formatting and Usage Notes .......................................................................................................... 213

Appendix I: Unique Order Numbers .................................................................................................. 214How to Identify Transactions When Duplicate Order Numbers Exist ............................................................................. 214 Other Transaction Methods Using Order Number as a Required Variable................................................................ 215 Configuring the Reject Duplicate Order Numbers Option for a Merchant Account .................................................... 215

Appendix J: Using Soft Indicators with Paymentech and TSYS ........................................................ 217Soft Indicator Implementation Guidelines ....................................................................................................................... 217 Setting Merchant Services Vendor Preferences to Support Soft Indicators ................................................................... 217

Appendix K: Orderstring Variables .................................................................................................... 219Example: OrderString Variable Formatting ................................................................................................................ 220 OrderString and lvl3orderstring variable Developer Notes......................................................................................... 220

Appendix L: Naming Conventions for Dummy Values in Required Variables ................................. 221Suggested Values for Dummy Values for Required Variables ................................................................................ 221 Methods Using the Dummy Variables ........................................................................................................................ 221

Page 7



Appendix M: Transaction IDs, Audit IDs and the Transaction Lifecycle ............................................ 222Development Notes on Audit IDs and Transaction IDs .................................................................................................. 222

Appendix N: Test Cards Used with Development Accounts ............................................................. 223Test Cards for TSYS and Global as Payment Processor .......................................................................................... 223 Test Cards for Fifth Third Processing Solutions (FTPS) as Payment Processor....................................................... 224

Appendix O: Notes for Processing Level II and Level III Data........................................................... 225 Appendix P: Usage Notes for the Enhanced TSYS Credit Card Processing Features ..................... 226Setting Skipjack Merchant Account Settings .................................................................................................................. 226 Changing the Merchant Account Setup Options to Use TYSY Enhanced Functions .................................................... 227 Developer Notes about the TSYS Platform Enhanced Features ................................................................................... 228

Appendix Q: Usage Guidelines for Using Paymentech as Payment Processor ................................ 229Setting the Batch Settlement Preferences for Paymentech Salem ................................................................................ 230

Appendix R: Skipjack Variable Mapping ........................................................................................... 231Selectable Variables ....................................................................................................................................................... 231 Variables Generated During Transaction Processing .................................................................................................... 232

Appendix S: Master Error Code Table .............................................................................................. 234Skipjack_Integration_Guide_Version1.0_RevM8.docx

Page 8



About this DocumentThis guide contains information about all Skipjack Financial Services transaction methods except the reporting methods and is intended for experienced application developers. The information includes specific integration and application development details for each method. A companion guide, the Skipjack Reporting API Integration Guide contains all details for using Reporting APIs. This documentation does not attempt to describe language-specific programming details. Instead, the purpose of this guide is to provide details about the various API methods, variables, values, parameters, usage notes, examples, and sample scenarios to aid you in your application development and integration. Although many of the operations can be performed using the Web-based Merchant Services interface, the information in this guide concentrates on the direct post and API-based transaction methods. The Merchant Services interface, however, must be used in some instances to configure the Skipjack Merchant Account for the API request to work. These details are included whenever relevant. For a detailed description about the Merchant Services User Interface and other online Skipjack applications, see the Obtaining Additional Information section for details. NOTE: This guide has been restructured. See the Obtaining Referenced Documents section for details about the new guides created as part of this content reorganization.

Copyright Notice 2009 Skipjack Financial Services. All rights reserved. The information contained herein is for information purposes only. Skipjack makes no warranty, expressed or implied, in this document. No part of this information may be reproduced in any form or by any means or transferred to any third party without the prior written consent of Skipjack Financial Services.

Trademark NoticeAll trademarks, registered trademarks, and service marks mentioned or used within this document are owned wholly by their respective owners.

Interchange Qualifications and Transaction RatesAs your Payment Solution Skipjack Financial Services cannot guarantee interchange qualification for any specific transaction. It is the responsibility of each Merchant to confirm that their transactions qualify for the correct interchange rates in consultation with their Merchant Account Provider and Payment Processor. If you experience issues with interchange qualification, please contact the Skipjack Financial Services Support Group so that we can work with your Payment Processor to identify and correct any issues. Your Payment Processor must provide the necessary information to direct you and/or Skipjack in the resolution process.

Page 9



Publication HistoryDate May 2006 August 2006 September 2006 September 2006 Version Version 0.9 (Draft) Version 1.0_RevA Version 1.0_RevD Version 1.0_RevE Comments Issued for internal review and limited circulation only. Released for distribution and publication on Website. Added information about support for Soft Indicators using Paymentech Salem and assorted editorial changes Added Appendix A: Permitted Country Code Values section and additional information about the use of rtCountry variables for Add and Edit recurring Payment methods to support Paymentech Soft Indicator Functionality Minor changes to e-mail variable descriptions. Minor changes to Response Code descriptions for all non Authorize/AuthorizeAPI methods. Added new (virtual) test credit card number for Global Payment Systems Editorial changes to reflect inputs from users. Enhancements made to the Soft Indicator details. Minor editorial changes and corrections. Removed erroneous Soft Indicator information regarding support for 3 digit and 3 letter Country codes. Added changes to reflect support for ApprovalCode variable in Authorize/AuthorizeAPI method. Added details for Ignore AVS settings in Orderstring variables plus minor editorial updates. Updated Payment Processors tables and info, changed some details in Change Transaction Status and Get Transaction Status sections, added 3 new Reauthorization Scenarios, and assorted editorial updates. Added new details about usage of optional ResponseFlags variable, added Advanced Processor information and URLs, and minor editorial updates. Added additional information regarding supported processors, and minor editorial updates. Corrected batch authorization method request example Clarified use of Special Characters for ItemDescription and rtItemDescription. Changed URL for Echo utility, changed Verified by Visa entry for COMDATA in processor table. Minor editorial updates. Modified the Track data examples to correct error Modified Approval Code information to reflect new code syntax. Restructured Skipjack Integration Guide and created separate guides: Skipjack Reporting API Guide and Skipjack Integration Overview Guide. Updated technical details and minor editorial changes throughout. Added details about new TSYS PIN-based Debit Service for debit processing. Clarified information about Level I, II, and III data usage details and background information. Minor editorial updates.

September 2006

Version 1.0_RevG

November 2006 April 2007

Version 1.0_RevK Version 1.0_RevL

April 2007

Version 1.0_RevL1

June 2007

Version 1.0_RevL2

August 2007

Version 1.0_RevL3

September 2007 October 2007 December 2007

Version 1.0_RevL4 Version 1.0_RevL5 Version 1.0_RevL6

January 2008 May 2008 August 2008

Version 1.0_RevL7 Version 1.0_RevL8 Version 1.0_RevM1

September 2008

Version 1.0_RevM2

Page 10



September 2008

Version 1.0_RevM3

Added note to the Trackdata Capture, Formatting and Usage Notes section of Appendix H: Using Trackdata Details in Transactions regarding potential for Declines with swiped transactions in special circumstances. Minor editorial updates. Added details about the TSYS enhancements for credit card processing. Added details about enhanced Change Status functionality. Clarified details about use of Split Settlement. Added information about AVS code G. Clarified details about TrackData usage. Updated Soft Indicator information. Clarified usage details for County Code usage. Added new Appendix R: Variable Mapping information. Assorted minor technical and editorial changes. NOTE: This version of the guide was released for internal Skipjack use only. Added details regarding new Change Status feature enhancements. Updated the szReturnCode table. Assorted minor technical and editorial changes. Minor editorial changes to Authorization Logic and Appropriate Failsafe Mechanisms section. Assorted minor technical and editorial changes.. Changes to clarify ChangeStatus response formatting and related details. Improved descriptions for OrderString and lvl3_orderstring variables. Added table for new Test Cards for use with Fifth Third Processing Solutions. Added new Skipjack Master Error Code section (Appendix to replace previous szResponseCode Error table and to provide additional troubleshooting and error information. Minor technical changes added as part of internal technical review.

December 2008

Version 1.0_RevM4

January 2009

Version 1.0_RevM5

February 2009 April 2007

Version 1.0_RevM6 Version 1.0_RevM7

April 2007

Version 1.0_RevM8

Page 11



Documentation ConventionsThe material presented in this guide uses the following text conventions throughout, where applicable.Convention Courier text Usage Code Snippets, HTML Code, Skipjack Transaction Network Request Response Examples text Browser Elements, Fields Names, and Menu Items, Emphasis Notes Hyperlinks (links) to external resources on the Web. Click on these to go to the document or web site identified by the link. Primary use is to denote crossreferences (clickable hotlinks in the PDF version) to a location within this document. Also used within tables in this document to enclose characters that might otherwise be overlooked. Italics Document Title See the Skipjack Integration Guide for details. Example click on a Submit button. make sure you enter your HTML Serial Number.... NOTE: You must consider the following when Visit http://www.skipjack.com to learn more about Skipjack Financial Services.

Bold text

Blue Underline

Quoted text

See the About this Document section for details. This field can also include the . (period) character.

Page 12



Definitions of Variable TypesThere are three types of variables for all methods: Required, Optional, and Conditional variables. 1. Required Variables are mandatory variables which must be included in all transaction data requests sent. If required variables are missing in transaction data sent to the Skipjack Transaction Network, an error code will be returned to your application. 2. Optional Variables are not required and may be omitted. 3. Conditional Variables are variables that are required if another condition applies, for instance variable A is required if variable B is not included or in cases of a variable applying to specific Payment Processors or services. There are relatively few conditional variables.

Permitted Syntax for Variable FieldsThe permitted characters for variables used in the transaction variable tables throughout are defined below. Please ensure you follow these conventions when entering data into the applicable variable fields.Formatting Type Numeric Alphabetic (Alpha) Only Alpha-Numeric Description of Permitted Characters All number characters only. All letters of the alphabet only. All numeric characters and alphabetic characters but excluding restricted characters. All numeric characters, all letters of the alphabet, and most symbols but excluding restricted characters. Characters that are reserved for special uses by internal system use and cannot be included in variable names or field values. Special characters only. Usage Notes Includes all integers. All letters of the alphabet excluding special characters "~`!@#$%^&*()_-+=. All numeric and alphabetic characters excluding special characters "~`!@#$%^&*()_-+=. All characters, including alpha-numeric characters but excluding restricted characters &,%,*. Restricted for special (system) uses: &,%.*

All Characters

Restricted Characters Special Characters

"~`!@#%^&*()_-+= only

Obtaining Additional InformationA complete listing of resources including User Guides, Integration Guides, Developer and Merchant resources, support links, and other resources is available from the Skipjack Financial Services Web site at the links listed below: http://www.skipjack.com/developers.aspx http://www.skipjack.com/support.aspx

Page 13



Obtaining Referenced DocumentsThis document references other Skipjack documentation available from the Skipjack Financial Services Web site by clicking on the links below. Skipjack Integration Guide (Latest version of this Guide) Skipjack Integration Troubleshooting Guide Skipjack Integration Overview Guide Skipjack TSYS PIN-based Debit Services Guide Skipjack Level II and III Transaction Overview Guide Skipjack Merchant Reporting Guide Skipjack Merchant Services Guide Skipjack Reporting API Integration Guide

Contacting Skipjack Financial ServicesIf you have problems using the Skipjack Transaction Network or have questions about its use that are not covered in this documentation, please contact Skipjack Financial Services. On the Web: http://www.skipjack.com Toll-Free Telephone Support Line: 1-888-368-8507 Email: [email protected]

Obtaining a Developer Account with Skipjack Financial ServicesYou can find out more information and request your Skipjack Development Account(s) online at http://www.skipjack.com/developers.aspx or by calling 1-888-368-8507 and speaking with a Skipjack Customer Support representative.

Obtaining a Merchant Account from a Financial InstitutionMerchant Accounts are provided by financial institutions and must be in place before the live application can activated within Skipjack Financial Services. There is some lead time required for the setup of the Merchant Account. Developers must ensure that the Merchant you are working with is aware of this and begins the process of obtaining their Merchant Account to ensure that live testing and rollout of your application can be completed on time.

Page 14



Getting Started: Application Development LifecycleOverview: Recommended Development ProcessWe suggest that you complete the steps in the order listed below: 1. Read all applicable development information including this document to understand the development process and options. 2. Familiarize yourself with the available integration tools and methods from Skipjack Financial Services. 3. Choose your integration methods keeping in mind the requirements of the Merchant and any other third-party systems requirements. 4. Write the code for your application. 5. Obtain and configure your Skipjack Development Account(s) by contacting Skipjack Financial Services by calling 1-888-368-8507 or on the Web: http://www.skipjack.com/developers.aspx. 6. Test your integration in the Skipjack Test Environment using your Skipjack Development Account(s). For further information about testing, see the testing details described in the Skipjack Developers Overview Guide. 7. Deploy your application Live in the Skipjack Financial Services Production Environment. 8. Test the integration and Skipjack Account settings in the Skipjack Production Environment. 9. Certify your application as Skipjack Certified. This will help reinforce and communicate the message to your users of your commitment to security, reliability, and dependability. Registration also ensures you are eligible for other programs offered by Skipjack Financial Services that are exclusively offered Certified Partners. Find out more about being Skipjack Certified by going to www.skipjack.com/certification. 10. Register your application online with Skipjacks Solution Finder to maximize your business opportunities. Registration in Solution Finder is free and provides Skipjacks sales partners with a link from their customers to your Web site. For more about registering, go to https://secure.skipjack.com/partners/search.aspx or email [email protected].

Page 15



Payment Processors Supported by Skipjack Financial ServicesThe Skipjack Transaction Network supports the Payment Processors (also called Processors in this document) listed below. Advanced Processors are noted by red* and transactions posted to these Payment Processors use a specific URL, as noted for each applicable transaction method. Skipjack has links to all Merchant Banks through the Processors listed below.TSYS (VITAL) NOVA First Data Nashville Global Payments East First Tennessee Bank Fifth Third (St. Pete) Concord EFS Net RBS LYNK Paymentech Salem* Paymentech Tampa* COMDATA*

Ecommerce Mail Order Retail Verified By Visa Master Card Secure Code Level I Level II Level III Soft Indicators /Descriptors Track 1 Data Track 2 Data PIN-based Debit

YES YES YES YES YES YES YES YES YES

YES YES YES NO NO YES NO NO NO

YES YES YES YES YES YES YES YES NO1

YES YES YES YES YES YES YES NO NO



YES NO YES NO NO YES NO NO NO

YES YES YES NO NO YES NO NO NO

YES YES YES YES YES YES YES YES YES


YES YES YES NO NO YES YES NO NO

NO YES YES

YES NO NO

YES NO NO

YES YES YES

YES NO NO

YES YES YES

YES NO NO

YES NO NO

YES YES NO

YES YES NO

YES YES NO

1

Settled on First Data Omaha

Page 16



Payment Processor Information for Canadian Merchant Accounts and Payment Processors Canadian Merchant Accounts are supported by Global Payments East and Paymentech only. All Merchant Account Providers in Canada (including Paymentech) can be processed through Global Payments East. To use Paymentech as your Payment Processor in Canada you must use Paymentech as your Merchant Account Provider. Canadian Merchant Accounts using Global Payments East must submit their Merchant Account information to Global Payments Systems for registration at least two weeks before it can be used for transaction processing. The registration process takes approximately 2 weeks to complete.

Page 17



Connection TypesThe Skipjack Transaction Network uses three main connection types for all transaction processing.

Direct Skipjack API PostsDirect posts are used to send data as name-value pairs directly to the Skipjack Transaction Network via a secure HTTPS using an HTTPS form POST request. A response is sent back from the Skipjack Transaction Network to the originating application as a comma-delimited test string with carriagereturn and Line Feed (CR/LF) record delimiters. Skipjack will also be providing a web service interface shortly, please contact your Relationship Manager for more information. Web services-based transaction processing will be supported for Authorize, Change Status and Recurring Payments methods. Exact WSDL locations will be provided in a separate Web Services document upon request.

Installed API PostsSkipjack provides the .NET Retail API for installation on client hardware. For more information please visit the Skipjack web site at http://www.skipjack.com/developers.aspx and use the Integration Toolkits link to access information about the Skipjack RetailAPI. Skipjack previously supported an installable COM API but not longer supports it for new integrations. (Skipjack Financial Services will continue to support existing applications that use COM-based posts.)

Batch PostsBatch posting is a mechanism for processing transactions as grouped batches in an offline mode. Batch posting may be more efficient for processing large volumes of transactions and situations where it is not practical to process each transaction separately.

Page 18



Level I, II, III Card Data Transaction OverviewThe Skipjack Transaction Network supports processing of all card types including Level I, Level II, and Level III card data. Level II and Level III transaction processing are sometimes collectively referred to as Enhanced Data transactions and are normally used in a business-to-business or business-to-government transactions rather than a consumer-level purchases.

Level I TransactionsLevel I card credit transaction data are submitted for all standard consumer credit card transactions and primarily used in credit card purchases made by most consumers. Level I data normally include all the required name-value pairs as described in the main section of this guide. For Level I card transactions the information returned and reported on the Customers card statement regarding the transaction is limited to basic transaction details, such as the Merchant Name, City, Date, Amount, and so on. Basic transaction processing rates are applied in accordance with the details provided by the Merchant Account Provider for Level I transactions.

Level II TransactionsLevel II credit cards are typically issued to individuals employed by large enterprises or organizations and governments for making corporate purchases, often for larger transaction amounts than typical Level I transactions. Level II transactions can qualify for a discounted transaction rates resulting in significant savings to the enterprise if all requirements of the Merchant Account Provider are met and the properly formatted transaction data is sent in the transaction request. Level II card data includes all the required Level I data plus three additional parameters. All must be sent to qualify for Level II rates. These parameters are: Purchase Order Number, Customer Code, and Customer Tax. The additional data collected in the transaction data may be used for back-office functions such as program administration (such as monitoring employee spending), accounting and reconciliation functions (for example, general ledger allocations), tax reporting and auditing (providing a breakdown of Local, State, Federal taxes) and supplier monitoring. Level II cardholders typically receive detailed card statements with enhanced details describing the sales tax breakdown, customer reference number (PO Number), and Merchant Order Number on their card statements.

Page 19



Example of Level II Data Request StringNOTE: Level II transaction name-value pairs shown in red. serialnumber=000289255730&ordernumber=FS4RRM8YHV4DFB2FNA5DWX&transactionamount=1.00&accou ntnumber=4445999922225&month=08&year=2009&cvv2=999&sjname=TestName&[email protected] m&streetaddress=8320 TestDrive&city=Houston&state=TX&zipcode=85284&phone=0000000000& shiptophone=0000000000&orderstring=001~Test Payment~1.00~1~N~||&comment=TEST PAYMENT&customercode=A10&purchaseordernumber=5553424234234234&customertax=0.10

NOTE 1: Skipjack Financial Services only supports Level II transaction processing for the Payment Processors listed in the Payment Processors Supported by Skipjack Financial Services section.

Level III TransactionsLevel III credit card transactions are sometimes called Purchase Cards or Corporate Card purchases. Level III transaction data include additional name-value request variables not used for Level I and Level II transactions. Level III transactions are important in the large business-to-business or business-to-government environments as considerably more data is collected for each transaction and can qualify for the lowest discount rates. The Level III transaction data includes all the required Level I and Level II transaction data (Level II data must be sent in a Level III request) as well as additional Level III transaction data. Level III transaction data can be used in an enterprise to support back-end processing and data exchange tasks typically used in accounting and reconciliation tasks. Obtaining the best discount rate depends on several requirements specified by the Merchant Account Provider and that the required Level III transaction parameters are sent for each transaction. At present, the Skipjack Transaction Network is one of the relative few Payment Gateways that fully support Level II and III transactions. As an integrator you must be aware that to be able to process Level II and Level III transaction data and obtain the expected (best) Level III transaction rates requires that all required Level III name-value pairs be properly formatted and sent in each Level III transaction request. NOTE 1: Skipjack Financial Services only supports Level III transaction processing for the Payment Processors listed in the Payment Processors Supported by Skipjack Financial Services section. NOTE 2: For Level III transactions all required Level I, Level II, and Level III name-value pairs must be submitted in each transaction request with valid values to qualify for the Level III discount rates. Omitting even a single required name-value pair or assigning an incorrect value for a variable (such as Purchase Order) may result in the transaction being downgraded from the fully-qualified rate to a less qualified rate resulting in unexpected (higher) per transaction rates for the Merchant.

Page 20



Example of Level III Data Request Stringsjname=Vendor Name&[email protected]&Streetaddress=123 Test Road&City=Cincinnati&State=OH&Zipcode=40511&Ordernumber=9727TEST&Accountnumber=4445999922 225&Month=07&Year=08&Transactionamount=51.40&&Shiptostreetaddress=123 TestRoad&Shiptocity=Cincinnati&Shiptostate=OH&Shiptozipcode=40511&Shiptophone=5135882100& Customertax=2.64&Customercode=123456&Purchaseordernumber=PONUMBER&Shiptocountry=840&Shipp ingamount=4.76&Shippinghandling=0.01&Restockingfee=0.02&Uniquevatinvoicenumber=1010&Vatta xamount=0.03&Vattaxrate=0.04&Customervatnumber=1234&Dutyamount=0.05&Summarycommoditycode= 2500&Nationaltax=0.06&Discountamount=0.07&Orderstring_lvl3=31711~PCARDTRANS~44.00~1.000~N ~EA~0.08~44.00~2500~0.09~0.10~0.11~0.12~30~0.13~||33910~PCARDTRANS~0.00~5.000~N~EA~0.00~0 .00~2500~0.00~0.00~0.00~0.00~0~0.00~||

NOTE: This string is sent as a single line of text. See Also See the Transaction Requests for Authorize and AuthorizeAPI section for a complete list of Level I, II, and III transaction data used in transaction Authorizations.

Page 21



Core & Supplementary Transaction MethodsThe methods described in this guide can be functionally classified as either Core or Supplementary methods. A detailed description of all Core and Supplementary transaction methods is provided.

Core MethodsThe Core transaction methods are fundamental methods that perform the most widely-used transaction functions. The Core methods include the following: 1. Authorize and AuthorizeAPI 2. Get Transaction Status 3. Change Transaction Status

Supplementary MethodsThe Supplementary methods are those that are used in conjunction with the Core methods to perform more specialized or tertiary operations on transactions. The available Supplementary Methods for transaction processing: 1. Recurring Payments a) Add Recurring Payment b) Get Recurring Payments Status c) Delete Recurring Payment d) Edit Recurring Payment 2. Batch Upload a) Batch Authorization b) Check Batch File Status c) Modify (Edit) Batch File Status d) Get Batch File Response 3. Reports API a) Transaction Detail Report b) Daily Deposit Summary c) Batch Summary Report d) Customized Report NOTE: For integration details about the Reporting API methods, see the companion guide Skipjack Reporting API Integration Guide. 4. Batch Settlement a) Close Current Open Batch b) Get Batch Settlement Status

Page 22



Authorize and AuthorizeAPI MethodsThe Authorize and AuthorizeAPI methods are used to submit transaction data to the Skipjack Transaction Network for Authorization. Both methods, Authorize and AuthorizeAPI, use the same variables, field names, and values in their requests and responses. The usage of each method is described in this section.

AuthorizeThe Authorize method sends an HTTPS POST request to the Skipjack transaction server and receives the responses as a postback with the responses as name-value pairs in the header of the response post.

Post-Back Locations for Authorize MethodThere are three locations for the response types (Approval, Decline, Failure) generated by an Authorize transaction method. Additional information about setting post-back locations can be found in the Skipjack Merchant Services Guide.

AuthorizeAPIThe AuthorizeAPI method sends a request to the transaction server via a HTTPS connection using a request POST and receives a comma-delimited response string with carriage return/ line feed (CR/LF) line breaks.

Transaction Requests for Authorize and AuthorizeAPIThis section describes the variables sent in transaction data requests for Authorize and AuthorizeAPI methods.

Details for Submitting Transaction Requests for Authorize and AuthorizeAPIDevelopment Server: Authorize Development Server Authorize *Advanced Processors Only See Payment Processors Supported by Skipjack Financial Services for a list of Advanced Processors. Development Server: AuthorizeAPI Development Server Authorize API *Advanced Processors Only See Payment Processors Supported by Skipjack Financial Services for a list of Advanced Processors. Production Server: Authorize https://developer.skipjackic.com/scripts/evolvcc.dll?Authorize https://developer.skipjackic.com/evolvcc/evolvcc.aspx?Authorize

https://developer.skipjackic.com/scripts/evolvcc.dll?AuthorizeAPI https://developer.skipjackic.com/evolvcc/evolvcc.aspx?AuthorizeAPI

https://www.skipjackic.com/scripts/evolvcc.dll?Authorize

Page 23



Production Server Authorize *Advanced Processors Only See Payment Processors Supported by Skipjack Financial Services for a list of Advanced Processors. Production Server: AuthorizeAPI Production Server AuthorizeAPI *Advanced Processors Only See Payment Processors Supported by Skipjack Financial Services for a list of Advanced Processors. Development Server Host Name Production Server Host Name Server Port HTTP Type Method

https://www.skipjackic.com/evolvcc/evolvcc.aspx?AuthorizeAPI

https://www.skipjackic.com/scripts/evolvcc.dll?AuthorizeAPI https://www.skipjackic.com/evolvcc/evolvcc.aspx?AuthorizeAPI

developer.skipjackic.com www.skipjackic.com 443 1.0 Compliant POST

NOTE: Requests submitted without a secure connection will be refused.

NOTE 1: The submitted variables and values and response string values are identical for both the Authorize and AuthorizeAPI methods. NOTE 2: Information highlighted in the following tables with yellow background fill indicates information applicable to those using Paymentech as their Payment Processor and implementing Soft Indicators. NOTE 3: Information highlighted with blue background fill in the following tables indicates information applicable to those using TSYS as their Payment Processor and processing TSYS PIN-based debit transactions. NOTE 4: Information highlighted with orange background fill in the following tables indicates information applicable to those using TSYS or GLOBAL as their Payment Processor and using POSEntryMode Settlement Flags options.

Request Variables for Authorize and AuthorizeAPI MethodsVariable Name Variable Description HTML Serial Number. Skipjack-assigned unique HTML serial number. DeveloperSerialNumber Developer Serial Number Conditional AlphaNumeric 12/12 1 ABC123456789 Required / Optional Required Variable Type Numeric Min / Max Length 12/12 Data Level 1 Example

SerialNumber

000111222333

Page 24



Developer Serial Number Assigned to the Skipjack Account. This variable is conditional as determined by whether or not this option is set as mandatory in the Merchant Services Interface. SJName Customer's Name Cardholders Billing Name.NOTE: You should not use the AND symbol (&) in this variable, or else this will truncate the name at this symbol and may cause problems with Skipjack Reports.

Required

All Characters

1/40

1

John Doe

Email

Customer's Billing Email Address Customer's Billing Street Address

Required

Valid email Characters AlphaNumeric and comma (',') and period ('.') AlphaNumeric comma (',') and period ('.') AlphaNumeric and comma (',') and period ('.') AlphaNumeric and comma (',') and period ('.')

1/40

1

[email protected]

StreetAddress

Required

1/40

1

1 Skipjack Way

StreetAddress2

Additional Billing Address Information

Optional

0/40

1

Apartment 1

StreetAddress3


Optional

0/40

1

Lower Level

StreetAddress4


Optional

0/40

1

Side Door

Page 25



City

Customer's Billing City All Spaces within a City will be removed

Required

AlphaNumeric

1/40

1

Cincinnati

State ZipCode

Customer's Billing State or Province Customer's Billing Zip or Postal Code Customer's Billing Country.*NOTE: Required variable when using Paymentech (Salem or Tampa) as your Payment Processor. See Appendix A: Permitted Country Code section for specific Country Codes used for this variable and any usage restrictions required by specific Payment Processors.

Required Required

AlphaNumeric AlphaNumeric and '-' AlphaNumeric

1/40 1/10

1 1

OH 12345 or 123456789 *For Paymentech Salem: UK OR For other Processors: USA Canada 840

Country

Optional*

*0/3 OR 0/40

1

Phone

Customer's Phone Number Customer's Fax Number The Ship To Name Customer's Billing Street Address

Optional

Numeric and dash ('-') Numeric and dash ('-') AlphaNumeric AlphaNumeric and comma (',') and period ('.') AlphaNumeric and comma (',') and period ('.') AlphaNumeric and

1/12

1

8005551212 or 800-555-1212 8005551212 or 800-555-1212 Jane Doe 1 Skipjack Way

Fax

Optional

1/12

1

ShipToName ShipToStreetAddress

Optional Optional

1/40 1/40

1 1

ShipToStreetAddress2


Optional

0/40

1

Apartment 1

ShipToStreetAddress3


Optional

0/40

1

Lower Level

Page 26



comma (',') and period ('.') ShipToStreetAddress4 Additional Billing Address Information Optional AlphaNumeric and comma (',') and period ('.') AlphaNumeric AlphaNumeric 0/40 1 Side Door

ShipToCity ShipToState

Customer's Billing City Customer's Billing State or Province

Optional Optional Level 1 Required Level 3

1/40 1/40

1 3

Cincinnati OH

ShipToZipCode

Customer's Billing Zip or Postal Code

Optional Level 1 Required Level 3

AlphaNumeric and dash ('-') AlphaNumeric

1/10

3

12345 or 123456789

ShipToCountry

Customer's Billing Country See the Appendix A: Permitted Country Code section for specific Country Codes used for this variable and any usage restrictions required by specific Payment Processors.

Optional Level 1 Required Level 3

0/40

3

USA, Canada, UK, 840

ShipToPhone

Phone Number for Customer at Shipping Destination Customers Fax Number Order Number The order identifier (ID) assigned by the Merchants application when the order is placed to identify the transaction

Required

Numeric and dash ('-') Numeric and dash ('-') AlphaNumeric

1/12

1

8005551212 or 800-555-1212

ShipToFax

Optional

1/12

1

8005551212 or 800-555-1212 ABC123 or 123

OrderNumber

Required

1/20*

1

Page 27



uniquely. OrderNumber should be uniquely generated by the application to prevent duplicates. (Duplicates order numbers are repeated Order Numbers that occur within a 24 hour period)NOTE: For those using Paymentech Salem as the Payment Processor the Order Number can be a maximum of 22 alphanumeric characters and must be unique per Settlement Batch, otherwise a Decline will be returned.

See also Appendix I: Unique Order Numbers: section. OrderDescription Soft Indicator Descriptor Applies only to Paymentech Salem and TSYS for processing credit card only. This variable must be in the format of X*Y where X is the Company Identifier and Y is the Item Identifier. Three formatting options are permitted: 3 characters*18 characters Optional Alphanumeric and a single asterisk * 4/22 1 DDS*123456789 012345678

Page 28



7 characters*14 characters 12 characters*9 characters. X+Y= 21 characters plus an asterisk (*) for a total of 22 characters. AccountNumber Customers Credit Card NumberNOTE: Spaces are not permitted.

Required

Numeric

13/18

1

41111111111111 1

Month

Customers Credit Card Expiration Month Customers Credit Card Expiration Year Card Verification ValueNOTE: CVV validation may not be supported by the credit card issuing bank.

Required

Numeric

1/2

1

9 or 09

Year

Required

Numeric

2/4

1

09 or 2009

CVV2

Optional

Numeric

3/4

1

123 or 1234

See also Appendix C: CVV and Interpreting CVV Return Codes section. TransactionAmount The purchase amount to be authorized on the Customer's credit ca

Date post:	24-Mar-2015
Category:	Documents
Upload:	sandyjo15
View:	325 times
Download:	0 times