CPAY MERCHANT INTEGRATION SPECIFICATION

Similar documents
Process Transaction API

Swedbank Payment Portal Implementation Overview

PROCESS TRANSACTION API

1. Introduction to CardPay

Frequently Asked Questions

3D Secure safe on-line shopping with your payment card

MONETA.Assistant API Reference

Cofred Automated Payments Interface (API) Guide

Implementation guide - Interface with the payment gateway PayZen 2.5

INTEGRATION PROCEDURES AND SPECIFICATIONS

How to set up Outlook Anywhere on your home system

INUVIKA OPEN VIRTUAL DESKTOP ENTERPRISE

WEEPAY V2 INTEGRATION DOCUMENT (BASIC INTEGRATION)

Secure Payment Form User s Guide

PayPal Express Checkout Integration Guide

Ecommerce User s Manual. August 2013

User Guide: Virtual Merchant

Hosted Credit Card Forms Implementation Guide

Processing e-commerce payments A guide to security and PCI DSS requirements

Developer Guide To The. Virtual Merchant

LiteCommerce Authorize.Net Module. Version 2.4

Credomatic Integration Resources. Browser Redirect API Documentation June 2007

Shopping Cart Interface Version 1.03

Paynow 3rd Party Shopping Cart or Link Integration Guide

Getting Started with Mal s. Adding Buy Now buttons to your web page

Website Payments Pro Hosted Solution Integration Guide. United Kingdom

CONFIGURING AND USING WEBDAV IN LENOVO EMC LIFELINE

3. From the Merchant Administration drop down select VCS Interfacing (page1)

API Integration Payment21 Recurring Billing

Merchant Plug-In. Specification. Version SIX Payment Services

Integrating LivePerson with Salesforce

ipayment Gateway API (IPG API)

A: This will depend on a number of factors. Things to consider and discuss with a member of our ANZ Merchant Services team are:

Installing and Configuring Microsoft Dynamics Outlook Plugin to Use with ipipeline MS CRM

Direct Post. Integration Guide

Paya Card Services Payment Gateway Extension. Magento Extension User Guide

Increase revenue. Reduce operating costs. Improve efficiencies. Accomplish all this and more with eselectplus.

Setting Up a CyberSource Web Payment Account

N-CAP Users Guide Everything You Need to Know About Using the Internet! How Electronic Payment Works

itransact Gateway Fast Start Guide

Open Catalog Interface (OCI) for VirtueMart

Learn how to create web enabled (browser) forms in InfoPath 2013 and publish them in SharePoint InfoPath 2013 Web Enabled (Browser) forms

eway AU Hosted Payment Page

The PayPal payment gateway and 4D Business Kit 2.2

Online Store Widget 101. A Guide for New Users

INTRODUCTION MERCHANT INTEGRATION. Ha noi, 10/7/2012

Elavon Payment Gateway - Redirect Integration Guide

Sage Pay Direct Integration and Protocol Guidelines Published: 01/08/2014

Global Transport Secure ecommerce Decision Tree

Webmail Using the Hush Encryption Engine

OpenGlobal WorldPay Recurring Payments (FuturePay) for VirtueMart

Skipjack ezpay Secure Online Order Form User Guide

Secure Hosting and Payments Technical Integration Guide

Skrill Payment Gateway Integration Guide

Encrypting*a*Windows*7*Hard*Disk* with%bitlocker%disk%encryption!

Durango Merchant Services Customer Vault API

Cart66 Lite Overview! 3. Managing Products! 3. Digital Products! 4. Digital Products Folder! 4. Product Variations! 4. Custom Fields! 5. Promotions!

Title Page. Hosted Payment Page Guide ACI Commerce Gateway

How to Use Print from Register the printer

Exchange Outlook Profile/POP/IMAP/SMTP Setup Guide

Audi Virtual Payment Client Integration Manual

MySagePay. User Manual. Page 1 of 48

