Transactions

Transactions

Overview

Our user transaction services also include a wide range of payment options, such as credit and debit cards, e-wallets, and bank transfers, which allows you to choose the most convenient payment method for you. Our platform also supports multiple currencies, which allows you to make international transactions with ease.

We also provide added security features, such as multi-factor authentication, to ensure that your transactions are protected from fraud. Our user transaction services are also fully compliant with all local and international regulations, such as PCI DSS, which ensures that your transactions are processed in a secure and compliant manner.

Version

Card Transaction

Status:

Production

Version:

V2

Category:

Transactions

Card Transaction

Overview

This API is designed to record financial transactions on a card or account level. It accepts an account or card identifier as an input, along with the transaction type, amount, and currency. Once the API receives this information, it will post the transaction, which could be a debit or credit to the account balance. This feature enables businesses to charge fees, process payments, or top up prepaid accounts. The API can also be used to monitor and track transaction activity for accounting and compliance purposes.

Real-time updates

The API updates account balances in real-time, providing immediate confirmation of the transaction to the cardholder.

Support for various types of financial transactions

The API allows for various types of financial transactions, including manual fee charging, credit card payments, and prepaid top-ups.

Input validation:

The API includes input validation to ensure that all provided information is accurate and in the correct format before processing the transaction.

How It Works

The API allows for processing of financial transactions by accepting inputs such as an account or card identifier, transaction type, amount and currency. These inputs are validated to ensure their validity, including the card or account identifier, the supported transaction type, and the correct format of the amount and currency provided.

Once the input validation is successful, the API will process the transaction and update the account balance accordingly, based on whether it is a debit or credit transaction. For instance, a credit card payment will result in a debit of the specified amount from the cardholder's account balance, while a prepaid top-up will result in a credit to the cardholder's account balance.

The API will then return a response including transaction details such as a unique transaction identifier, status, and any other relevant details. It is important to note that this API is only applicable for transactions where the card issuer or financial institution holds the account balance, and is not intended for use with external wallets or store of value.

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.

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.

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.

https://api-sandbox.network.global

Card Transaction

Download

Status:

Production

Version:

V2

Category:

Transactions
/SB/CardServices/Transaction/V2/CardTransaction
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_card_transactionheadermsg_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 “TRANSACTION”
msg_function* requiredstring50Static Value - REQ_CARD_TRANSACTION
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
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* 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
transactiontransaction_code* requiredstring32Transaction code For Payment- PAYCC For Reversal- PAYACC-REV For Debit- DEBITCC For Debit Reversal- DEBITCC-REV
amount* requiredstring20Amount
currency* requiredstring3Currency
descriptionstring255Transaction description
counter_party_numberstring20Source Number
transaction_ref_numberstring12Transaction reference number
custom_fieldskeystring32Custom Tag
valuestring128Tag value

{
    "NISrvRequest": {
        "request_card_transaction": {
            "header": {
                "msg_id": "89658",
                "msg_type": "TRANSACTION",
                "msg_function": "REQ_CARD_TRANSACTION",
                "src_application": "BNK",
                "target_application": "WAY4",
                "timestamp": "2024-03-19T14:55:18.587+04:00",
                "bank_id": "NIC"
            },
            "body": {
                "card_identifier_id": "99984100111514120378",
                "card_identifier_type": "EXID",
                "wallet_id": "",
                "transaction": {
                    "transaction_code": "PAYACC",
                    "amount": "66.00",
                    "currency": "AED",
                    "description": "Demo Manual Payment Transaction",
                    "counter_party_number": "999851",
                    "transaction_ref_number": "58986"
                }
            }
        }
    }
}

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

Node TypeTypeLengthDescription
NISrvResponseresponse_card_transactionheadermsg_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 RES_CARD_TRANSACTION
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* requiredstring15Timestamp of the response - Format YYYY-MM-DDtHH:MM:SS.SSS+04:00
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_code* requiredstring
status* requiredstring1Status of the request

{
    "NISrvResponse": {
        "response_card_transaction": {
            "header": {
                "msg_id": "89658",
                "msg_type": "TRANSACTION",
                "msg_function": "REP_CARD_TRANSACTION",
                "src_application": "BNK",
                "target_application": "WAY4",
                "timestamp": "2024-03-19T14:56:14.784+04:00",
                "bank_id": "NIC"
            },
            "exception_details": {
                "application_name": "TCC-ADP",
                "date_time": "2024-03-19T14:56:14.784+04:00",
                "status": "S",
                "error_code": "000",
                "error_description": "Success"
            },
            "body": {
                "card_identifier_id": "99984100111514120378",
                "card_identifier_type": "EXID",
                "response_code": "0",
                "status": "Waiting"
            }
        }
    }
}

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.