Sie sind auf Seite 1von 43

Skipjack Integration Overview Guide

2008 Skipjack Financial Services

Skipjack Integration Overview Guide

Table of Contents
About this Document ............................................................................................................................. 4
Copyright Notice ................................................................................................................................................................. 4 Trademark Notice ............................................................................................................................................................... 4 Interchange Qualifications and Transaction Rates ............................................................................................................. 4 Publication History .............................................................................................................................................................. 5 Documentation Conventions............................................................................................................................................... 5 Definitions of Variable Types .......................................................................................................................................... 6 Permitted Syntax for Variable Fields .............................................................................................................................. 6 Obtaining Additional Information......................................................................................................................................... 7 Obtaining Referenced Documents ................................................................................................................................. 7 Contacting Skipjack Financial Services .............................................................................................................................. 7

Getting Started: Application Development Lifecycle ............................................................................. 8


Overview: Recommended Development Process .............................................................................................................. 8 Obtaining a Merchant Account from a Financial Institution ................................................................................................ 9 Obtaining a Developer Account with Skipjack Financial Services...................................................................................... 9 The Credit Card Authorization Processing Overview ....................................................................................................... 10 Skipjack Transaction Network High-Level Topology ........................................................................................................ 10 Name-Value Pairs ............................................................................................................................................................. 10 Simplified Credit Card Transaction Processing Network Topology ............................................................................. 10 Participants and Network Elements in Transaction Processing ....................................................................................... 11 Credit Card Authorization ................................................................................................................................................. 12 Transaction Processing Approval Phases ........................................................................................................................ 12 Step 1: Validation Phase .............................................................................................................................................. 12 Step 2: Authorization Phase ............................................................................................................................................. 13 Step 3: Verification Phase ................................................................................................................................................ 13

Overview of the Credit Card Settlement Process ................................................................................ 14


Batch Settlement............................................................................................................................................................... 14 Batch Settlement Configuration Options ...................................................................................................................... 14 Real-Time Settlement ....................................................................................................................................................... 16 Configuring Batch Settlement Options for Skipjack Merchant Accounts .......................................................................... 16 Transaction Lifecycle and Transaction States .................................................................................................................. 17 Core versus Supplementary Transaction Methods .......................................................................................................... 18 Core Methods ................................................................................................................................................................... 18 Supplementary Methods ................................................................................................................................................... 18

Blind Credits........................................................................................................................................ 19
Prerequisites and Requirements for Performing Blind Credits ......................................................................................... 19 szReturnCode Error Messages Associated with Blind Credits .................................................................................... 19 Using Blind Credits versus Change Status: Credit ........................................................................................................... 19 Configuring the Skipjack Merchant Account to Permit Blind Credits ................................................................................ 20

Unique Order Numbers ....................................................................................................................... 21


How to Identify Transactions When Duplicate Order Numbers Exist ............................................................................... 21 Other Transaction Methods Using Order Number as a Required Variable ...................................................................... 22 Configuring the Reject Duplicate Order Numbers Option for a Merchant Account .......................................................... 22

Transaction Settlement Methods ........................................................................................................ 24


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

Merchant Account Configuration Options ........................................................................................... 25


E-mail Responses - Types of Email Responses .............................................................................................................. 25 E-mail Sent by the Skipjack Transaction Network ............................................................................................................ 25 Options for Setting E-mail Response Settings in the Merchant Account Interface .......................................................... 25 E-mail Response Message Types .................................................................................................................................... 26 Editing E-mail Response Templates................................................................................................................................. 27

Page 2 of 43

2008 Skipjack Financial Services

Skipjack Integration Overview Guide

Mapping the Transaction Variables to E-mail Template Variables................................................................................... 27 E-mail Template Tags ....................................................................................................................................................... 28 Mapping Skipjack Variables to the E-mail Template ........................................................................................................ 29 Additional Transaction-Generated Variables for E-mail Responses ................................................................................ 30 E-mail Lists - Creating E-mail Lists ................................................................................................................................... 31 Web Page Response Files ............................................................................................................................................... 32 Changing the Web Response Files .................................................................................................................................. 32

Security Information ............................................................................................................................ 34


Skipjack Transaction Network Security ............................................................................................................................ 34 Skipjack Transaction Network Login Password Policy Enforcement ............................................................................... 34 Security Measures in Application Development and Integration ...................................................................................... 35 Hiding Serial Numbers in HTTP POST Requests ............................................................................................................ 35 Defenses Against Common Fraud Attempts and Methods .............................................................................................. 35 Protecting and Storing Your Account Credentials ............................................................................................................ 35 Card Issuer and Industry Wide Security Programs and Requirements ............................................................................ 35

Testing Guidelines .............................................................................................................................. 36


General Testing Guidelines .............................................................................................................................................. 36 Test Cards Used with Development Accounts for Integration Testing ............................................................................. 37 Serial Number Management and Usage for Secure Login ............................................................................................... 38 Login to Skipjack Financial Services using the Secure Login .......................................................................................... 38 Troubleshooting Secure Login Problems ......................................................................................................................... 39 Changing Passwords and Allowable Password Syntax ................................................................................................... 39 Example: Permitted Password Syntax ......................................................................................................................... 39 Authorization Testing ........................................................................................................................................................ 40 Settlement Testing/Deposit Testing .................................................................................................................................. 40 Response Testing ............................................................................................................................................................. 41 E-mail Response .......................................................................................................................................................... 41 Response Page ............................................................................................................................................................ 41 Backend Response URL .............................................................................................................................................. 41 Third-Party Applications ............................................................................................................................................... 41 Functional Testing ........................................................................................................................................................ 41 Migrating From Development to Production Environment ........................................................................................... 41

Developer and Integration Support ..................................................................................................... 42


Support Ticketing System Overview ................................................................................................................................. 42 Knowledge Base Overview and Links .............................................................................................................................. 42 Monitoring Skipjack Financial Services Status ................................................................................................................. 43

Skipjack_Integration_Overview_Guide_Version1.0_RevM1.doc

Page 3 of 43

2008 Skipjack Financial Services

Skipjack Integration Overview Guide

About this Document


This guide contains general electronic credit card transaction processing, integration testing guidelines, security information, Skipjack Account management details. This guide is a companion guide to the Skipjack Integration Guide. (This information was previously included in the Skipjack Integration Guide). This guide is intended for experienced developers and integrators as well as anyone needing a basic overview of the Skipjack Transaction Network and related overview information. NOTE: The information in this guide was previously contained in the Skipjack Integration Guide. For detailed information about supported transaction processing methods, name-value pair values and requirements, and other related integration details, please consult the Skipjack Integration Guide.

Copyright Notice
2008 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 Notice
All trademarks, registered trademarks, and service marks mentioned or used within this document are owned wholly by their respective owners.

Interchange Qualifications and Transaction Rates


As 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 4 of 43

2008 Skipjack Financial Services

Skipjack Integration Overview Guide

Publication History
Date August 2008 Version Version1.0_RevM1 Comments First version of this guide for release in this format. Content moved from the Skipjack Integration Guide (SIG) as part of Skipjack Integration Guide restructuring.

Documentation Conventions
The 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 <form name="Button" action="https://vpos.skipjack.com/ezPay/order. asp" method="post"> 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 5 of 43

