/

to search

Introducing Setu Changelog Check it out ↗

#Payment Channel

This is the initiating payment channel.

typedescription
INTInternet Portal
INTBInternet Banking
MOBMobile Application
BNKBRNCHBank Branch
BSCBusiness correspondent
AGTOffline Agent
KIOSKKIOSK
ATMATM
MOBBMobile Banking
POSPOS
MPOSMPOS

#Payment Mode

Payment modes supported by a biller.

type
Cash
Internet Banking
Credit Card
Debit Card
Prepaid Card
IMPS
NEFT
UPI
Wallet
AEPS
Account Transfer
Bharat QR
USSD

#State and City mapping

Click here for State and City Biller Coverage Mapping

#Customer

Customer object holds the customer mobile number and the customer bill parameters.

parametertypedescription
mobilestring (6, 10 and 20 digits)Customer Mobile Number
billParameters{ name: string, value: string}[]Bill Parameters. The parameters to send is found in the biller details API.
billParameters[].namestringName of the bill parameter. name should match the parameter in biller details API.
billParameters[].valuestringValue of the bill parameter. Value is validate according to the regex found in the biller details.

#Biller

Biller object holds the biller ID.

parametertypedescription
idstringThe Biller ID on BBPS

#Agent

Details pertaining to the Agent which initiates the transaction. Values of the field if provided to NPCI has to be matched against it.

parametertypedescription
idstringThe Agent ID on BBPS
channelPaymentChannelPayment Channel used by Agent.
ipstring,ipv4Agent server IP address
macstring,macServer MAC address
mobilestringAgent Mobile number
geocodestringAgent Geocode
postalCodestringAgent Pincode
terminalIdstringAgent terminal ID
imeistringAgent IMEI
ifscstringAgent IFSC
osiOS or AndroidInitiating device OS
appstringInitiating app name

#Initiating Channel & Required Agent parameters

ChannelAgent parameters
BNKBRNCHifsc,mobile,geocode,postalCode
MOBip,imei,os,app
MOBBip,imei,os,app
INTip,mac
INTBip,mac
ATMterminalId
KIOSKterminalId
AGTterminalId,mobile,geocode,postalCode
BSCterminalId,mobile,geocode,postalCode

#Initiating Channel & Eligible Payment modes

Payment ModeINTINTBMOBMOBBATMBNKBRNCHKIOSKAGTBSC
CashNNNNNYYYY
Internet BankingYYYYYNNNN
Credit CardYYYYYYYYY
Debit CardYYYYYYYYY
Prepaid CardYYYYYYYYY
IMPSYYYYNYNYY
NEFTYYYYYYNYY
UPIYYYYNYNYY
WalletYYYYNYYYY
AEPSNNYNNYNYY
Account TransferNNNNNYNNY
Bharat QRNNYYNYNYY
USSDNNYYNNNNN

#Failure Reason

parametertypedescription
codestringError codes includes Application, Banking and BBPS error codes
messagestringError code description
typeFUND_TRANSFER or BBPS or APPError Type. BBPS errors are due to BBPS, and code and message field contain the actual BBPS error.

#Payment Details

parametertypedescription
modePayment ModePayment Mode
paymentRefIdstring (6 - 35 characters)Payment Reference ID tagged by agent
amountintegerAmount in paise
timestampdate-timeTimestamp
selectedPaymentOptionsSelected Payment Option[]Array of selected payment options

#Payment Bill

The Payment Bill object contains information about a specific bill to be paid.

ParameterTypeDescription
billNumberstringUnique identifier for the bill
amountintegerAmount to be paid for the bill in paise

#Bill Status

typedescription
ProcessingFetching a bill (or) Paying a bill is in progress
SuccessSuccessfully fetched a bill (or) paid a bill
FailureUnable to fetch a bill or pay a bill

#Transaction Status

typedescription
ProcessingTransaction is in progress
SuccessTransaction is successful
ErrorTransaction has failed

#Dispute Status

