EPX Certification Credentials

Transcription

1 Version 1.5 Electronic Payment Exchange 1201 N. Market Street, Suite 701 Wilmington, DE

2 Confidentiality Statement 2013 Electronic Payment Exchange. All rights reserved. This document contains confidential and proprietary information that belongs exclusively to Electronic Payment Exchange. Receipt of this document imposes the obligation on the recipient to protect the information from loss or disclosure to other parties. This publication may not be reproduced or distributed for any purpose without the written permission of EPX Electronic Payment Exchange. ii

3 Table of Contents EPX Certification Credentials 1 Server Post Certification 1 PayPage Certification 1 Batch Processing Certification 1 Address Verification and Interchange Qualification 2 Setting Max Connection Timeout 2 BRIC Lifetime 2 Accessing the Certification Environment 2 Four Part Key 3 Certification URLs 3 Using DNS 3 Testing Values 4 ACH 4 Credit Card 4 PIN-Less 4 Track Data 5 Credit Card 5 PIN-less Debit Electronic Payment Exchange. iii

4 To certify with EPX, you will be working with an Integration Specialist who will assist you with any issues or questions you may have during the integration process. To complete the certification, you are required to submit the requests and successful responses for each type of transaction in the certification environment to be performed in the production environment. The requests and responses should be submitted for certification in text or XML format via . Once this information is sent to the Integration department it is reviewed and an Integration Specialist will contact you to discuss issues or present your certification document. Note: Dummy data should be used when integrating and certifying to EPX. Server Post Certification To complete the Server Post certification, you are required to submit the requests and successful responses received for each transaction type (TRAN_TYPE) in the Certification environment to be performed in the production environment. The requests and responses should be submitted in text or XML format via for certification. PayPage Certification To complete the PayPage certification, you are required to submit a sample of the KeyExchange and PayPage posts that are being used to call the product, as well as the scripts and images used to customize the PayPage. Batch Processing Certification To complete the Batch Processing certification, you are required to submit a sample request and response file from the certification batch system that contains each transaction type (TRAN_TYPE) that will be used in production Electronic Payment Exchange. 1

5 Address Verification and Interchange Qualification The Address Verification System (AVS) is a system used to verify the identity of the person claiming to own the credit card. The system will check the billing address and/or the zip code of the credit card provided by the user with the address and/or zip code on file at the credit card company. As described below, in some cases sending AVS will allow the transaction to achieve a better interchange rate when processed. o o o Retail (Card Present) transactions where the credit/debit card is present and a card swipe is performed do not require AVS information to be submitted to receive the best interchange rate. The track data being supplied with the transaction request, when the customer swipes their credit card, is sufficient for qualifying for the best interchange rate. Retail (Card Not Present or Magnetic Strip Unreadable) transactions where the credit/debit card information is key entered require AVS information to be submitted and the AVS response received must be B, C, D G, I, M, P, R, S, U, W, X, Y, or Z in order to achieve the best interchange rate. If you receive another AVS response, the interchange qualification for that transaction will downgrade. Card Not Present Ecommerce or MOTO transactions require the AVS information to be sent in order to receive the best interchange qualification. The attempt to check AVS is sufficient and the AVS response received does not change the interchange qualification of the transaction. Setting Max Connection Timeout When communicating with EPX it is recommended that 35 seconds be set as the merchant timeout value once the connection is established to account for any out of the norm issuer behavior. The EPX internal processes are similarly configured to time out around 33 seconds. BRIC Lifetime The EPX BRIC (GUID/Token) can be used to create new transactions within the EPX system, but it is important to know how long the value will be available for this use. BRICs received with the response of a financial transaction, such as an authorization, will only be accessible for 13 months from creation. This limitation applies to all financial BRICs by default. Since each financial transaction created with a BRIC receives a new BRIC in the response, a common practice is for merchants to replace the previous BRIC with the new one, as this new token is valid for a new 13 months. For those merchants who need the BRIC availability to exceed this limitation, the BRIC Storage transaction is available and will create BRICs that will be accessible indefinitely. For more information about the usage of a BRIC, refer to the EPX BRIC Reference manual. Accessing the Certification Environment This document contains information on accessing the certification environment for processing transactions. The following sections contain information on the four part key which defines the merchant s profile, a list of certification URLs that are currently available, testing the ACH and credit card values, the amount response code triggers, and the process for certification Electronic Payment Exchange. 2

6 Warning: DO NOT use real customer data for testing. EPX DOES NOT accept liability for any data submitted to the test environment. The Certification environment merchant accounts are used by all in certification, so any data submitted can potentially be viewed by other merchants in certification. Be sure to use only fictitious account holder data when performing any certification transactions! Four Part Key In the production environment, the four part key defines the merchant profile. For certification purposes, one of the below certification accounts can be used. You may have received instruction on which account to use, if you have not, it is up to your discretion. All of the accounts are similar in profile setup. If you would like to process in the batch environment or access the websuite reporting tool in the certification environment, contact your Integration Specialist for login information. CUST_NBR MERCH_NBR DBA_NBR TERMINAL_NBR Certification URLs The table below contains a list of various URLs for certification. You may discuss with your integration specialist which URLs you may use during integration. URL secure.epxuap.com: sftp.epxuap.com Description websuite Reporting Tool (HTTPS Protocol) HTTPS Post Transaction (HTTPS Protocol) SSL Socket Transaction (XML) Secure KeyExchange for use with PayPage BuyerWall PayPage BuyerWall vpost File Transfer URL (SFTP Protocol) Using DNS When connecting to EPX, it is best to use the DNS rather than the IP address. Redundancy on the EPX side allows for an easy change of Internet Service Providers (ISPs) when there is an issue. EPX uses a short time to live (TTL) on the DNS values so that within seconds we can change the IP behind the DNS entry when it is necessary. In some cases, the merchant will have a firewall in their environment that is blocking outbound access to EPX. In this scenario, the merchant must contact EPX in order to get the range of IP s so that the EPX smart DNS can 2013 Electronic Payment Exchange. 3

7 work effectively and the merchant is not restricted to only one EPX IP address outbound. To attain the IP address ranges EPX utilizes, send your request to Testing Values Below are values that can be used in the test environment to simulate various accounts using credit card, credit card track data, and ACH information. These account numbers will generate approval responses. ACH The table below contains the test account and routing numbers used when testing the ACH processes. Account Number Routing Number Credit Card The table below contains the list of test numbers used with specific card types, and lengths of the test numbers used. Card Association Card Number Length MasterCard Visa Amex Diners Discover JCB Solo Switch PIN-Less Note: The Solo and Switch test card numbers get the same response as the MasterCard test card numbers. The table below contains the list of test numbers used with specific card types, and lengths of the test numbers used. Card Association Card Number Length MasterCard Visa Electronic Payment Exchange. 4

8 Track Data The table below contains the list of test card types, numbers, and Track 1 and 2 Data. Credit Card Note: The Code column indicates the Card Type value that will be returned in the Authorization Response. Card Type Code Card Number Track 1 and 2 Data Network MasterCard M B ^CARD/TEST ^ = Visa V B ^CARD/TEST^ = Amex S B ^ISO/AMEX TEST^ = Discover N B ^PROCESSORS/MARQUEE TEST^ PIN-less Debit = MasterCard Visa Amex Discover Card Type Code Card Number Track 1 and 2 Data Network Visa O N/A Visa O N/A Visa O N/A Visa O N/A MasterCard O N/A MasterCard O N/A MasterCard O N/A MasterCard O N/A = = = = = = = = Accel Star NYCE Pulse Star Accel NYCE Pulse 2013 Electronic Payment Exchange. 5