Java SFA merchant integration guide
|
|
- Justina Patterson
- 8 years ago
- Views:
Transcription
1 Java SFA merchant integration guide
2
3 Installing the SFA JAVA Library Pre-requisites 1. The Merchant's machine where SFA will be installed should have JDK1.3 installed. 2. The Merchant must possess the key file generated by the Payment Gateway (available in the zip as key). The file name should not be changed, where is the merchant ID. Steps for obtaining the key file 1. Login into the Merchant Web Interface using the Merchant Super User login. 2. Click on the link Personalize>> Key Download 3. Save the.key file sent by the Payment Gateway in a local folder. ote The key file can be downloaded only once. Please keep the key file in a secure location. Contact PG System Administrator in case the key file needs to be regenerated. The JAVA SFA comes bundled as 2 zip files - 1. SFAClient.zip - This zip file contains the components, which provide the core SFA functionality and test pages 2. SFA_Dependencies.zip - This zip file contains the components that are required for the SFA to function The installation process for SFA_Dependencies.zip is as follows 1. Copy the ZIP file to a temporary location on the Merchant site 2. The zip has the following files 1) cryptix32.jar Required by SFA to encrypt the data sent to the epg 2) jcert.jar Required to establish the SSL connection with epg 3) jnet.jar Required to establish the SSL connection with epg 4) jsse.jar Required to establish the SSL connection with epg
4 5) Servlet.jar HTTP Request/Response handling 3. Copy the folder to a desired location (folder path names should not have spaces). 4. Set the Jar files in the system classpath (classpath must contain the absolute path to the jar files with the names of the jar files included) The Installation process for SFAClient.zip is as follows - 1. Copy the ZIP file to a temporary location on the Merchant site 2. Unzipping shall create a folder called SFAClient. 3. SFAClient contains the following files/directories 1. sfa.jar SFA Client library (contains a sfa.properties file and a set of class files) 2. TestPages Sample pages 4. Editing the sfa.properties file a. Open the file sfa.jar using WIZIP. Open the sfa.properties file. ote - If WIZIP or a similar facility is not available on the machine then the following java command can be used for extracting the properties file Jar -xvf sfa.jar To jar the file again use, Jar -cvf sfa.jar com sfa.properties b. For the parameter 'Key.Directory' in the properties file set the name of the folder, which contains the merchant key. A trailing slash has to be put at the end of this value. The name of the file need not be set. Save the file after making other relevant changes. c. For the parameter tracelog, set the name of the folder to which sfa logs needs to be written. It shall point to a folder to which write permissions are available to java.
5 d. Enable the verbose parameter to true only when necessary as the log generated might be considerable depending on the number of transactions. e. To verify the success of the above operations open the jar file again and check if the properties file has the values set. 5. Copy the sfa.jar to any desired folder (folder path names should not have spaces). 6. Set the sfa.jar in the system classpath (classpath must contain the absolute path to the jar files with the names of the jar files included). The Merchants jsp pages can now start using the SFA library. Test pages are shipped along with the distribution, which can be used for test/understanding purposes. ote: 1. The verbose parameter in sfa.properties should be set to true only when needed. Setting the java keystore for SSL communications 1. It is necessary to import the public certificates of Payment Gateway s Intermediate CA and Root CA into the keystore of the JDK so that the SSL communication can be facilitated. Get the appropriate certificates from PG Administrator. a. Import the Root CA. keytool -import -trustcacerts -alias pgrootca -file $CERT_LOCATIO$\epgRootca.cer -keystore $JAVA_HOME$\jre\lib\security\cacerts -storepass changeit Where, $CERT_LOCATIO$ is the location of the cert file $JAVA_HOME$ refers to the folder in which the JDK is installed The directory delimiter "\" must be changed as per the Operating System b. A message is displayed on the console "Trust this certificate? [no]:" Type 'y'. c. A message "Certificate was added to keystore" should be displayed indicating the certificate was successfully imported into the keystore
6 d. Similarly import the intermediate ca certificate. ote: 1. The certificate import step assumes that the Merchant is using the SU JVM. If a JVM other than the SU JVM is used, then the above step must be altered accordingly to import the certificates so that SSL communication can be established
7 Appendix A What s in This Appendix? The MOTO and the SSL Merchant s use the Store Front Adaptor for integrating with the Payment Gateway. This appendix details the data that is passed from the Merchant to the Payment Gateway via the Store Front Adaptor. The following sections define the various parameters and their definitions. ote - 1. The information provided in the section VBV fields for MOTO Merchants and VBV fields for SSL Merchant are applicable only to the Merchants enrolled for MPI. For MOTO merchants who support MPI, it is mandatory to send the data received from the MPI to the Payment Gateway. 2. In case of the SSL Merchant, the Card details will be accepted by the Payment Gateway. Hence, the Object mapping to the Card details mentioned below need not be populated.
8 Merchant Information Function ame - setmerchantdetails Sr o Parameter Details Valid values Mandatory Data with maximum size of 8 1 astrmerchantid ID assigned by the Payment Gateway to the Merchant Data with maximum size of 8 2 astrvendor Same as Merchant ID Data with maximum size of 8 3 astrpartner Same as merchant ID Corresponds to the IP Address of the Customer. In case of a SSL merchant this data will be captured by the Payment Gateway. However, a MOTO merchant has to pass this data to the Payment Gateway. This data is mandatory for a MOTO merchant and non-mandatory for the SSL Data with maximum size of (for SSL) 4 astrcustipaddress merchant 20 (for MOTO) 5 astrmerchanttxnid Transaction number generated by the Merchant for Alpha-numeric data with reference. Root Transactions should have unique maximum size of 50 Transaction Reference umber. 6 astrorderreferenceo Alpha-numeric data with Order number generated by the Merchant for his/her maximum size of 30 reference. 7 astrrespurl URL of the Merchants site on which the Payment Gateway must post the results of the transaction. This parameter is valid only in case of a SSL merchant The MOTO merchant Data with maximum size of (for SSL always receives the response via the PGResponse Object 80 merchants only) 8 astrrespmethod HTTP method (GET/POST) to be used by the Payment Gateway for posting the results of the transaction to the Merchants site. In case of SSL Merchants the value Data with maximum size of 4 should be POST as the response is sent via a redirection.. (GET/POST) 9 astrcurrcode Currency of the transaction Data with maximum size of 3. ISO Alpha Currency Code IR for transactions in Rupees. 10 astrinvoiceo Invoice number generated by the Merchants application Alpha-numeric data with maximum size of 20
9 Sr o Parameter Details Valid values Mandatory Data with maximum size of 20. Indicates the type of transaction. This field can contain req.preauthorization 11 astrmessagetype either of the values mentioned in the adjacent field req.sale umeric with maximum size of 15 digits. Maximum exponent is 5.For example, maximum possible data in the amount field can be 12 astramount Amount of the transaction Data with maximum size of 9 13 astrgmtoffset GMT Time Offset of the Merchants sites locale Format: GMT+hh:mm 14 astrext1 15 astrext2 16 astrext3 Reserved 17 astrext4 Additional fields provided to the Merchant for passing any Data with maximum size of specific data 50 Additional field provided to the Merchant for passing any Data with maximum size of specific data. To be filled in as true by SSL merchant 50 Data with maximum size of 50 Additional field provided to the Merchant for passing any Data with maximum size of specific data astrext5 Additional field provided to the Merchant for passing any Data with maximum size of specific data 50 Function ame - setmerchantrelatedtxndetails Sr o Parameter Details Valid values Mandatory Data with maximum size of 8. Id given to the Merchant for identification by 1 astrmerchantid ID assigned by the Payment Gateway to the Merchant the PG Data with maximum size of 8 2 astrvendor Same as Merchant ID. 3 astrpartner Same as Merchant ID Data with maximum size of 8. 4 astrmerchanttxnid 5 astrroottxnsysrefum 6 astrrootpref Alpha-numeric data with Transaction number generated by the Merchant for maximum size of 50 reference.. Transaction reference number generated by the Payment Gateway for the original transaction and sent to the merchant. Example, for an Authorization transaction the Root Transaction System reference of Pre-Authorization needs to be given. Similarly, for a Refund transaction the Root Transaction System reference of Authorization needs umeric data with maximum to be given size of 15 RR number sent by the Payment Gateway to the merchant for the original transaction. Example, for an Authorization transaction the RR of Pre-Authorization needs to be given. Similarly, for a Refund transaction the umeric data with maximum RR of Authorization needs to be given. size of 20
10 Sr o Parameter Details Valid values Mandatory 7 astrrootauthcode Auth Code sent by the Payment Gateway to the merchant umeric data with maximum for the original transaction size of 6 8 astrcurrcode Currency of the transaction Data with maximum size of 3. ISO Alpha Currency Code. IR for transactions in Rupees Data with maximum size of 20. Indicates the type of transaction. This field can contain req.refund 9 astrmessagetype either of the values mentioned in the adjacent field req.authorization umeric with maximum size of 15 digits. Maximum exponent is 5.For example, maximum possible data in the amount field can be 10 astramount Amount of the transaction astrgmtoffset GMT Time Offset of the Merchants sites locale Data with maximum size of 9. GMT+hh:mm 12 astrext1 13 astrext2 14 astrext3 15 astrext4 16 astrext5 Additional fields provided to the Merchant for passing any Data with maximum size of specific data 50 Additional field provided to the Merchant for passing any Data with maximum size of specific data 50 Additional field provided to the Merchant for passing any Data with maximum size of specific data 50 Additional field provided to the Merchant for passing any Data with maximum size of specific data 50 Additional field provided to the Merchant for passing any Data with maximum size of specific data 50
11 Card Information Function ame - setcarddetails Sr o Field Details Valid values Mandatory 1 astrcardtype Data with maximum size of 5. VISA Visa MC- MasterCard 2 astrcardum umeric data with maximum size of 20 Alphaumeric data with maximum size of 5. 3 astrcvvum For VISA,This field should contain the value in the following format CVVum $ Presence Indicator Where CVVum is a CVV value Presence indicator is one of the following 1 CVV2 value is present 2 CVV2 value is on the Card, but is illegible 9 Cardholder states CVV2 is not present on the Card e.g 010$1, 011$2, $9 4 astrexpdtr yyyy Data with maximum size of 4. 5 astrexpdtmon mm Data with maximum size of 2. 6 astrameoncard 7 astrinstrtype Alphabetic data with maximum size of 80 Data with maximum size of 5. Mode of payment - CREDI - For credit cards Credit/ Debit DEBIT- For Debit Cards
12 Ship To Address Function ame - setaddressdetails The Payment Gateway will store the Ship To Address details in its database only if all the details mentioned as mandatory are populated. If the merchant is not capturing the Address then this object can be passed as null to the SFA. However, if the Class is instantiated and passed to the SFA, then it is necessary to populate the fields marked as mandatory Sr o Field Details Valid values Mandatory 1 astraddrline1 Alphabetic data with maximum size of 50 2 astraddrline2 Alphabetic data with maximum size of 50 3 astraddrline3 Alphabetic data with maximum size of 50 4 astrcity Alphabetic data with maximum size of 30 5 astrstate Alphabetic data with maximum size of 30 6 astrzip umeric data with maximum size of 10 digits 7 astrcountryalphacode 8 astr Alphabetic data with maximum size of 3 ID for IDIA Alpha-umeric data with maximum size of 80 Bill To Address Function ame - setaddressdetails The Payment Gateway will store the Ship To Address details in its database only if all the details mentioned as mandatory are populated. If the merchant is not capturing the Address then this object can be passed as null to the SFA. However, if the Class is instantiated and passed to the SFA, then it is necessary to populate the fields marked as mandatory Sr o Field Details Valid values Mandatory If customer is a registered customer with the merchant, then his ID needs to be Data with maximum size of 10 1 astrcustomerid populated in this field. 2 astrcustomerame Data with maximum size of 80 3 astraddrline1 4 astraddrline2 5 astraddrline3 6 astrcity 7 astrstate 8 astrzip 9 astrcountryalphacode 10 astr Alphabetic data with maximum size of 50 Alphabetic data with maximum size of 50 Alphabetic data with maximum size of 50 Alphabetic data with maximum size of 30 Alphabetic data with maximum size of 30 umeric data with maximum size of 10 digits Alphabetic data with maximum size of 3 ID for India Alpha-umeric data with maximum size of 80
13 Customer Details (required for FDMS) Function ame - setcustomerdetails Customer information is sent to the Fraud Detection system for risk verification. If the merchant is not capturing the said details, then this object can be passed as null to the SFA. However, if the Class is instantiated and passed to the SFA, then it is necessary to populate the fields marked as mandatory Sr o Field Details Valid values Mandatory 1 strfirstame 2 strlastame Alphabetic data with maximum size of 50 Alphabetic data with maximum size of 50 3 OfficeAddress Object of Address Type 4 HomeAddress Object of Address Type umeric data passed as string. Max length of 5 Mobileo 15 yyyy-mmdd Alphabetic data with maximum length of 10 6 Registration Date 7 BillingShippingAddrMatch or Alphabetic data with maximum size of 1. Address (for Home/Office address details) Function ame - setaddressdetails Home and Office address details are sent to the Fraud Detection system for risk verification. If the merchant is not capturing the Address details, then this object can be passed as null to the SFA. However, if the Class is instantiated and passed to the SFA, then it is necessary to populate the fields marked as mandatory Sr o Field Details Valid values Mandatory 1 astraddrline1 Alphabetic data with maximum size of 50 2 astraddrline2 Alphabetic data with maximum size of 50 3 astraddrline3 Alphabetic data with maximum size of 50 4 astrcity Alphabetic data with maximum size of 30 5 astrstate Alphabetic data with maximum size of 30 umeric data passed as string with maximum size of 6 astrzip 10 digits 7 astrcountryalphacode Alphabetic data with maximum size of 3 ID for IDIA 8 astr Alphabetic data with maximum size of 80
14 Session Information Function ame - setsessiondetails Session information is sent to the Fraud Detection system for risk verification. The details have to be captured by the merchant if the merchant wishes to run the transaction through the FDMS system. In case the merchant is not capturing the details, then this object can be passed as null to the SFA. However, if the Class is instantiated and passed to the SFA, then it is necessary to populate the fields marked as mandatory Sr o Field Details Valid values Mandatory IP Address of the system from where the end 1 strremoteaddr customer is performing the transaction. The value stored in the cookie named Alphabetic data with maximum size of 50 2 strcookie vsc Alphabetic data with maximum size of 50 3 strbrowsercountry Alphabetic data with maximum size of 16 4 strbroswerlanguage strbroswerlocallangu Alphabetic data with maximum size of 30 5 agevariant Alphabetic data with maximum size of 30 6 struseragent Merchandise Information Function ame - setmerchandisedetails Merchandise information is sent to the Fraud Detection system for risk verification. The details along with Session, customer information are used by the FDMS for risk verification. In case the merchant is not capturing the details, then this object can be passed as null to the SFA. However, if the Class is instantiated and passed to the SFA, then it is necessary to populate the fields marked as mandatory. In case the purchased goods is related to Airline ticket, then this object need not be filled in and can be passed as null to the SFA. Instead the Airline details needs to be filled by the merchant. Sr o Field Details Valid values Mandatory 1 stritempurchased e.g., Computer, Shirts, Alphabetic data with maximum size of 24 umeric data passed as string with maximum 2 Quantity length of 3 Alphabetic data with maximum size of 24 3 strbrand Alphabetic data with maximum size of 24 4 strmodelumber Alphabetic data with maximum size of 32 5 strbuyer s ame Flag indicating whether Cardame and Buyerame Matches Alphabetic data with maximum size of 1 6 MatchingCardBuyerame or
15 Airline Transaction Information Function ame - setairlinetransactiondetails Airline transaction information is sent to the Fraud Detection system for risk verification. The details along with Session, customer information are used by the FDMS for risk verification. In case the merchant is not capturing the details, then this object can be passed as null to the SFA. However, if the Class is instantiated and passed to the SFA, then it is necessary to populate the fields marked as mandatory. In case the purchased goods is related to merchandise, then this object need not be filled in and can be passed as null to the SFA. Instead the merchandise details needs to be filled by the merchant. Sr o Field Details Valid values Mandatory 1 strbookingdate yyyy-mm-dd Alphabetic data with maximum size of 10 2 strflightdate yyyy-mm-dd Alphabetic data with maximum size of 10 Hh:mm (24 hr Alphabetic data with maximum size of 5 3 strflighttime format) Alphabetic data with maximum size of 12 4 strflighto Alphabetic data with maximum size of 32 5 strpassengerame umeric data passed as string with 6 ooftickets maximum length of 2 Flag indicating whether Card ame and Buyer ame Matches Alphabetic data with maximum size of 1 7 MatchingCardBuyerame or 8 strpr Alphabetic data with maximum size of 24 9 strsectorfrom Alphabetic data with maximum size of strsectorto Alphabetic data with maximum size of 24
16 VBV Fields for a MOTO Merchant Function ame - setmpiresponsedetails Sr o Field Details Valid values Mandatory 1 astreci umeric value associated with the VBV process provided by the MPI Data of the size 2. Conditional Mandatory (in case of VBV status ). In all other cases, the values must be sent if the MPI has provided the same 2 astrxid This value is generated during the VBV validation Data with maximum size of process 28 Data with size of 1 character. Conditional Mandatory (in case of VBV status ). In all other cases, the values must be sent if the MPI has provided the same 3 astrvbvstatus Single character status indicated by either of - Authentication Successful - Authentication failed U - Processing Failure The result of the VBV E - ot Enrolled validations. A Attempts 4 astrcavv 5 astrshoppingcontext 6 astrpurchaseamount 7 astrcurrencyval This value is generated during the VBV validation process if the Conditional Mandatory validation (in case of VBV status ). In all other cases, the values is Data with maximum size of 28 must be sent if the MPI has successful provided the same The Payment Gateway currently stores the value of the Shopping Context that is passed to it. This value is not passed to the Data with maximum size of Acquirer. 256 The Payment Gateway currently stores the value of the Purchase Amount that is passed to it. This value is not passed to the Data with maximum size of Acquirer 20. The Payment Gateway currently stores the value of the Currency value that is passed to it. This value is not passed to the Data with a maximum size of Acquirer 3.
17 VBV Fields for a SSL Merchant Function ame - setmpirequestdetails Sr o Field Details Valid values 1 astrpurchaseamount Amount of the transaction Data with maximum size of 20. Unformatted purchase amount. It should not contain any special such as $ etc. Example ,100 Data with maximum size of 20. This field should contain a currency symbol, with an thousands separator (s), decimal point and ISO minor units defined for the currency specified in the Purchase Currency field. 2 astrdisplayamount Formatted purchase amount. Ex. IR1, Data with size of 3. Data with size of This is the currency code used by the 3. ISO umeric Currency Code. 3 astrcurrencyval merchant Example astrexponent 5 astrorderdesc 6 astrrecurfreq 7 astrrecurend 8 astrinstallment 9 astrdevicecategory 10 astrwhatiuse 11 astraccepthdr Denotes the number of digits after the Data with maximum size of 3. decimal point in the amount If the amount is then the exponent is 2 Brief description of items purchased, determined by the Merchant Data with a maximum size of 125 This field is calculated based on installments and the Recur End and it Data with maximum size of 3. denotes the frequency of payment Example: 12 This field indicates the end date of recurring value. It should be less than the card expiry date. It is also an optional field Data with maximum size of 8. umber of Installments This attribute indicates mode of transaction. For an internet based transaction the value to be set is "0". Example: Data with maximum size of 3. Example: 12 Always use value 0 This field is used by the MPI to denote the browser version. This field can be empty and is used by the MPI to denote the browser version. The Accept request-header field can be used to specify certain media types which are acceptable for the response. This indicates the MIME type the client can accept. Accept headers can be used to indicate that the request is specifically limited to a small set of desired types, as Ex: image/gif, image/x-xbitmap, image/jpeg, in the case of a request for an in-line image/pjpeg, application/vnd.ms-powerpoint, image. The server property request.getheader("accept") can be application/x-shockwave-flash, */* application/vnd.ms-excel, application/msword, used for setting this value Mandator y 12 astragenthdr The User-Agent-header contains information about the user agent (typically a newsreader) generating the article, for statistical purposes and tracing of standards violations to specific software needing correction. Although not one of the mandatory headers, posting agents SHOULD normally include it. The server property request.getheader("user- Agent") can be used for setting this value. This indicates the type and version of browser used by the cardholder Ex: Mozilla/4.0 (compatible; MSIE 5.5; Windows T 5.0)
e Merchant Plug-in (MPI) Integration & User Guide
Payment solutions for online commerce e Merchant Plug-in (MPI) Integration & User Guide Enabling merchants to integrate their payment processing with PayPoint.net s 3D Secure Merchant Plug In (MPI) solution.
More informationVirtual Payment Client Integration Reference. April 2009 Software version: 3.1.21.1
Virtual Payment Client Integration Reference April 2009 Software version: 3.1.21.1 Copyright MasterCard and its vendors own the intellectual property in this Manual exclusively. You acknowledge that you
More informationMasterCard In tern et Gatew ay Service (MIGS)
Master Card Inter national MasterCard In tern et Gatew ay Service (MIGS) MIGS Payment Client Reference Manual Prepared By: Patrick Hayes Department: Principal Consultant, ebusiness Solutions Date Written:
More informationMyGate Response Codes. Version 2.1
MyGate Codes Version 2.1 Overview In every message request type sent to the Transaction Pipeline a response message type will be generated by MyGate. A response message will identify the success or failure
More informatione Merchant Plug-in (MPI) Integration & User Guide
e Merchant Plug-in (MPI) Integration & User Guide Enabling merchants to integrate their payment processing with SECPay s 3-D Secure Merchant Plug In (MPI) solution. This document provides the details of
More informationANZ egate Virtual Payment Client
ANZ egate Virtual Payment Client Integration Notes Contents Purpose of notes 3 For enquiries and support 3 Contents of ANZ egate kit 3 Sample Codes 3 Bank Hosted, Merchant Hosted and Merchant Hosted with
More informationA BETTER WAY TO PAY Unified Merchants API (UMAPI).Net Integration Manual
A BETTER WAY TO PAY Unified Merchants API (UMAPI).Net Integration Manual Version 2.3 Contents 1 INTRODUCTION... 5 1.1 Purpose and Objective... 5 1.2 Audience... 5 1.3 Assumptions / Exclusions... 5 1.4
More informationTHE PROXY SERVER 1 1 PURPOSE 3 2 USAGE EXAMPLES 4 3 STARTING THE PROXY SERVER 5 4 READING THE LOG 6
The Proxy Server THE PROXY SERVER 1 1 PURPOSE 3 2 USAGE EXAMPLES 4 3 STARTING THE PROXY SERVER 5 4 READING THE LOG 6 2 1 Purpose The proxy server acts as an intermediate server that relays requests between
More informationEntrust Certificate Services. Java Code Signing. User Guide. Date of Issue: December 2014. Document issue: 2.0
Entrust Certificate Services Java Code Signing User Guide Date of Issue: December 2014 Document issue: 2.0 Copyright 2009-2014 Entrust. All rights reserved. Entrust is a trademark or a registered trademark
More informationElavon Payment Gateway- Reporting User Guide
Elavon Payment Gateway- Reporting User Guide Version: v1.1 Contents 1 About This Guide... 4 1.1 Purpose... 4 1.2 Audience... 4 1.3 Prerequisites... 4 1.4 Related Documents... 4 1.5 Terminology... 4 1.6
More informationMIGS Payment Client Installation Guide. EGate User Manual
MIGS Payment Client Installation Guide EGate User Manual April 2004 Copyright The information contained in this manual is proprietary and confidential to MasterCard International Incorporated (MasterCard)
More informationMiGS Virtual Payment Client Integration Guide. July 2011 Software version: MR 27
MiGS Virtual Payment Client Integration Guide July 2011 Software version: MR 27 Copyright MasterCard and its vendors own the intellectual property in this Manual exclusively. You acknowledge that you must
More informationBank and SecurePay Response Codes
Bank and SecurePay s Last updated: 19/07/2013 Bank s for Credit Card Transactions APPROVED 00 Approved 08 Honour with ID 11 Approved VIP (not used) 16 Approved, Update Track 3 (not used) 77 Approved (ANZ
More informationProcess Transaction API
Process Transaction API Document Version 5.9 March 2011 For further information please contact Beanstream customer support at (250) 472-2326 or support@beanstream.com. BEAN # Page 2 of 90 Date Overview...
More informationMultifactor Authentication
10 CHAPTER The user can integrate additional access control devices like biometric devices to the Cisco PAM to ensure security. These devices are configured as Generic Readers in the Cisco PAM server.
More informationSafeNet KMIP and Google Cloud Storage Integration Guide
SafeNet KMIP and Google Cloud Storage Integration Guide Documentation Version: 20130719 Table of Contents CHAPTER 1 GOOGLE CLOUD STORAGE................................. 2 Introduction...............................................................
More informationDirect Post. Integration Guide
Direct Post Integration Guide Updated September 2013 Table of Contents 1 Introduction... 4 1.1 What is Direct Post?... 4 1.2 About this Guide... 4 1.3 Features and Benefits... 4 1.4 Card Types Accepted...
More informationSwedbank Payment Portal Implementation Overview
Swedbank Payment Portal Implementation Overview Product: Hosted Pages Region: Baltics September 2015 Version 1.0 Contents 1. Introduction 1 1.1. Audience 1 1.2. Hosted Page Service Features 1 1.3. Key
More informationRecurring Credit Card Billing
Recurring Credit Card Billing Recurring Credit Card Billing (RCCB) allows recurring debits to a credit card in a PCI compliant method. System Overview This document is intended for merchants and developers
More informationNetswipe Processing Implementation
Netswipe Processing Implementation Direct Integration with Jumio s Payment Gateway Revision History Version Date published Description 1.0.0 November 22 nd, 2011 Initial release. 1.0.1 January 12 th, 2012
More informationNetwork Merchants Inc (NMI) Integration Resources. Direct Post API Documentation April 2010
Network Merchants Inc (NMI) Integration Resources Direct Post API Documentation April 2010 Table of Contents Methodology... 2 Direct Post Method (Server to Server) FIG. 1... 2 Transaction Types... 3 Sale
More informationMiGS Merchant Administration Guide. July 2013 Software version: MR 29
MiGS Merchant Administration Guide July 2013 Software version: MR 29 Copyright MasterCard and its vendors own the intellectual property in this Manual exclusively. You acknowledge that you must not perform
More informationExchange Reporter Plus SSL Configuration Guide
Exchange Reporter Plus SSL Configuration Guide Table of contents Necessity of a SSL guide 3 Exchange Reporter Plus Overview 3 Why is SSL certification needed? 3 Steps for enabling SSL 4 Certificate Request
More informationCreating an authorized SSL certificate
Creating an authorized SSL certificate for On-premises Enterprise MeetingSphere Server The On-premises Enterprise MeetingSphere Server requires an authorized SSL certificate. This document provides a step-by-step
More informationPROCESS TRANSACTION API
PROCESS TRANSACTION API Document Version 8.7 May 2015 For further information please contact Digital River customer support at (888) 472-0811 or support@beanstream.com. 1 TABLE OF CONTENTS 2 Lists of tables
More informationSecure XML API Integration Guide. (with FraudGuard add in)
Secure XML API Integration Guide (with FraudGuard add in) Document Control This is a control document DESCRIPTION Secure XML API Integration Guide (with FraudGuard add in) CREATION DATE 02/04/2007 CREATED
More informationVerify Needed Root Certificates Exist in Java Trust Store for Datawire JavaAPI
Verify Needed Root Certificates Exist in Java Trust Store for Datawire JavaAPI Purpose This document illustrates the steps to check and import (if necessary) the needed root CA certificates in JDK s trust
More informationCHAPTER 7 SSL CONFIGURATION AND TESTING
CHAPTER 7 SSL CONFIGURATION AND TESTING 7.1 Configuration and Testing of SSL Nowadays, it s very big challenge to handle the enterprise applications as they are much complex and it is a very sensitive
More informationINTRODUCTION MERCHANT INTEGRATION. Ha noi, 10/7/2012
INTRODUCTION MERCHANT INTEGRATION Ha noi, 10/7/2012 0 Index Index... 1 1. Purpose... 2 2. Content... 2 2.1 Integrate payment gateway... 2 2.2 Edit the specifications of international payment gateway...
More informationipayment Gateway API (IPG API)
ipayment Gateway API (IPG API) Accepting e-commerce payments for merchants Version 3.2 Intercard Finance AD 2007 2015 Table of Contents Version control... 4 Introduction... 5 Security and availability...
More informationMerchant Plug-In. Specification. Version 3.2. 110.0093 SIX Payment Services
Merchant Plug-In Specification Version 3.2 110.0093 SIX Payment Services Table of contents 1 Introduction... 3 1.1 Summary... 3 1.2 Requirements... 4 1.3 Participation and Result of the Authentication...
More informationDevelopers Integration Lab (DIL) Certificate Installation Instructions. Version 1.4
Developers Integration Lab (DIL) Certificate Installation Instructions Version 1.4 July 22, 2013 REVISION HISTORY REVISION DATE DESCRIPTION 0.1 17 September 2011 First Draft Release DIL Certificate Installation
More informationUnified Merchants API (UMAPI) Java Integration Guide
A BETTER WAY TO PAY Unified Merchants API (UMAPI) Java Integration Guide Version 2.6 Page enets UMAPI Java Merchant Integration Manual Contents 1 Introduction... 3 1.1 Purpose and Objective... 3 1.2 Audience...
More informationCredomatic Integration Resources. Browser Redirect API Documentation June 2007
Credomatic Integration Resources Browser Redirect API Documentation June 2007 Table of Contents Methodology... 2 Browser Redirect Method (Browser to Server) FIG. 1... 2 API Authentication Parameters...
More informationA: This will depend on a number of factors. Things to consider and discuss with a member of our ANZ Merchant Services team are:
1 ANZ egate FAQ s Contents Section 1 General information: page 1 Section 2 Technical information for ANZ egate Merchants: page 5 November 2010 Section 1 General information Q: What is ANZ egate? A: ANZ
More informationSkipjack VPOS User Guide
Skipjack VPOS User Guide Skipjack 2230 Park Avenue Cincinnati, OH 45206 www.skipjack.com User Guide Table of Contents Click on a topic below to view its contents. Logging in to Your Account p. 3 Launch
More informationHow to Order and Install Odette Certificates. Odette CA Help File and User Manual
How to Order and Install Odette Certificates Odette CA Help File and User Manual 1 Release date 24.02.2014 Contents Preparation for Ordering an Odette Certificate... 3 Step 1: Prepare the information you
More informationMerchant Administration
Merchant Administration User Guide Version 4.2.0 For TNSPay 4.2 Disclaimer Copyright 2010 TNS Payment Technologies Pty Ltd ("TNS"). All rights reserved. This document is provided by TNS on the basis that
More informationChapter 1: How to Configure Certificate-Based Authentication
Chapter 1: How to Configure Certificate-Based Authentication Introduction Product: CA ControlMinder Release: All OS: All This scenario describes how a system or a CA ControlMinder administrator configures
More informationRealex Payments. Magento Community / Enterprise Plugin. Configuration Guide. Version: 1.1
Realex Payments Magento Community / Enterprise Plugin Configuration Guide Version: 1.1 Document Information Document Name: Magento Community / Enterprise Plugin Configuration Guide Document Version: 1.1
More informationSSL Configuration on Weblogic Oracle FLEXCUBE Universal Banking Release 12.0.87.01.0 [August] [2014]
SSL Configuration on Weblogic Oracle FLEXCUBE Universal Banking Release 12.0.87.01.0 [August] [2014] Table of Contents 1. CONFIGURING SSL ON ORACLE WEBLOGIC... 1-1 1.1 INTRODUCTION... 1-1 1.2 SETTING UP
More informationSecure XML API Integration Guide - Periodic and Triggered add in
Secure XML API Integration Guide - Periodic and Triggered add in Document Control This is a control document DESCRIPTION Secure XML API Integration Guide - Periodic and Triggered add in CREATION DATE 15/05/2009
More informationMerchant One Payment Systems Integration Resources. Direct Post API Documentation June 2007
Merchant One Payment Systems Integration Resources Direct Post API Documentation June 2007 Table of Contents Methodology... 2 Direct Post Method (Server to Server) FIG. 1... 2 Transaction Types... 3 Sale
More informationPayvision Payment Processor. Technical Integration
Payvision Payment Processor Technical Integration Rights of use: COMPLYING WITH ALL APPLICABLE COPYRIGHT LAWS IS THE RESPONSABILITY OF THE USER. WITHOUT LIMITING THE RIGHTS UNDER COPYRIGHT, NO PART OF
More informationFirst Data Merchant Solutions EMEA Payment Gateway
` First Data Merchant Solutions EMEA Payment Gateway Virtual Terminal & Online Portal User Guide Version 2.1 firstdatams.co.uk First Data Merchant Solutions is a trading name of First Data Europe Limited,
More informationVirtual Terminal & Online Portal
Authipay Gateway Virtual Terminal & Online Portal User Guide Version 5 (EMEA) Virtual Terminal & Online Portal User Guide Version 5 (EMEA) CONTENTS 1 Introduction... 5 2 Processing Transactions... 6 2.1
More informationPowerChute TM Network Shutdown Security Features & Deployment
PowerChute TM Network Shutdown Security Features & Deployment By David Grehan, Sarah Jane Hannon ABSTRACT PowerChute TM Network Shutdown (PowerChute) software works in conjunction with the UPS Network
More informationHosted Credit Card Forms Implementation Guide
Hosted Credit Card Forms Implementation Guide Merchant implementation instructions to integrate to the Setcom s hosted credit card forms. Covers: fraud screening, Verified by Visa, MasterCard SecureCode
More informationSYNDICATEBANK GLOBAL DEBIT CARDS. Steps for VbV (Verified by VISA) password creation for securing Internet transactions:
SYNDICATEBANK GLOBAL DEBIT CARDS Steps for VbV (Verified by VISA) password creation for securing Internet transactions: Syndicatebank Global Debit card is enabled for Internet Transactions from 04.11.2009
More informationConfiguring an Oracle Business Intelligence Enterprise Edition Resource in Metadata Manager
Configuring an Oracle Business Intelligence Enterprise Edition Resource in Metadata Manager 2011 Informatica Abstract This article shows how to create and configure an Oracle Business Intelligence Enterprise
More informationHow to Order and Install Odette Certificates. Odette CA Help File and User Manual
How to Order and Install Odette Certificates Odette CA Help File and User Manual 1 Release date 28.07.2014 Contents Preparation for Ordering an Odette Certificate... 3 Step 1: Prepare the information you
More informationTROUBLESHOOTING RSA ACCESS MANAGER SINGLE SIGN-ON FOR WEB-BASED APPLICATIONS
White Paper TROUBLESHOOTING RSA ACCESS MANAGER SINGLE SIGN-ON FOR WEB-BASED APPLICATIONS Abstract This white paper explains how to diagnose and troubleshoot issues in the RSA Access Manager single sign-on
More informationInstalling Digital Certificates for Server Authentication SSL on. BEA WebLogic 8.1
Installing Digital Certificates for Server Authentication SSL on BEA WebLogic 8.1 Installing Digital Certificates for Server Authentication SSL You use utilities provided with the BEA WebLogic server software
More informationEMC Clinical Archiving
EMC Clinical Archiving Version 1.7 Installation Guide EMC Corporation Corporate Headquarters Hopkinton, MA 01748-9103 1-508-435-1000 www.emc.com Legal Notice Copyright 2014-2015 EMC Corporation. All Rights
More informationPayment Client 3.2.0.0
Payment Client 3.2.0.0 Deployment Guide Version 1.0 Disclaimer Copyright 2009 TNS Payment Technologies Pty Ltd ("TNS"). All rights reserved. This document is provided by TNS on the basis that you will
More informationAdeptia Suite 6.2. Application Services Guide. Release Date October 16, 2014
Adeptia Suite 6.2 Application Services Guide Release Date October 16, 2014 343 West Erie, Suite 440 Chicago, IL 60654, USA Phone: (312) 229-1727 x111 Fax: (312) 229-1736 Document Information DOCUMENT INFORMATION
More informationFirst Data Merchant Solutions Virtual Terminal & Manager
First Data Merchant Solutions Virtual Terminal & Manager User Guide Version 2.2 firstdatams.co.uk First Data Merchant Solutions is a trading name of First Data Europe Limited, a private limited company
More informationHow to Order and Install Odette Certificates. Odette CA Help File and User Manual
How to Order and Install Odette Certificates Odette CA Help File and User Manual 1 Release date 20.07.2015 Contents Preparation for Ordering an Odette Certificate... 3 Step 1: Prepare the information you
More informationINTEGRATION PROCEDURES AND SPECIFICATIONS
ipos Credit Card Payment Gateway INTEGRATION PROCEDURES AND SPECIFICATIONS Revision 7 Contents Contents 2 Introduction 3 ipos the simple online credit card solution 3 The Transaction Flow 4 Security 7
More informationWorking With Virtual Hosts on Pramati Server
Working With Virtual Hosts on Pramati Server 13 Overview Virtual hosting allows a single machine to be addressed by different names. There are two ways for configuring Virtual Hosts. They are: Domain Name
More informationVirtual Terminal User Guide
Payment solutions for online commerce Virtual Terminal User Guide Copyright PayPoint.net 2010 This document contains the proprietary information of PayPoint.net and may not be reproduced in any form or
More informationConfiguring Secure Socket Layer and Client-Certificate Authentication on SAS 9.3 Enterprise BI Server Systems That Use Oracle WebLogic 10.
Configuring Secure Socket Layer and Client-Certificate Authentication on SAS 9.3 Enterprise BI Server Systems That Use Oracle WebLogic 10.3 Table of Contents Overview... 1 Configuring One-Way Secure Socket
More informationOracle ebs Adapter Installation and Configuration Guide
IBM Security Identity Manager Version 6.0 Oracle ebs Adapter Installation and Configuration Guide SC27-4403-03 IBM Security Identity Manager Version 6.0 Oracle ebs Adapter Installation and Configuration
More informationIntegrating EJBCA and OpenSSO
Integrating EJBCA and OpenSSO EJBCA is an Enterprise PKI Certificate Authority issuing certificates to users, servers and devices. In an organization certificate can be used for strong authentication.
More informationVolume PLANETAUTHORIZE PAYMENT GATEWAY. vtiger CRM Payment Module. User Guide
Volume 2 PLANETAUTHORIZE PAYMENT GATEWAY vtiger CRM Payment Module User Guide S A L E M A N A G E R M E R C H A N T S E R V I C E S User Guide and Installation Procedures Information in this document,
More informationMerchant Application Form for Credit and Debit Card Payment Gateway
Merchant Application Form for Credit and Debit Card Payment Gateway MERCHANT PRE-QUAPPLICATION FORM Merchant application form With this intake form you can apply for our online payment solutions. The information
More informationMiGS Merchant Administration User Manual. MiGS User Manual
MiGS Merchant Administration User Manual MiGS User Manual June 2006 MasterCard International Copyright The information contained in this manual is proprietary and confidential to MasterCard International
More informationANZ Secure Gateway Virtual Terminal QUICK REFERENCE GUIDE NOVEMBER 2015
ANZ Secure Gateway Virtual Terminal QUICK REFERENCE GUIDE NOVEMBER 2015 2 Contents Welcome 3 1. Getting Started 4 1.1 Virtual Terminal Activation 4 2. Configuring the Virtual Terminal 7 2.1 General Settings
More informationWEB TERMINAL AND RECURRING BILLING
PROCESSING TRANSACTIONS WITH WEB TERMINAL AND RECURRING BILLING Document Version 1.4 December 2013 For further information please contact Digital River customer support at 0800 756 3350 or clientsupport.uk@digitalriver.com.
More informationGateway Direct Post API
Gateway Direct Post API http://merchantguy.com @MerchantGuy Questions? info@merchantguy.com Contents Methodology....3! Direct Post Method (Server to Server FIG. 1...3 Transaction Types.....4! Sale (sale)..4!
More informationSecure Messaging Server Console... 2
Secure Messaging Server Console... 2 Upgrading your PEN Server Console:... 2 Server Console Installation Guide... 2 Prerequisites:... 2 General preparation:... 2 Installing the Server Console... 2 Activating
More information*ROAMpay powered by ROAM
*ROAMpay powered by ROAM Table of Contents 1. Introduction 2. Setting up Service 3. Supporting ROAMpay Customers 4. Helpful Links and Contacts 5. ROAMpay User s Guide Welcome to ROAMpay powered by ROAM!
More informationFraud Detection Module (basic)
Table of contents 1. Introduction 1.1 Benefits 1.2 Contents 2. Activation and configuration 2.1 Blocking rules 2.1.1 Card country 2.1.2 IP address country 2.1.3 Country consistency 2.1.4 3-D Secure 2.2
More informationInternet Payment Gateway
Internet Payment Gateway Merchant Administration Console Merchant Services TABLE OF CONTENTS Introduction to the Merchant Administration Console... 5 Console Overview... 5 Login Conditions... 5 Merchant
More informationMerchant Application Form
emerchantpay Limited Merchant Application Form Hand written applications will not be accepted. CORPORATION DETAILS European Company Details n-european Company Details If applicable Company Registration
More informationMerchant Console User Manual
Merchant Console User Manual INDEX 1 SECTION 1 Logging into USAePay Merchant Console Page 1 SECTION 2 Sale (vterminal) Page 3 SECTION 3 Credit (vterminal) Page 4 SECTION 4 Void (vterminal) Page 5 SECTION
More informationitransact Gateway Fast Start Guide
itransact Gateway Fast Start Guide itransact Gateway Fast Start Guide Table of Contents 1. Version and Legal Information... 1 2.... 2 Quick Setup... 2 The Card Setup... 2 Order Form Setup... 3 Simple
More informationConference Manual Section 3.4.1
Conference Manual Section 3.4.1 ACM CREDIT CARD CLEARANCE SERVICE AGREEMENT ACM REGISTRATION SERVICES CREDIT CARD PROCESSING ACM will be happy to provide service for all ACM conferences. MasterCard, Visa
More informationDIRECT INTEGRATION GUIDE DIRECT INTEGRATION GUIDE. Version: 9.16
DIRECT Version: 9.16-1 - 1 Direct HTTP Integration... 4 1.1 About This Guide... 4 1.2 Integration Disclaimer... 4 1.3 Terminology... 5 1.4 Pre-Requisites... 6 1.5 Integration Details... 7 1.6 Authentication...
More information1 Reflection ZFE 5. 2 Security Considerations 13. 3 Troubleshooting the Installation 19. Contents 1
1 Reflection ZFE 5 Introducing Reflection ZFE......................................................... 5 Reflection ZFE components.................................................. 5 System requirements..............................................................
More informationSecure Card Data. Specification. Version 3.1.5. 110.0097 SIX Payment Services
Secure Card Data Specification Version 3.1.5 110.0097 SIX Payment Services Table of Contents 1 Introduction... 3 1.1 Data Security and PCI DSS... 3 1.2 Summary... 3 1.3 Requirements... 3 1.4 Supported
More informationHTTPS Configuration for SAP Connector
HTTPS Configuration for SAP Connector 1993-2015 Informatica LLC. No part of this document may be reproduced or transmitted in any form, by any means (electronic, photocopying, recording or otherwise) without
More informationConfiguring SSL in OBIEE 11g
By Krishna Marur Configuring SSL in OBIEE 11g This white paper covers configuring SSL for OBIEE 11g in a scenario where the SSL certificate is not in a format that Web Logic Server (WLS) readily accepts
More informationreference: HTTP: The Definitive Guide by David Gourley and Brian Totty (O Reilly, 2002)
1 cse879-03 2010-03-29 17:23 Kyung-Goo Doh Chapter 3. Web Application Technologies reference: HTTP: The Definitive Guide by David Gourley and Brian Totty (O Reilly, 2002) 1. The HTTP Protocol. HTTP = HyperText
More informationSEZ SEZ Online Manual- DSC Signing with Java Applet. V Version 1.0 ersion 1.0
SEZ SEZ Online Manual- V Version 1.0 ersion 1.0 Table of Contents 1 Introduction...2 2 DSC signing functionality with java applet...2 3 Troubleshooting...5 4 Annexure I: JAVA Console Setting... 13 5 Annexure
More informationVersion 9. Generating SSL Certificates for Progeny Web
Version 9 Generating SSL Certificates for Progeny Web Generating SSL Certificates for Progeny Web Copyright Limit of Liability Trademarks Customer Support 2015. Progeny Genetics, LLC, All rights reserved.
More informationOverview of Web Services API
1 CHAPTER The Cisco IP Interoperability and Collaboration System (IPICS) 4.5(x) application programming interface (API) provides a web services-based API that enables the management and control of various
More informationMONETA.Assistant API Reference
MONETA.Assistant API Reference Contents 2 Contents Abstract...3 Chapter 1: MONETA.Assistant Overview...4 Payment Processing Flow...4 Chapter 2: Quick Start... 6 Sandbox Overview... 6 Registering Demo Accounts...
More informationConfiguring HTTPS support. Overview. Certificates
Configuring HTTPS support Overview Destiny provides the option to configure secure access when password information is transmitted between the client browser and the server. Destiny can switch from HTTP
More informationFraud Detection. Configuration Guide for the Fraud Detection Module v.4.2.0. epdq 2014, All rights reserved.
Configuration Guide for the Fraud Detection Module v.4.2.0 Table of Contents 1 What is the... Fraud Detection Module? 4 1.1 Benefits 1.2 Access 1.3 Contents... 4... 4... 4 2 Fraud detection... activation
More informationDirector and Certificate Authority Issuance
VMware vcloud Director and Certificate Authority Issuance Leveraging QuoVadis Certificate Authority with VMware vcloud Director TECHNICAL WHITE PAPER OCTOBER 2012 Table of Contents Introduction.... 3 Process
More informationBarclaycard SmartPay. Hosted Payment Page Integration Guide. Version 3.0 released April 2012
Barclaycard SmartPay Hosted Payment Page Integration Guide Version 3.0 released April 2012 DOC Version Control Version No. Date Issued Reason for Change 1.0 July 2010 Initial Document 2.0 February 2012
More informationMySagePay. User Manual. Page 1 of 48
MySagePay User Manual Page 1 of 48 Contents About this guide... 4 Getting started... 5 Online help... 5 Accessing MySagePay... 5 Supported browsers... 5 The Administrator account... 5 Creating user accounts...
More informationSafeNet KMIP and Amazon S3 Integration Guide
SafeNet KMIP and Amazon S3 Integration Guide Documentation Version: 20130524 2013 SafeNet, Inc. All rights reserved Preface All intellectual property is protected by copyright. All trademarks and product
More informationEMC Documentum Content Services for SAP Repository Manager
EMC Documentum Content Services for SAP Repository Manager Version 6.0 Installation Guide P/N 300 005 500 Rev A01 EMC Corporation Corporate Headquarters: Hopkinton, MA 01748 9103 1 508 435 1000 www.emc.com
More informationFirst Data E-commerce Payments Gateway
First Data E-commerce Payments Gateway High performance payment processing solution designed specifically to meet the requirements of global Card-Not-Present PSP When you partner with First Data for your
More informationEnabling SSL and Client Certificates on the SAP J2EE Engine
Enabling SSL and Client Certificates on the SAP J2EE Engine Angel Dichev RIG, SAP Labs SAP AG 1 Learning Objectives As a result of this session, you will be able to: Understand the different SAP J2EE Engine
More information