Your SlideShare is downloading. ×
Ebay Payment Interface.doc
Ebay Payment Interface.doc
Ebay Payment Interface.doc
Ebay Payment Interface.doc
Ebay Payment Interface.doc
Ebay Payment Interface.doc
Ebay Payment Interface.doc
Ebay Payment Interface.doc
Ebay Payment Interface.doc
Ebay Payment Interface.doc
Ebay Payment Interface.doc
Ebay Payment Interface.doc
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Ebay Payment Interface.doc

1,278

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
1,278
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
21
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. EasyShop Ebay Interface Documentation
  • 2. Ebay Interface Implementation Guide Page 2 of 12 Table of Contents INTRODUCTION.........................................................................................................................................................3 EBAY PAYMENT INTERFACE................................................................................................................................4 WHAT IS THE EBAY PAYMENT INTERFACE ?.......................................................................................................................4 HOW DOES THE EBAY PAYMENT INTERFACE WORK?...........................................................................................................4 STANDARD PAYMENT INTERFACE......................................................................................................................................4 COLLECTING PAYMENT DATA...........................................................................................................................................5 RENDERING A RESPONSE TO THE CUSTOMER.......................................................................................................................5 EBAY PAYMENT INTERFACE IMPLEMENTATION.........................................................................................6 MERCHANT REQUESTS THE GATEWAY’S PAYMENT FORM.....................................................................................................6 CONFIGURING THE GATEWAY RESPONSE (RECEIPT PAGE OR RELAY RESPONSE)......................................................................6 PAYMENT FORM SETTINGS...............................................................................................................................................6 EBAY PAYMENT FORM SUBMISSION.................................................................................................................7 OTHER FEATURES AND OPTIONS.......................................................................................................................9 ADDING A BANNER..........................................................................................................................................................9 CREATING AN AUCTION/ ITEM NUMBER FIELD.......................................................................................................................9 OTHER OPTIONS.............................................................................................................................................................9 OPTION 1....................................................................................................................................................................10 OPTION 2....................................................................................................................................................................10 GLOSSARY.................................................................................................................................................................11 This version of SecurePay Customer Payment Interface Last revised: 10/02/2006 Proprietary and Confidential
  • 3. Ebay Interface Implementation Guide Page 3 of 12 Introduction This document describes minimum requirements to allow SecurePay to process both authentication and authorization transactions in real time via the Ebay Payment Interface. SecurePay provides a payment gateway that facilitates electronic commerce by enabling merchants to accept credit cards and electronic checks as methods of payment for goods and services sold online. The gateway acts as a bridge between the merchant’s website and the financial institutions that process payment transactions. Payment data is collected online from the shopper and submitted to the gateway for real-time authorization. However, the payment gateway is targeted towards merchants that process Card-Not-Present transactions. In a Card-Not- Present transaction, the merchant and the shopper are not in the same physical location and the customer usually calls in the payment data or keys in the details of the credit card on a website. All e-commerce and mail/telephone orders are Card- Not-Present transactions. The SecurePay Ebay Payment Interface (CPI) is a Hypertext Markup Language (HTML) based integration. It uses standard form information to submit a number of variables to SecurePay securely hosted payment page for the purpose of transaction processing. Once processed, transaction status information is returned to a predefined script to allow fulfillment of orders automatically. SecurePay EasyShop provides a secure Ebay Payment Interface checkout to: • Present a payment page to your customers requesting card and billing/delivery details • Submit card information to facilitate cardholder authentication • Submit transactions for real-time authorization • Present order confirmations and return status results • Return customers to your store This version of SecurePay Customer Payment Interface Last revised: 10/02/2006 Proprietary and Confidential
  • 4. Ebay Interface Implementation Guide Page 4 of 12 Ebay Payment Interface What is the Ebay Payment Interface ? The Ebay Payment Interface is a method and system enabling rapid access to online commerce solutions where people type in their credit card details for secure real-time online payments to the payment gateway. This method allows a merchant’s server to securely connect directly to the payment gateway to submit transaction data. The merchant retains full control of the payment data collection and the user experience. If you are an ebay seller and would like to process buyer’s payments through your merchant account, our ebay checkout feature is the perfect solution. With ebay checkout, your customers will have the option of paying for auction items through EasyShop shopping cart. How does the Ebay Payment Interface Work? When using the Ebay Payment Interface, transactions flow in the following way: 1. The customer’s browser connects securely to the merchant’s server to transmit payment information. 2. The merchant’s server initiates a secure connection to SecurePay the payment gateway and then initiates an HTTPS post of the transaction data to SecurePays’gateway server 3. SecurePay payment gateway receives and processes the transaction data. SecurePay payment gateway then generates and submits the transaction response to the merchant’s server. 4. The merchant’s server receives and processes the response. 5. Finally, the merchant’s server communicates the success or failure of the authorization to the customer’s browser. Standard Payment Interface Easy to use and implement, the standard interface enable merchants to accept payments from their customers by simply adding Hypertext Markup Language (HTML) code to their website. This interface is generic in format and it is targeted for straight forward payment processing. This version of SecurePay Customer Payment Interface Last revised: 10/02/2006 Proprietary and Confidential
  • 5. Ebay Interface Implementation Guide Page 5 of 12 Ebay Payment Interface Collecting Payment Data The merchant can choose to host the web page where the customer enters payment data, or request that the gateway host the page. The page hosted by the gateway to collect payment data is referred to as the Customer Payment Form, and can be configured by the merchant to look like their website. Using the gateway-hosted Customer Payment Form, merchants can collect payment data securely without having a secure website. Rendering a Response to the Customer The response returned by the gateway to the customer’s browser is referred to as a Receipt Page. The merchant can configure the Receipt Page to look like their website. However, the merchant also has the option to receive the transaction response from the gateway, customize it, and send back a receipt page to the gateway. The gateway then relays the merchant-generated receipt page to the customer’s browser. This response option is referred to as Relay Response. Merchants who use Relay Response can exercise a greater degree of control over the messaging of a response to the customer. This version of SecurePay Customer Payment Interface Last revised: 10/02/2006 Proprietary and Confidential
  • 6. Ebay Interface Implementation Guide Page 6 of 12 Ebay Payment Interface Implementation In order to integrate to SecurePay Payment Gateway, the merchant can request the payment form via services@SecurePay.com. The interface is in a pre-defined form usually in the following format: https://www.securepay.com/ebay/index.asp Note: Keep in mind that because SecurePay requires the use of real time instructions for transaction authentication, you will first need to post the HTML form to a script location URL on your web server or secure network. Your instructions should then execute the posting of the transaction and authentication data to the gateway transact URL indicated above. Merchant Requests the Gateway’s Payment Form If the merchant does not have the ability to host secure web pages then the post string needs to contain only the information required to identify the merchant and request the gateway’s Payment Form. If the merchant has collected information from a customer on their site before requesting the gateway’s Payment Form, the merchant can include that information in the post string as hidden fields. This result in the gateway rendering a Payment Form populated with the information passed in by the merchant. Configuring the Gateway Response (Receipt Page or Relay Response) The post string can contain information that indicates to the gateway how the Receipt Page rendered by SecurePay should be formatted. Merchants requesting Relay Response can also provide a URL in the post string to which the gateway will post a response. The merchant’s site can receive, parse, and customize the response and post it back to the gateway. The gateway will then relay the response to the customer. Payment Form Settings The merchant can also indicate in the instructions the set of fields on the Payment Form that should be displayed to the customer, as well as the set of fields the customer will be required to fill out. Note: Specifying payment form fields as “Required” in the Merchant Interface payment form settings will require the selected fields for all transactions submitted to the gateway. The merchant can also define the method by which the customer should be returned to the merchant website and the destination URL to which the customer will be returned. This version of SecurePay Customer Payment Interface Last revised: 10/02/2006 Proprietary and Confidential
  • 7. Ebay Interface Implementation Guide Page 7 of 12 Ebay Payment Form Submission This section describes how to access the SecurePay gateway via HTML form to post transactions to the SecurePay gateway. The basic HTML tags used to construct the form to post a transaction to the SecurePay gateway can be found in the following format: <TABLE> <FORM ACTION="https://www.securepay.com/payment/index.asp"> METHOD=POST In your script, make a form post to SecurePay.Com and pass the required properties. The SecurePay.Com script will process the order, and then return the response values back to the page. The following HTML code demonstrates the ability to send additional information to the system, including information that is specified by the customer. The result of this HTML code snippet is a page that displays a form allowing the customer to submit their payment information. <TABLE> <FORM ACTION="https://www.securepay.com/ebay/index.asp" METHOD="Post"> <TR> <TD> <center> For the script to function properly the following variables must be passed to the gateway. Securepay.Com CGI interface will expect data as FORM Variables. This would be a “POST” method in a HTML form format. The SecurePay.Com CGI script is expecting the following "Key=Value" pairs. This is done behind the scenes by the SecurePay component. Success_URL = "The URL that the transaction will be redirected to upon completion of a successful transaction.” Failure_URL = "The URL that the transaction will be redirected to upon completion of a declined transaction.” MERCH_ID = "A unique Merchant identifier assigned to the Merchant by SecurePay.Com." After passing these variables to the interface on the SecurePay.Com server a transaction with the merchant's credit card processor will be made. The response of that transaction determines to which redirect URL (Success_URL or Failure_URL) the client is passed. All variables regarding the transaction are sent to the merchant in the notification email. The return output can be modified upon request. This version of SecurePay Customer Payment Interface Last revised: 10/02/2006 Proprietary and Confidential
  • 8. Ebay Interface Implementation Guide Page 8 of 12 Ebay Payment Form Submission Any form fields that need to be sent to the system would be enclosed as <INPUT> fields within the opening <FORM> tag and the closing </FORM> tag. For example, a form that contained a merchant’s_ID field and/or returnURL field would look like this: <INPUT TYPE=HIDDEN NAME="merch_id" VALUE="your Merchant ID goes here"> <INPUT TYPE=HIDDEN NAME="returnURL" VALUE="your internet address http://www.com goes here"> Note: Merchants that use the form must complete the values of the hidden variables in the example above. • The Merch_ID=” variable to reflect your SecurePay.Com merchant Merchant ID value ID contains 5 numbers, • The “ReturnURL” variable to reflect merchant web site this number designates to whom the payment is going to. This version of SecurePay Customer Payment Interface Last revised: 10/02/2006 Proprietary and Confidential
  • 9. Ebay Interface Implementation Guide Page 9 of 12 Other Features and Options Several additional enhancements can be employed to modify the customer payment form. The customer payment form can be branded to personalize merchant information, initially set up under the merchant ID on SecurePay. The following are options that the merchants can add to their e-commerce payment interface. Adding a banner • Merchants can take advantage of the use of personal banners for their customer payment form. The merchant will need to submit to SecurePay.com via e-mail to support@securepay.com a 400 x 80 pixel image in .jpg format. Note: If the merchant uses SecurePay EasyShop to create their own e-commerce store, the banner created will be used on their interface. Creating an auction/ item number field • On the ebay payment interface, merchants can pass the global reference ID for an eBay catalog product. Ebay catalog products provide stock information that sellers can use to pre- fill item specifics and other listing details. The code is as follows: </STYLE> </HEAD> <BODY> <FORM action="GetItem.asp" method="post"> <P><B>Item ID: </B> <INPUT type="text" name="itemID"> Other Options • If merchants do not have an e-commerce web site, a customized linked page can be created and stored on the SecurePay.com web servers. The link will provide access to the Customer payment Form. • SecurePay Easyshop provides a great amount of flexibility when creating the interface for the Ebay Payment Form. This interface enables the merchants to provide for the customer… o “Pay By Credit Card” link This version of SecurePay Customer Payment Interface Last revised: 10/02/2006 Proprietary and Confidential
  • 10. Ebay Interface Implementation Guide Page 10 of 12 Other Features and Options Below are examples of the code, the merchant can use to create the “Pay by Credit Card” link and/or that passes an amount of the customers choice. Option 1 Copy and paste the code on your e-commerce web site: <a href="https://www.securepay.com/ebay/index.asp?merch_id=xxxxx"> Pay By Credit Card</a> Note: Replace the value of Merch_id with your 5 digit SecurePay ID Option 2 Copy and paste the code on your e-commerce web site: <p><a href="https://www.securepay.com/ebay/index.asp? merch_id=xxxxx&amount=00.00">Pay By Credit Card</a></p> Note: Replace the value of Merch_id with your 5 digit SecurePay ID This version of SecurePay Customer Payment Interface Last revised: 10/02/2006 Proprietary and Confidential
  • 11. Ebay Interface Implementation Guide Page 11 of 12 Glossary Term Definition ASP Active Server Page- Microsoft’s Server side scripting language CGI Common Gateway Interface- A way of interfacing computer programs CPI Customer Payment Interface- Secure checkout payment page HTML Hypertext Mark Up Language- Language used to construct web pages HTTP HyperText Transfer Protocol- Th protocol used most often to transfer information from World Wide Web servers to browsers. Also called Hyper Text transport protocol HTTPS HyperText Transfer Protocol Secure- A version of http for secure transactions POST An HTTP command which sends data from a client to a server, or one server to another URL Uniform Resource Locator- An internet address STRING A type of data or text SCRIPT A set of instructions. The computer executes the instructions, then returns data, a value which could be a number, a string, a list, or another data type Success_URL The URL that the transaction will be redirected to upon completion of a successful transaction Failure_URL The URL that the transaction will be redirected to upon completion of a declined transaction Merch_id A unique merchant identifier assigned to the merchant by SecurePay.com Auction/Item The global reference ID for an eBay catalog product. Number eBay catalog products provide stock information that sellers can use to pre-fill Item Specifics and other listing details This version of SecurePay Customer Payment Interface Last revised: 10/02/2006 Proprietary and Confidential
  • 12. Ebay Interface Implementation Guide Page 12 of 12 All code is developed by SecurePay.Com is protected by Copyright. Copyright 2006, SecurePay.Com, Inc., All rights Reserved. Distribution rights are held by SecurePay.Com. This file is not to be published or distributed within written permission from SecurePay.Com. Questions and inquiries should be directed to: SecurePay Support SecurePay.Com 4400 North Point Parkway Alpharetta, GA 30022 678-325-2602 support@securepay.com --- End Documentation --- This version of SecurePay Customer Payment Interface Last revised: 10/02/2006 Proprietary and Confidential

×