Buy Now Pay Later

Overview

Our Buy Now Pay Later services provide an easy and flexible payment option for your customers, allowing them to make purchases now and pay for them at a later date. This can help to increase sales by making it easier for customers to make larger purchases, or to buy more frequently.

Our Buy Now Pay Later services also include the ability to set up recurring payments, which can help to increase customer loyalty by making it easy for customers to make regular payments for their purchases. Our platform also allows customers to track and manage their payments, which can help to improve their experience and satisfaction.

Version

Financial Posting

Status:

Production

Version:

V2

Category:

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.

https://api-sandbox.network.global

Financial Posting

Status:

Production

Version:

V2

Category:

Buy Now Pay Later
/BnplServices/Transaction/V2/FinancialPosting
curl --location --request POST '#{PARAM_URL}' --header 'Authorization: Bearer {{ access_token }}' {custom_headers} --data-raw '#{JSON_PAYLOAD}'
curl --location --request GET 'https://api-sandbox.network.global/v1/tokenkc/generate' \--data-raw '#{JSON_PAYLOAD}'
curl --location --request POST 'https://api-sandbox.network.global/v1/tokenkc/generate' \--data-raw '#{JSON_PAYLOAD}'

Node Child Node Type Length Description
Authorization* requiredBearer xxxx* requiredstringAuthorization Header (Bearer Token)
Content-Type* requiredapplication/json* requiredstringContent Type
X-Request-ID* requireda1v2n3dass* requiredstring12Request ID for identification of each request call, maximum 12 characters
X-Correlation-IDc3ajh65string12Reference to a particular transaction or event chain, maximum 12 characters
X-OrgId* requiredNSGB2* requiredstringOrganization/Financial institution ID
X-Timestamp2023-07-24stringTimestamp
X-SrcAppclientstringSource application
X-ChannelBankstringRequest Channel

Node TypeTypeLengthDescription
NISrvRequestrequest_financial_postingheadermsg_id* requiredstring12The msg_id sent in the request will be sent back in response in this field
msg_type* requiredstring12Message Type – This can have either “TRANSACTION†or “ENQUIRY†As for this API the value expected is “TRANSACTIONâ€
msg_function* requiredstring50Static Value - REQ_FINANCIAL_POSTING
src_application* requiredstring10Source 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* requiredstring10The 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* requiredstring30Timestamp of the request - Format YYYY-MM-DDtHH:MM:SS.SSS+04:00
tracking_idstring15Transaction Tracking Id
bank_id* requiredstring4Bank 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â€
bodycard_identifier_id* requiredstring32454545XXXXXX1234
card_identifier_type* requiredstring20CONTRACT_NUMBER is used for clear card number or EXID which is a unique identifier for the card generated by CMS
transaction_type* requiredstring32Transaction Type
posting_scopestring1'A' or 'C' (A for Account , C for Card)
currency* requiredstring3Currency
amount* requiredstring18Amount
descriptionstring255Transaction description
transaction_ref_number* requiredstring12Transaction reference number
transaction_datestring20Transaction 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-Typeapplication/jsonstringContent Type

Node TypeTypeLengthDescription
NISrvResponseresponse_financial_postingheadermsg_id* requiredstring12Unique Source Message ID eg ada123456fdsf
msg_type* requiredstring12Message Type – This can have either “TRANSACTION†or “ENQUIRY†As for this API the value expected is “TRANSACTIONâ€
msg_function* requiredstring50Default REP_LOANONCALL_QUICKCASH
src_application* requiredstring10Source 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_idstring15Transaction Tracking Id
bank_id* requiredstring4Bank 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_detailsapplication_name* requiredstring20Application Name
date_time* requiredstring30Timestamp of the response Format “YYYY-MM-DD HH:MM:SSâ€
status* requiredstring1Status of the request (S/F)
error_code* requiredstring4EAI Internal Error Code (Check error codes section for the complete list of error codes and error code descriptions)
error_description* requiredstring100Error Description (Check error codes section for the complete list of error codes and error code descriptions)
transaction_ref_idstring20The tracking_id sent in the request will be sent back in response in this field.
bodycard_identifier_id* requiredstring32454545XXXXXX1234
card_identifier_type* requiredstring20CONTRACT_NUMBER is used for clear card number or EXID which is a unique identifier for the card generated by CMS
response_codestring4Response code
statusstring1Status of the request (S/F) Success- S, Failure - F
transaction_ref_numberstring12Transaction 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
200Sample Description
400Bad Request
401Unauthorized
403Forbidden
500Internal Server Error
502Bad gateway
503Scheduled Maintenance
504Gateway Timeout
596Service Not Found

How It Works

Follow the steps below. For more details, read the Quick Start Guide.