Overview
Our Buy Now Pay Later (BNPL) services offer flexible payment options that empower customers to make purchases immediately while paying over time. By removing financial barriers at checkout, merchants can increase conversion rates, boost average order values, and enhance customer loyalty. Our seamless integration delivers a frictionless shopping experience across both online and in-store environments, with simple eligibility checks and transparent terms. This win-win solution helps businesses grow revenue while giving customers the purchasing power they need with manageable payment schedules.
Get Eligible Plans
Instantly shows payment options a customer qualifies for, with personalized terms and rates based on their profile.
Balance Transfer
Moves debt from accounts to your platform, typically offering lower interest rates and consolidated payments.
LoanOnCall QuickCash
Provides instant cash loans to pre-approved customers, with funds deposited directly to their bank accounts.
Financial Posting
Automatically records and reconciles payment transactions across accounting systems, ensuring accurate financial tracking and regulatory compliance with detailed audit trails.
Balance Conversion
Transforms credit purchases into fixed installment plans with structured payment terms.
Financial Posting
Status:
Production
Version:
V2
Product:
Buy Now Pay Later
Overview
This service processes and records all financial transactions related to installment plans. It handles payment allocations, principal and interest calculations, late fee assessments, and updates account balances accordingly. The API ensures accurate financial record-keeping while maintaining detailed transaction histories for reporting and reconciliation.
Status:
Production
Version:
V2
Product:
Buy Now Pay Later
Node | Child Node | Type | Length | Description |
---|---|---|---|---|
Authorization | Bearer xxxx | string | Authorization Header (Bearer Token) | |
Content-Type | application/json | string | Content Type | |
X-Request-ID | a1v2n3dass | string | 12 | Request ID for identification of each request call, maximum 12 characters |
X-Correlation-ID | c3ajh65 | string | 12 | Reference to a particular transaction or event chain, maximum 12 characters |
X-OrgId | NSGB2 | string | Organization/Financial institution ID | |
X-Timestamp | 2023-07-24 | string | Timestamp | |
X-SrcApp | client | string | Source application | |
X-Channel | Bank | string | Request Channel |
Node Type | Type | Length | Description | |||||||
---|---|---|---|---|---|---|---|---|---|---|
NISrvRequest | request_financial_posting | header | msg_id | string | 12 | The msg_id sent in the request will be sent back in response in this field | ||||
msg_type | string | 12 | Message Type – This can have either “TRANSACTION†or “ENQUIRY†As for this API the value expected is “TRANSACTION†| |||||||
msg_function | string | 50 | Static Value - REQ_FINANCIAL_POSTING | |||||||
src_application | string | 10 | Source Application: This is a free Text and the client can populate the source system from where the API is Initiated Example: IVR, IB, MB No Validations of these are kept at Network Systems | |||||||
target_application | string | 10 | The target_application can hold any value from FI side, this can be used by FI to check the target system of the API call | |||||||
timestamp | string | 30 | Timestamp of the request - Format YYYY-MM-DDtHH:MM:SS.SSS+04:00 | |||||||
tracking_id | string | 15 | Transaction Tracking Id | |||||||
bank_id | string | 4 | Bank Id is Unique Id 4 digit code for each client and the same will be provided once the client setup is completed in our core system. For sandbox testing – Please use “NIC†| |||||||
body | card_identifier_id | string | 32 | 454545XXXXXX1234 | ||||||
card_identifier_type | string | 20 | CONTRACT_NUMBER is used for clear card number or EXID which is a unique identifier for the card generated by CMS | |||||||
transaction_type | string | 32 | Transaction Type | |||||||
posting_scope | string | 1 | 'A' or 'C' (A for Account , C for Card) | |||||||
currency | string | 3 | Currency | |||||||
amount | string | 18 | Amount | |||||||
description | string | 255 | Transaction description | |||||||
transaction_ref_number | string | 12 | Transaction reference number | |||||||
transaction_date | string | 20 | Transaction date Format (YYYY-MM-DD HH:mm:ss) |
{
"NISrvRequest": {
"request_financial_posting": {
"header": {
"msg_id": "236001",
"msg_type": "TRANSACTION",
"msg_function": "REQ_FINANCIAL_POSTING",
"src_application": "IVR",
"target_application": "CMS",
"timestamp": "2020-07-20T10:49:02.366+04:00",
"tracking_id": "236001",
"bank_id": "NIC"
},
"body": {
"card_identifier_id": "99984100148297467162",
"card_identifier_type": "EXID/CONTRACT_NUMBER",
"transaction_type": "MC-MF-STMT_FEE",
"posting_scope": "C",
"currency": "AED",
"amount": "900",
"description": "Manual Fee",
"transaction_ref_number": "220518144629",
"transaction_date": "2022-01-15 16:26:36"
}
}
}
}
Node | Child Node | Type | Length | Description | |
---|---|---|---|---|---|
Content-Type | application/json | string | Content Type |
Node Type | Type | Length | Description | |||||||
---|---|---|---|---|---|---|---|---|---|---|
NISrvResponse | response_financial_posting | header | msg_id | string | 12 | Unique Source Message ID eg ada123456fdsf | ||||
msg_type | string | 12 | Message Type – This can have either “TRANSACTION†or “ENQUIRY†As for this API the value expected is “TRANSACTION†| |||||||
msg_function | string | 50 | Default REP_LOANONCALL_QUICKCASH | |||||||
src_application | string | 10 | Source Application: This is a free Text and the client can populate the source system from where the API is Initiated Example: IVR, IB, MB No Validations of these are kept at Network Systems | |||||||
tracking_id | string | 15 | Transaction Tracking Id | |||||||
bank_id | string | 4 | Bank Id is Unique Id 4 digit code for each client and the same will be provided once the client setup is completed in our core system. For sandbox testing – Please use “NIC†| |||||||
exception_details | application_name | string | 20 | Application Name | ||||||
date_time | string | 30 | Timestamp of the response Format “YYYY-MM-DD HH:MM:SS†| |||||||
status | string | 1 | Status of the request (S/F) | |||||||
error_code | string | 4 | EAI Internal Error Code (Check error codes section for the complete list of error codes and error code descriptions) | |||||||
error_description | string | 100 | Error Description (Check error codes section for the complete list of error codes and error code descriptions) | |||||||
transaction_ref_id | string | 20 | The tracking_id sent in the request will be sent back in response in this field. | |||||||
body | card_identifier_id | string | 32 | 454545XXXXXX1234 | ||||||
card_identifier_type | string | 20 | CONTRACT_NUMBER is used for clear card number or EXID which is a unique identifier for the card generated by CMS | |||||||
response_code | string | 4 | Response code | |||||||
status | string | 1 | Status of the request (S/F) Success- S, Failure - F | |||||||
transaction_ref_number | string | 12 | Transaction reference number |
{
"NISrvResponse": {
"response_financial_posting": {
"header": {
"msg_id": "236001",
"msg_type": "TRANSACTION",
"msg_function": "REP_LOANONCALL_QUICKCASH",
"src_application": "IVR",
"tracking_id": "236001",
"bank_id": "NIC"
},
"exception_details": {
"application_name": "TCC-ADP",
"date_time": "2023-02-01T16:39:47.314+04:00",
"status": "S",
"error_code": "000",
"error_description": "Success",
"transaction_ref_id": "236001"
},
"body": {
"card_identifier_id": "99984100148297467162",
"card_identifier_type": "EXID\/CONTRACT_NUMBER",
"response_code": "000",
"status": "S",
"transaction_ref_number": "220518144629"
}
}
}
}
Code | Description |
---|---|
200 | Sample Description |
400 | Bad Request |
401 | Unauthorized |
403 | Forbidden |
500 | Internal Server Error |
502 | Bad gateway |
503 | Scheduled Maintenance |
504 | Gateway Timeout |
596 | Service Not Found |