You are on page 1of 15

EBS THIRD PARTY INTEGRATION MANUAL

This manual has been prepared for reference of E-Billings Solutions Pvt Ltd
hereafter referred as EBS. This manual is intended to be used by the EBS and its
employees only to facilitate use of Payment Gateway. This manual has been
prepared on a best effort basis. Despite every effort to avoid errors it is likely
that some errors may creep in. The EBS may at its sole discretion modify, alter,
delete, add or amend any of the contents of this manual without assigning any
reason or prior intimation to the Customer. It is notified that the EBS shall not be
responsible for any damage or loss of action to anyone, of any kind in any
manner arising by the use of this manual.
The contents of this manual are proprietary to the EBS and contain information
that is privileged and confidential. Use or dissemination of the contents of this
manual in any manner whatsoever is strictly prohibited. No part of this manual
may be reproduced or copied in any form without the prior permission of the
EBS. Breach of this condition shall be liable for legal action.

Contents
1.Third Party Integration Setup
2.Steps For Integration
i) Inputs to EBS
ii) Response From EBS
3. Possibilities of Errors & Solutions

1.THIRD PARTY INTEGRATION SETUP


It allows a merchant to collect the payment option from their domain. EBS Direct
Integration allows Merchant to collect payment options from the payment page and to
pass on to EBS Secure Server. The main goal is to skip the payment option selection
page, which reduces a step in the payment process.

EBS identifies Merchant by Account ID, which is unique four/five digit number provided
once signed with us. Both EBS Account ID and EBS Secret Key is viewable by login in
EBS Merchant Admin Panel, Click on Accounts->Settings. You can login to Merchant
Admin Panel by https://secure.ebs.in
Note: To reset the secret key merchant should send an Email to support@ebs.in
requesting to reset the secret key.

EBS Direct Integration Kit can be implemented in two methods,


i)

Normal Integration Kits(PHP, ASP, VB, Asp.Net, JSP, Perl)

ii)

Shopping Cart Kits (Prestashop, Joomla, Opencart, Cscart, Magento etc..)

NORMAL INTEGRATION KITS


To implement the Third party/EMI kit procedure, the additional parameter
(payment_option) has to be added on the payment page(pay file) of our
EBS integration files.
Relevant integration files can be downloaded through
https://support.ebs.in/app/index.php?/Knowledgebase/List/Index/10/integration-kits

The following files will be provided,


a.Pay page : Pay file (pay.html) is a sample file, from where you can get the
necessary information (Billing & Shipping etc..) from your customer/cardholders.
Also, the page can customize at your end for your convenience based on your
website requirement & platform.
b. RC43: This file has the algorithm, which is responsible for encryption and
decryption process.
c. Response Page : This is a sample code of your Response page. After the
transaction, response page is used to retrieve all the DR parameter values.
Return_url parameter value points to the response file.
Note: All the 3 pages are sample files, you can customize as per your
need without affecting the flow.
SHOPPING CART KITS
Relevant shopping cart files can be downloaded through our support website on
the below link,
https://support.ebs.in/app/index.php?/Knowledgebase/List/Index/7/shoppingcart-kits
As in the above case, the additional parameter (payment_option) has to be
added on the corresponding payment file from where the other DR parameter

values(Account ID, Mode, Return URL, Sale Amount, Description, Reference


Number, Billing & Shipping Address) are passed.
Note : The payment file will be provided in different NAME based on the
kit.

INTEGRATION PROCEDURE
In this Integration, the payment option selection page can be integrated in your
merchant website wherein the customer can select the payment mode in your domain.
On integrating this kit in your end,
i)

For Net Banking payment options, the customer will be directly routed to the
corresponding Bank URL from your application.

ii)

For CARD payment options, the customer will be directed to the EBS page to
enter the credentials and then the process will be the same as earlier. The
integration kit for the same has been attached.

2.INTEGRATION STEPS
Inputs
Inputs are the mandatory parameters which should be passed onto the EBS Secure
Server to process the Payment from the Merchant Payment/Confirmation page.
Following table gives the parameter list, which should be passed from the payment
page:
Post URL: https://secure.ebs.in/pg/ma/sale/pay

Parameter
account_id

Type
Char

Min
4
1
1

reference_no

Description
Your EBS Account ID
Your reference number towards
order

amount

Total Sale Amount

Char
Decim
al

description

Detail description of the sale

Char

mode

Mode : either TEST/LIVE


This is the url you want EBS to
return back after transaction
is successful.
Cardholder Name
Cardholders billing address
Cardholders billing city
Cardholders billing state
Cardholders billing country.[3
Digit country code]
Cardholders billing postal code.
Cardholders billing phone.
Cardholders billing email.
Customer delivery Name
Customer delivery address
Customer delivery city
Customer delivery state
Customer delivery country.[3
Digit country code]
Customer delivery postal code.
Payment Option
MD5 hash of all the parameters
with
your EBS secret key.

Char

return_url
name
Address
city
state
country
postal_code
phone
email
ship_name
ship_address
ship_city
ship_state
ship_country
ship_postal_code
Payment_option
secure_hash

Char
Char
Char
Char
Char
Char
Char
Char
Char
Char
Char
Char
Char
Char
Char
Char

1
4
1
1
1
1
1
3
1
5
1
1
1
1
1
3
1
4
32

Char

i)

All the above parameters are mandatory to be passed on the merchant pay
file.

ii)

The below parameters can be passed as a hidden fields,


