Buy Now Pay Later

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

Get Eligible Transactions

Status:

Production

Version:

V2

Category:

Buy Now Pay Later

Overview

 

This API retrieves a list of transactions that qualify for conversion into an installment plan. The eligibility of each transaction is determined based on specific criteria, such as transaction amount, type, and the time frame within which it occurred. This allows users to view which of their past purchases are eligible for installment payments, providing flexibility in managing payments. The API returns details for each transaction, including its ID, amount, and date. This functionality is useful for users looking to convert larger purchases into manageable installments.

How It Works

 

When offering installment plans to your customers, you have the option to apply them to specific transactions, an eligible balance, or both. To offer this feature on a per-transaction basis, you can use this API to first retrieve a list of transactions that qualify for conversion. Afterward, the client can select the transaction they wish to convert and then use the next API to complete the refinancing process.

https://api-sandbox.network.global

Get Eligible Transactions

Status:

Production

Version:

V2

Category:

Buy Now Pay Later
/BnplServices/Enquiry/V2/GetCardTransactions
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

Node TypeTypeLengthDescription
NISrvRequestrequest_get_card_transactionsheadermsg_id* requiredstring12Message ID, this field should be unique id for each Api call. This will be generated from client side. If the same message ID is used the system will decline the API call with Error Description “Duplicate Message ID”
msg_type* requiredstring12Message Type – This can have either “TRANSACTION” or “ENQUIRY” As for this API the value expected is “ENQUIRY”
msg_function* requiredstring50Message functions: Should be “REQ_GET_CARD_TRANSACTIONS”
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 response Date & time Format DD/MM/YYYY HH:MM:SS
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”
instance_idstring10instance_id
bodycard_identifier_id* requiredstring32Card Identifier
card_identifier_type* requiredstring20CONTRACT_NUMBER is used for clear card number or EXID which is a unique identifier for the card generated by CMS
plan_numberstring

{
    "NISrvRequest": {
        "request_get_card_transactions": {
            "header": {
                "msg_id": "236001",
                "msg_type": "ENQUIRY",
                "msg_function": "REQ_GET_CARD_TRANSACTIONS",
                "src_application": "IVR",
                "target_application": "WAY4",
                "timestamp": "2020-07-20T10:49:02.366+0:00",
                "tracking_id": "236001",
                "bank_id": "NIC",
                "instance_id": "236001"
            },
            "body": {
                "card_identifier_id": "454545XXXXXX1234",
                "card_identifier_type": "EXID",
                "plan_number": "00166"
            }
        }
    }
}

Node Child Node Type Length Description
Content-Typeapplication/jsonstringContent Type

Node TypeTypeLengthDescription
NISrvResponseresponse_get_card_transactionsheadermsg_id* requiredstring12Message ID, this field should be unique id for each Api call. This will be generated from client side. If the same message ID is used the system will decline the API call with Error Description “Duplicate Message ID”
msg_type* requiredstring12Message Type – This can have either “TRANSACTION” or “ENQUIRY” As for this API the value expected is “ENQUIRY”
msg_function* requiredstring50Message functions: Should be “REP_GET_CARD_TRANSACTIONS”
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 response Date & time Format DD/MM/YYYY HH:MM:SS
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.
bodynumberOfTransactionsstring3Number of transactions
transactioncard_identifier_type* requiredstring20CONTRACT_NUMBER is used for clear card number or EXID which is a unique identifier for the card generated by CMS
card_identifier_id* requiredstring32card_identifier_id
masked_pan* requiredstring16Pan in Masked form
trans_date* requiredstring10Transaction date & the format is DD/MM/YYYY
post_date* requiredstring10Posting date & the format is DD/MM/YYYY
debit_credit_flag* requiredstring1Type of direction
response_code* requiredstring3Return code
description* requiredstring255Transaction description
transaction_ref_number* requiredstring12Transaction reference number
currency* requiredstring3Currency code Ex: AED
amount* requiredstring20Amount
source_currency* requiredstring3Transaction Currency
source_amount* requiredstring20Transaction amount
auth_codestring32Authorization code
merchant_idstring32Merchant ID number
merchant_category_codestring4SIC
merchant_namestring64Merchant Name
merchant_addressstring64Merchant Address
merchant_citystring64Merchant City
merchant_countrystring64Merchant Country
merchant_category_groupstring20Category Group
trans_idstring20Transaction Id
balance_typestring20RETAIL

{
    "NISrvResponse": {
        "response_get_card_transactions": {
            "header": {
                "msg_id": "236001",
                "msg_type": "ENQUIRY",
                "msg_function": "REP_GET_CARD_TRANSACTIONS",
                "src_application": "IVR",
                "target_application": "WAY4",
                "timestamp": "2020-07-20T10:49:02.366+04:00",
                "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": {
                "numberOfTransactions": "019",
                "transaction": {
                    "card_identifier_type": "EXID",
                    "card_identifier_id": "454545XXXXXX1234",
                    "masked_pan": "454545XXXXXX1234",
                    "trans_date": "01\/12\/2022",
                    "post_date": "04\/12\/2022",
                    "debit_credit_flag": "D",
                    "response_code": "00",
                    "description": "",
                    "transaction_ref_number": "00",
                    "currency": "AED",
                    "amount": "210.00",
                    "source_currency": "AED",
                    "source_amount": "210.00",
                    "auth_code": "",
                    "merchant_id": "",
                    "merchant_category_code": "",
                    "merchant_name": "",
                    "merchant_address": "",
                    "merchant_city": "",
                    "merchant_country": "",
                    "merchant_category_group": "",
                    "trans_id": "",
                    "balance_type": ""
                }
            }
        }
    }
}

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.

1- Process 1

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Amet, sed at amet cras fringilla adipiscing nunc, in pulvinar. Sagittis pellentesque leo et proin convallis justo vitae in.

2- Process 1

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Amet, sed at amet cras fringilla adipiscing nunc, in pulvinar. Sagittis pellentesque leo et proin convallis justo vitae in.

3- Process 1

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Amet, sed at amet cras fringilla adipiscing nunc, in pulvinar. Sagittis pellentesque leo et proin convallis justo vitae in.

4- Process 1

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Amet, sed at amet cras fringilla adipiscing nunc, in pulvinar. Sagittis pellentesque leo et proin convallis justo vitae in.

5- Process 1

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Amet, sed at amet cras fringilla adipiscing nunc, in pulvinar. Sagittis pellentesque leo et proin convallis justo vitae in.