Card Services
Overview
Our remittance solution provides the facility to initiate cross-border remittance from any sender’s card/account/wallet (via internet/mobile banking) to Recipient bank accounts/digital wallets.
This solution works for P2P(person-to-person)/A2A(Account-to-account) cross-border payments.
Get Conversion Rate
Status:
Production
Version:
V2
Category:
Remittance Services
Overview
This service is used to retrieve the current FX rates being used by scheme from the source amount/currency to the destination amount/currency.
Get Conversion Rate
Status:
Production
Version:
V2
Category:
Remittance Services
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 | |||||||
---|---|---|---|---|---|---|---|---|---|---|
NISrvRequest | request_foreign_exchange_rates | header | msg_id | 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 | string | 12 | Message Type – This can have either “TRANSACTION” or “ENQUIRY” As for this API the value expected is “ENQUIRY” | |||||||
msg_function | string | 50 | Static Value - REQ_GET_EXCHANGE_RATE | |||||||
src_application | 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 | 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 | string | 30 | Timestamp of the request - Format YYYY-MM-DDtHH:MM:SS.SSS+04:00 | |||||||
tracking_id | string | 30 | Tracking_id of the request - Format YYYY-MM-DDtHH:MM:SS.SSS+04:00 | |||||||
bank_id | 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 | scheme | string | 1 | This identifier is used to indicate the scheme.'M' - MasterCard 'V' - Visa | ||||||
destination_currency_code | string | 3 | Destination currency to know the exchange rate | |||||||
source_currency_code | string | 3 | source currency code | |||||||
destination_amount | string | 13 | Destination Transaction amount | |||||||
source_amount | string | 13 | Source Transaction amount | |||||||
markup | string | 6 | Percentage FX mark up rate |
{
"NISrvRequest": {
"request_foreign_exchange_rates": {
"header": {
"msg_id": "{{$timestamp}}",
"msg_type": "ENQUIRY",
"msg_function": "REQ_FOREIGN_EXCHANGE_RATES",
"src_application": "MOA",
"target_application": "ALL",
"timestamp": "2024-07-29T16:07.44+04:00",
"tracking_id": "528",
"bank_id": "REM"
},
"body": {
"scheme": "V",
"destination_currency_code": "GBP",
"source_currency_code": "USD",
"rate_product_code": "A",
"destination_amount": "50"
}
}
}
}
Node | Child Node | Type | Length | Description | |
---|---|---|---|---|---|
Content-Type | application/json | string | Content Type |
Node Type | Type | Length | Description | |||||||
---|---|---|---|---|---|---|---|---|---|---|
NISrvResponse | response_foreign_exchange_rates | header | msg_id | 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 | string | 12 | Message Type – This can have either “TRANSACTION” or “ENQUIRY” As for this API the value expected is “ENQUIRY” | |||||||
msg_function | string | 50 | Static Value - RES_GET_EXCHANGE_RATE | |||||||
src_application | 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 | 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 | string | 30 | Timestamp of the response Date & time Format DD/MM/YYYY HH:MM:SS | |||||||
tracking_id | string | 30 | Tracking ID of the response Date & time Format DD/MM/YYYY HH:MM:SS | |||||||
bank_id | 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 | string | 20 | Application Name | ||||||
date_time | string | 30 | Timestamp of the response Format “YYYY-MM-DD HH:MM:SS” | |||||||
status | string | 1 | Status of the request (S/F) | |||||||
error_code | string | 4 | EAI Internal Error Code (Check error codes section for the complete list of error codes and error code descriptions) | |||||||
error_description | 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 | BankID | string | 4 | Identifier assigned by NI to uniquely identify the client | ||||||
ExchangeRate | string | 14 | exchange rate applied to convert source currency to destination currency | |||||||
source_amount | string | 14 | Transaction amount in source currency | |||||||
destinationAmount | string | 14 | Transaction amount in destination currency | |||||||
settlement_amount | string | 1 | status code of the transaction | |||||||
custom_fields | key | string | 100 | |||||||
value | string | 100 |
{
"NISrvRequest": {
"request_foreign_exchange_rates": {
"header": {
"msg_id": "{{$timestamp}}",
"msg_type": "ENQUIRY",
"msg_function": "REQ_FOREIGN_EXCHANGE_RATES",
"src_application": "MOA",
"target_application": "ALL",
"timestamp": "2024-07-29T16:07.44+04:00",
"tracking_id": "528",
"bank_id": "REM"
},
"body": {
"scheme": "V",
"destination_currency_code": "GBP",
"source_currency_code": "USD",
"rate_product_code": "A",
"destination_amount": "50"
}
}
}
}
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 |
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.