Debit Solutions

Overview

Our one-stop, centralised solution for Debit Card processing is designed to provide you with a seamless and secure payment experience. Whether you are a small business or a large enterprise, our solution is cost-effective, easily configurable and scalable to meet your specific needs.

With our Debit Card processing solution, you can easily accept payments from your customers and enjoy faster access to your funds. Our platform supports all major debit card networks, so you can accept payments from customers regardless of their bank.

Activate Debit cards

Users can activate debit cards when they are first issued or after they have been deactivated for any reason.

Check card balances

Users can check the balance on a debit card in real-time or on a scheduled basis.

View transaction history

Users can view a detailed record of all transactions made with a debit card, including the date, time, amount, and location of each transaction.

Reload cards

Users can add funds to a debit card, either by transferring money from another account or by purchasing a reload card.

Resolve disputes

Users can access a process for resolving disputes or issues that may arise with debit card transactions.

Protect against fraud

Users can access measures to detect and prevent fraudulent activity on debit cards, such as monitoring for suspicious activity or requiring additional authentication for certain transactions.

Manage card accounts

Users can view and manage their debit card accounts, including the ability to set spending limits, view transaction history, and update personal information.

Download

Client Create(Post)

This API is used to create a new cardholder within a financial institution. It can be used to register a new customer and issue them with a card.

Account Create(Post)

The Account Create API allows for the creation of new customer accounts. Parameters include customer ID, card type, branch code, Product code, currency, and custom fields.

Card Create(Post)

A card creation API in a payment processing company allows users to add a credit or debit card to their account on the payment platform.

Card Activate(Post)

This API is used for activating newly issued cards or ones that have been renewed. Enables transactions on a new or replaced card by activating it.

Card Set Pin(Post)

This API enables the setting of a personal identification number (PIN) for a specific card, which can then be used for point of sale or ATM transactions.

Card Pin Verification(Post)

This API is used to check if a PIN provided by the cardholder matches the one associated with the card, in order to confirm the identity of the cardholder.

Card Pin Change(Post)

This API allows a cardholder to change their PIN by verifying their current PIN and setting a new one. The new PIN will be used for Point of Sales or ATM transactions.

Pin Tries Counter Reset(Post)

This API allows to reset the number of attempts a user has made to enter the correct PIN, in case the user has entered the incorrect PIN multiple times.

Get CVV2(Post)

This API allows consumers to retrieve the CVV2 (Card Verification Value 2) for a specific card.

Lookup Card Identifier(Post)

This API allows you to obtain an alternative identifier for a given card by using its identifier as input, the API will then return a different type of identifier such as tokenized card identifier.

Cards List(Post)

This API obtains a comprehensive listing of all the cards linked to a specific cardholder, including prepaid, credit, and debit cards.

Accounts List(Post)

The List of Accounts API is a useful tool for payment processing companies that offer a range of financial products, such as credit cards, debit cards, and bank accounts. This API allows customers to easily view a list of all their accounts with the payment processing company, providing a convenient way to manage their finances and keep track of their spending.

Card Details Enquiry(Post)

This API is used to retrieve information about a specific card such as the primary account number, the product the card is associated with, the status of the card, and any balances associated with the card.

Customer Details(Post)

A customer details enquiry API allows a payment processing company to retrieve information about a customer's account. This could be used, for example, by a merchant to get information about a customer's billing address or by a customer service representative to verify account details.

Card Transaction(Post)

This API posts a financial transactions on card or account by debiting or crediting the account balance with provided amount and currency.

Card Statement Summary(Post)

This API is used to Retrieve past transactions made using a specific card.

Card Status Change(Post)

This API is used to change the status of a card or account, such as blocking or unblocking it. It is used primarily for security purposes.

Get Card Transactions(Post)

This API is used to Retrieve past transactions made using a specific card.

Card Replacement(Post)

This API is used to request a new card to replace a lost, stolen, damaged, or expired card.

Client Update(Post)

A client update API in a payment processing company allows users to update information for an existing client account in the payment processing system.

Account Update(Post)

This API allows for the updating of an existing account for a cardholder.

Card Update(Post)

The API facilitates the modification of an existing card associated with a specific account and cardholder.

Get Limits(Post)

This API allows customers to easily view a summary of their limit usage, providing a convenient way to keep track of their spending and manage their finances.

Card Balance Enquiry(Post)

Obtains information about the card's available funds and balances related to the product type.

Switch Restrictions(Post)