typedescription
INITIALIZEDInitialized
ASSIGNEDComplaint has been accepted.
RE_ASSIGNEDWhen Customer BBPOU re assigned the complaint to the Biller BBPOU.
ASSIGNED_TO_BOUWhen BBPCU assign the complaint to BBPOU. If the COU and BOU are same for a transaction, then the status of complaint will be changed to Assigned to OU
ASSIGNED_TO_COUWhen BBPCU assign the complaint to BBPOU. If the COU and BOU are same for a transaction, then the status of complaint will be changed to Assigned to OU
ASSIGNED_TO_OUWhen BBPCU assign the complaint to BBPOU. If the COU and BOU are same for a transaction, then the status of complaint will be changed to Assigned to OU
RESOLVEDOnce the BBPOU resolves the customer related complaint, the BBPOU updates the system.
UNRESOLVEDIf the BBPOU does not respond to the complaint within the specified TAT (Super escalation), the complaint status changed to unresolved.

#Bill Period

type
ONETIME
DAILY
WEEKLY
BIMONTHLY
MONTHLY
QUARTERLY
HALFYEARLY
YEARLY
ASPRESENTED
NA

#Biller Selection Type

typedescription
SINGLEUser can pay only one bill from the fetch response
MULTIPLEUser can pay any combination of bills from the fetch response
ALLUser must pay all bills in the fetch response

#Biller Response Type

typedescription
SINGLEBiller returns a single bill in the fetch response
LISTBiller returns multiple bills in the fetch response
SELECTIVEBiller returns bills based on specific criteria

#Fetched Bill

parametertypedescription
customerNamestringBill owner
amountintegerBill amount in paise
dueDatedateBill due date
billDatedateBill date
billNumberstringBill number
billPeriodBill PeriodBill period of the bill fetch / payment requested. NA when bill period is unavailable.
labelstringAdditional label for the bill
minAmountintegerMinimum amount that can be paid for this bill in paise
maxAmountintegerMaximum amount that can be paid for this bill in paise
amountMultipleintegerBill payment amount should be multiple of this value in paise
paymentOptionsPayment Option[]Array of payment options available for this bill

#Payment Option

ParameterTypeDescription
namestringThe display name of the option
amountintegerThe amount that can be paid for this option in paise
minAmountintegerThe minimum amount that can be paid for this option in paise
maxAmountintegerThe maximum amount that can be paid for this option in paise
amountMultipleintegerThe payment amount should be a multiple of this value in paise

#Selected Payment Option

ParameterTypeDescription
namestringThe display name of the option from bill fetch
amountintegerThe amount being paid for this option in paise

#Exactness

Limits on acceptable payment amounts set by the biller.

typedescription
ExactOnly the exact amount specified in fetched bill can be paid
Exact and belowAmount specified in fetched bill or less can be paid
Exact and aboveAmount specified in fetched bill or more can be paid
AnyAny amount can be paid
RANGEAmount within specified minAmount and maxAmount specified in fetched bill can be paid

#Payment Limit

parametertypedescription
paymentModePayment Modepayment mode
supportsPendingStatusboolWhether payment mode for biller supports pending status
minLimitinteger or nullMinimum acceptable amount in paise
maxLimitinteger or nullMaximum acceptable amount in paise

#Dispute Type

typedescription
account-not-updatedTransaction Successful, account not updated
double-paymentDouble payment updated
paid-to-wrong-accountErroneously paid in wrong account
amount-deducted-biller-credited-no-transaction-idAmount deducted, biller account credited but transaction ID not received
amount-deducted-biller-not-credited-no-transaction-idAmount deducted, biller account not credited & transaction ID not received
amount-deducted-multiple-timesAmount deducted multiple times
othersOther reason

#Biller Customer Params

parametertypedescription
dataTypeNUMERIC or ALPHANUMERICValue format
maxLengthinteger or nullValue's max length
minLengthinteger or nullValue's min length
optionalboolIs the parameter optional
paramNamestringParameter name
regexstring (Regex)Value Regex
valuesstringPossible default values
visibilityboolVisibility of the customer parameter in COU/AIs front-end screen

#Fetch API Type

typedescription
BILL_FETCHBiller can accept a Bill Fetch request.
BILL_VALIDATEBiller can accept a Bill Validate request.
BILL_DIRECTBiller can accept direct payment without a Bill Fetch or Bill Validate.

#Biller Payment Channel

