Remittance Solutions
Overview
The Network Remittance solution offers plug-and-play integration that connects you to a high-volume remittance channel seamlessly. This gives you flexibility to choose the gateway or partner that suits your requirements based on quote rates and other preferences, allowing you to get the best possible foreign exchange rates to grow your revenue.
Convenience and Accessibility
Send money to virtually any country using multiple channels, including online platforms, mobile apps, physical locations, and bank transfers, ensuring flexibility and convenience for all users.
Cost-Effectiveness
Benefit from competitive fees and reduced transaction costs, offering affordable international fund transfers with efficient currency conversion and processing systems.
Speed and Efficiency
Experience expedited cross-border remittances, typically processed within minutes to a few hours, with the assurance of real-time transaction tracking for complete transparency and peace of mind.
Security
Ensure security and compliance with advanced fraud protection measures, encryption technologies, and adherence to regulatory standards, including anti-money laundering (AML) and know-your-customer (KYC) requirements.
Financial Inclusion
Services integrate with mobile wallets and payment systems, expanding financial access for users who rely on mobile technology.
Flexibility and Customization
Recipients can choose their preferred payment method, including direct bank deposits, cash pickups, or mobile money accounts, with the flexibility to send and receive money in multiple currencies.
Economic Benefits
Facilitating remittances not only supports families by providing quick and reliable funds but also boosts local economies, contributing to small businesses and overall economic development.
Customer Support
Cross-border remittance services provide round-the-clock customer support to address any issues or concerns, improving the overall user experience.
The remittance platform features a cutting-edge gateway engine. It provides cardholders with optimal foreign exchange rates through ecosystem partners. NI shall integrate with these partners and offer a unified set of APIs for cardholders. Integration efforts are minimal for funding institutions, ensuring a quick time to market.
It’s important to note that NI can assist in designing the UI/UX at the front end, provided the client agrees.
Remit to VISA - (Accounts & Wallets)
Remit to Accounts & Wallets
Create Payout
Status:
Production
Version:
V2
Product:
Account Remittance Solution
Create Payout....
Overview
The Create Payout API can be used to create the payout transaction to initiate the cross-border remittance payouts via NI. This service is used to create and submit the payout to either bank account or UPI ID or mobile wallet in destination corridors.
This request is used to create the transaction with the money transfer values from the quotation received, and further input details for the transfer, beneficiary, and account details for instance.
Depending on each country’s bank compliance requirements, some additional fields might be mandatory when sending payouts.
Create new payout
API allows financial institutions to submit the payout to either bank account or UPI ID or mobile wallet in destination corridors.
Flexible data structure
Depending on each country’s bank compliance requirements, some additional fields might be mandatory when sending payouts.
Hierarchical organization
This request is used to create the transaction with the money transfer values from the quotation received, and further input details for the transfer, beneficiary, and account details for instance.
Create Payout
Status:
Production
Version:
V2
Product:
Account Remittance Solution
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_create_payout | 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_CREATE_PAYOUT | |||||||
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 | |||||||
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 | transaction_reference | string | 10 | Transaction Identifier - client provided | ||||||
recipient_account | string | 110 | beneficiary account number(IBAN or BAN) /wallet ID/UPI ID | |||||||
recipient_account_type | string | 20 | Account type - Checking/Savings/wallet/UPI | |||||||
payout_amount | string | 20 | payout amount | |||||||
payout_currency | string | 3 | payout amount currency | |||||||
origination_country | string | 3 | country in which payout is initiated | |||||||
recipient_bank_name | string | 140 | Name of the Bank holding the receiving account | |||||||
recipient_bank_branch_name | string | 140 | Name of the Bank branch holding the receiving account | |||||||
recipient_bank_branch_code | string | 45 | Beneficiary's bank branch code | |||||||
recipient_bank_code | string | 12 | bank code associated with the bank name - bank identification code (BIC) (Required for Account transfers only) | |||||||
recipient_bank_code_type | string | 15 | Baneficiary bank account bank code type | |||||||
recipient_bank_bic | string | 11 | Baneficiary bank account Business Identifier Code(BIC) | |||||||
payment_type | string | 3 | Type of payout transaction initiated - A2A, P2P | |||||||
source_of_funds | string | 35 | sender's source of funds (Required for MC & Visa only) | |||||||
sender_type | string | 1 | type of sender (Required for Visa only) | |||||||
sender_account_number | string | 200 | Sender account number | |||||||
sender_first_name | string | 140 | Sender 's first name | |||||||
sender_last_name | string | 140 | Sender 's last name | |||||||
sender_address_line1 | string | 500 | Sender 's address line1 (Required for MC & VisaDirect only) | |||||||
sender_address_line2 | string | 500 | Sender 's address line2 (Required for dLocal & VisaDirect only) | |||||||
sender_address_city | string | 35 | Sender 's address city (Required for dLocal & VisaDirect only) | |||||||
sender_address_postalcode | string | 16 | Sender 's address postal code (Required for MC & VisaDirect only) | |||||||
sender_address_state | string | 25 | Sender 's address state (Required for VisaDirect only) | |||||||
sender_address_country | string | 3 | Sender 's address country (Required for MC & VisaDirect only) | |||||||
recipient_type | string | 1 | type of recipient (Required for VisaDirect only) | |||||||
recipient_first_name | string | 70 | Beneficiary's bank account name | |||||||
recipient_last_name | string | 70 | Recipient's last name | |||||||
recipient_address_line1 | string | 500 | recipient 's address line1 (Required for MC & VisaDirect only) | |||||||
recipient_address_line2 | string | 500 | recipient 's address line2 (Required for MC & VisaDirect only) | |||||||
recipient_address_city | string | 35 | recipient 's address city (Required for VisaDirect only) | |||||||
recipient_address_postalcode | string | 16 | recipient 's address postal code (Required for VisaDirect only) | |||||||
recipient_address_state | string | 25 | recipient 's address state (Required for VisaDirect only) | |||||||
recipient_address_country | string | 3 | recipient 's address country (Required for MC & VisaDirect only) | |||||||
recipient_country_of_birth | string | 3 | recipient 's country of birth (Required for VisaDirect only) | |||||||
recipient_dob | string | 10 | Recipient 's date of birth (Required for VisaDirect only) | |||||||
recipient_id_type | string | 10 | Recipent identification type | |||||||
recipient_id_number | string | 35 | Recipent identification number | |||||||
recipient_phone | string | 30 | recipient's contact number (Required for dLocal only) | |||||||
recipient_mail | string | 210 | recipient's email address (Required for dLocal only) | |||||||
intiating_client_id | string | 20 | Identifier assigned by Visa to uniquely identify the originating entity (Required for VisaDirect only) | |||||||
payout_method | string | 1 | payout method to indicate account or wallet (Required for VisaDirect only) | |||||||
preferred_vendor | string | 10 | customer/client's preferred vendor for cross-border services | |||||||
recipient_bank_account_name | string | 70 | Beneficiary bank account name | |||||||
recipient_account_country_code | string | 3 | Beneficiary bank account country code (Required for VisaDirect only) | |||||||
recipient_account_currency_code | string | 3 | Beneficiary bank account currency code | |||||||
recipient_wallet_operator_name | string | 20 | identifies the operator that has issued the recipient's account and is going to receive and post to recipient's wallet (Required for VisaDirect only) | |||||||
sender_country_of_birth | string | 3 | Sender 's country of birth (Required for VisaDirect only) | |||||||
sender_dob | string | 10 | Sender 's date of birth (Required for dLocal & VisaDirect only) | |||||||
sender_nationality | string | 3 | Sender 's country of birth (Required for dLocal only) | |||||||
purpose_of_payment | string | 39 | Purpose of payment is required in certain markets to clearly identify the purpose of the payment | |||||||
custom_fields | key | string | 100 | |||||||
value | string | 100 |
{
"NISrvRequest": {
"request_create_payout": {
"header": {
"msg_id": "236001",
"msg_type": "TRANSACTION",
"msg_function": "REQ_CREATE_PAYOUT",
"src_application": "BNK",
"target_application": "DLOCAL",
"timestamp": "2024-03-06T11:45:02.366+04:00",
"bank_id": "NIC"
},
"body": {
"transaction_reference": "1709306653t",
"recipient_account": "",
"recipient_account_type": "",
"payout_amount": "",
"payout_currency": "",
"origination_country": "",
"recipient_bank_name": "",
"recipient_bank_branch_name": "",
"recipient_bank_branch_code": "",
"recipient_bank_code": "",
"recipient_bank_code_type": "",
"recipient_bank_bic": "",
"payment_type": "",
"source_of_funds": "",
"sender_type": "",
"sender_account_number": "",
"sender_first_name": "",
"sender_last_name": "",
"sender_address_line1": "",
"sender_address_line2": "",
"sender_address_city": "",
"sender_address_postalcode": "",
"sender_address_state": "",
"sender_address_country": "",
"recipient_type": "",
"recipient_first_name": "",
"recipient_last_name": "",
"recipient_address_line1": "",
"recipient_address_line2": "",
"recipient_address_city": "",
"recipient_address_postalcode": "",
"recipient_address_state": "",
"recipient_address_country": "",
"recipient_country_of_birth": "",
"recipient_dob": "",
"recipient_id_type": "",
"recipient_id_number": "",
"recipient_phone": "",
"recipient_mail": "",
"intiating_client_id": "",
"payout_method": "",
"preferred_vendor": "DLOCAL",
"recipient_bank_account_name": "",
"recipient_account_country_code": "",
"recipient_account_currency_code": "",
"recipient_wallet_operator_name": "",
"sender_country_of_birth": "",
"sender_dob": "",
"sender_nationality": "",
"purpose_of_payment": "",
"custom_fields": [
{
"key": "",
"value": ""
}
]
}
}
}
}
Node | Child Node | Type | Length | Description | |
---|---|---|---|---|---|
Content-Type | application/json | string | Content Type |
Node Type | Type | Length | Description | |||||||
---|---|---|---|---|---|---|---|---|---|---|
NISrvResponse | response_get_receipt | 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_RECEIPT | |||||||
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 | |||||||
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 | preferred_vendor | string | 10 | customer/client's preferred vendor for cross-border services | ||||||
transaction_reference | string | 100 | Transaction Identifier - client provided | |||||||
payout_id | string | 50 | unique identifier generated by each system to idenitify the transaction | |||||||
receipt_date | string | 4 | date of the receipt Date & Time (UTC) | |||||||
country | string | 3 | recipient country | |||||||
amount | string | 20 | amount credited to beneficiary's bank account | |||||||
currency | string | 3 | currency code of the transaction amount | |||||||
payment_date | string | 25 | Date of the Payment Date & Time (UTC) | |||||||
processing_id | string | 10 | Processing ID | |||||||
beneficiary_name | string | 50 | Name of the beneficiary | |||||||
payment_method | string | 32 | payment method used - bank_transfer | |||||||
bank_name | string | 140 | Name of the beneficiary's bank | |||||||
bank_branch | string | 140 | Name of the bank branch | |||||||
bank_account | string | 210 | Bank Account number | |||||||
wallet_id | string | 210 | Wallet ID | |||||||
custom_fields | key | string | 100 | |||||||
value | string | 100 |
{
"NISrvResponse": {
"response_get_receipt": {
"header": {
"msg_id": "236001",
"msg_type": "ENQUIRY",
"msg_function": "RES_GET_RECEIPT",
"src_application": "BNK",
"target_application": "DLOCAL",
"timestamp": "2024-03-06T11:50: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": {
"preferred_vendor": "DLOCAL",
"transaction_reference": "1709306653t",
"payout_id": "1298123",
"receipt_date": "0323",
"country": "IN",
"amount": "900",
"currency": "INR",
"payment_date": "2024-03-01T15:44:21Z[UTC]",
"processing_id": "32432424",
"beneficiary_name": "Siva Sankar",
"payment_method": "bank_transfer",
"bank_name": "HDFC",
"bank_branch": "HDFC",
"bank_account": "12345678912",
"wallet_id": "4234242",
"custom_fields": [
{
"key": "",
"value": ""
}
]
}
}
}
}
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 |