2008 Skipjack Financial Services

Skipjack Integration Overview Guide

Definitions of Variable Types


There 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 Fields


The 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

Page 6 of 43

2008 Skipjack Financial Services

Skipjack Integration Overview Guide

Obtaining Additional Information


A complete listing of Developer resources including User Guides, Integration Guides, Developer and Merchant Resources, support links, and other resources is available from the Skipjack Financial Services Web site. You can obtain the latest version (in Adobe PDF format) of this document as well as other referenced documentation from the links below. http://www.skipjack.com/developers.aspx http://www.skipjack.com/support.aspx

Obtaining Referenced Documents


This document references other Skipjack documentation available from the Skipjack Financial Services Web site by clicking on the links below. Skipjack Integration Overview Guide NEW AUGUST 2008 (Latest Version of This Guide) Skipjack Integration Guide Skipjack Merchant Reporting Guide Skipjack Merchant Services Guide Skipjack Reporting API Integration Guide NEW AUGUST 2008

Contacting Skipjack Financial Services


If 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: support@skipjack.com

Page 7 of 43

2008 Skipjack Financial Services

Skipjack Integration Overview Guide

Getting Started: Application Development Lifecycle


Overview: Recommended Development Process
We suggest that you complete the steps in the order listed below: 1. Read all applicable development information including this document (Skipjack Integration Guide) 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 Guidelines section. 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 partners@skipjack.com.

Page 8 of 43

2008 Skipjack Financial Services

Skipjack Integration Overview Guide

Obtaining a Merchant Account from a Financial Institution


Merchant 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.

Obtaining a Developer Account with Skipjack Financial Services


You 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.

Page 9 of 43

2008 Skipjack Financial Services

Skipjack Integration Overview Guide

The Credit Card Authorization Processing Overview


The section below provides general information about the credit card transaction processing process. As an application developer or integrator you can really only begin to understand the development and integration needs of your application after you have a working knowledge of how credit card transactions are processed. This section will provide the basic general overview of the credit card Authorization process (Approval Process).

Skipjack Transaction Network High-Level Topology


The simplified network topology below illustrates the Skipjack Transaction Network and its relationship with the other networks used by the Acquiring Banks, Processors, and the credit card Issuers for transaction processing. Although this network topology illustration is highly simplified, it serves to identify the functional elements used for credit card transaction processing. These network elements are referred to throughout this documentation.

Name-Value Pairs
Data is securely sent between your application and the Skipjack Transaction Network as name-value pairs across the Internet as an HTTPS POST request. The response returned from the Skipjack Transaction Network is formatted as a comma-delimited text string with records separated by carriage return/line feed (CR/LF) breaks.

Simplified Credit Card Transaction Processing Network Topology

Page 10 of 43

2008 Skipjack Financial Services

Skipjack Integration Overview Guide

Participants and Network Elements in Transaction Processing


Participants and Network Elements Customer Skipjack Transaction Network (Payment Gateway) Payment Processor Acquiring Bank Issuer (Issuing Bank) Role Initiates the transaction by making a purchase of goods or services. Performs an intermediary role between the Customer and Processor. Skipjack Financial Services maintains secure leased lines to a variety of Payment Processors. Formats and sends transaction data to the appropriate financial networks. Transfers funds to the depositing bank account to pay the Merchant for the Customer transaction. Issues credit cards to Customers and determines whether sufficient credit is available on Customers account to permit transaction. Acts as an intermediary between the various financial institutions. The public network that carries the transaction data between the Merchants Application (Your Application) and the Skipjack Transaction Network. Skipjack Transaction Network refuses any insecure (non-SSL) transaction data. The Merchants Application (Your Application) that initiates and controls the transaction data that is submitted to the Skipjack Transaction Network.

Credit Card Associations (Not Shown) Internet (TCP/IP)

Your Application

Page 11 of 43

2008 Skipjack Financial Services

Skipjack Integration Overview Guide

Credit Card Authorization


The Authorization Process is the process where credit card transaction details are passed between the Merchants application and the various networks (Skipjack Financial Services, Processor, and Issuers networks) to obtain an Approval (or Decline) for each transaction. The Authorization process is used to determine whether sufficient credit (also sometimes called headroom in the financial industry) is available on the Customers credit card for the purchase amount submitted. Additionally, the Authorization process is used to authenticate the cardholder and the credit card used in the transaction against the registered credit cardholders information on record with the card Issuer. A successful outcome of the Authorization process is a transaction Approval. Subsequent actions can then be performed on the Approved transaction for example: Settlement of funds, adding Recurring Payments, and so forth. Normally, the Authorization Process takes only a few seconds (or less) for real-time transactions and is entirely transparent to the Merchant and the Customer. The transaction details collected from the Customer at the time of purchase are submitted to the Skipjack Transaction Network. These transaction details include the credit-card-specific details (such as credit card number and expiry date) and the purchase-specific details (such as Order Number and transaction amount). This transaction data is encrypted and transmitted across the HTTPS connection from the Merchants Application to the Skipjack Transaction Network. The network used is shown in the figure above, Simplified Credit Card Transaction Processing Network Topology.

Transaction Processing Approval Phases


The Authorization Process has three distinct phases which are listed below. Each is discussed in more detail below. 1. Validation Phase 2. Authorization Phase 3. Verification Phase

Step 1: Validation Phase


The transaction data received by the Skipjack Transaction Network is passed through algorithms to determine if the data is valid and complete and that all required variable fields are completed. If the data is not valid or incomplete, subsequent transaction processing is halted and an error response is returned to the originating application. The variable that denotes a Validation Phase success or failure is the szReturnCode variable. The Validation Phase is completed entirely within the Skipjack Transaction Network.

Page 12 of 43

2008 Skipjack Financial Services

Skipjack Integration Overview Guide

Once the transaction data successfully completes Validation the transaction data is sent to the Processor for the Authorization Phase. For szReturnCode values see the section in the Skipjack Integration Guide.

Step 2: Authorization Phase


During the Authorization Phase, the transaction data is sent from the Skipjack Transaction Server to the Processor and Issuers networks to determine the following: 1. Sufficient funds are available on cards credit limit for the transaction amount. 2. The Customer making the purchase is the registered cardholder. The transaction data is sent from the Skipjack Transaction Network to the Issuers/Processors networks to determine if sufficient credit is available on the card. An AUTHCODE is generated by the Issuer/Processor and this variable is returned to the Skipjack Transaction Network and then on to the originating application. The szAuthorizeDeclinedMessage is also returned to the Merchants application at this point. If there is insufficient credit available on the card or if there are other reasons for the transaction to be Declined (such as a reported stolen card) the transaction is Declined by the Issuer. A text message describing the reason for the returned szAuthorizeDeclinedMessage (either Approval or Decline) failure is also returned to the application. Only transaction data that passes the Authorization Phase with a valid Authorization (Approval) is sent for processing to the Verification Phase, described below.

Step 3: Verification Phase


