Asia · INR · 5 routes
Payouts to India
Route catalog · IN
Choose a payout method
Supported currencies
Cutoff & delivery timing
Realtime, 24x7 up to INR 500, 000 via IMPS (List of IMPS enabled banks available)
Real Time subject to cut-off 18:00 local time via RTGS (All Banks)
Same Day via NEFT (All banks)
Nium will automatically select the fastest payment mode (IMPS, RTGS and NEFT in order) given the cut-off times and restrictions of the available payment modes.
Scroll horizontally to compare supported modes
| Transaction limit per end-user | B2B | B2P | P2P | P2B |
|---|---|---|---|---|
| + Max | No limit | No limit | No limit | No limit |
| − Min | INR 1 | INR 1 | INR 1 | INR 1 |
Route details
Select a supported mode
Beneficiary statement narrative
Bank Reference Number will be visible in Beneficiary's bank statement. The statement narrative in this corridor also depends on other factors so it might not be the same for all transactions. Remitter Name will be visible in Beneficiary's bank statement for NEFT payment mode.
Network participant
Bank
Channels
All banks in India
Routing code
IFSC
Proof of payment
Upon request, Proof of Payment for a transaction can be made available.
Notes
Trade transactions have a max amount limit of INR 1.5 Mn. List of trade purpose codes - IR01801; IR01802; IR01803; IR01804; IR01805; IR01806; IR01807; IR01808; IR01809; IR01810; IR018011; IR014; IR020
Trade transactions with purpose codes IR014, IR01806, IR0808 & IR0810 are supported to all banks other than IDFC bank i.e IFSC code starting with IDFB.
It is good to have Invoice Date and Invoice Number for Trade Transactions.
Purpose code of IR001 and IR002 is supported only for P2P transactions
Mandatory data requirements
Remitter
- Remitter Name
- Remitter Account Type
- Remitter Address
- Remitter Country Code
- Remit Purpose Code
Beneficiary
- Beneficiary Name
- Beneficiary Account Type
- Beneficiary Account Number
- Beneficiary Country Code
- Beneficiary Bank Name
Routing
- Routing Code Type 1 - IFSC Code
- Routing Code Value 1
Supporting documents
- Remitter Beneficiary Relationship
- Nature of Business
- Duration of Contract
- Commercial Agreement
- Current Invoice
Beneficiary account type
CORPORATE
Beneficiary statement narrative
Bank Reference Number will be visible in Beneficiary's bank statement. The statement narrative in this corridor also depends on other factors so it might not be the same for all transactions. Remitter Name will be visible in Beneficiary's bank statement for NEFT payment mode.
Network participant
Bank
Channels
All banks in India
Routing code
IFSC
Proof of payment
Upon request, Proof of Payment for a transaction can be made available.
Notes
Trade transactions have a max amount limit of INR 1.5 Mn. List of trade purpose codes - IR01801; IR01802; IR01803; IR01804; IR01805; IR01806; IR01807; IR01808; IR01809; IR01810; IR018011; IR014; IR020
Trade transactions with purpose codes IR014, IR01806, IR0808 & IR0810 are supported to all banks other than IDFC bank i.e IFSC code starting with IDFB.
It is good to have Invoice Date and Invoice Number for Trade Transactions.
Purpose code of IR001 and IR002 is supported only for P2P transactions
Mandatory data requirements
Remitter
- Remitter Name
- Remitter Account Type
- Remitter Address
- Remitter Country Code
- Remit Purpose Code
Beneficiary
- Beneficiary Name
- Beneficiary Account Type
- Beneficiary Account Number
- Beneficiary Country Code
- Beneficiary Bank Name
Routing
- Routing Code Type 1 - IFSC Code
- Routing Code Value 3
Supporting documents
- Remitter Beneficiary Relationship
- Nature of Business
- Duration of Contract
- Commercial Agreement
- Current Invoice
Beneficiary account type
INDIVIDUAL
Beneficiary statement narrative
Bank Reference Number will be visible in Beneficiary's bank statement. The statement narrative in this corridor also depends on other factors so it might not be the same for all transactions. Remitter Name will be visible in Beneficiary's bank statement for NEFT payment mode.
Network participant
Bank
Channels
All banks in India
Routing code
IFSC
Proof of payment
Upon request, Proof of Payment for a transaction can be made available.
Notes
Trade transactions have a max amount limit of INR 1.5 Mn. List of trade purpose codes - IR01801; IR01802; IR01803; IR01804; IR01805; IR01806; IR01807; IR01808; IR01809; IR01810; IR018011; IR014; IR020
Trade transactions with purpose codes IR014, IR01806, IR0808 & IR0810 are supported to all banks other than IDFC bank i.e IFSC code starting with IDFB.
It is good to have Invoice Date and Invoice Number for Trade Transactions.
Purpose code of IR001 and IR002 is supported only for P2P transactions
Mandatory data requirements
Remitter
- Remitter Name
- Remitter Account Type
- Remitter Address
- Remitter Country Code
- Remit Purpose Code
Beneficiary
- Beneficiary Name
- Beneficiary Account Type
- Beneficiary Account Number
- Beneficiary Country Code
- Beneficiary Bank Name
Routing
- Routing Code Type 1 - IFSC Code
- Routing Code Value 2
Supporting documents
- Remitter Beneficiary Relationship
Beneficiary account type
INDIVIDUAL
Beneficiary statement narrative
Bank Reference Number will be visible in Beneficiary's bank statement. The statement narrative in this corridor also depends on other factors so it might not be the same for all transactions. Remitter Name will be visible in Beneficiary's bank statement for NEFT payment mode.
Network participant
Bank
Channels
All banks in India
Routing code
IFSC
Proof of payment
Upon request, Proof of Payment for a transaction can be made available.
Notes
Trade transactions have a max amount limit of INR 1.5 Mn. List of trade purpose codes - IR01801; IR01802; IR01803; IR01804; IR01805; IR01806; IR01807; IR01808; IR01809; IR01810; IR018011; IR014; IR020
Trade transactions with purpose codes IR014, IR01806, IR0808 & IR0810 are supported to all banks other than IDFC bank i.e IFSC code starting with IDFB.
It is good to have Invoice Date and Invoice Number for Trade Transactions.
Purpose code of IR001 and IR002 is supported only for P2P transactions
Mandatory data requirements
Remitter
- Remitter Name
- Remitter Account Type
- Remitter Address
- Remitter Country Code
- Remit Purpose Code
Beneficiary
- Beneficiary Name
- Beneficiary Account Type
- Beneficiary Account Number
- Beneficiary Country Code
- Beneficiary Bank Name
Routing
- Routing Code Type 1 - IFSC Code
- Routing Code Value 4
Supporting documents
- Remitter Beneficiary Relationship
- Nature of Business
- Duration of Contract
- Commercial Agreement
- Current Invoice
Beneficiary account type
CORPORATE
Supported currencies
Cutoff & delivery timing
Real Time, 24x7
Scroll horizontally to compare supported modes
| Transaction limit per end-user | B2P | P2P |
|---|---|---|
| + Max | INR 200,000 | INR 200,000 |
| − Min | Not specified | Not specified |
Route details
Select a supported mode
Beneficiary statement narrative
Remitter Name will be visible in Beneficiary's bank statement. The statement narrative in this corridor also depends on other factors so it might not be the same for all transactions.
Network participant
Bank
Channels
All major banks in India. List available.
Proof of payment
Upon request, Proof of Payment for a transaction can be made available.
Notes
Proxy Value is validated before initiation of a payment
Value for proxy type should be VPA
Trade purpose codes are not supported. List of trade purpose codes - IR01801; IR01802; IR01803; IR01804; IR01805; IR01806; IR01807; IR01808; IR01809; IR01810; IR018011; IR014; IR020
Payments made to a proxy categorised as a business might see reduced success rates due to validations in place by the beneficiary bank
Mandatory data requirements
Remitter
- Remitter Name
- Remitter Identification Type
- Remitter Account Type
- Remitter Country Code
- Remitter Identification Number
- Remitter Purpose Code
- Remitter Address
- Remitter City
Beneficiary
- Beneficiary Name
- Beneficiary Account Type
- Beneficiary Country Code
Other
Payout Method - PROXY
Proxy Type (VPA)
Proxy Value (UPI Address)
Supporting documents
- Remitter Beneficiary Relationship
- Nature of Business
- Duration of Contract
- Commercial Agreement
- Current Invoice
Beneficiary account type
INDIVIDUAL
Beneficiary statement narrative
Remitter Name will be visible in Beneficiary's bank statement. The statement narrative in this corridor also depends on other factors so it might not be the same for all transactions.
Network participant
Bank
Channels
All major banks in India. List available.
Proof of payment
Upon request, Proof of Payment for a transaction can be made available.
Notes
Proxy Value is validated before initiation of a payment
Value for proxy type should be VPA
Trade purpose codes are not supported. List of trade purpose codes - IR01801; IR01802; IR01803; IR01804; IR01805; IR01806; IR01807; IR01808; IR01809; IR01810; IR018011; IR014; IR020
Payments made to a proxy categorised as a business might see reduced success rates due to validations in place by the beneficiary bank
Mandatory data requirements
Remitter
- Remitter Name
- Remitter Identification Type
- Remitter Account Type
- Remitter Country Code
- Remitter Identification Number
- Remitter Purpose Code
- Remitter Address
- Remitter City
Beneficiary
- Beneficiary Name
- Beneficiary Account Type
- Beneficiary Country Code
Other
Payout Method - PROXY
Proxy Type (VPA)
Proxy Value (UPI Address)
Supporting documents
- Remitter Beneficiary Relationship
Beneficiary account type
INDIVIDUAL
Supported currencies
Cutoff & delivery timing
Same-day processing subject to cutoff of 7:30 UTC
Scroll horizontally to compare supported modes
| Transaction limit per end-user | B2B | B2P | P2P | P2B |
|---|---|---|---|---|
| + Max | No limit | No limit | No limit | No limit |
| − Min | INR 1,500,000 | INR 1,500,000 | INR 1,500,000 | INR 1,500,000 |
Route details
Select a supported mode
Beneficiary statement narrative
Ultimate Sender Name and narrative details will be passed as part of pacs.008 message to beneficiary bank. Details available on beneficiary statement will be dependent on beneficiary bank.
Network participant
Bank
Channels
All major banks enabled with SWIFT
Routing code
IFSC Code
Proof of payment
pacs.008 can be considered as a proof of payment and can be provided on request
Notes
For WIRES, NIUM supports transactions with SHA Fee Type
Mandatory data requirements
Remitter
- Remitter Name
- Remitter Account Type
- Remitter Identification Type
- Remitter Identification Number
- Remitter Address
- Remitter Country code
- Remit Purpose Code
Beneficiary
- Beneficiary Name
- Beneficiary Account Number
- Beneficiary Account Type
- Beneficiary Country Code
- Beneficiary Address
- Beneficiary City
- Beneficiary Postcode
Routing
- Routing Code Type 1 - IFSC CODE
- Routing Code Value
Supporting documents
- Remitter Beneficiary Relationship
- Nature of Business
- Duration of Contract
- Commercial Agreement
- Current Invoice
Beneficiary account type
CORPORATE
Beneficiary statement narrative
Ultimate Sender Name and narrative details will be passed as part of pacs.008 message to beneficiary bank. Details available on beneficiary statement will be dependent on beneficiary bank.
Network participant
Bank
Channels
All major banks enabled with SWIFT
Routing code
IFSC Code
Proof of payment
pacs.008 can be considered as a proof of payment and can be provided on request
Notes
For WIRES, NIUM supports transactions with SHA Fee Type
Mandatory data requirements
Remitter
- Remitter Name
- Remitter Account Type
- Remitter Identification Type
- Remitter Identification Number
- Remitter Address
- Remitter Country code
- Remit Purpose Code
Beneficiary
- Beneficiary Name
- Beneficiary Account Number
- Beneficiary Account Type
- Beneficiary Country Code
- Beneficiary Address
- Beneficiary City
- Beneficiary Postcode
Routing
- Routing Code Type 1 - IFSC CODE
- Routing Code Value
Supporting documents
- Remitter Beneficiary Relationship
- Nature of Business
- Duration of Contract
- Commercial Agreement
- Current Invoice
Beneficiary account type
INDIVIDUAL
Beneficiary statement narrative
Ultimate Sender Name and narrative details will be passed as part of pacs.008 message to beneficiary bank. Details available on beneficiary statement will be dependent on beneficiary bank.
Network participant
Bank
Channels
All major banks enabled with SWIFT
Routing code
IFSC Code
Proof of payment
pacs.008 can be considered as a proof of payment and can be provided on request
Notes
For WIRES, NIUM supports transactions with SHA Fee Type
Mandatory data requirements
Remitter
- Remitter Name
- Remitter Account Type
- Remitter Identification Type
- Remitter Identification Number
- Remitter Address
- Remitter Country code
- Remit Purpose Code
Beneficiary
- Beneficiary Name
- Beneficiary Account Number
- Beneficiary Account Type
- Beneficiary Country Code
- Beneficiary Address
- Beneficiary City
- Beneficiary Postcode
Routing
- Routing Code Type 1 - IFSC CODE
- Routing Code Value
Supporting documents
- Remitter Beneficiary Relationship
Beneficiary account type
INDIVIDUAL
Beneficiary statement narrative
Ultimate Sender Name and narrative details will be passed as part of pacs.008 message to beneficiary bank. Details available on beneficiary statement will be dependent on beneficiary bank.
Network participant
Bank
Channels
All major banks enabled with SWIFT
Routing code
IFSC Code
Proof of payment
pacs.008 can be considered as a proof of payment and can be provided on request
Notes
For WIRES, NIUM supports transactions with SHA Fee Type
Mandatory data requirements
Remitter
- Remitter Name
- Remitter Account Type
- Remitter Identification Type
- Remitter Identification Number
- Remitter Address
- Remitter Country code
- Remit Purpose Code
Beneficiary
- Beneficiary Name
- Beneficiary Account Number
- Beneficiary Account Type
- Beneficiary Country Code
- Beneficiary Address
- Beneficiary City
- Beneficiary Postcode
Routing
- Routing Code Type 1 - IFSC CODE
- Routing Code Value
Supporting documents
- Remitter Beneficiary Relationship
- Nature of Business
- Duration of Contract
- Commercial Agreement
- Current Invoice
Beneficiary account type
CORPORATE
Supported currencies
Cutoff & delivery timing
Same-day processing subject to cutoff of 07:30 UTC
Scroll horizontally to compare supported modes
| Transaction limit per end-user | B2B | B2P | P2P | P2B |
|---|---|---|---|---|
| + Max | No limit | No limit | No limit | No limit |
| − Min | Not specified | Not specified | Not specified | Not specified |
Route details
Select a supported mode
Beneficiary statement narrative
Ultimate Sender Name and narrative details will be passed as part of pacs.008 message to beneficiary bank. Details available on beneficiary statement will be dependent on beneficiary bank.
Network participant
Bank
Channels
All SWIFT enabled banks in the country
Routing code
SWIFT
Proof of payment
pacs.008 can be considered as a proof of payment and can be provided on request
Notes
WIRES can be sent to all countries except for OFAC listed.
pacs.008 can be provided on request.
AUD · CHF · EUR · GBP · HKD · JPY · NZD · SGD · USD only
NIUM does not support OUR charge type for CAD currency WIRES
Processing of payments to Crimea, Donetsk, Luhansk, Sevastopol regions of Ukraine is prohibited. This list is subject to change.
CAD only
For foreign currency wire currencies USD, EUR, GBP - NIUM supports both OUR and SHA fee type while for other currencies AUD, CAD, CHF, JPY, NZD, HKD, SGD - NIUM supports only SHA fee type
Mandatory data requirements
Remitter
- Remitter Name
- Remitter Account Type
- Remitter Identification Type
- Remitter Identification Number
- Remitter Address
- Remitter Country Code
- Remit Purpose Code
Beneficiary
- Beneficiary Name
- Beneficiary Account Type
- Beneficiary Account Number
- Beneficiary Country Code
- Beneficiary Address
- Beneficiary City
- Beneficiary Postcode
- Beneficiary Address (Recommended)
- Beneficiary City (Recommended)
- Beneficiary Postcode (Recommended)
Routing
- Routing Code Value 1
- Routing Code Type 1 - SWIFT Code
Supporting documents
- Remitter Beneficiary Relationship
- Nature of Business
- Duration of Contract
- Commercial Agreement
- Current Invoice
Beneficiary account type
CORPORATE
Beneficiary statement narrative
Ultimate Sender Name and narrative details will be passed as part of pacs.008 message to beneficiary bank. Details available on beneficiary statement will be dependent on beneficiary bank.
Network participant
Bank
Channels
All SWIFT enabled banks in the country
Routing code
SWIFT
Proof of payment
pacs.008 can be considered as a proof of payment and can be provided on request
Notes
WIRES can be sent to all countries except for OFAC listed.
pacs.008 can be provided on request.
AUD · CHF · EUR · GBP · HKD · JPY · NZD · SGD · USD only
NIUM does not support OUR charge type for CAD currency WIRES
Processing of payments to Crimea, Donetsk, Luhansk, Sevastopol regions of Ukraine is prohibited. This list is subject to change.
CAD only
For foreign currency wire currencies USD, EUR, GBP - NIUM supports both OUR and SHA fee type while for other currencies AUD, CAD, CHF, JPY, NZD, HKD, SGD - NIUM supports only SHA fee type
Mandatory data requirements
Remitter
- Remitter Name
- Remitter Account Type
- Remitter Identification Type
- Remitter Identification Number
- Remitter Address
- Remitter Country Code
- Remit Purpose Code
Beneficiary
- Beneficiary Name
- Beneficiary Account Type
- Beneficiary Account Number
- Beneficiary Country Code
- Beneficiary Address
- Beneficiary City
- Beneficiary Postcode
- Beneficiary Address (Recommended)
- Beneficiary City (Recommended)
- Beneficiary Postcode (Recommended)
Routing
- Routing Code Value 1
- Routing Code Type 1 - SWIFT Code
Supporting documents
- Remitter Beneficiary Relationship
- Nature of Business
- Duration of Contract
- Commercial Agreement
- Current Invoice
Beneficiary account type
INDIVIDUAL
Beneficiary statement narrative
Ultimate Sender Name and narrative details will be passed as part of pacs.008 message to beneficiary bank. Details available on beneficiary statement will be dependent on beneficiary bank.
Network participant
Bank
Channels
All SWIFT enabled banks in the country
Routing code
SWIFT
Proof of payment
pacs.008 can be considered as a proof of payment and can be provided on request
Notes
WIRES can be sent to all countries except for OFAC listed.
pacs.008 can be provided on request.
AUD · CHF · EUR · GBP · HKD · JPY · NZD · SGD · USD only
NIUM does not support OUR charge type for CAD currency WIRES
Processing of payments to Crimea, Donetsk, Luhansk, Sevastopol regions of Ukraine is prohibited. This list is subject to change.
CAD only
For foreign currency wire currencies USD, EUR, GBP - NIUM supports both OUR and SHA fee type while for other currencies AUD, CAD, CHF, JPY, NZD, HKD, SGD - NIUM supports only SHA fee type
Mandatory data requirements
Remitter
- Remitter Name
- Remitter Account Type
- Remitter Identification Type
- Remitter Identification Number
- Remitter Address
- Remitter Country Code
- Remit Purpose Code
Beneficiary
- Beneficiary Name
- Beneficiary Account Type
- Beneficiary Account Number
- Beneficiary Country Code
- Beneficiary Address
- Beneficiary City
- Beneficiary Postcode
- Beneficiary Address (Recommended)
- Beneficiary City (Recommended)
- Beneficiary Postcode (Recommended)
Routing
- Routing Code Value 1
- Routing Code Type 1 - SWIFT Code
Supporting documents
- Remitter Beneficiary Relationship
Beneficiary account type
INDIVIDUAL
Beneficiary statement narrative
Ultimate Sender Name and narrative details will be passed as part of pacs.008 message to beneficiary bank. Details available on beneficiary statement will be dependent on beneficiary bank.
Network participant
Bank
Channels
All SWIFT enabled banks in the country
Routing code
SWIFT
Proof of payment
pacs.008 can be considered as a proof of payment and can be provided on request
Notes
WIRES can be sent to all countries except for OFAC listed.
pacs.008 can be provided on request.
AUD · CHF · EUR · GBP · HKD · JPY · NZD · SGD · USD only
NIUM does not support OUR charge type for CAD currency WIRES
Processing of payments to Crimea, Donetsk, Luhansk, Sevastopol regions of Ukraine is prohibited. This list is subject to change.
CAD only
For foreign currency wire currencies USD, EUR, GBP - NIUM supports both OUR and SHA fee type while for other currencies AUD, CAD, CHF, JPY, NZD, HKD, SGD - NIUM supports only SHA fee type
Mandatory data requirements
Remitter
- Remitter Name
- Remitter Account Type
- Remitter Identification Type
- Remitter Identification Number
- Remitter Address
- Remitter Country Code
- Remit Purpose Code
Beneficiary
- Beneficiary Name
- Beneficiary Account Type
- Beneficiary Account Number
- Beneficiary Country Code
- Beneficiary Address
- Beneficiary City
- Beneficiary Postcode
- Beneficiary Address (Recommended)
- Beneficiary City (Recommended)
- Beneficiary Postcode (Recommended)
Routing
- Routing Code Value 1
- Routing Code Type 1 - SWIFT Code
Supporting documents
- Remitter Beneficiary Relationship
- Nature of Business
- Duration of Contract
- Commercial Agreement
- Current Invoice
Beneficiary account type
CORPORATE
Supported currencies
Cutoff & delivery timing
1. 24x7 Availability
2. Real-time for Fast fund Enabled (Details on fast-fund enabled countries available on request)
3. T+2 for other countries
Scroll horizontally to compare supported modes
| Transaction limit per end-user | B2B | B2P | P2P | P2B |
|---|---|---|---|---|
| + Max | USD 50,000 | USD 50,000 | USD 2,500 | USD 50,000 |
| − Min | Not specified | Not specified | Not specified | Not specified |
Route details
Select a supported mode
Network participant
VISA
Notes
For more information, please contact your NIUM account manager team. Additional information and approval from VISA is required before this payout method can be made available.
Origination of funds is allowed only from a set of countries as mentioned in the table below.
In case the transaction currency does not match the destination card issuer currency, amount will be converted and credited in currency of the card issuer.
In few countries, only few banks may allow the transactions.
Below additional daily/monthly/yearly limits applicable for P2P transactions whichever reached first Per Day - 30 transactions or USD 10,000 per Beneficiary card Per Week - 50 transactions or USD 25,000 per Beneficiary card Per Month - 150 transactions or USD 50,000 per Beneficiary card.
Below additional daily/monthly/yearly limits applicable for B2P/B2B transactions whichever reached first Per Day - 30 transactions or USD 50,000 per Beneficiary card Per Week - 50 transactions or USD 100,000 per Beneficiary card Per Month - 150 transactions or USD 200,000 per Beneficiary card.
Mandatory data requirements
Remitter
- Remitter Name
- Remitter Identification Type
- Remitter Identification Number
- Remitter Country Code
Beneficiary
- Beneficiary Card Number
- Beneficiary Name
- Beneficiary Country Code
Beneficiary account type
CORPORATE
Network participant
VISA
Notes
For more information, please contact your NIUM account manager team. Additional information and approval from VISA is required before this payout method can be made available.
Origination of funds is allowed only from a set of countries as mentioned in the table below.
In case the transaction currency does not match the destination card issuer currency, amount will be converted and credited in currency of the card issuer.
In few countries, only few banks may allow the transactions.
Below additional daily/monthly/yearly limits applicable for P2P transactions whichever reached first Per Day - 30 transactions or USD 10,000 per Beneficiary card Per Week - 50 transactions or USD 25,000 per Beneficiary card Per Month - 150 transactions or USD 50,000 per Beneficiary card.
Below additional daily/monthly/yearly limits applicable for B2P/B2B transactions whichever reached first Per Day - 30 transactions or USD 50,000 per Beneficiary card Per Week - 50 transactions or USD 100,000 per Beneficiary card Per Month - 150 transactions or USD 200,000 per Beneficiary card.
Mandatory data requirements
Remitter
- Remitter Name
- Remitter Identification Type
- Remitter Identification Number
- Remitter Country Code
Beneficiary
- Beneficiary Card Number
- Beneficiary Name
- Beneficiary Country Code
Beneficiary account type
INDIVIDUAL
Network participant
VISA
Notes
For more information, please contact your NIUM account manager team. Additional information and approval from VISA is required before this payout method can be made available.
Origination of funds is allowed only from a set of countries as mentioned in the table below.
In case the transaction currency does not match the destination card issuer currency, amount will be converted and credited in currency of the card issuer.
In few countries, only few banks may allow the transactions.
Below additional daily/monthly/yearly limits applicable for P2P transactions whichever reached first Per Day - 30 transactions or USD 10,000 per Beneficiary card Per Week - 50 transactions or USD 25,000 per Beneficiary card Per Month - 150 transactions or USD 50,000 per Beneficiary card.
Below additional daily/monthly/yearly limits applicable for B2P/B2B transactions whichever reached first Per Day - 30 transactions or USD 50,000 per Beneficiary card Per Week - 50 transactions or USD 100,000 per Beneficiary card Per Month - 150 transactions or USD 200,000 per Beneficiary card.
Mandatory data requirements
Remitter
- Remitter Name
- Remitter Identification Type
- Remitter Identification Number
- Remitter Country Code
Beneficiary
- Beneficiary Card Number
- Beneficiary Name
- Beneficiary Country Code
Beneficiary account type
INDIVIDUAL
Network participant
VISA
Notes
For more information, please contact your NIUM account manager team. Additional information and approval from VISA is required before this payout method can be made available.
Origination of funds is allowed only from a set of countries as mentioned in the table below.
In case the transaction currency does not match the destination card issuer currency, amount will be converted and credited in currency of the card issuer.
In few countries, only few banks may allow the transactions.
Below additional daily/monthly/yearly limits applicable for P2P transactions whichever reached first Per Day - 30 transactions or USD 10,000 per Beneficiary card Per Week - 50 transactions or USD 25,000 per Beneficiary card Per Month - 150 transactions or USD 50,000 per Beneficiary card.
Below additional daily/monthly/yearly limits applicable for B2P/B2B transactions whichever reached first Per Day - 30 transactions or USD 50,000 per Beneficiary card Per Week - 50 transactions or USD 100,000 per Beneficiary card Per Month - 150 transactions or USD 200,000 per Beneficiary card.
Mandatory data requirements
Remitter
- Remitter Name
- Remitter Identification Type
- Remitter Identification Number
- Remitter Country Code
Beneficiary
- Beneficiary Card Number
- Beneficiary Name
- Beneficiary Country Code
Beneficiary account type
CORPORATE
Supported currencies
Cutoff & delivery timing
Realtime, 24x7 up to INR 500, 000 via IMPS (List of IMPS enabled banks available)
Real Time subject to cut-off 18:00 local time via RTGS (All Banks)
Same Day via NEFT (All banks)
Nium will automatically select the fastest payment mode (IMPS, RTGS and NEFT in order) given the cut-off times and restrictions of the available payment modes.
Scroll horizontally to compare supported modes
| Transaction limit per end-user | B2B | B2P | P2P | P2B |
|---|---|---|---|---|
| + Max | No limit | No limit | No limit | No limit |
| − Min | INR 1 | INR 1 | INR 1 | INR 1 |
Route details
Select a supported mode
Beneficiary statement narrative
Bank Reference Number will be visible in Beneficiary's bank statement. The statement narrative in this corridor also depends on other factors so it might not be the same for all transactions. Remitter Name will be visible in Beneficiary's bank statement for NEFT payment mode.
Network participant
Bank
Channels
All banks in India
Routing code
IFSC
Proof of payment
Upon request, Proof of Payment for a transaction can be made available.
Notes
Trade transactions have a max amount limit of INR 1.5 Mn. List of trade purpose codes - IR01801; IR01802; IR01803; IR01804; IR01805; IR01806; IR01807; IR01808; IR01809; IR01810; IR018011; IR014; IR020
Trade transactions with purpose codes IR014, IR01806, IR0808 & IR0810 are supported to all banks other than IDFC bank i.e IFSC code starting with IDFB.
It is good to have Invoice Date and Invoice Number for Trade Transactions.
Purpose code of IR001 and IR002 is supported only for P2P transactions
Mandatory data requirements
Remitter
- Remitter Name
- Remitter Account Type
- Remitter Address
- Remitter Country Code
- Remit Purpose Code
Beneficiary
- Beneficiary Name
- Beneficiary Account Type
- Beneficiary Account Number
- Beneficiary Country Code
- Beneficiary Bank Name
Routing
- Routing Code Type 1 - IFSC Code
- Routing Code Value 2
Supporting documents
- Remitter Beneficiary Relationship
- Nature of Business
- Duration of Contract
- Commercial Agreement
- Current Invoice
Beneficiary account type
CORPORATE
Beneficiary statement narrative
Bank Reference Number will be visible in Beneficiary's bank statement. The statement narrative in this corridor also depends on other factors so it might not be the same for all transactions. Remitter Name will be visible in Beneficiary's bank statement for NEFT payment mode.
Network participant
Bank
Channels
All banks in India
Routing code
IFSC
Proof of payment
Upon request, Proof of Payment for a transaction can be made available.
Notes
Trade transactions have a max amount limit of INR 1.5 Mn. List of trade purpose codes - IR01801; IR01802; IR01803; IR01804; IR01805; IR01806; IR01807; IR01808; IR01809; IR01810; IR018011; IR014; IR020
Trade transactions with purpose codes IR014, IR01806, IR0808 & IR0810 are supported to all banks other than IDFC bank i.e IFSC code starting with IDFB.
It is good to have Invoice Date and Invoice Number for Trade Transactions.
Purpose code of IR001 and IR002 is supported only for P2P transactions
Mandatory data requirements
Remitter
- Remitter Name
- Remitter Account Type
- Remitter Address
- Remitter Country Code
- Remit Purpose Code
Beneficiary
- Beneficiary Name
- Beneficiary Account Type
- Beneficiary Account Number
- Beneficiary Country Code
- Beneficiary Bank Name
Routing
- Routing Code Type 1 - IFSC Code
- Routing Code Value 1
Supporting documents
- Remitter Beneficiary Relationship
- Nature of Business
- Duration of Contract
- Commercial Agreement
- Current Invoice
Beneficiary account type
INDIVIDUAL
Beneficiary statement narrative
Bank Reference Number will be visible in Beneficiary's bank statement. The statement narrative in this corridor also depends on other factors so it might not be the same for all transactions. Remitter Name will be visible in Beneficiary's bank statement for NEFT payment mode.
Network participant
Bank
Channels
All banks in India
Routing code
IFSC
Proof of payment
Upon request, Proof of Payment for a transaction can be made available.
Notes
Trade transactions have a max amount limit of INR 1.5 Mn. List of trade purpose codes - IR01801; IR01802; IR01803; IR01804; IR01805; IR01806; IR01807; IR01808; IR01809; IR01810; IR018011; IR014; IR020
Trade transactions with purpose codes IR014, IR01806, IR0808 & IR0810 are supported to all banks other than IDFC bank i.e IFSC code starting with IDFB.
It is good to have Invoice Date and Invoice Number for Trade Transactions.
Purpose code of IR001 and IR002 is supported only for P2P transactions
Mandatory data requirements
Remitter
- Remitter Name
- Remitter Account Type
- Remitter Address
- Remitter Country Code
- Remit Purpose Code
Beneficiary
- Beneficiary Name
- Beneficiary Account Type
- Beneficiary Account Number
- Beneficiary Country Code
- Beneficiary Bank Name
Routing
- Routing Code Type 1 - IFSC Code
- Routing Code Value 3
Supporting documents
- Remitter Beneficiary Relationship
Beneficiary account type
INDIVIDUAL
Beneficiary statement narrative
Bank Reference Number will be visible in Beneficiary's bank statement. The statement narrative in this corridor also depends on other factors so it might not be the same for all transactions. Remitter Name will be visible in Beneficiary's bank statement for NEFT payment mode.
Network participant
Bank
Channels
All banks in India
Routing code
IFSC
Proof of payment
Upon request, Proof of Payment for a transaction can be made available.
Notes
Trade transactions have a max amount limit of INR 1.5 Mn. List of trade purpose codes - IR01801; IR01802; IR01803; IR01804; IR01805; IR01806; IR01807; IR01808; IR01809; IR01810; IR018011; IR014; IR020
Trade transactions with purpose codes IR014, IR01806, IR0808 & IR0810 are supported to all banks other than IDFC bank i.e IFSC code starting with IDFB.
It is good to have Invoice Date and Invoice Number for Trade Transactions.
Purpose code of IR001 and IR002 is supported only for P2P transactions
Mandatory data requirements
Remitter
- Remitter Name
- Remitter Account Type
- Remitter Address
- Remitter Country Code
- Remit Purpose Code
Beneficiary
- Beneficiary Name
- Beneficiary Account Type
- Beneficiary Account Number
- Beneficiary Country Code
- Beneficiary Bank Name
Routing
- Routing Code Type 1 - IFSC Code
- Routing Code Value 4
Supporting documents
- Remitter Beneficiary Relationship
- Nature of Business
- Duration of Contract
- Commercial Agreement
- Current Invoice
Beneficiary account type
CORPORATE
Supported currencies
Cutoff & delivery timing
Real Time, 24x7
Scroll horizontally to compare supported modes
| Transaction limit per end-user | B2P | P2P |
|---|---|---|
| + Max | INR 200,000 | INR 200,000 |
| − Min | Not specified | Not specified |
Route details
Select a supported mode
Beneficiary statement narrative
Remitter Name will be visible in Beneficiary's bank statement. The statement narrative in this corridor also depends on other factors so it might not be the same for all transactions.
Network participant
Bank
Channels
All major banks in India. List available.
Proof of payment
Upon request, Proof of Payment for a transaction can be made available.
Notes
Proxy Value is validated before initiation of a payment
Value for proxy type should be VPA
Trade purpose codes are not supported. List of trade purpose codes - IR01801; IR01802; IR01803; IR01804; IR01805; IR01806; IR01807; IR01808; IR01809; IR01810; IR018011; IR014; IR020
Payments made to a proxy categorised as a business might see reduced success rates due to validations in place by the beneficiary bank
Mandatory data requirements
Remitter
- Remitter Name
- Remitter Identification Type
- Remitter Account Type
- Remitter Country Code
- Remitter Identification Number
- Remitter Purpose Code
- Remitter Address
- Remitter City
Beneficiary
- Beneficiary Name
- Beneficiary Account Type
- Beneficiary Country Code
Other
Payout Method - PROXY
Proxy Type (VPA)
Proxy Value (UPI Address)
Supporting documents
- Remitter Beneficiary Relationship
- Nature of Business
- Duration of Contract
- Commercial Agreement
- Current Invoice
Beneficiary account type
INDIVIDUAL
Beneficiary statement narrative
Remitter Name will be visible in Beneficiary's bank statement. The statement narrative in this corridor also depends on other factors so it might not be the same for all transactions.
Network participant
Bank
Channels
All major banks in India. List available.
Proof of payment
Upon request, Proof of Payment for a transaction can be made available.
Notes
Proxy Value is validated before initiation of a payment
Value for proxy type should be VPA
Trade purpose codes are not supported. List of trade purpose codes - IR01801; IR01802; IR01803; IR01804; IR01805; IR01806; IR01807; IR01808; IR01809; IR01810; IR018011; IR014; IR020
Payments made to a proxy categorised as a business might see reduced success rates due to validations in place by the beneficiary bank
Mandatory data requirements
Remitter
- Remitter Name
- Remitter Identification Type
- Remitter Account Type
- Remitter Country Code
- Remitter Identification Number
- Remitter Purpose Code
- Remitter Address
- Remitter City
Beneficiary
- Beneficiary Name
- Beneficiary Account Type
- Beneficiary Country Code
Other
Payout Method - PROXY
Proxy Type (VPA)
Proxy Value (UPI Address)
Supporting documents
- Remitter Beneficiary Relationship
Beneficiary account type
INDIVIDUAL
Supported currencies
Cutoff & delivery timing
Same-day processing subject to cutoff of 7:30 UTC
Scroll horizontally to compare supported modes
| Transaction limit per end-user | B2B | B2P | P2P | P2B |
|---|---|---|---|---|
| + Max | No limit | No limit | No limit | No limit |
| − Min | INR 1,500,000 | INR 1,500,000 | INR 1,500,000 | INR 1,500,000 |
Route details
Select a supported mode
Beneficiary statement narrative
Ultimate Sender Name and narrative details will be passed as part of pacs.008 message to beneficiary bank. Details available on beneficiary statement will be dependent on beneficiary bank.
Network participant
Bank
Channels
All major banks enabled with SWIFT
Routing code
IFSC Code
Proof of payment
pacs.008 can be considered as a proof of payment and can be provided on request
Notes
For WIRES, NIUM supports transactions with SHA Fee Type
Mandatory data requirements
Remitter
- Remitter Name
- Remitter Account Type
- Remitter Identification Type
- Remitter Identification Number
- Remitter Address
- Remitter Country code
- Remit Purpose Code
Beneficiary
- Beneficiary Name
- Beneficiary Account Number
- Beneficiary Account Type
- Beneficiary Country Code
- Beneficiary Address
- Beneficiary City
- Beneficiary Postcode
Routing
- Routing Code Type 1 - IFSC CODE
- Routing Code Value
Supporting documents
- Remitter Beneficiary Relationship
- Nature of Business
- Duration of Contract
- Commercial Agreement
- Current Invoice
Beneficiary account type
CORPORATE
Beneficiary statement narrative
Ultimate Sender Name and narrative details will be passed as part of pacs.008 message to beneficiary bank. Details available on beneficiary statement will be dependent on beneficiary bank.
Network participant
Bank
Channels
All major banks enabled with SWIFT
Routing code
IFSC Code
Proof of payment
pacs.008 can be considered as a proof of payment and can be provided on request
Notes
For WIRES, NIUM supports transactions with SHA Fee Type
Mandatory data requirements
Remitter
- Remitter Name
- Remitter Account Type
- Remitter Identification Type
- Remitter Identification Number
- Remitter Address
- Remitter Country code
- Remit Purpose Code
Beneficiary
- Beneficiary Name
- Beneficiary Account Number
- Beneficiary Account Type
- Beneficiary Country Code
- Beneficiary Address
- Beneficiary City
- Beneficiary Postcode
Routing
- Routing Code Type 1 - IFSC CODE
- Routing Code Value
Supporting documents
- Remitter Beneficiary Relationship
- Nature of Business
- Duration of Contract
- Commercial Agreement
- Current Invoice
Beneficiary account type
INDIVIDUAL
Beneficiary statement narrative
Ultimate Sender Name and narrative details will be passed as part of pacs.008 message to beneficiary bank. Details available on beneficiary statement will be dependent on beneficiary bank.
Network participant
Bank
Channels
All major banks enabled with SWIFT
Routing code
IFSC Code
Proof of payment
pacs.008 can be considered as a proof of payment and can be provided on request
Notes
For WIRES, NIUM supports transactions with SHA Fee Type
Mandatory data requirements
Remitter
- Remitter Name
- Remitter Account Type
- Remitter Identification Type
- Remitter Identification Number
- Remitter Address
- Remitter Country code
- Remit Purpose Code
Beneficiary
- Beneficiary Name
- Beneficiary Account Number
- Beneficiary Account Type
- Beneficiary Country Code
- Beneficiary Address
- Beneficiary City
- Beneficiary Postcode
Routing
- Routing Code Type 1 - IFSC CODE
- Routing Code Value
Supporting documents
- Remitter Beneficiary Relationship
Beneficiary account type
INDIVIDUAL
Beneficiary statement narrative
Ultimate Sender Name and narrative details will be passed as part of pacs.008 message to beneficiary bank. Details available on beneficiary statement will be dependent on beneficiary bank.
Network participant
Bank
Channels
All major banks enabled with SWIFT
Routing code
IFSC Code
Proof of payment
pacs.008 can be considered as a proof of payment and can be provided on request
Notes
For WIRES, NIUM supports transactions with SHA Fee Type
Mandatory data requirements
Remitter
- Remitter Name
- Remitter Account Type
- Remitter Identification Type
- Remitter Identification Number
- Remitter Address
- Remitter Country code
- Remit Purpose Code
Beneficiary
- Beneficiary Name
- Beneficiary Account Number
- Beneficiary Account Type
- Beneficiary Country Code
- Beneficiary Address
- Beneficiary City
- Beneficiary Postcode
Routing
- Routing Code Type 1 - IFSC CODE
- Routing Code Value
Supporting documents
- Remitter Beneficiary Relationship
- Nature of Business
- Duration of Contract
- Commercial Agreement
- Current Invoice
Beneficiary account type
CORPORATE
Supported currencies
Cutoff & delivery timing
Same-day processing subject to cutoff of 07:30 UTC
Scroll horizontally to compare supported modes
| Transaction limit per end-user | B2B | B2P | P2P | P2B |
|---|---|---|---|---|
| + Max | No limit | No limit | No limit | No limit |
| − Min | Not specified | Not specified | Not specified | Not specified |
Route details
Select a supported mode
Beneficiary statement narrative
Ultimate Sender Name and narrative details will be passed as part of pacs.008 message to beneficiary bank. Details available on beneficiary statement will be dependent on beneficiary bank.
Network participant
Bank
Channels
All SWIFT enabled banks in the country
Routing code
SWIFT
Proof of payment
pacs.008 can be considered as a proof of payment and can be provided on request
Notes
WIRES can be sent to all countries except for OFAC listed.
pacs.008 can be provided on request.
AUD · CHF · EUR · GBP · HKD · JPY · NZD · SGD · USD only
NIUM does not support OUR charge type for CAD currency WIRES
Processing of payments to Crimea, Donetsk, Luhansk, Sevastopol regions of Ukraine is prohibited. This list is subject to change.
CAD only
For foreign currency wire currencies USD, EUR, GBP - NIUM supports both OUR and SHA fee type while for other currencies AUD, CAD, CHF, JPY, NZD, HKD, SGD - NIUM supports only SHA fee type
Mandatory data requirements
Remitter
- Remitter Name
- Remitter Account Type
- Remitter Identification Type
- Remitter Identification Number
- Remitter Address
- Remitter Country Code
- Remit Purpose Code
Beneficiary
- Beneficiary Name
- Beneficiary Account Type
- Beneficiary Account Number
- Beneficiary Country Code
- Beneficiary Address
- Beneficiary City
- Beneficiary Postcode
- Beneficiary Address (Recommended)
- Beneficiary City (Recommended)
- Beneficiary Postcode (Recommended)
Routing
- Routing Code Value 1
- Routing Code Type 1 - SWIFT Code
Supporting documents
- Remitter Beneficiary Relationship
- Nature of Business
- Duration of Contract
- Commercial Agreement
- Current Invoice
Beneficiary account type
CORPORATE
Beneficiary statement narrative
Ultimate Sender Name and narrative details will be passed as part of pacs.008 message to beneficiary bank. Details available on beneficiary statement will be dependent on beneficiary bank.
Network participant
Bank
Channels
All SWIFT enabled banks in the country
Routing code
SWIFT
Proof of payment
pacs.008 can be considered as a proof of payment and can be provided on request
Notes
WIRES can be sent to all countries except for OFAC listed.
pacs.008 can be provided on request.
AUD · CHF · EUR · GBP · HKD · JPY · NZD · SGD · USD only
NIUM does not support OUR charge type for CAD currency WIRES
Processing of payments to Crimea, Donetsk, Luhansk, Sevastopol regions of Ukraine is prohibited. This list is subject to change.
CAD only
For foreign currency wire currencies USD, EUR, GBP - NIUM supports both OUR and SHA fee type while for other currencies AUD, CAD, CHF, JPY, NZD, HKD, SGD - NIUM supports only SHA fee type
Mandatory data requirements
Remitter
- Remitter Name
- Remitter Account Type
- Remitter Identification Type
- Remitter Identification Number
- Remitter Address
- Remitter Country Code
- Remit Purpose Code
Beneficiary
- Beneficiary Name
- Beneficiary Account Type
- Beneficiary Account Number
- Beneficiary Country Code
- Beneficiary Address
- Beneficiary City
- Beneficiary Postcode
- Beneficiary Address (Recommended)
- Beneficiary City (Recommended)
- Beneficiary Postcode (Recommended)
Routing
- Routing Code Value 1
- Routing Code Type 1 - SWIFT Code
Supporting documents
- Remitter Beneficiary Relationship
- Nature of Business
- Duration of Contract
- Commercial Agreement
- Current Invoice
Beneficiary account type
INDIVIDUAL
Beneficiary statement narrative
Ultimate Sender Name and narrative details will be passed as part of pacs.008 message to beneficiary bank. Details available on beneficiary statement will be dependent on beneficiary bank.
Network participant
Bank
Channels
All SWIFT enabled banks in the country
Routing code
SWIFT
Proof of payment
pacs.008 can be considered as a proof of payment and can be provided on request
Notes
WIRES can be sent to all countries except for OFAC listed.
pacs.008 can be provided on request.
AUD · CHF · EUR · GBP · HKD · JPY · NZD · SGD · USD only
NIUM does not support OUR charge type for CAD currency WIRES
Processing of payments to Crimea, Donetsk, Luhansk, Sevastopol regions of Ukraine is prohibited. This list is subject to change.
CAD only
For foreign currency wire currencies USD, EUR, GBP - NIUM supports both OUR and SHA fee type while for other currencies AUD, CAD, CHF, JPY, NZD, HKD, SGD - NIUM supports only SHA fee type
Mandatory data requirements
Remitter
- Remitter Name
- Remitter Account Type
- Remitter Identification Type
- Remitter Identification Number
- Remitter Address
- Remitter Country Code
- Remit Purpose Code
Beneficiary
- Beneficiary Name
- Beneficiary Account Type
- Beneficiary Account Number
- Beneficiary Country Code
- Beneficiary Address
- Beneficiary City
- Beneficiary Postcode
- Beneficiary Address (Recommended)
- Beneficiary City (Recommended)
- Beneficiary Postcode (Recommended)
Routing
- Routing Code Value 1
- Routing Code Type 1 - SWIFT Code
Supporting documents
- Remitter Beneficiary Relationship
Beneficiary account type
INDIVIDUAL
Beneficiary statement narrative
Ultimate Sender Name and narrative details will be passed as part of pacs.008 message to beneficiary bank. Details available on beneficiary statement will be dependent on beneficiary bank.
Network participant
Bank
Channels
All SWIFT enabled banks in the country
Routing code
SWIFT
Proof of payment
pacs.008 can be considered as a proof of payment and can be provided on request
Notes
WIRES can be sent to all countries except for OFAC listed.
pacs.008 can be provided on request.
AUD · CHF · EUR · GBP · HKD · JPY · NZD · SGD · USD only
NIUM does not support OUR charge type for CAD currency WIRES
Processing of payments to Crimea, Donetsk, Luhansk, Sevastopol regions of Ukraine is prohibited. This list is subject to change.
CAD only
For foreign currency wire currencies USD, EUR, GBP - NIUM supports both OUR and SHA fee type while for other currencies AUD, CAD, CHF, JPY, NZD, HKD, SGD - NIUM supports only SHA fee type
Mandatory data requirements
Remitter
- Remitter Name
- Remitter Account Type
- Remitter Identification Type
- Remitter Identification Number
- Remitter Address
- Remitter Country Code
- Remit Purpose Code
Beneficiary
- Beneficiary Name
- Beneficiary Account Type
- Beneficiary Account Number
- Beneficiary Country Code
- Beneficiary Address
- Beneficiary City
- Beneficiary Postcode
- Beneficiary Address (Recommended)
- Beneficiary City (Recommended)
- Beneficiary Postcode (Recommended)
Routing
- Routing Code Value 1
- Routing Code Type 1 - SWIFT Code
Supporting documents
- Remitter Beneficiary Relationship
- Nature of Business
- Duration of Contract
- Commercial Agreement
- Current Invoice
Beneficiary account type
CORPORATE
Supported currencies
Cutoff & delivery timing
1. 24x7 Availability
2. Real-time for Fast fund Enabled (Details on fast-fund enabled countries available on request)
3. T+2 for other countries
Scroll horizontally to compare supported modes
| Transaction limit per end-user | B2B | B2P | P2P | P2B |
|---|---|---|---|---|
| + Max | USD 50,000 | USD 50,000 | USD 2,500 | USD 50,000 |
| − Min | Not specified | Not specified | Not specified | Not specified |
Route details
Select a supported mode
Network participant
VISA
Notes
For more information, please contact your NIUM account manager team. Additional information and approval from VISA is required before this payout method can be made available.
Origination of funds is allowed only from a set of countries as mentioned in the table below.
In case the transaction currency does not match the destination card issuer currency, amount will be converted and credited in currency of the card issuer.
In few countries, only few banks may allow the transactions.
Below additional daily/monthly/yearly limits applicable for P2P transactions whichever reached first Per Day - 30 transactions or USD 10,000 per Beneficiary card Per Week - 50 transactions or USD 25,000 per Beneficiary card Per Month - 150 transactions or USD 50,000 per Beneficiary card.
Below additional daily/monthly/yearly limits applicable for B2P/B2B transactions whichever reached first Per Day - 30 transactions or USD 50,000 per Beneficiary card Per Week - 50 transactions or USD 100,000 per Beneficiary card Per Month - 150 transactions or USD 200,000 per Beneficiary card.
Mandatory data requirements
Remitter
- Remitter Name
- Remitter Identification Type
- Remitter Identification Number
- Remitter Country Code
Beneficiary
- Beneficiary Card Number
- Beneficiary Name
- Beneficiary Country Code
Beneficiary account type
CORPORATE
Network participant
VISA
Notes
For more information, please contact your NIUM account manager team. Additional information and approval from VISA is required before this payout method can be made available.
Origination of funds is allowed only from a set of countries as mentioned in the table below.
In case the transaction currency does not match the destination card issuer currency, amount will be converted and credited in currency of the card issuer.
In few countries, only few banks may allow the transactions.
Below additional daily/monthly/yearly limits applicable for P2P transactions whichever reached first Per Day - 30 transactions or USD 10,000 per Beneficiary card Per Week - 50 transactions or USD 25,000 per Beneficiary card Per Month - 150 transactions or USD 50,000 per Beneficiary card.
Below additional daily/monthly/yearly limits applicable for B2P/B2B transactions whichever reached first Per Day - 30 transactions or USD 50,000 per Beneficiary card Per Week - 50 transactions or USD 100,000 per Beneficiary card Per Month - 150 transactions or USD 200,000 per Beneficiary card.
Mandatory data requirements
Remitter
- Remitter Name
- Remitter Identification Type
- Remitter Identification Number
- Remitter Country Code
Beneficiary
- Beneficiary Card Number
- Beneficiary Name
- Beneficiary Country Code
Beneficiary account type
INDIVIDUAL
Network participant
VISA
Notes
For more information, please contact your NIUM account manager team. Additional information and approval from VISA is required before this payout method can be made available.
Origination of funds is allowed only from a set of countries as mentioned in the table below.
In case the transaction currency does not match the destination card issuer currency, amount will be converted and credited in currency of the card issuer.
In few countries, only few banks may allow the transactions.
Below additional daily/monthly/yearly limits applicable for P2P transactions whichever reached first Per Day - 30 transactions or USD 10,000 per Beneficiary card Per Week - 50 transactions or USD 25,000 per Beneficiary card Per Month - 150 transactions or USD 50,000 per Beneficiary card.
Below additional daily/monthly/yearly limits applicable for B2P/B2B transactions whichever reached first Per Day - 30 transactions or USD 50,000 per Beneficiary card Per Week - 50 transactions or USD 100,000 per Beneficiary card Per Month - 150 transactions or USD 200,000 per Beneficiary card.
Mandatory data requirements
Remitter
- Remitter Name
- Remitter Identification Type
- Remitter Identification Number
- Remitter Country Code
Beneficiary
- Beneficiary Card Number
- Beneficiary Name
- Beneficiary Country Code
Beneficiary account type
INDIVIDUAL
Network participant
VISA
Notes
For more information, please contact your NIUM account manager team. Additional information and approval from VISA is required before this payout method can be made available.
Origination of funds is allowed only from a set of countries as mentioned in the table below.
In case the transaction currency does not match the destination card issuer currency, amount will be converted and credited in currency of the card issuer.
In few countries, only few banks may allow the transactions.
Below additional daily/monthly/yearly limits applicable for P2P transactions whichever reached first Per Day - 30 transactions or USD 10,000 per Beneficiary card Per Week - 50 transactions or USD 25,000 per Beneficiary card Per Month - 150 transactions or USD 50,000 per Beneficiary card.
Below additional daily/monthly/yearly limits applicable for B2P/B2B transactions whichever reached first Per Day - 30 transactions or USD 50,000 per Beneficiary card Per Week - 50 transactions or USD 100,000 per Beneficiary card Per Month - 150 transactions or USD 200,000 per Beneficiary card.
Mandatory data requirements
Remitter
- Remitter Name
- Remitter Identification Type
- Remitter Identification Number
- Remitter Country Code
Beneficiary
- Beneficiary Card Number
- Beneficiary Name
- Beneficiary Country Code
Beneficiary account type
CORPORATE