Debit Solutions
Overview
Our centralized solution for Debit Card services allows users to access and use debit cards seamlessly within the payment processing system. Debit cards are linked directly to a user’s bank account, enabling secure purchases and cash withdrawals at locations that accept the card. Users of debit card services in a payment processing company can typically:
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 (if applicable for certain debit/prepaid hybrid models), 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.
Balance Transfer
Status:
Production
Version:
V2
Product:
Debit Solutions
Balance Transfer
Overview
This API allows you to effortlessly transfer funds between accounts. Customize your transfer using optional parameters and receive instant feedback on your transaction.
Streamlined transfer process
The API simplifies the fund transfer process, making it easy for users to transfer funds without any hassle.
Customizable options
Users can tailor their transfers according to their specific needs by utilizing the API's optional parameters.
Detailed transaction feedback
Users receive instant feedback regarding the success or failure of their transactions, ensuring transparency and peace of mind.
How It Works
The Balance Transfer API facilitates fund transfers between accounts using various parameters, including currency, amount, and a brief description of the transfer. A unique reference number and plan number are also included. The API also provides optional parameters, such as interest rates, fees, grace periods, and allocation amounts. Once the parameters are set, the API executes the transfer between the source and destination accounts and returns a response indicating the success or failure of the transaction.
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.
Status:
Production
Version:
V2
Product:
Debit Solutions
| Node | Child Node | Type | Length | Description |
|---|---|---|---|---|
| Authorization | Bearer xxxx | string | Authorization Header (Bearer Token) | |
| Content-Type | application/json | string | Content Type |
| Node Type | Type | Length | Description | |||||||
|---|---|---|---|---|---|---|---|---|---|---|
| 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 | Request Type Default TRANSACTION | |||||||
| msg_function | string | 50 | Function name to be used Default REQ_BALANCE_TRANSFER | |||||||
| src_application | string | 10 | Source requesting channel Ex IVR | |||||||
| target_application | string | 10 | Target application name Ex PCMS | |||||||
| timestamp | string | 30 | Timestamp of the request Format DD/MM/YYYY HH:MM:SS | |||||||
| bank_id | string | 4 | Source Bank Id Ex bankID | |||||||
| instance_id | string | 10 | InstanceID | |||||||
| body | currency | string | ||||||||
| amount | string | |||||||||
| description | string | |||||||||
| transaction_ref_number | string | |||||||||
| plan_number | string | |||||||||
| override_options | number_of_portions | string | ||||||||
| interest_rate | string | |||||||||
| fee_waive | string | |||||||||
| ad-hoc_fee_type | string | |||||||||
| ad-hoc_fee | string | |||||||||
| grace_period | string | |||||||||
| free_period_number | string | |||||||||
| portion_amount | string | |||||||||
| allocate_interest_amount | string | |||||||||
{
"NISrvResponse": {
"request_balance_transfer": {
"header": {
"msg_id": "236001",
"msg_type": "TRANSACTION",
"msg_function": "REQ_BALANCE_TRANSFER",
"src_application": "IVR",
"target_application": "CMS",
"timestamp": "2020-07-20T10:49:02.366+04:00",
"bank_id": "NIC",
"instance_id": "InstanceID"
},
"body": {
"currency": "AED",
"amount": "3000.00",
"description": "Balance Transfer 270620221110",
"transaction_ref_number": "11100521",
"plan_number": "00166",
"override_options": {
"number_of_portions": "",
"interest_rate": "10",
"fee_waive": "N",
"ad-hoc_fee_type": "F",
"ad-hoc_fee": "20",
"grace_period": "1",
"free_period_number": "1",
"portion_amount": "40000",
"allocate_interest_amount": "1000"
}
}
}
}
}
| Node | Child Node | Type | Length | Description | ||||
|---|---|---|---|---|---|---|---|---|
| Content-Type | application/json | string | Content Type | |||||
| Node Type | Type | Length | Description | |||||||
|---|---|---|---|---|---|---|---|---|---|---|
| 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 | Request Type Default TRANSACTION | |||||||
| msg_function | string | 50 | Function name to be used Default RES_BALANCE_TRANSFER | |||||||
| src_application | string | 10 | Source requesting channel Ex IVR | |||||||
| target_application | string | 10 | Target application name Ex PCMS | |||||||
| timestamp | string | 30 | Timestamp of the request Format DD/MM/YYYY HH:MM:SS | |||||||
| bank_id | string | 4 | Source Bank Id Ex bankID | |||||||
| instance_id | string | 10 | InstanceID | |||||||
| exception_details | ||||||||||
{
"NISrvResponse": {
"response_balance_transfer": {
"header": {
"msg_id": "236001",
"msg_type": "TRANSACTION",
"msg_function": "RES_BALANCE_TRANSFER",
"src_application": "IVR",
"target_application": "CMS",
"timestamp": "2020-07-20T10:49:02.366+04:00",
"bank_id": "NIC",
"instance_id": "InstanceID"
},
"exception_details": {
"application_name": "TCC-ADP",
"date_time": "2023-02-01T16:39:47.314+04:00",
"status": "S",
"error_code": "000",
"error_description": "Success"
}
}
}
}
| 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 |