In the Verification Phase, transaction data is further scrutinized by the Processor, Issuers, and the Skipjack Transaction Network servers to determine whether the credit card is being used by the registered cardholder. Fraud prevention methods may also be run at this phase to authenticate the user and the card. There are basic two fraud-prevention checks that may be done during the Verification Phase: 1. Address Verification System (AVS) checking is performed using a comparison of the numeric portion of the address information sent in the transaction data to the address information on record for the registered cardholder within the Issuers network. 2. Card Verification Value (CVV) code matching is performed to determine whether the cryptographic hash of the CVV code passes and the code matches that originally issued on the card. Once each of these checks is completed, response messages and variables are returned from the Issuers/Processors networks back to the originating application.
Page 13 of 43

2008 Skipjack Financial Services

Skipjack Integration Overview Guide

A final Approval (or Decline) of the transaction is based on the aggregate outcome of each of the variables and return codes. A final filtering (if enabled on Skipjack Transaction Network) is done in the form of AVS filtering. An Approval means that the Merchant has the promise that the funds are reserved for the transaction amount and product or services can be delivered to the Customer. The actual transfer of funds from the Issuing Bank to the Merchants Account requires a separate set of transaction processing to be performed later, usually at the end of the business day. This process, called the Settlement Process, is described in more detail in the Overview of the Credit Card Settlement Process.

Overview of the Credit Card Settlement Process


The transfer of funds from the Customers credit card account to the Merchants bank account is termed the Settlement Process (also referred to as Capture in the financial industry). Transactions are normally Settled for Authorized (Approved) transactions and Credits. Settlement, regardless of the precise mechanism used, initiates the fund transfer from the cardholders issuing bank account into the Merchants Account. This normally occurs in one to three business days from the time the transaction is submitted for Settlement. In special circumstances, Skipjack Financial Services can configure a particular Merchant Account to minimize this time for Settlement to occur, however Skipjack Financial Services cannot control this time frame absolutely. Contact Skipjack Financial Services if you require your account be optimized for the quickest possible Settlement times. Note: The time required to deposit the funds depends upon the credit card type, the Batch Settlement submission configuration, and the banks involved in the Settlement process. Skipjack Transaction Network does not determine the deposit timing. Transaction Settlement timing is influenced by a number of transaction variables, transaction methods, and Merchant Account configuration options. These topics are discussed in the following sections, below.

Batch Settlement
Batch Settlement (also called off-line Settlement) is the most common mechanism used for transaction Settlement. Batch Settlement is the most practical and cost effective mechanism because for transaction since it makes efficient use of network resources. Batch Settlement is the most common and preferred method by Processors and Banks and as such Batch Settlement incurs lower fees from the Processors and Banks involved.

Batch Settlement Configuration Options


There are a number of Batch Settlement configuration options offered by the Skipjack Transaction Network for each Skipjack Merchant Account. 1. Automatic Daily: This is the default Settlement configuration option applied to each new Skipjack Merchant Account. When this option is set, this configuration requires no further

Page 14 of 43

2008 Skipjack Financial Services

Skipjack Integration Overview Guide

action on the Merchants part to Settle transactions and Credits. Accounts set to Automatic Daily Settlement results in a Settlement Batch being initiated every 24 hours at the same time. All transactions in the Settlement Batch (all Approved transactions and Credits) that are in the Pending Settlement state are then Settled. The Settlement Batch close time and batch Settlement submission time can both be configured from the Skipjack Merchant Account Interface to control the timing of Automatic Daily Settlements. 2. Manual Daily: This configuration option requires that the Merchant to specify which transactions are to be Settled for each Settlement batch. Any Approved transactions which are marked for Settlement, along with all Credits, will be submitted for Settlement in a Settlement Batch once a day. The time specified in the Settlement Batch configuration options will dictate when the Settlement Batch is submitted. There is no need for the Merchant to close the batch since it will be closed and queued automatically at the configured time. 3. Manual None: This Settlement Batch configuration options requires that the Merchant specify which Approved transactions be marked for inclusion in each Settlement Batch. This option requires the Merchant to close the Settlement Batch prior to all marked transactions being submitted for Settlement. Care must be taken to prevent duplicate submission of the Settlement Batch, as described below. Note: If multiple Settlement requests are sent within the time that it takes the Skipjack Transaction Network to write the record to the database it is possible that multiple Settlements may occur. Double Settlement typically can occur if: I. The Merchant Settles a transaction in Merchant Services then goes back to the Web browser and Settles again without refreshing the browser display. II. Merchant uploads using the Change Transaction Status method to the Skipjack Transaction Network twice in quick succession. 4. Never None: This Batch Settlement configuration option sets all transactions, both Approvals and Credits, to never Settle, effectively locking the transactions into their current state. This option could be used, for example, in very special circumstances, such as when a Merchant is changing banks or Processors and wishes to delay Settling transactions until the changeover is complete.

Page 15 of 43

2008 Skipjack Financial Services

Skipjack Integration Overview Guide

Real-Time Settlement
One type of transaction Settlement is real-time Settlement. Real-time Settlement submission can be set by setting the Merchant Account to Manual Daily and forcing a transaction to Settle using the szForceSettlement variable (flag) of the in the Change Transaction Status method. Real-time Settlement is not normally applied to individual credit card transactions because Processors and banks impose high fees for submitting more than a single transaction Settlement batch. These fees would be very costly for settling each transaction in real time, particularly in highvolume environments. Real-time Settlement may only be practically used in very special circumstances. Contact Skipjack Financial Services if you are contemplating using this option to determine whether or not this is viable or if an alternative Settlement option would be more suitable.

Configuring Batch Settlement Options for Skipjack Merchant Accounts


The frequency of transaction Settlement can be configured using the Skipjack Merchant Interface. To change the Batch Settlement configuration in a Merchant Account: 1. Login to the Merchant Account. 2. Select the Batch Settlement Preferences button on the bottom on the window. 3. The Current Settings are displayed beside the fields for entering the new (desired) settings. Enter or select the desired settings into each form field provided. All fields must contain data otherwise an error message will be displayed when the form is submitted. 4. Select the Submit button to send the requested changes to the Skipjack Server. 5. A confirmation Status Message is displayed confirming the Batch Settlement updates are completed successfully. 6. Use the Back button or menu option to navigate back to any desired previous screen to continue working from within the Merchant Interface. Note: It may take up to 24 hours before new Settlement configuration settings take effect. Therefore Skipjack Financial Services suggests that all transactions be Settled prior to changing the Settlement configuration.

Page 16 of 43

2008 Skipjack Financial Services

Skipjack Integration Overview Guide

Transaction Lifecycle and Transaction States


The table below lists the transaction status options for each transaction.
Transaction State Pending Authorization Authorized Pending-Settlement Settled Pending Manual-Settlement Denied (Failed Authorization) Pending Credit Pending Delete Deleted Frozen Archived Description Transaction has been submitted for Authorization but has not yet been Authorized (Approved). Authorized by Issuing bank and awaiting Settlement. Funds have been transferred into the Merchants bank account. Transaction has been Authorized and is awaiting manual Settlement. Transaction failed Authorization by the Processor or did not pass AVS. Transaction has had a Credit amount applied to it and is awaiting Settlement. Transaction has been submitted for deletion but has not yet been Processed. Transaction has been deleted, but can be viewed, although it cannot be revived. Transaction is frozen and cannot be further processed until Thawed. Transaction is submitted for Settlement (whether from an Approval or a Credit), an archive is created. The archive displays the original Approval/Credit details of the transaction.

