The Billing API is a programmatic interface that allows developers to manage and automate billing-related tasks and transactions within an application or system, enabling efficient and customizable financial interactions between a service provider and its customers. New Billing Plan Request adds a new billing schedule to an existing customer or adds a new billing schedule for a new customer.

Billing Endpoint: {{GatewayAPIURL}}/Billing/Plan

Request Field Description:

Request Object:

Customer Object

Bill Sequence

Additional Data

Response Field Description

Billing Plan

Customer Object

KEYFIELD STATUSTYPEVALUE DESCRIPTION
abidOptionalnumericAuto Generated e.g.123Billing ID
customer_idMandatoryalphanumeric“AUTO” for auto generated id’s
starts from 100000 OR User Generated e.g. CID001
The customer id is either system generated or user specific. Based on customer id, billing is processed for the customer.
tokenMandatoryalphanumericVariable LengthBilling token generated by gateway
plan_typeMandatorystring 1-Recurring 2- Installment 3 -One Time ScheduleThe type of plan chosen for billing occurence
schedule_typeMandatorystringD- DailyW- WeeklyM- MonthlyY- YearlyS- Scheduled PaymentThe type of scheduled payments chosen on daily, weekly, monthly and yearly basis.
start_dateMandatorystringFormat- yyyy-mm-ddThe date when the payments start. Should be greater than the present date.
end_dateConditionalstringFormat- yyyy-mm-ddThe date when the payments end. Required for recurring payments
periodicityConditionalnumericValue-1 to 10Depending on the plan type and schedule, the periodicity can be passed. It defines the interval between schedules.
end_typeMandatorynumeric0-One Time Schedule1-Until Cancelled2-Until Date3-No of PaymentHow the plan should end.Until Cancelled,Until Certain number of payments or Until End Date
no_of_paymentsConditionalnumericValue-1 to 99Required for Installment plan type. Number of payments to be made for Installment Billing plan
amountMandatorynumericFormat 0 or 0.00The amount per occurrence/event of the bill.
reference_idMandatorystringvarchar(50)Any number that can be used as reference for the billing plan
max_retryOptionalnumericMaximum No. of Attempts-10Number of retry attempts if a transaction fails at the time of execution
nameOptionalstringVariable LengthName of the customer
activeMandatorybooleantrue – Activefalse- Inactive (Default)Depending on the Active and Inactive status, the transaction will be executed for occurence for the day.
billing_modeOptionalstring0 – Manual1 – Auto (Default)If this is set Manual, Billing sequence needs to be given for each event/occurence when the transaction should go through
bill_dayConditionalstringFor schedule type weeklyBill Day – Select any day between Sunday to Saturday
For schedule type monthly,yearlyBill Day – Select any day between 1 to 28
Depending on the plan type and schedule, the Bill Day can be passed.
email_receiptOptionalbooleantrue-activefalse-inactiveIndicator to send email receipt to customer based on any action.
merchant_terminal_idOptionalnumericTerminal IDTerminal ID of the merchant

Bill Sequence

KEYFIELD STATUSTYPEVALUEDESCRIPTION
amountConditionalnumericFormat 0 or 0.00Billing amount for the given sequence
schedule_dateConditionalstringFormat- yyyy-mm-ddDate for the specific occurrence of the bill
reference_idConditionalstringvarchar(50)Any number that can be used as reference for the billing plan queue
sequence_numberConditionalnumericNumber of SequenceEvent number or the sequence number to identify a particular occurrence in a recurring bill

Additional Data

KEYFIELD STATUSTYPEVALUEDESCRIPTION
idOptionalstringup to 2 Characters1 to 20Based on the selection on Custom User defined fields and id
valueOptionalstringup to 255 CharactersBased on the selection on Custom User defined fields and values

Response Field Description

KEYTYPEVALUEDESCRIPTION
result_codestring1 – Approved2- Declined3- ErrorThe overall status of the transaction.
result_sub_codestring000- ApprovalResponse sub code.
result_textstringupto 100 characters APPROVAL, DECLINEDDescription of the outcome of the transaction from First Data
transaction_datetimenumericFormat: yyyyMMddTHHmmssZDate and Time of the transaction response

Billing Plan

KEYTYPEVALUEDESCRIPTION
abidnumericAuto Generated e.g.123Billing ID
customer_idalphanumericCan be AUTO Generated e.g. 100000ORUser Generated e.g. CID001The customer ID is either system generated or user specific.
tokenstringnumeric value generate by token generation process.Token details from token table.
plan_typenumeric1-Recurring2- Installment3 -One Time ScheduleThe type of billing plan selected.
schedule_typestringD- DailyW- WeeklyM- MonthlyY- YearlyS- Scheduled PaymentThe type of billing schedule selected
amountstringUpto 2 decimal placesBilling amount
start_datestringFormat- yyyy-mm-ddStart date of the billing plan
periodicitynumericValue-1 to 10Depending on the plan type and schedule, the periodicity can be passed. It defines the interval between schedules
end_typestring0- One Time Schedule1 – Until Cancelled2-Until Date3 – No of PaymentEnd type selected for the billing plan
no_of_paymentsnumericValue – 1 to 99Number of payments to be made in the installment plan
reference_idstringvarchar(50)Any number that can be used as reference for the billing plan
namestringVariable LengthName of the customer
activebooleantrue – Activefalse- Inactive (Default)Status of the billing plan
billing_modestring0- Manual1- AutoSequence of manual billing schedule
max_retrynumericMaximum No. of Attempts-10Number of retry attempts if a transaction fails at the time of execution
bill_daystringFor schedule type weeklyBill Day – Select any day between Sunday to SaturdayFor schedule type monthly,yearlyBill Day – Select any day between 1 to 28Depending on the plan type and schedule, the bill day passed.
email_receiptbooleantrue-active false-inactiveIndicator to send email receipt to customer based on any action.
merchant_terminal_idnumericTerminal IDTerminal ID of the merchant

Bill Sequence

KEYTYPEVALUEDESCRIPTION
reference_idConditionalvarchar(50)Any number that can be used as reference for the billing plan
sequence_numberConditionalVariable ValueEvent number or the sequence number to identify a particular occurrence in a recurring bill
amountConditionalFormat 0 or 0.00Billing amount for the given sequence
schedule_dateConditionalFormat- yyyy-mm-ddDate for the specific occurrence of the bill