How To Set Up The Barclaycard Epdq Cardholder Payment Interface (Cpi) On Papercut (Barclay Card) On A Microsoft Card (For A Credit Card) With A Creditcard (For An Account)

GestPay Technical Specifications iframe Payment Page

PayDollar PayGate. Integration Guide (For third party shopping cart platform v1.0)

How to Create E-Commerce Web Site

Zapper for ecommerce. Magento Plugin Version Checkout

Website Payments Pro Hosted Solution Integration Guide. Hong Kong

PayPal Usage Document

Accepting Ecommerce Payments & Taking Online Transactions

PAYU HUNGARY KFT. PAYMENT INFORMATION. PayU Hungary Kft. T: Budapest, F:

INTEGRATE SALESFORCE.COM SINGLE SIGN-ON WITH THIRD-PARTY SINGLE SIGN-ON USING SENTRY A GUIDE TO SUCCESSFUL USE CASE

Merchant One Payment Systems Integration Resources. Direct Post API Documentation June 2007

Simple Integration Mobile Ready Cutting-edge Innovation

PROCUREMENT CARD US BANK ACCESS ONLINE SYSTEM USER GUIDE

Fraud Detection Module (basic)

Green Pharm is committed to your privacy. We disclose our information practices below and we agree to notify you of:

SPARROW Gateway. Developer Data Vault Payment Type API. Version 2.7 (6293)

Rapid 3.0 Transparent Redirect API. Official eway Documentation. Version 0.82

Virtual POS Services Information Guide

Contents. Contents... i. Chapter 1 Introduction...1. Chapter 2 Using PSiGate...9. Index...25

TSYS Credit Card Driver for 3700 POS

Easy CollECt and the transaction ManagEr interface

Alpha e-pay v2 Merchant User Manual (v1.9)

Streamlining Purchases with Website Payment Preferences

VP-ASP Shopping Cart QUICK START GUIDE Version th Feb 2010 Rocksalt International Pty Ltd

Online Payment s. Simple Fast Secure

Fraud Detection. Configuration Guide for the Fraud Detection Module v epdq 2014, All rights reserved.

Note that if at any time during the setup process you are asked to login, click either Cancel or Work Offline depending upon the prompt.

Server based signature service. Overview

SENTRY Payment Gateway

VeriSign Payment Services

InstaMember USER S GUIDE

P309 - Proofpoint Encryption - Decrypting Secure Messages Business systems

Test and Go Live User Guide. Version 4.3 February 2014 Business Gateway

CHARGE Anywhere Universal Shopping Cart

Transcription:

CPAY MERCHANT INTEGRATION SPECIFICATION 1

CONTENTS Using this specification... 3 Purpose... 3 Audience... 3 Introduction... 4 Payment Process... 5 Payment Parameters... 6 Technical Details... 8 Communication Protocols... 8 Passing Parameters... 8 2

USING THIS SPECIFICATION PURPOSE The purpose of this document is to introduce cpay payment platform to the e-commerce merchants. The document specifies the payment process using cpay as a payment platform. Also defines the interaction between the e-shop and cpay. AUDIENCE The document is intended for business divisions of e-commerce organizations. Also provides technical information to IT divisions in order to successfully integrate cpay to the e-shops. 3

INTRODUCTION Each e-commerce provider should offer to the customers reliable and secure payment procedures. The procedures should ensure fast payments processing and decreased number of claims. This would result in faster delivery of goods and encourage customer loyalty. cpay offers a reliable and easy-to-integrate platform for online card payments. Thus the e-shop handles the shopping cart and cpay handles the payment of the selected goods. The e-shop securely redirects the customer to cpay sending in parallel the payment parameters. The customer provides only card details at cpay. cpay supports the traditional cardholder authentication with CVV as well as 3D Secure authentication. This ensures additional security in processing of card operations and decreases fraud payments. 4