Page 17 of 43

2008 Skipjack Financial Services

Skipjack Integration Overview Guide

Core versus Supplementary Transaction Methods


The methods described through the development process can be functionally classified as either Core or Supplementary methods. A detailed description of all Core and Supplementary transaction methods is provided.

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

Supplementary Methods
The 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 4. Batch Settlement a) Close Current Open Batch b) Get Batch Settlement Status For detailed integration detailed about each of these Skipjack Financial Services transaction processing methods see the Skipjack Integration Guide and Skipjack Reporting Integration Guide.

Page 18 of 43

2008 Skipjack Financial Services

Skipjack Integration Overview Guide

Blind Credits
A Blind Credit is a Credit (Refund) applied to a transaction for which a record is not currently held within the Merchant Register (Skipjack Transaction Network database). A Blind Credit may be required when a Merchant moves their business from another payment gateway to Skipjack Financial Services and a customer requests a Credit to be applied to transactions previously processed by the other payment gateway. When submitting a Blind Credit using the Authorize/AuthorizeAPI methods (see the Skipjack Integration Guide for details) a negative TransactionAmount is specified in the Transaction Amount variable. To perform a Blind Credit the Merchant must obtain all credit card information from the customer (Account Number, Name, Expiry, CVV code, etc.) in order to complete the Blind Credit.

Prerequisites and Requirements for Performing Blind Credits


To use Blind Credits on a specific Merchant Account the following must be enabled and supported: Blind Credits must be supported both by your Financial Institutions Merchant Account. The Allow Blind Credit option must be enabled on your Skipjack Merchant Account. Please contact Skipjack Customer Support or your Skipjack Authorized Reseller to enable this feature on your Merchant Account if you do not have the necessary account permissions to set this option yourself.

szReturnCode Error Messages Associated with Blind Credits


szReturnCode Value -93 Error Name/Type Blind Credits Request Refused. Description Allow Blind Credits option must be enabled on the Skipjack Merchant Account. See the Configuring the Skipjack Merchant Account to Permit Blind Credits section for details. -94 Blind Credits Failed. The Blind Credit transaction failed.

Using Blind Credits versus Change Status: Credit


The Change Transaction Status Method (see the Skipjack Integration Guide for details) can be used, by specifying the szDesiredStatus=Credit variable, for crediting transactions where the Merchant does not have all credit card information available and/or they want to provide a Credit (refund) to the customer where the transaction was originally submitted through the Skipjack Transaction Network. When using the Change Transaction Status method, the Merchant does not need to submit the any credit card information to perform the Credit.

Page 19 of 43

2008 Skipjack Financial Services

Skipjack Integration Overview Guide

Blind Credits are used in situations where the original transaction was processed using a competitors payment gateway. Therefore, it is necessary to re-enter all credit card information or swipe the credit card to complete the Blind Credit transaction. You would use the Authorize/AuthorizeAPI method specifying a TransactionAmount with a negative value to complete a Blind Credit.

Configuring the Skipjack Merchant Account to Permit Blind Credits


By default the Skipjack Merchant Account is configured to not permit blind credits. Depending on your Skipjack Merchant Account permissions, you may change these configuration options to allow Blind Credits for a specific Skipjack Merchant Account. To display and set the Skipjack Merchant Account settings for the Allow Blind Credit option: 1. Login to the Merchant Account at https://secure.skipjack.com using your account credentials supplied by Skipjack Financial Services. 2. Click on the Edit Account button located in the bottom section of the Account Summary page. 3. Scroll down the page to locate the Allow Blind Credits section, as shown below.

4. Select the check-box beside the Allow Blind Credit to enable this configuration option on the Skipjack Merchant Account. 5. Click the Submit button to make the changes to the configuration settings. NOTE: If you are not able to access Account Setup Page configuration page you do not have the required account permissions to make these changes. Contact the Skipjack Financial Services Customer Support and request these configuration changes be applied to your Skipjack Merchant Account or obtain access privileges needed to configure these account options.

Page 20 of 43

2008 Skipjack Financial Services

Skipjack Integration Overview Guide

Unique Order Numbers


The Order Number assigned to each transaction must be generated by your application. The Order Number variable is a Required transaction variable for many Core and Supplementary transaction methods (see the Supplementary Methods section for a listing of these methods). Except in rare circumstances and for application testing, the OrderNumber assigned to each transaction should be unique to prevent duplicate records with the same Order Number in the Merchant Registry. In terms of the Skipjack Transaction Network database, Duplicate Order Numbers are those Order Numbers submitted within a 24 hour period that use the same Order Number value as a previously submitted. If the Order Number matches any Approved or Pending Credit transaction records (duplicates) in the Merchant Register an error code is returned if the Reject Duplicate Order Numbers configuration option is set in the Skipjack Merchant Account the szReturnCode Value=-84 (error code) is returned from the Skipjack Transaction Network and the transaction is Declined. NOTE 1: The Order Number variable can be a maximum of 22 characters for those using Paymentech as their Payment Processor. In these cases the Order Number must be unique per Settlement Batch. NOTE 2: By default the Skipjack Merchant Account does not prevent your application from submitting a duplicate Order Number. (The Reject Duplicate Order Numbers option is off).

How to Identify Transactions When Duplicate Order Numbers Exist


The Transaction ID (szTransactionId) generated by the Skipjack Transaction Network can be used to differentiate and identify transactions that do have duplicate Order Number within the Merchant registry. To differentiate between transactions that has duplicate Order Numbers: 1. Use the Get Transaction Status method specifying the transaction date to retrieve the szTransactionId associated with the transaction you wish to perform any subsequent action upon, such as a Change Transaction Status method. For information about the use of the Get Transaction Status method see also the Get Transaction Status section of the Skipjack Integration Guide. 2. Use the TransactionId variable, obtained in step 1 above, to identify the transaction you wish to change.

Page 21 of 43

2008 Skipjack Financial Services

Skipjack Integration Overview Guide

Other Transaction Methods Using Order Number as a Required Variable


The Order Number variable is Required and used in the following transaction methods: Get Transaction Status Method (szOrderNumber) Change Transaction Status Method (szOrderNumber) Add Recurring Payment Method (rtOrderNumber) Edit Recurring Payments Method (rtOrderNumber)

Configuring the Reject Duplicate Order Numbers Option for a Merchant Account
By default the Skipjack Merchant Account is configured to permit duplicate Order Numbers for a Skipjack Merchant Account. Typically this configuration is not problematic or is actually preferred for testing certain application behaviors in a Development environment. However, rejecting transactions based on duplicate order numbers is recommended for Skipjack Merchant Accounts that are processing Live transactions. Depending on your Skipjack Merchant Account permissions, your Skipjack Merchant Account settings may allow or reject transactions based on Order Number duplicates. To set the Reject duplicate transactions based on order number settings Merchant Account options: 1. Login to the Merchant Account at https://secure.skipjack.com. 2. Select the Edit Account button in the bottom section of the Account Summary page to display the Account Setup Page. 3. Scroll down the page to the Reject duplicate transactions based on order number section. You should see the section shown below: 4. Select the check-box beside the option to toggle the option on and off. This option is set when the checkmark is displayed in the check box (selected).

