Skip to content
Flag of India

Asia · INR · 5 routes

Payouts to India

Imported payout availability and route requirements

Payout destination · IN

India

Asia · INR

Supported payout methods

Supported currencies

INR

Cutoff & delivery timing

Instant · 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. · B2B · B2P · P2P · P2B

Transaction limit per end-user B2BB2PP2PP2B
MinINR 1INR 1INR 1INR 1
MaxNot specifiedNot specifiedNot specifiedNot specified

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

FX source

Live Interbank based rates available 24x7, including off-market hours

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

NameAccount TypeAddressCountry Code

BENEFICIARY

NameAccount TypeAccount NumberCountry CodeBank Name

ROUTING

Code Type 1 - IFSC CodeCode Value 1

OTHER

Remit Purpose Code

Supporting documents

Remitter Beneficiary RelationshipNature of BusinessDuration of ContractCommercial AgreementCurrent Invoice

Route source

LOCAL · Business to business · 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

FX source

Live Interbank based rates available 24x7, including off-market hours

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

NameAccount TypeAddressCountry Code

BENEFICIARY

NameAccount TypeAccount NumberCountry CodeBank Name

ROUTING

Code Type 1 - IFSC CodeCode Value 3

OTHER

Remit Purpose Code

Supporting documents

Remitter Beneficiary RelationshipNature of BusinessDuration of ContractCommercial AgreementCurrent Invoice

Route source

LOCAL · Business to person · 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

FX source

Live Interbank based rates available 24x7, including off-market hours

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

NameAccount TypeAddressCountry Code

BENEFICIARY

NameAccount TypeAccount NumberCountry CodeBank Name

ROUTING

Code Type 1 - IFSC CodeCode Value 2

OTHER

Remit Purpose Code

Supporting documents

Remitter Beneficiary RelationshipNature of BusinessDuration of ContractCommercial AgreementCurrent Invoice

Route source

LOCAL · Person to person · 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

FX source

Live Interbank based rates available 24x7, including off-market hours

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

NameAccount TypeAddressCountry Code

BENEFICIARY

NameAccount TypeAccount NumberCountry CodeBank Name

ROUTING

Code Type 1 - IFSC CodeCode Value 4

OTHER

Remit Purpose Code

Supporting documents

Remitter Beneficiary RelationshipNature of BusinessDuration of ContractCommercial AgreementCurrent Invoice

Route source

LOCAL · Person to business · CORPORATE

Supported currencies

INR

Cutoff & delivery timing

Instant · Real Time, 24x7 · B2P · P2P

Transaction limit per end-user B2PP2P
MinNot specifiedNot specified
MaxINR 200,000INR 200,000

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

FX source

Live Interbank based rates available 24x7, including off-market hours

Channels

All major banks in India. List available.

Proof of payment

Upon request, Proof of Payment for a transaction can be made available.

Notes

1. Proxy Value is validated before initiation of a payment

2. Value for proxy type should be VPA

3. Trade purpose codes are not supported. List of trade purpose codes - IR01801; IR01802; IR01803; IR01804; IR01805; IR01806; IR01807; IR01808; IR01809; IR01810; IR018011; IR014; IR020

4. 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

NameIdentification TypeAccount TypeCountry CodeIdentification NumberPurpose CodeAddressCity

BENEFICIARY

NameAccount TypeCountry Code

OTHER

Payout Method - PROXYProxy Type (VPA)Proxy Value (UPI Address)

Supporting documents

Remitter Beneficiary RelationshipNature of BusinessDuration of ContractCommercial AgreementCurrent Invoice

Route source

PROXY · Business to person · 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

FX source

Live Interbank based rates available 24x7, including off-market hours

Channels

All major banks in India. List available.

Proof of payment

Upon request, Proof of Payment for a transaction can be made available.

Notes

1. Proxy Value is validated before initiation of a payment

2. Value for proxy type should be VPA

3. Trade purpose codes are not supported. List of trade purpose codes - IR01801; IR01802; IR01803; IR01804; IR01805; IR01806; IR01807; IR01808; IR01809; IR01810; IR018011; IR014; IR020

4. 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

NameIdentification TypeAccount TypeCountry CodeIdentification NumberPurpose CodeAddressCity

BENEFICIARY

NameAccount TypeCountry Code

OTHER

Payout Method - PROXYProxy Type (VPA)Proxy Value (UPI Address)

Supporting documents

Remitter Beneficiary RelationshipNature of BusinessDuration of ContractCommercial AgreementCurrent Invoice

Route source

PROXY · Person to person · INDIVIDUAL

Supported currencies

INR

Cutoff & delivery timing

T1 · Same-day processing subject to cutoff of 7:30 UTC · B2B · B2P · P2P · P2B

Transaction limit per end-user B2BB2PP2PP2B
MinINR 1,500,000INR 1,500,000INR 1,500,000INR 1,500,000
MaxNot specifiedNot specifiedNot specifiedNot 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

FX source

Live Interbank based rates available 24x7, including off-market hours

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

NameAccount TypeIdentification TypeIdentification NumberAddressCountry code

BENEFICIARY

NameAccount NumberAccount TypeCountry CodeAddressCityPostcode

ROUTING

Code Type 1 - IFSC CODECode Value

OTHER

Remit Purpose Code

Supporting documents

Remitter Beneficiary RelationshipNature of BusinessDuration of ContractCommercial AgreementCurrent Invoice

Route source

LOCAL · Business to business · 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

FX source

Live Interbank based rates available 24x7, including off-market hours

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

NameAccount TypeIdentification TypeIdentification NumberAddressCountry code

BENEFICIARY

NameAccount NumberAccount TypeCountry CodeAddressCityPostcode

ROUTING