Maxium amount accepted by the biller for the Payment Channel.

parametertypedescription
paymentChannelPayment ChannelPayment Channel
supportsPendingStatusboolWhether payment channel for biller supports pending status
minLimitinteger or nullMinimum acceptable amount in paise
maxLimitinteger or nullMaximum acceptable amount in paise

#Biller Plan Information

parametertypedescription
amountintegerPlan amount in paise
idstringPlan ID
categoryTypestringPlan Category defined by the biller.
categorySubTypestringPlan Sub-Category defined by the biller.
descriptionstringPlan description
effectiveFromdatePlan effective from
effectiveTodatePlan effective to
statusACTIVE or DEACTIVEPlan status

#Transaction

/transactions

#Query Parameters

parametertypedescription
limitintegerDefault: 250, Maximum: 1000, Minimum: 1
afterstring
startDatedatestart date of the timestamp provided by the partner while making the request. Full-date notation as defined by RFC 3339, section 5.6, for example, 2017-07-21
endDatedateend date of the timestamp provided by the partner while making the request. Full-date notation as defined by RFC 3339, section 5.6, for example, 2017-07-21
billerIdstringTransaction's Biller ID
statusTransaction StatusTransaction Status
mobilestring (6, 10 and 20 digits)Customer Mobile Number

#Response

parametertypedescription
refIdstringBBPS Reference ID
statusTransaction StatusTransaction Status
transactionIdstringSetu Transaction ID
partnerRefIdstring (6 - 35 characters)Payment Reference ID tagged by agent
billsPayment Bill[]Details of bills paid
billerIdstringBBPS Biller ID
amountintegerAmount in paise
customerMobileNumberstring (6, 10 and 20 digits)Customer Mobile Number
timestampdate-timeTransaction timestamp

#Dispute

/disputes

#Query Parameters

parametertypedescription
statusDispute StatusDispute status
limitintegerDefault: 250, Maximum: 1000, Minimum: 1
afterstring
transactionIdsstring[]Disputes' Setu Transaction IDs
partnerRefIdsstring[]Disputes' Partner Transaction IDs
billerIdsstring[]DIsputes' Biller ID
customerMobileNumberstring (6, 10 and 20 digits)Customer Mobile Number

#Response

parametertypedescription
assignedstringBBPOU to which the complaint is assigned
billerIdstringDispute's Transaction Biller ID
complaintIdstringComplaint ID for the dispute provided by BBPS
complaintStatusDispute StatusBBPS Complaint status
customerMobileNumberstring (6, 10 and 20 digits)Customer Mobile Number
partnerRefIdstring (6 - 35 characters)Payment Reference ID tagged by agent
refIdstringBBPS reference ID for the dispute request
remarksstringBBPS Remarks for the complaint
responseCodestringBBPS Response code for the dispute request
responseReasonstringBBPS Response reason for the dispute request
transactionIdstringSetu Transaction ID

#Biller MDM

/billers

#Query Parameters

parametertypedescription
categoryNamestring[]Category of the biller
idsstring[]biller Ids
limitintegerDefault: 250, Maximum: 1000, Minimum: 1
afterstringBillers are sorted via the Biller ID. Providing a biller Id fetches billers right after this biller in a paginated way.
searchstringsearches the provided text over biller name and biller alias
pincodestring
coveragestringBBPS coverage. Used to search billers having a specific coverage area
countrystringBBPS Country Code. Used to search billers operating in a certain country
statestringBBPS state code. Used to search billers operating in a certain state
citystringcity name, used to search billers operating in a certain city
updatedSincedate-timeFetch billers updated on or after the provided timestamp
tagsstring
paymentChannelPayment Channel[]
paymentModePayment Mode[]

#Response