5. Select the Submit button to invoke the changes. 6. Use your Web browsers Back button to return to previous pages to continue working or select the Exit link to log out of the Merchant Register.

Page 22 of 43

2008 Skipjack Financial Services

Skipjack Integration Overview Guide

Note: If you are not able to access Account Setup Page, you do not have the required account permissions. Contact the Skipjack Financial Services Support to have this configuration change applied to your Skipjack Merchant Account.

Page 23 of 43

2008 Skipjack Financial Services

Skipjack Integration Overview Guide

Transaction Settlement Methods


Transaction Settlement is the process of moving funds for Authorized transactions into the Merchants Account (bank account). Transaction Settlement can be accomplished in a number of ways, some of which can only be performed using the Merchant Interface while others can be performed using the Batch Settlement APIs. Each is identified in this section.

Available Only Though Merchant Services


Some transaction Settlement functions and options can only be performed using the Merchant Services interface, including: Freeze Batch Thaw Batch Re-open Batch Delete Batch View Transactions in a Batch

For information about the above mentioned Batch Settlement functions that must be configured using the Merchant Services Interface, see the Skipjack Merchant Services Guide.

Performed using Batch Settlement API Methods


The following Batch Settlement methods can be completed using the API methods: Close Current Open Batch Get Batch Settlement Status

Page 24 of 43

2008 Skipjack Financial Services

Skipjack Integration Overview Guide

Merchant Account Configuration Options


E-mail Responses - Types of Email Responses
The Skipjack Transaction Network provides the ability to send e-mail responses to any combination of the following e-mail addresses: Customer, Merchant, a selected list of other interested parties. The content of the e-mails sent is configurable and can contain a mixture of transaction-related information, response details, and additional text that is appropriate to the Customer and Merchant.

E-mail Sent by the Skipjack Transaction Network


E-mails will automatically be sent as soon as a transaction is returned to the Skipjack Transaction Network during Authorization if e-mail response options are configured within the Merchants Interface. NOTE: E-mail notification must be enabled on the Merchant Services Interface for the account for e-mail notification to function.

Options for Setting E-mail Response Settings in the Merchant Account Interface
There are four configuration settings that can be used to control to whom the e-mail responses are sent, as described in the table below.
E-mail Type Notify Merchant Notify Customer E-mail List Description This option enables Merchants to receive confirmation of order information. This option enables Customers to receive confirmation of order information. An e-mail list allows Merchants to add other e-mail recipients to receive confirmation of order information. This entry populates the From field with the Merchants desired e-mail address for all e-mails that are sent to Customers. Configuration Location Within Merchants Account Preferences on the Merchant Interface. Within Merchants Account Preferences on the Merchant Interface. Within the Web Page Response files for the appropriate vendor account. Configured during Skipjack Merchant Account set up.

Originating E-mail

Note: Do not add duplicate e-mail addresses or the Merchants e-mail address to an e-mail list response. Enabling E-mail Responses to Customers and Merchants on the Merchant Interface

Page 25 of 43

2008 Skipjack Financial Services

Skipjack Integration Overview Guide

E-mail Response Message Types


Once the credit card transaction is returned to the Skipjack Transaction Network during the Authorization process, an appropriate e-mail option is executed according to the e-mail configuration settings described in the table above. There are three types of e-mail response templates that can be executed. The three response templates are used to provide feedback about the transactions Authorization status, either Success or Failure. 1. Success: This e-mail is sent to the recipients to indicate that the transaction has been successfully Authorized. 2. Failure: This e-mail indicates that the credit card has failed Authorization. The reasons for Authorization failure vary, but the details received from the Processor are returned in the szAuthorizationresponseCode return field. 3. Processor Error or System Failure: Indicates that there has been a problem with the credit card Processor and the Customer should wait a few minutes and re-try their transaction. An appropriate response will be sent to the recipients designated in the Notify Merchant, Notify Customer and E-mail List selections on the Merchant Interface.

Page 26 of 43

2008 Skipjack Financial Services

Skipjack Integration Overview Guide

Editing E-mail Response Templates


You can customize the e-mail templates or use the default e-mail templates which are automatically generated during the vendor account set up process. To edit the E-mail Response Templates: 1. Login to the Merchant Account using your login credentials via https://secure.skipjack.com . 2. Click on the Edit Account button located in the bottom section of the Account Summary page. 3. Scroll down the page to locate the section E-mail Response Templates. You should see the section shown below:

NOTE: Use the Edit button to make your changes, or select the Reset button to discard the changes and set the default templates provided by Skipjack.

Mapping the Transaction Variables to E-mail Template Variables


There are slightly different naming conventions assigned to the same variables fields that are used in transaction data fields and in the e-mail templates fields. This section allows you to map the e-mail template tags to the transaction variable names. When you edit the E-mail templates notice that they contain Skipjack e-mail tags in the format <Example Tag>. You may choose to leave these tags within your files so information is displayed when you and your Customers receive the e-mail.

Page 27 of 43

2008 Skipjack Financial Services

Skipjack Integration Overview Guide

E-mail Template Tags


The table below lists the available E-mail template tags.
E-mail Template Tag <OrderNumber> <AuthorizationNumber> <TransactionDate> <TransactionAmount> <ShipToName> <ShipToAddress> <ShipToAddress2> <ShipToAddress3> <ShipToAddress4> <ShipToCity> <ShipToState> <ShipToZipCode> <ShipToCountry> <ShipToPhone> <ShipToFax> <BillToName> <BillToAddress> <BillToAddress2> <BillToAddress3> <BillToAddress4> <BillToCity> <BillToState> <BillToZipCode> <BillToCountry> <BillToPhone> <BillToFax> <OrderString> <CreditString> <AuthorizationResponse> <Comment> <UserDefinedFields> <CustomerEmail> <TransId> Description The identification number for a specific order. The code returned from the credit card processor. The date of the transaction. The amount of the transaction. The name of the person or organization to where the item is shipped. The shipping address. Any secondary information for long addresses. Any secondary information for long addresses. Any secondary information for long addresses. The city to where the item is shipped. The state to where the item is shipped. The zip code for the shipping address. The country to where the item is shipped. The phone number of the person or organization where the item is shipped. The fax number of the person or organization where the item is shipped. The name of the person or organization who will be billed for the transaction. The billing address. Any secondary information for the billing address. Any secondary information for the billing address Any secondary information for the billing address The city to where the item is billed. The state to where the item is billed. The zip code of the billing item The country to where the item is billed. The phone number of the person or organization where the item is billed. The fax number of the person or organization where the item is billed. The unique item catalog number, item cost, quantity of the item sold, description of the item sold, and, if applicable, the tax information. The same information as the <OrderString>, noted above. Transaction Approval or Decline response. Any information contained in the comment field. The information contained in the user defined field. Customer provided e-mail address. Skipjack assigned transaction identifier (ID).

Page 28 of 43

2008 Skipjack Financial Services

Skipjack Integration Overview Guide

Mapping Skipjack Variables to the E-mail Template