PAYMENT PROCESS Step Step 1. Step 2. Step 3. Step 4. Step 5. Step 6. Description The customer selects goods at the e-shop and adds them to the shopping cart The customer clicks on the Pay button. The e-shop redirects the payment parameters to cpay via the customer s browser. The customer now interacts with cpay. The customer enters card information at cpay. Additional cardholder authentication is performed If the customer s card is registered for 3D Secure cpay processes the card payment. cpay redirects the customer s browser back to the e-shop to a success page or failure page according to the payment status. 5

PAYMENT PARAMETERS A payment URL is provided to the merchant in order to redirect the customer s browser: Parameter PaymentURL Description URL at cpay for collecting shopping parameters and prompting cardholder for card details. The URL is: https://www.cpay.com.mk/client/page/default.aspx?xml_id=/mk- MK/.loginToPay/ The e-shop should provide several parameters to cpay for each payment: Parameter Format Length Required? Description AmountToPay numeric 12 Yes Amount of the payment, multiplied by 100. e.g. 1. MKD should be represented with the value 100. AmountCurrency Swift codes e.g MKD 3 Yes Currency of the payment. Details1 alphanumeric 100 Yes Details about the payment. The details are provided later in the customer s bank statement as movement details. Details2 alphanumeric 100 Yes More details about the payment. The payment reference at the e-shop could be passed as Details2 for example. PayToMerchant alphanumeric 100 Yes Merchant s id at cpay MerchantName alphanumeric 200 Yes Merchant s name PaymentOKURL alphanumeric 500 Yes After the payment is processed successfully, cpay redirects the cardholder s browser back to the e-shop at the URL PaymentOKURL. The PaymentOKURL could contain get parameters, so that the merchant can identify the payment and track its success. PaymentFailURL alphanumeric 500 Yes After the payment is processed with failure, cpay redirects the cardholder s browser back to the e-shop at the URL PaymentFailURL. FirstName alphanumeric 64 No Cardholder s first name LastName alphanumeric 64 No Cardholder s last name The PaymentOKURL could contain get parameters, so that the merchant can identify the payment and track its failure. 6

Address alphanumeric 128 No Cardholder s billing address City alphanumeric 100 No Cardholder s billing address - city Zip alphanumeric 50 No Cardholder s billing address - zip Country alphanumeric 100 No Cardholder s billing address - country Telephone alphanumeric 32 No Cardholder s telephone Email alphanumeric 64 No Cardholder s e-mail cpay generates a response and returns it to PaymentOKURL or PaymentFailURL depending on the payment result. The response echoes the parameters from the request and contains one more parameter: Parameter Format Length Description cpaypaymentref numeric 10 Reference of the card payment in cpay 7

TECHNICAL DETAILS COMMUNICATION PROTOCOLS The communication between the customer and the e-shop varies according to the e-shop s architecture. The communication between the customer and cpay is always encrypted in HTTPS with server certificate only. The HTTP parameters are sent to cpay using the method POST. PASSING PARAMETERS When the customer presses the Pay button the POST parameters are sent to cpay. An easy way to implement this functionality is to insert fields of type hidden at the e-shop payment form. These fields would contain values about the merchant, amount, payment details all required and some optional parameters listed in the Payment Parameters section. For example: <form action="https://cpay.com.mk/testpayments" method="post" ID="Form1">... <input type="hidden" id="amounttopay" name="amounttopay" value="5000"/> <input type="hidden" id="amountcurrency" name="amountcurrency" value="mkd"/> 8

<input type="hidden" id="details1" name="details1" value="hotel reservation Palma riva"/><!-- purchase info --> <input type="hidden" id="details2" name="details2" value="76854"/><!-- payment reference at e-shop --> <input type="hidden" id="paytomerchant" name="paytomerchant" value="123745"/> <input type="hidden" id="merchantname" name="merchantname" value="m Tours"/> <input type="hidden" id="paymentokurl" name="paymentokurl" value="http://sampleeshop/eshopok.html"/> <input type="hidden" id="paymentfailurl" name="paymentfailurl" value="http://sampleeshop/eshopcancel.html"/>... </form> 9