This API allows customers to seamlessly switch restrictions on their credit or debit cards, helping them to make decisions about their spending.

Update Limits(Post)

This API enables customers to quickly and easily view any limits on their credit or debit cards, helping them to make informed decisions about their spending.

Get Companies(Post)

This API enables customers to Get the details of the companies

Get Restrictions(Post)

This API enables customers to quickly and easily view any restrictions on their credit or debit cards, helping them to make informed decisions about their spending.

Bulk Card Create(Post)

Bulk card create can generate a pool of no-name plastic cards ready for instant issuance.

Bulk List Of Cards(Post)

Bulk list of cards can be used to check the status of bulk card create requests or to access the list of pre-embossed cards.

Bulk Card Summary(Post)

Bulk card summary can be used to check summary of the cards available in stock.

Bulk Move Cards(Post)

Bulk move cards can be used to move card/list of cards or batches from one client to another.

OnlineEmbossing(Post)

This API is used to immediately send a request for card embossing.

Card Direct Debit(Post)

This API retrieves direct debit details of specific account details.

Card Direct Debit Update(Post)

This API receives updates on direct debit details of specific accounts used by the bank.

P2P Transfer(Post)

This API facilitates debiting from the "source identifier" and crediting to the "target identifier" for the requested amount within the same financial institution.

Account Transaction(Post)

This API retrieves all accounts within a commercial or multi-currency hierarchy under a specific client ID or account number.

Account Status Change(Post)

This API updates block codes on the account level for an account identifier.

Switch MCC(Post)

This API enables or disables MCC groups/codes for a card.

Release Pending Authorization(Post)

This API cancels pending authorizations. It will only search for pending authorizations.

Get MCC Controls(Post)

This API retrieves all blocked and/or allowed MCC groups and codes.

Account Balance Enquiry(Post)

The Account Balance API receives balance details of account numbers.

Account Hierarchy Enquiry(Post)

This API retrieves all accounts within a commercial or multi-currency hierarchy under a specific client ID or account number.

Get Account Transactions(Post)

This API pulls transactions which are authorized, time_based/posted, or statemented to account.

Get Dictionaries MCC(Post)

This API retrieves all blocked and/or allowed MCC groups and codes.

Set FXRates(Post)

This service is used by an FI to set FX rates for a currency.

Get FXRates(Post)

This service is used by an FI to get FX rates for a currency.

Account Transfer(Post)

This API is used to transfer account and its sub accounts and cards from one product to another.

Get Eligible Transactions(Post)

This API retrieves a list of transactions that qualify for conversion into an installment plan.

Refinance Transaction(Post)

This API allows the conversion of a specific transaction into an installment plan.

Get Plan List(Post)

This API allows fetching the list of active instalment plans.

Get Plan Details ById(Post)

This API allows fetching all the details related to active instalment plan.

Card Contact Details(Post)

This API allows fetching the customer contact details.

Get Card Transactions

Status:

Production

Version:

V2

Product:

Credit Solutions

Get Card Transactions

Overview

This API allows developers to retrieve transaction history for a specific card. It requires one of the supported card identifier as an input and returns all transaction details within a specified date range. The API connects to the card issuer's management system and retrieves the transaction history for the provided card number. The returned information includes details such as transaction amount, merchant name, and transaction date. API has capability to list posted transactions, authorized transactions or statement transactions.

Transaction history retrieval

The primary feature of this API is its ability to retrieve transaction history for a specific card. It allows developers to easily access a cardholder's transaction history within a specified date range, providing them with the information they need to display the transaction history to the customer or for internal purposes.

Date range filtering

The API allows developers to specify a date range when retrieving transaction history, providing them with a more targeted and relevant set of information. This feature is particularly useful for businesses that need to monitor transaction activity over a specific period of time.

Secure data transfer

The API uses standard HTTP protocols to receive the request and return the response and it also uses the necessary authentication credentials such as an API key, which provides an additional layer of security to protect the cardholder's information.

How It Works

A developer makes a request to the API endpoint, including the necessary details such as the card number and the date range in the request body. The API receives the request and processes it by connecting to the card issuer's management system using the provided card number as the identifier. The API then retrieves the transaction history for the provided card number and date range. The API generates a response containing the transaction details in a JSON format The developer receives the response and can then use the information to display the transaction history to the customer or for internal purposes.

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.

Node	Child Node	Type	Length	Description
Authorization* required	Bearer xxxx* required	string		Authorization Header (Bearer Token)
Content-Type* required	application/json* required	string		Content Type