The variable naming conventions used within the e-mail templates are different from those used in the application interface for some fields. A guide to mapping the Skipjack variables to the e-mail template tags is displayed below.
Variable Name Sjname Email Streetaddress City State Zipcode Ordernumber Accountnumber Month Year Serialnumber Transactionamount Orderstring E-mail Template Tag Name <BillToName> <CustomerEmail> <BillToAddress> <BillToCity> <BillToState> <BillToZipCode> <OrderNumber> Not Available Not Available Not Available Not Available <TransactionAmount> <OrderString>, <CreditString> <ShipToPhone> <BillToAddress2> <BillToAddress3> <BillToAddress4> <BillToCountry> <BillToPhone> <BillToFax> <ShipToName> <ShipToAddress> <ShipToAddress2> <ShipToAddress3> <ShipToAddress4> <ShipToCity> Description The name of the person or organization who will be billed for the transaction. E-mail address that the Customer specifies. The billing address. The city to where the item is billed. The State or Province to where the item is billed. The Zip Code of the billing address. The identification number for a specific order. The credit card account number. This is not available for inclusion. The expiry month of the credit card used in the transaction. This is not available for inclusion. The expiry year of the credit card used in the transaction. This is not available for inclusion. The credit card account number. This is not available for inclusion. The amount of the transaction. The unique item catalog number, item cost, quantity of the item sold, description of the item sold, and, if applicable, the tax information. The phone number of the person or organization to where the item is shipped. Secondary billing address information for long addresses. Secondary billing address information for long addresses. Secondary billing address information for long addresses. The country to which the item is billed. The phone number of the person or organization where the item is billed. The fax number of the person or organization where the item is billed. The name of the person or organization where the item is shipped. The shipping address. Secondary shipping address information for long addresses. Secondary shipping address information for long addresses. Secondary shipping address information for long addresses. The City to where the item is shipped.

Shiptophone Streetaddress2 Streetaddress3 Streetaddress4 Country Phone Fax Shiptoname Shiptostreetaddress Shiptostreetaddress2 Shiptostreetaddress3 Shiptostreetaddress4 Shiptocity

Page 29 of 43

2008 Skipjack Financial Services

Skipjack Integration Overview Guide

Shiptostate Shiptozipcode Shiptocountry Shiptofax Cvv2 Comment udf1 udf30

<ShipToState> <ShipToZipCode> <ShipToCountry> <ShipToFax> Not Available <Comment> <UserDefinedFields>

The State or Province to where the item is shipped. The Zip or Postal Code of the shipping address. The country to where the item is to be shipped. The fax number of the person or organization where the item is shipped. CVV value on credit card used in transaction. This is not available for inclusion. Information contained in the comment field. Information contained in the user defined field.

Additional Transaction-Generated Variables for E-mail Responses


The following variables exist within the Merchant Account profile or are generated by Skipjack after a transaction has been performed. These variables can be called into the e-mail templates by using the following tags.
Variable Name Authorization Code Date and time of Transaction Status of the transaction Address Verification results Merchant Name Merchant Phone Number Merchant Email Transaction ID E-mail Template Tag Name <AuthorizationNumber> <TransactionDate> <AuthorizationResponse> <AuthorizationResponse> <MerchantName> <MerchantPhone> <MerchantEmail> <TransId> Description The code returned from the credit card Processor. The date of the transaction. Transaction Approval or Decline status. Transaction AVS results. Merchant name as configured in Skipjack Merchant Account profile. Merchant phone number as configured in the Skipjack Merchant Account profile. Merchant e-mail as configured in the Skipjack Merchant Account profile. Skipjack-defined transaction identifier (ID).

The tag <UserDefinedFields> can be requested in the e-mail templates. These UserDefinedFields cannot be requested with specific <tags> they must be requested as a group. This tag will return ALL of the User Defined Variables in a group (maximum of 30 user defined fields are available). Each variable will be separated by a line break.

Page 30 of 43

2008 Skipjack Financial Services

Skipjack Integration Overview Guide

E-mail Lists - Creating E-mail Lists


When a Merchant Account is first created, an e-mail address is assigned to the Merchant Account and is used as the notification and the from e-mail address. The e-mail list feature allows the Merchant to add additional e-mail addresses to this e-mail list to receive copies. This feature can be used, for example for notification e-mails to staff required to fulfill an order. To add or update the E-mail list for a Merchant Account: 1. Login to Merchant Services using your login credentials via https://secure.skipjack.com. 2. Scroll down the page to the Email List section of the page. 3. To edit your e-mail list, click on the Edit button. 4. Add the desired e-mail address into the space provided and click Return to add the e-mail to the list. Each e-mail address will appear on a new line. Click on Reset to discard the changes. 5. Click Submit to replace the old e-mail list with the newly updated list. NOTE 1: Do not add the Merchant or Originating e-mail address to this list because these are already automatically included, by default, on the list. Adding them (again) will result in duplicate e-mails sent to each of these e-mail accounts. NOTE 2: For e-mail delivery, there are a number of network components outside of Skipjack Financial Services control that may be subject to failure and other errors. It is recommended that you do not use e-mail as your primary notification mechanism for transactions. Instead, use the Dynamic Web Response page, the Interactive Register, or the Reporting Tool.

Page 31 of 43

2008 Skipjack Financial Services

Skipjack Integration Overview Guide

Web Page Response Files


By default the Skipjack Transaction Network is configured to use the default Web Page Response in the table below. NOTE: Response files only apply to transactions submitted using the Authorize (not AuthorizeAPI) method. See the Skipjack Integration Guide for information about the Authorize/Authorize API methods. See Also For more information about the Authorize method, see the Skipjack Integration Guide for details. Default Web Page Response File Settings in the Merchant Account Interface
Response File Thank You For Your Order Invalid Field Entry Description Indicates that all the required fields in the order form have been filled out with valid information. This does not mean that the transaction is successful, or that the credit card has been Authorized. Indicates that the Customer has made a mistake in the information that they entered in the order form and that they must return to the order page and check to see that: 1) they entered information in all required fields, and 2) that they have valid information in the correct locations. Indicates that the credit card number is not valid, or that they are trying to enter a credit card type that the Merchant Account does not accept. Indicates there has been a problem at the credit card Processor and the Customer should wait a few minutes and resubmit the transaction.

Invalid Credit Card System Failure

You can configure the Merchant Account to use Web Response Files other than the above listed defaults.

Changing the Web Response Files


To change the Web Response Files applied to transactions: 1. Login to the Merchant Account using your login credentials via https://secure.skipjack.com. 2. On the Account Preferences page, select the Preferences link to display the Vendor Preferences page. 3. Select the Response Files link to open the Response Files page. 4. Scroll midway down the page and select the radio button for Default if you wish to use the default pages.

Page 32 of 43

2008 Skipjack Financial Services

Skipjack Integration Overview Guide

5. If you wish to use custom pages, select either the Edit or View button for the page type you wish to edit or view. 6. To Edit a page, select the Edit button for the page you wish to change (there are 4 choices). The HTML code of the page your wish to edit is displayed in a window. 7. In the window, edit, paste, or write new code as required for the customized response message you wish Customers to see. 8. When you have finished editing your HTML code, select the Save button to save the changes. If you have successfully updated the Web Response Files this is indicated by the confirmation message displayed. 9. Use the Back button on your Web browser to navigate back to the Account Summary page to continue working within the Merchant Services Interface. Note: Because of the JavaScript used for the redirect never use the word submit" for the Submit button on any form that posts to SkipjackIC. When using the Skipjack redirect, the name "submit" is reserved. Use another appropriate word instead.

