Pay BBPS Bill

post https://staging.eko.in:25004/ekoapi/v3/customer/payment/bbps

Make payment for utility bills, mobile recharge, etc via BBPS

time	status	user agent
Retrieving recent requests…

Loading…

What is BBPS?

Bharat Bill Payment System (BBPS) is an RBI mandated system which offers integrated and interoperable bill payment services to customers across geographies with certainty, reliability and safety of transactions.

Workflow

Active BBPS Bill Payment service for your agent using the Activate Service for Agent API and passing service code = 53
Fetch bill
Get a list of parameters required for that particular biller/operator by calling the Get Operator Parameters API
1. Parameters name passed in the payment API should be exactly the same as param_name returned here.
2. Parameter value entered by the user should be verified as per the param_type and regex returned here.
Just before calling the payment API, generate secret-key-timestamp, secret-key, and request-hash
Make payment by calling this API with all the required parameters (as per step-3)

📘
High Commission (Offline)
This will allow API partner to send fetch bill and pay bill transaction via new high commission channel parallel to existing instant channels. Note that it will only work for billers that have high_commission channel available to them. You can check that in fetch biller details API response. Note that high commission channel is parallel to that of regular instant channel. It will not affect transaction flow (including old request structure) from existing regular channel.
The hc_channel is optional parameter; you can pass its value as 1 to choose high commissions channel for you transaction otherwise it will to the "instant" channel. Please note that high commission channel might take upto 6 hours to complete transaction on the biller side.

Biller List

Body Params

initiator_id

string

required

Your registered mobile number (See Platform Credentials for UAT)

user_code

string

required

Unique code (mobile number) of your registered agent/retailer

client_ref_id

string

required

A unique ID for every API call generated at your end

utility_acc_no

string

required

Account number provided by operator for which bill needs to be paid

confirmation_mobile_no

string

required

Customer's mobile number

sender_name

string

required

Name of the Customer

operator_id

string

required

See the Get Operators API

amount

string

required

Amount value of the bill/ recharge

source_ip

string

required

IP of the agent/retailer making this payment. This is crucial for security & fraud prevention.

latlong

string

required

Your agent's location (latitude,longitude). This is crucial for security & fraud prevention.

billfetchresponse

string

Needs to be passed only when value of this parameter is 1 in Get operator list API. You will get the value of this parameter in [Fetch Bill API] (https://developers.eko.in/reference#fetch-bills-api)

dob

string

Defaults to DD/MM/YYYY

For LIC: Date of birth of the policy holder

postalcode

int32

For MSEB: The postal PIN code (6-digits)

Headers

developer_key

string

required

Your static API key (See Guide)

secret-key

string

required

Your dynamically generated security key, unique for every request (See Guide)

secret-key-timestamp

string

required

The current timestamp used to generate secret-key

request_hash

string

required

Generated hash of following concatenated values: secret_key_timestamp + utility_acc_no + amount + user_code (See Guide)

Response

Language

Credentials

Request


xxxxxxxxxx
24
1
curl --location --request POST 'https://staging.eko.in:25004/ekoapi/v2/billpayments/paybill?initiator_id=9962981729' \
2
--header 'developer_key: becbbce45f79c6f5109f848acd540567' \
3
--header 'secret-key-timestamp: 1626696381248' \
4
--header 'secret-key: I/EzGL4m0Bxu9OHW45iW/jVrOej8tEqfnDEplyVeVTc=' \
5
--header 'request_hash: Fsn/3iuQole5Ka30N0QW1Dku/YwCZqh8gWFtX2MNNtE=' \
6
--header 'Content-Type: application/json' \
7
--header 'Connection: Keep-Alive' \
8
--header 'Accept-Encoding: gzip' \
9
--header 'User-Agent: okhttp/3.9.0' \
10
--data-raw '{
11
    
12
    "source_ip":"121.121.1.1",
13
    "user_code":"20810200",
14
    
15
    "amount":"50" ,
16
    "client_ref_id":"202105311125123456",
17
    "utility_acc_no":"151627591",
18
    "confirmation_mobile_no":"9999999999",
19
    "sender_name":"Kaushik",
20
    "operator_id":"22",
21
    "latlong":"77.06794760,77.06794760"
22
     "hc_channel" : 1 
23
}
24
'

Click Try It! to start a request and see the response here! Or choose an example:

application/json

What is BBPS?

Workflow

📘High Commission (Offline)

Biller List

200200

📘
High Commission (Offline)