Account ID, Reference No, Mode, Return_URL, Amount, secure Hash

Follow the instructions given below,


1.Kindly add an additional parameter with the variable name "payment_option" on
your payment file along with the other DR parameters (Account_id, Mode, Amount,
Return URL ,Billing & Shipping Information etc..) in the EBS integration files.
2.A separate Code has been assigned for each and every payment option mentioned
below to pass the corresponding values through the parameter payment_option.
For EX:- TEST PAYMENT METHOD = > 1001
The Payment methods are
i)

Credit

ii)

Debit

iii)

Cash

iv)

Net Banking

v)

EMI

3.Pass the separate code from your database OR using an array function through
the added parameter "payment_option". So that the corresponding payment option
will be displayed on your website for the customer selection.
Similarly payment option codes will be listed below for the other payment methods,

How to make a Payment


ScreenShot For Sample Payment Method Page

Screen shot EBS Payment Page Once Payment method selected

i)

Once the payment method selected on the merchant website, you will redirected to our EBS payment page.

For Ex:- If customer choose Visa payment method on the merchant website, only the
corresponding selected option will be shown on our EBS payment page as figured in the
above screen shot.
ii)

Hence, customer has to enter the card credentials to proceed for further
payment completion.

Screenshots for sample EMI page

Screen shot EBS Payment Page Once Payment method selected

Ex:-

If customer choose 3 month EMI/6 month EMI payment method on the merchant
website, only the corresponding selected option will be shown on our EBS payment
page as figured in the above screen shot.

Response From EBS :


In this sample response page, you have to provide your EBS secret key. The response given back to the
return URL, the parameters in the response are listed below. The response of the transaction is given
back using POST method to the URL pointed by ReturnURL parameter in the pay page.
Once the transaction completed, the corresponding status and details of the same will be given back to the
URL pointed by ReturnURL parameter. This response will be given back in encrypted format using EBS
secret key. The response has the following parameters:
If the ResponseCode is '0' the transaction is successful.
If the ResponseCode is not '0' the transaction has been declined or an error condition as detected, such
as the customer typed an invalid card number.
Recommended validation in the response file to avoid duplication of records in your backend
1) Pass your order id in the reference_no parameter and in response file, check whether MerchantRefNo
and your order id matches.
2) Check the amount of the order and the "amount" parameter in the response is equal
If both the conditions results as true, insert order in your back end, which nullifies the duplications.
Is Flagged :
Flagged transactions are potentially risky transactions, which will be verified by our Risk team and updated manually as authorized/canceled within 24 hours.
If required, we may contact you to provide details/confirmation for the action to be taken for such risky
payments.
Note : Please do not process/ship the product/service to the customer until the transaction is
approved/authorized and captured.
IsFlagged can have two boolean values YES/NO
"Yes",indicates that the transaction is waiting for manual verification.
"No", indicates that it is authorized and ready for capture.
If the transaction is successful(response code= "0") and if the IsFlagged is "No", then the service can be
provided immediately.
If the transaction is successful(response code = "0") and if the IsFlagged is "Yes", then the service for
the corresponding payment has to be kept on hold until the manual verification is completed and authorized by EBS.
Session Time Out: - 15 minutes

Response Parameters
Parameter
ResponseCode
IsFlagged

Description
Response Code which gives the status of the transaction. 0
(Zero) for success and for other value, Failed.
It can be either YES/NO. YES denotes that its waiting for
manual approval.

ResponseMessage
BillingAddress

Response Message which tells about the Response Code

Amount

Sales Amount of the transaction


CardHolder Billing City

BillingCity

CardHolder Billing Address

BillingCountry

CardHolder Billing Country

DateCreated
BillingEmail

DateTime of the transaction

Mode

CardHolder Email Id
In which mode the transaction has been completed. Either
TEST/LIVE

BillingName

CardHolder Billing Name

PaymentId

Unique Payment Id given for all the payments by EBS

BillingPhone

CardHolder Contact Number

BillingPostalCode

CardHolder Postal Code

ReferenceNo

Provided by Merchant to identify the transaction

DeliveryAddress

Shipping Address

DeliveryCity

Shipping City

DeliveryCountry

Shipping Country

DeliveryName

Person Name, to whom its shipped

DeliveryPostalCode
DeliveryState
Payment Option code
TransactionId

Shipping Postal Code


Shipping state
1001
A Unique Id given for identifying the transaction.

3.POSSIBILITIES OF ERROR & DESCRIPTIONS


I. Selected Payment Option Not activated, please try another option

In order to avoid the above error message, kindly satisfy the below criteria,
i)

Ensure that the registered Account ID value has been passed on the EBS payment file.
Since , the payment options will not be applicable on our EBS DEMO Account (5880).
Note : To retrieve the registered Account details, log on to your EBS secure portal through
secure.ebs.in and navigate to the tab Account - > Settings - > there you can find your
account details( Account ID & Secret Key).

ii)

The Payment option code value has to be passed through the parameter payment_option
only based on the corresponding PG( Axis, Citi, SBI, HDFC)

iii)

If the selected payment method (Credit/Debit/Cash/Net-Banking/EMI/PayPal) has not been


activated on the corresponding merchant account from EBS.

To ensure prompt support, EBS has a simple online ticketing system accessible
24x7 at http://support.ebs.in. Each ticket will be responded in 8 to 24 Business
working Hours, with ticket number to facilitate status check anytime thereafter.

Please send your suggestions/ feedback to:

support@ebs.in

+91 44 4231 3333