Page 33 of 43

2008 Skipjack Financial Services

Skipjack Integration Overview Guide

Security Information
This section contains information about security-related issues and how security is handled for transactions within the Skipjack Transaction Network.

Skipjack Transaction Network Security


When a transaction reaches the Skipjack Transaction Network, it is securely stored to reduce risk of unauthorized access via the Internet. Each transaction is individually encrypted using a proprietary security technology called SkipjackIC. Each transaction carries its own key enfolded within it, which means that in the unlikely event that one transaction is compromised, the information gained cannot be used to compromise other transactions because each key is unique to a single transaction. Once within the Skipjack Transaction Network, credit card numbers are securely stored in the Skipjack Transaction Network rather than in the Merchants database where security measures may be more difficult to implement. An additional security feature is that only the last four digits of a credit card number are displayed in the Reporting APIs, Merchant Services Interface, e-mail, and system response notices. This ensures that credit card information held within the Skipjack Transaction Network cannot be obtained from these sources. Used together, these methods prevent credit card information stored within the Skipjack Financial Services database from being compromised in the highly-unlikely event that an unauthorized person gains access to the Skipjack Transaction Network.

Skipjack Transaction Network Login Password Policy Enforcement


Skipjack Transaction Network enforces a rigorous login password policy to restrict access to sensitive data by authorized individuals only. Login passwords are changed on a regular basis to enhance password protection in compliance with industry security standards. It is important that you choose a Login password that is secure and robust and not easily guessed. This password should be securely protected. NOTE: Electronic storage of Login password credentials is not recommended or endorsed by Skipjack Financial Services.

Page 34 of 43

2008 Skipjack Financial Services

Skipjack Integration Overview Guide

Security Measures in Application Development and Integration


Please ensure that you read, understand, and apply the following guidelines and principles to all your application and integration development processes. This will prevent unexpected and unauthorized access to transaction data used by your application and aid in protecting against fraudulent transactions.

Hiding Serial Numbers in HTTP POST Requests


HTML serial numbers and Developer Serial Numbers should be protected from unauthorized viewing. For information about protecting the HTML Serial Numbers in your application see the following information located on the Skipjack Financial Services Web site. Security and Encryption Information

Defenses Against Common Fraud Attempts and Methods


Credit card fraud is a major concern for all Merchants, particularly in card-not-present transaction environments. If you are building an application to handle these types of transactions, please ensure that you carefully consider common fraud prevention techniques during your application development and integration.

Protecting and Storing Your Account Credentials


Additional information and guidelines for storing your Merchant and Development account credentials and Login credentials as well as other security information is described on the Skipjack Financial Services Web site at https://secure.skipjack.com/?p=SECURITY.

Card Issuer and Industry Wide Security Programs and Requirements


The credit card associations have jointly put into place stringent requirements for security and data control for all Merchants accepting credit cards. The CISP (Cardholder Information Security Program) and the Payment Card Industry (PCI) standards describe protections and considerations that your application must address.
Card Issuer Visa MasterCard Site Data Protection (SDP) American Express Discover Industry Wide Program CISP SDP Link http://usa.visa.com/merchants/risk_management/cisp.html https://sdp.mastercardintl.com/

DSOP DISC PCI

http://www10.americanexpress.com/sif/cda/page/0,1641,17457,00.asp http://www.discovercard.com/customer-service/security/?gcmpgn=0801_gf_se_txt http://www.skipjack.com/solutions.aspx?cmsphid=85781357|4347063|9143480

Page 35 of 43

2008 Skipjack Financial Services

Skipjack Integration Overview Guide

Testing Guidelines
Testing can be performed in the Development phase using the Skipjack Transaction Network Development (Test) environment and a test credit card. This allows developers ensure that their application functions correctly.

General Testing Guidelines


To avoid complications and problems, ensure that the following general testing guidelines are applied to your application development: 1. Ensure that the correct HTML Serial Number and Developer Serial Number is being used for each Skipjack Account. For example, ensure that you are not using your Developer Account credentials for a Production account or vice versa. 2. Ensure that your application is set to POST to the correct location (Unique Developer URL or Production URL for each transaction method). See the Skipjack Integration Guide for information about where to post for each transaction method. 3. Test your application against with all commonly used Web browsers. 4. Ensure that any configurations setting in your Skipjack Account are properly configured in both the Development Account and in the Production Account.

Page 36 of 43

2008 Skipjack Financial Services

Skipjack Integration Overview Guide

Test Cards Used with Development Accounts for Integration Testing


The test credit cards (virtual test cards) listed below can be used with the Skipjack Test Accounts for the Payment Processors listed.
Note 1: Skipjack Merchant Services DOES NOT SUPPORT testing within PRODUCTION ACCOUNTS USING THESE TEST CARD NUMBERS! Use only LIVE cards for PRODUCTION TESTING. Note 2: Use of these Test Cards is at your own risk and is governed by the Test Card usage policies of each respective Payment Processors/Card Issuer. Do not use these Test Cards for any other purposes than is permitted by each respective Test Card usage policies. Vital Test Account Number and Expiry Date 4445999922225 (Visa) Expiry Date: Any Future Date Global 4003000123456781 (Visa) 5499990123456781 (MasterCard) Expiry Date: Any Future Date 341111597242000 (American Express) Expiry Date:12/06 Test AVS Street Number and Street Name Test AVS Zip Code CVV 8320 (Do not submit Street Name) 85284 999 Any 4 Digits 303292010 123 CID =UNKNOWN with AMEX Global will not reject an invalid CVV2 on a test account, however a return code describing the CVV2 code comparison will be returned. Maximum Transaction Amount Usage Notes $150.00 $10.99 Any amount above this is Declined. Global Test Accounts are not automatically issued by Skipjack. Contact Skipjack Technical Support for special setup requirements.

Page 37 of 43

2008 Skipjack Financial Services

Skipjack Integration Overview Guide

Serial Number Management and Usage for Secure Login


The secure Login page allows Merchants and developers to securely access the Merchant Services and Reporting areas of Skipjack Transaction Network. To access each area you must enter your login credentials. Note: Live (Production) and Developer (Demo) Vendor (Login) Serial Numbers are different.
Developer (Demo) Merchant Services Vendor (Login) Serial #1 Username Password Vendor (Login) Serial #1 Username Password Live (Production) Vendor (Login) Serial #2 Username Password Vendor (Login) Serial #2 Username Password

Reports

Developers must use the Developer (Demo) credentials while their application is in the testing phase and will be issued a new, Live (Production) Vendor (Login) Serial Number, once they migrate from the Development environment to the Production environment. Merchants must use the Live (Production) credentials to Login to the Live area once their application has been launched in the Production environment.

Login to Skipjack Financial Services using the Secure Login


To login to your secure Skipjack Transaction Network account: 1. Open the Secure Login Page at https://secure.skipjack.com . This page allows Merchants and Developers to securely access the Merchant Services and Reporting areas of Skipjack Transaction Network. 2. Enter the correct credentials into each field provided. Ensure that you are using the Developer Serial Number for accessing the Development Accounts or the Production Serial Number for Production (Live) environment. 3. In the Select your desired login area: select the radio button beside the appropriate area you wish to Login to. 4. Select the Login button to send your Login request.