Code Type 1 - IFSC CODECode Value

OTHER

Remit Purpose Code

Supporting documents

Remitter Beneficiary RelationshipNature of BusinessDuration of ContractCommercial AgreementCurrent Invoice

Route source

LOCAL · Business to person · 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

FX source

Live Interbank based rates available 24x7, including off-market hours

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

NameAccount TypeIdentification TypeIdentification NumberAddressCountry code

BENEFICIARY

NameAccount NumberAccount TypeCountry CodeAddressCityPostcode

ROUTING

Code Type 1 - IFSC CODECode Value

OTHER

Remit Purpose Code

Supporting documents

Remitter Beneficiary RelationshipNature of BusinessDuration of ContractCommercial AgreementCurrent Invoice

Route source

LOCAL · Person to person · 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

FX source

Live Interbank based rates available 24x7, including off-market hours

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

NameAccount TypeIdentification TypeIdentification NumberAddressCountry code

BENEFICIARY

NameAccount NumberAccount TypeCountry CodeAddressCityPostcode

ROUTING

Code Type 1 - IFSC CODECode Value

OTHER

Remit Purpose Code

Supporting documents

Remitter Beneficiary RelationshipNature of BusinessDuration of ContractCommercial AgreementCurrent Invoice

Route source

LOCAL · Person to business · CORPORATE

Supported currencies

USD EUR SGD GBP AUD CAD HKD JPY CHF NZD

Cutoff & delivery timing

T1 · Same-day processing subject to cutoff of 07:30 UTC · B2B · B2P · P2P · P2B

Transaction limit per end-user B2BB2PP2PP2B
MinNot specifiedNot specifiedNot specifiedNot specified
MaxNot specifiedNot specifiedNot specifiedNot 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.

[{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

FX source

Live Interbank based rates available 24x7, including off-market hours

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.

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.

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

NameAccount TypeIdentification TypeIdentification NumberAddressCountry Code

BENEFICIARY

NameAccount TypeAccount NumberCountry CodeAddressCityPostcodeAddress (Recommended)City (Recommended)Postcode (Recommended)

ROUTING

Code Value 1Code Type 1 - SWIFT Code

OTHER

Remit Purpose Code

Supporting documents

Remitter Beneficiary RelationshipNature of BusinessDuration of ContractCommercial AgreementCurrent Invoice

Route source

SWIFT · Business to business · 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.}]

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

FX source

Live Interbank based rates available 24x7, including off-market hours

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.

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.

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

NameAccount TypeIdentification TypeIdentification NumberAddressCountry Code

BENEFICIARY

NameAccount TypeAccount NumberCountry CodeAddressCityPostcodeAddress (Recommended)City (Recommended)Postcode (Recommended)

ROUTING

Code Value 1Code Type 1 - SWIFT Code

OTHER

Remit Purpose Code

Supporting documents

Remitter Beneficiary RelationshipNature of BusinessDuration of ContractCommercial AgreementCurrent Invoice

Route source

SWIFT · Business to person · 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.

[{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

FX source

Live Interbank based rates available 24x7, including off-market hours

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.

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.

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

NameAccount TypeIdentification TypeIdentification NumberAddressCountry Code

BENEFICIARY

NameAccount TypeAccount NumberCountry CodeAddressCityPostcodeAddress (Recommended)City (Recommended)Postcode (Recommended)

ROUTING

Code Value 1Code Type 1 - SWIFT Code

OTHER

Remit Purpose Code

Supporting documents

Remitter Beneficiary RelationshipNature of BusinessDuration of ContractCommercial AgreementCurrent Invoice

Route source

SWIFT · Person to person · 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.

[{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

FX source

Live Interbank based rates available 24x7, including off-market hours

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.

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.

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

NameAccount TypeIdentification TypeIdentification NumberAddressCountry Code

BENEFICIARY

NameAccount TypeAccount NumberCountry CodeAddressCityPostcodeAddress (Recommended)City (Recommended)Postcode (Recommended)

ROUTING

Code Value 1Code Type 1 - SWIFT Code

OTHER

Remit Purpose Code

Supporting documents

Remitter Beneficiary RelationshipNature of BusinessDuration of ContractCommercial AgreementCurrent Invoice

Route source

SWIFT · Person to business · CORPORATE

Supported currencies

INR

Cutoff & delivery timing

T2 · 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 · B2B · B2P · P2P · P2B

Transaction limit per end-user B2BB2PP2PP2B
MinNot specifiedNot specifiedNot specifiedNot specified
MaxUSD 50,000USD 50,000USD 2,500USD 50,000

Route details

Select a supported mode

Network participant

VISA

FX source

Live Interbank based rates from NIUM are available 24x7, including off-market hours

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

NameIdentification TypeIdentification NumberCountry Code

BENEFICIARY

Card NumberNameCountry Code

Route source

CARD · Business to business · CORPORATE

Network participant

VISA

FX source

Live Interbank based rates from NIUM are available 24x7, including off-market hours

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

NameIdentification TypeIdentification NumberCountry Code

BENEFICIARY

Card NumberNameCountry Code

Route source

CARD · Business to person · INDIVIDUAL

Network participant

VISA

FX source

Live Interbank based rates from NIUM are available 24x7, including off-market hours

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

NameIdentification TypeIdentification NumberCountry Code

BENEFICIARY

Card NumberNameCountry Code

Route source

CARD · Person to person · INDIVIDUAL

Network participant

VISA

FX source

Live Interbank based rates from NIUM are available 24x7, including off-market hours

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

NameIdentification TypeIdentification NumberCountry Code

BENEFICIARY

Card NumberNameCountry Code

Route source

CARD · Person to business · CORPORATE

← All Asia markets