Node Type				Type	Length	Description
NISrvRequest	request_get_card_transactions	header	msg_id* required	string	12	Message 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* required	string	12	Message Type – This can have either “TRANSACTION” or “ENQUIRY” As for this API the value expected is “TRANSACTION”
			msg_function* required	string	50	Message functions: Should be “REQ_GET_CARD_TRANSACTIONS”
			src_application* required	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* required	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* required	string	30	Timestamp of the request - Format YYYY-MM-DDtHH:MM:SS.SSS+04:00
			bank_id* required	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* required	string	32	Card Identifier
			card_identifier_type* required	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* required	string	16	authorized, time_based/posted, statemented
			date_from	string	10	Format DD/MM/YYYY. Maximum interval is 90days. Conditional for posted.
			date_to	string	10	Format DD/MM/YYYY. Maximum interval is 90days.Conditional for posted
			statement_period	string	4	Format YYMM (Maximum statement is 12 months from the current date).
			no_of_transactions_requested	string	2	Maximum number of transactions to be fetched in a request. Value should be between 1 and 99 default is 50
			requested_page_no	string	4	Page number of the current request, could be from 1 to 99.
			return_mcc_group	string	4	To retrun MCC group
			condition_filter	string	255	Filter for Aggregate transactions

{"NISrvRequest":{"request_get_card_transactions":{"header":{"msg_id":"58965","msg_type":"ENQUIRY","msg_function":"REQ_GET_CARD_TRANSACTIONS","src_application":"BNK","target_application":"WAY4","timestamp":"2024-03-19T14:52:37.534+04:00","bank_id":"NIC"},"body":{"card_identifier_id":"99984100111514120378","card_identifier_type":"EXID","transaction_type":"authorized","date_from":"01\/01\/2024","date_to":"31\/12\/2026","statement_period":""}}}}

{
    "NISrvRequest": {
        "request_get_card_transactions": {
            "header": {
                "msg_id": "58965",
                "msg_type": "ENQUIRY",
                "msg_function": "REQ_GET_CARD_TRANSACTIONS",
                "src_application": "BNK",
                "target_application": "WAY4",
                "timestamp": "2024-03-19T14:52:37.534+04:00",
                "bank_id": "NIC"
            },
            "body": {
                "card_identifier_id": "99984100111514120378",
                "card_identifier_type": "EXID",
                "transaction_type": "authorized",
                "date_from": "01/01/2024",
                "date_to": "31/12/2026",
                "statement_period": ""
            }
        }
    }
}

Node	Child Node		Type	Length	Description
Content-Type	application/json		string		Content Type

Node Type					Type	Length	Description
NISrvResponse	response_get_card_transactions	header	msg_id* required		string	12	Message 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* required		string	12	Message Type – This can have either “TRANSACTION” or “ENQUIRY” As for this API the value expected is “ENQUIRY”
			msg_function* required		string	50	Message functions: Should be “REP_GET_CARD_TRANSACTIONS”
			src_application* required		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* required		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* required		string	30	Timestamp of the response Date & time Format DD/MM/YYYY HH:MM:SS
			bank_id* required		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* required		string	20	Application Name
			date_time* required		string	30	Timestamp of the response Format “YYYY-MM-DD HH:MM:SS”
			status* required		string	1	Status of the request (S/F)
			error_code* required		string	4	EAI Internal Error Code (Check error codes section for the complete list of error codes and error code descriptions)
			error_description* required		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* required		string	32	card identifier
			card_identifier_type* required		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* required		string	16	Type of the card transaction the expected values are - authorized, time_based/posted, statemented
			date_from		string	10	Format YYYY-MM-DD Conditional for posted
			date_to		string	10	Format YYYY-MM-DD Conditional for posted
			statement_period		string	4	Format YYMM Conditional Mandatory for statemented
			no_of_transactions_returned* required		string	3	Number of transactions
			no_of_transactions_requested		string	2	Maximum number of transactions to be fetched in a request. Value should be between 1 and 99 default is 50
			requested_page_no		string	4	Page number of the current request, could be from 1 to 99.
			total_no_of_pages		string	2	Total number of requests
			condition_filter		string	255	Condition_filter sent in request
			transaction	card_identifier_type* required	string	20	CONTRACT_NUMBER is used for clear card number or EXID which is a unique identifier for the card generated by CMS
				card_identifier_id* required	string	32	card_identifier_id
				masked_pan* required	string	16	Pan in Masked form
				trans_date* required	string	10	Transaction date & the format is DD/MM/YYYY
				post_date* required	string	10	Posting date & the format is DD/MM/YYYY
				debit_credit_flag* required	string	1	Type of direction
				response_code* required	string	3	Return code
				description* required	string	255	Transaction description
				transaction_ref_number* required	string	12	Transaction reference number
				currency* required	string	3	Currency code Ex: AED
				amount* required	string	20	Amount
				source_currency* required	string	3	Transaction Currency
				source_amount* required	string	20	Transaction amount
				auth_code	string	32	Authorization code
				merchant_id	string	32	Merchant ID number
				merchant_category_code	string	4	SIC
				merchant_name	string	64	Merchant Name
				merchant_city	string	64	Merchant City
				merchant_country	string	64	Merchant Country
				transaction_code	string	32	Transaction code
				merchant_category_group	string	20	Category Group
				trans_id	string	20	Transaction Id
				balance_type	string	20	RETAIL
				loyalty_code	string	32	Loyalty Code
				loyalty_amount	string	32	Loyalty amount
				loyalty_currency	string	32	Loyalty currency
				labels	string	32	Labels
				transaction_category	string	32	Transaction Category
				original_contract	string	32	Original Contract

