Payment Intimation
Payment Intimation API is used to submit insurance proposal payment details and mandate information after a successful customer payment, and to confirm proposal tracking details with the insurer.For enum values, please refer to the Master Lookup API available in the Building Block.
Request Body required
1SB Payment Intimation request
- Array [
- ]
- Array [
- ]
Distributor object
Return a JSON object with latitude and longitude properties to point to location of user.
Possible values: <= 20 characters
Distributor ID assigned to each consumer by 1SB.
Possible values: <= 20 characters
PoSP code or SP code or Brokder Qualified Person.
Possible values: <= 20 characters, [B2B, B2C]
This is used by insurance companies to identify sales channel.
varFields object[]
varField array hold any additional data related to Distributor
Possible values: <= 20 characters
Name of additional fields
Possible values: <= 20 characters
Value of additional fields
trackInfo object required
Tracking information for proposal and policy
Possible values: <= 100 characters
Manufacturer application number
Possible values: <= 100 characters
Quote ID generated by manufacturer
Possible values: <= 100 characters
Proposal number
Possible values: <= 100 characters
Policy number
Possible values: <= 50 characters, [BCIBL, GFPL]
Insurance company merchant name
Possible values: <= 50 characters
Merchant ID provided by insurer
Possible values: <= 15 characters, [NBHI, TAGIC, BAGIC, HDFCERGO]
Insurance company identifier
Possible values: <= 20 characters, [Reassure, MEDICARE]
Product code
personalInformation object required
Proposer and insured personal details
individualDetails object[] required
Possible values: [LIFE ASSURED, PROPOSER]
Role of member
Sequence number of member
Possible values: <= 10 characters, [MR, MRS, MS]
Title of member
Possible values: <= 50 characters
First name
Possible values: <= 50 characters
Last name
Possible values: <= 10 characters, [MALE, FEMALE, OTHER, TRANSGENDER, OTHERS]
Gender of Member
Date of Birth of Member. Date is formatted string as per ISO 8601 standard.Format - YYYY-MM-DD
Possible values: <= 20 characters, [DIVORCEE, MARRIED, SINGLE, WIDOW, WIDOWER]
Marital status
Possible values: <= 100 characters
Email address
Possible values: <= 10 characters
Mobile number
Possible values: <= 10 characters
Pin / Zip code
Quoted premium amount
Possible values: [HY, M, Q, S, Y]
Premium payment frequency
paymentDetails object required
Payment transaction details
Possible values: <= 100 characters
Payment order ID
Possible values: <= 5 characters, [INR]
By default should be INR
Consumer reference number
Possible values: [Success]
Payment status
Payment gateway transaction ID
Possible values: [Internet Banking, UPI, Credit Card]
Mode of payment
Transaction amount
Date is formatted string as per ISO 8601 standard.Format - YYYY-MM-DD
Raw response received from PG.
Payment type
Auto debit start date. Date is formatted string as per ISO 8601 standard.Format - YYYY-MM-DD
Auto debit mode
eMandateDetails object
eMandate / subscription details
Frequency of mandate
Mandate debit amount
Mandate method
Mandate start date.Date is formatted string as per ISO 8601 standard.Format - YYYY-MM-DD
Mandate end date. Date is formatted string as per ISO 8601 standard.Format - YYYY-MM-DD
Subscription Id provided by gateway
Subscription description
Mandate status
- 200
Successful Response
Schema
Request ID
Error list
data object
data object
Response status code
Response message
trackInfo object
Manufacturer application number
Manufacturer quote ID
Proposal number
Policy number
Receipt number
{
"reqId": "d7fbc496-3634-47b6-ae32-22c4cd6a085f",
"errors": [
{}
],
"data": {
"data": {
"status": "200",
"message": "Success",
"trackInfo": {
"manuApplicationNo": "string",
"manufacturerQuoteID": "string",
"proposalNo": "string",
"policyNumber": null,
"receiptNumber": null
}
}
}
}