Page 38 of 43

2008 Skipjack Financial Services

Skipjack Integration Overview Guide

Troubleshooting Secure Login Problems


If you experience difficulties during Secure Login, check the following: 1. Check your Login credentials for accuracy (Login Serial Number, Username, and Password). 2. Ensure you are using the Login Serial Number issued with your account and not the HTML Serial Number. 3. Ensure that someone in your organization has not changed your Skipjack password without informing you. 4. If you do copy-and-paste your login information (which is not recommended by Skipjack Financial Services), please ensure that spaces are not being inadvertently copied into the Login fields. Delete any spaces from the Login field. NOTE: Skipjack Financial Services strongly recommends not storing your password electronically to avoid any possible unauthorized access to your Skipjack Account. 5. If you have forgotten your password, click on the appropriate link to display the Forgotten Password window appropriate to the environment you are trying to access. Follow the displayed prompts to obtain the correct password. For Live (Production) Account Passwords click the link below to send Skipjack Technical Support a request for a temporary password to replace your forgotten account credentials at: https://ms.skipjackic.com/scripts/MerchantServices.dll?MerchantServices84 For Developer (Demo) Account Passwords click the link below to send Skipjack Technical Support a request for a temporary password to replace your forgotten account credentials at: https://developer.skipjackic.com/scripts/MerchantServices.dll?MerchantServices84

Changing Passwords and Allowable Password Syntax


When prompted to change a password the following rules apply: Password must be 8 to 12 characters long, and Must contain characters of all three types: capital letters, lower-case letters, and numbers.

Passwords that do not use all three types of characters or are not the correct length will be rejected.

Example: Permitted Password Syntax


eXAmple12345 (For security reasons, please do not use this password.) NOTE: When there have been five UNSUCCESSFUL Login attempts, YOUR ACCOUNT WILL BE FROZEN FOR ONE HOUR from the last unsuccessful attempt. Skipjack Financial Services is unable to unlock a frozen account during this period.

Page 39 of 43

2008 Skipjack Financial Services

Skipjack Integration Overview Guide

Authorization Testing
Test your application for Authorization using the following testing guidelines: 1. Test all credit card types that your Skipjack Account will accept on the Development Platform (Visa, MasterCard, American Express, JCB, Discover, Diners Club). Test cards for use in the Development environment are listed above in the Test Cards Used with Development Accounts for Integration Testing section. 2. When testing is successful on the Development platform retest on the Production Account prior to making the application publicly accessible (before going Live). 3. Use real (Live) credit cards, whenever possible, especially when the test is being conducted on a Production Account. 4. Ensure that each transaction is Approved and is listed as Approved in the Merchant Services Register for every Authorization submitted. 5. Ensure that there is a valid Approval Code returned for every tested transaction. 6. Ensure a unique Order Number (Ordernumber variable) is used for each transaction. 7. Ensure that all variables posted to the Skipjack Transaction Network are being returned with valid data for each transaction. You should review these within the Merchant Services Register as well as from with your application. 8. Delete all test transactions (Authorizations) before they are Settled if you do not wish to proceed with Settlement testing, as described below.

Settlement Testing/Deposit Testing


Settlement testing must be performed using actual (Live) credit cards on the Production Account(s). You cannot Settle test credit card transactions that were Authorized using the test cards listed in the Test Cards Used with Development Accounts for Integration Testing section. Your Settlement testing should test the following conditions: 1. On the Production Account ensure that Approved test transactions are Settled as configured in the Skipjack Account configuration. 2. Check that the correct transaction amounts are deposited into the Merchant's Account. 3. Remember to Credit (Refund) the amount to the card if using a real (live) credit card. CAUTION: Do not mix test transactions and Live (real) credit card data in Settlement Batches otherwise the Settlement Batch will abort and corrupt all the transaction data in that Settlement Batch. If test transactions are Authorized, Delete them before sending the batch for Settlement. Use only Live credit cards for batch Settlement testing.

Page 40 of 43

2008 Skipjack Financial Services

Skipjack Integration Overview Guide

Response Testing
Please ensure that each of the following Skipjack Transaction Network system responses are functioning as intended. This section will describe the basic checks and tests that should be performed on system responses.

E-mail Response
Ensure that the e-mail response to the Merchant and/or Customer contains the correct information with the appropriate variables and the wording of the e-mail is appropriate and accurate (For example you should confirm that the phone number, contact information, and similar information is correct within e-mail responses.) Test and check that the correct Merchant recipient(s) are receiving the appropriate e-mail notifications for each transaction.

Response Page
Ensure that the Response Page displayed to the Customer contains the correct information, is properly worded, and is displayed for each transaction. This can be tested using test credit cards on Test Accounts by submitting test Approval and Decline for transaction Authorization.

Backend Response URL


If using the Backend Response URL with your application ensure that the Backend Response URL is being triggered correctly and that all required information is being accurately sent to the receiving location.

Third-Party Applications
Ensure that any third-party applications that are being updated with response information are properly receiving all information correctly and in a timely manner

Functional Testing
Test that all applicable functions within the application (such as the Change Status method, Get Status method, error checking, scripts, etc.) are working properly without errors.

Migrating From Development to Production Environment


When you move your application from the Development environment to the Production environment, ensure the following: All settings described above for Development environment are set identically within the new environment. That testing is performed on Live transactions using a live (real) credit card to ensure that the account is properly functioning in the Production environment.

Page 41 of 43

2008 Skipjack Financial Services

Skipjack Integration Overview Guide

Developer and Integration Support


Support Ticketing System Overview
Skipjack Financial Services provides online Support Ticketing System that allows users to submit trouble tickets and post general queries in real time 24 hours a day, 365 days a year. When using this system a response will be received by e-mail or telephone as quickly as possible. To submit a Support Ticket or General Support query: 1. Login to http://support.skipjack.com. 2. Select the Submit Ticket link. 3. You must have a Skipjack Account to submit a ticket. If you require a New Account follow the on-screen prompts to create a new account. Your account will be created and an e-mail confirmation of this will be sent to your specified e-mail address. 4. Login to your account and select the appropriate link to display a form in which to send your ticket. Be sure to include your telephone number and extension if you want to be contacted by phone.

Knowledge Base Overview and Links


Skipjack Financial Services provides an online knowledge base that provides information on a wide range of Support and Development topics. View this online information at http://support.skipjack.com.

Select the Knowledgebase link to access the online topics. Information is organized in a topical manner with most recent articles listed for easy selection, as shown above.
Page 42 of 43

2008 Skipjack Financial Services

Skipjack Integration Overview Guide

Monitoring Skipjack Financial Services Status


The current status of the Skipjack Transaction Network is monitored by Skipjack Financial Services in real-time and the summary of this monitoring is displayed http://www.skipjackstatus.net. Users can add Skipjack Transaction Network and Web server status to your RSS or Atom Readers by clicking on the buttons provided. (Select the (?) link adjacent t the Feeds header for details about how to do this.)

Page 43 of 43

Das könnte Ihnen auch gefallen