{"NISrvResponse":{"response_get_card_transactions":{"header":{"msg_id":"58965","msg_type":"ENQUIRY","msg_function":"REP_GET_CARD_TRANSACTIONS","src_application":"BNK","target_application":"WAY4","timestamp":"2024-03-19T14:58:30.054+04:00","bank_id":"NIC"},"exception_details":{"application_name":"TCC-ADP","date_time":"2024-03-19T14:58:30.054+04:00","status":"S","error_code":"000","error_description":"Success"},"body":{"card_identifier_id":"99984100111514120378","card_identifier_type":"EXID","transaction_type":"authorized","date_from":"01\/01\/2024","date_to":"31\/12\/2026","statement_period":"","no_of_transactions_returned":"1","no_of_transactions_requested":"50","requested_page_no":"1","transactions":[{"card_identifier_id":"99984100111514120378","card_identifier_type":"EXID","masked_pan":"999841XXXXXX5605","trans_date":"2024-03-19 14:56:05","post_date":"","debit_credit_flag":"C","response_code":"0","description":"Payment To Client Contract   Demo Manual Payment Transaction","transaction_ref_number":"492855564032","currency":"AED","amount":"-66.0","source_currency":"AED","source_amount":"66.0","auth_code":"448584","merchant_name":"Demo Manual Payment Transaction","transaction_code":"","trans_id":"10812"}]}}}}

{
    "NISrvResponse": {
        "response_get_card_transactions": {
            "header": {
                "msg_id": "58965",
                "msg_type": "ENQUIRY",
                "msg_function": "REP_GET_CARD_TRANSACTIONS",
                "src_application": "BNK",
                "target_application": "WAY4",
                "timestamp": "2024-03-19T14:58:30.054+04:00",
                "bank_id": "NIC"
            },
            "exception_details": {
                "application_name": "TCC-ADP",
                "date_time": "2024-03-19T14:58:30.054+04:00",
                "status": "S",
                "error_code": "000",
                "error_description": "Success"
            },
            "body": {
                "card_identifier_id": "99984100111514120378",
                "card_identifier_type": "EXID",
                "transaction_type": "authorized",
                "date_from": "01\/01\/2024",
                "date_to": "31\/12\/2026",
                "statement_period": "",
                "no_of_transactions_returned": "1",
                "no_of_transactions_requested": "50",
                "requested_page_no": "1",
                "transactions": [
                    {
                        "card_identifier_id": "99984100111514120378",
                        "card_identifier_type": "EXID",
                        "masked_pan": "999841XXXXXX5605",
                        "trans_date": "2024-03-19 14:56:05",
                        "post_date": "",
                        "debit_credit_flag": "C",
                        "response_code": "0",
                        "description": "Payment To Client Contract   Demo Manual Payment Transaction",
                        "transaction_ref_number": "492855564032",
                        "currency": "AED",
                        "amount": "-66.0",
                        "source_currency": "AED",
                        "source_amount": "66.0",
                        "auth_code": "448584",
                        "merchant_name": "Demo Manual Payment Transaction",
                        "transaction_code": "",
                        "trans_id": "10812"
                    }
                ]
            }
        }
    }
}

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