parametertypedescription
categoryNamestringBiller Category
citystringBiller City
countrystringBiller Country
coveragestringBiller coverage
createdAtdate-timeBiller Created At
customerParamsBiller Customer Params[]Customer Parameter format descrption
exactnessExactnessBiller Exactness
fetchApiTypeFetch API TypeBiller Fetch API Type
idstringBiller ID
logostringBiller logo
modifiedAtdate-timeBiller Modified At
namestringBiller Name
payWithoutFetchAllowedboolWhether biller allows bill payment without a fetch or not. Even in case of BILL_FETCH API type, certain bills make the fetch optional
paymentChannelsBiller Payment Channel[]Payment Channel limits set by the biller.
paymentModesPayment Limit[]Payment mode limits set by the biller.
pincodestringBiller Pincode
supportsPendingStatusboolWhether the biller supports pending status. In this case, a payment can be in progress for up to 2 days.
tagsstringAdditional Tags of the biller.
statestringBiller State
plansBiller-Plan-Information[]Plans provided by the biller.
enforcesSameDayFetchPayboolWhether the biller requires bill payment to be on the same calendar day as bill fetch.
bbpsUpdateTimestampdate-timeLast updated date-time of the Biller accurate to the nearest day.
responseTypeBiller Response TypeIndicates how the biller provides bill information in the fetch response
selectionTypeBiller Selection TypeSpecifies how users can select bills for payment (only applicable for LIST response type)

#Dispute Request

/bills/dispute/request

#Request Body

parametertypedescription
txnReferenceIdstringSetu Transaction ID
disputeTypeDispute TypeDispute type
descriptionstring (100 characters)Dispute description

#Dispute Response

/bills/dispute/response

#Response Body

parametertypedescription
refIdstringBBPS Reference ID
disputeIdstringDispute ID used for the complaint
statusDispute StatusDispute Status
assignedTostringThe entity who has this complaint assigned to.
remarksstringRemarks of the complaint

#Fetch Request

/bills/fetch/request

#Request Body

parametertypedescription
customerCustomerCustomer Object
billerBillerBiller Object
AgentAgentAgent Object

#Fetch Response

/bills/fetch/response

#Response Body

parametertypedescription
refIdstringBBPS reference ID for the fetch request.
statusBill StatusBill fetch request status.
failureReasonFailure ReasonFailure reason on status Failure
billFetched BillSingle fetched bill. Used when billerResponseType is 'SINGLE'.
billsFetched Bill[]Array of fetched bills. Used when billerResponseType is 'LIST'.
additionalInfo{"name":"value"}[]Additional information of the bill sent by the biller
billerRefIdstringBiller reference ID used by the biller for the request.
exactnessExactnessBiller Exactness
paymentLimitsPayment Limit[]Payment limits
billerResponseTypeBiller Response TypeIndicates whether the biller provides a single bill ('SINGLE') or multiple bills ('LIST')
billerSelectionTypeBiller Selection TypeSpecifies how users can select bills for payment (only applicable for LIST response type)

Note: The billerResponseType field indicates which bill data field to use. For 'SINGLE' type, use the bill field (contains zero or one bill). For 'LIST' type, use the bills field (contains one or more bills in an array).


#Payment Request

/bills/payment/request

#Request Body

parametertypedescription
refIdstringBBPS Reference ID from previous bill fetch request. Mandatory for non-adhoc payments.
agentAgentDetails of agent processing the payment. Mandatory for adhoc payments.
billerBillerDetails of biller receiving the payment. Mandatory for adhoc payments.
customerCustomerDetails of the customer making the payment. Mandatory for adhoc payments.
billsPayment Bill[]Details of bills to be paid. Mandatory for LIST billers only.
paymentDetailsPayment DetailsDetails specific to the payment being made. Mandatory for all payments.

Note:

  • For non-adhoc payments, only refId, paymentDetails, and potentially bills (for LIST billers) are required.
  • For adhoc payments, agent, biller, customer, and paymentDetails are mandatory. refId and bills are not applicable.

#Payment Response

/bills/payment/response

#Response Body

parametertypedescription
refIdstringBBPS Reference ID
statusBill StatusTransaction Status
failureReasonFailure ReasonFailure information in case of Transaction failure
transactionIdstringSetu Transaction ID
billerRefIdstringInternal reference number used by the Biller for a transaction.
billerIdstringBBPS Biller ID
paymentDetailsPayment DetailsPayment Details for the transaction
additionalInfo{"name":"value"}[]Additional information of the bill sent by the biller
refundStatusRefund StatusRefund status if the payment failed and the amount was debited.
billsPayment Bill[]Details of bills paid. Present for LIST billers only.

Was this page helpful?