Skip to content
Flag of Japan

Asia · JPY · 2 routes

Payouts to Japan

Imported payout availability and route requirements

Payout destination · JP

Japan

Asia · JPY

Supported payout methods

Supported currencies

JPY

Cutoff & delivery timing

Instant · Realtime 24x7 · B2B · B2P · P2P · P2B

Transaction limit per end-user B2BB2PP2PP2B
MinJPY 1JPY 1JPY 1JPY 1
MaxJPY 50,000,000JPY 50,000,000JPY 50,000,000JPY 50,000,000

Route details

Select a supported mode

Beneficiary statement narrative

Remitter Name will be visible in the Beneficiary’s Account Statement.

Network participant

Partner

FX source

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

Channels

All banks in Japan supporting Zengin payments

Routing code

Zengin Code

Notes

1. The fields Beneficiary address, Beneficiary identification type & Beneficiary identification value are mandatory for transactions above 1Mn JPY

2. The identification value is expected to be the beneficiary's My Number. My number should be exactly 12 characters if the beneficiary is an individual

3. The beneficiary name in Latin characters is mandatory

4. However it is also advised to additionally send the beneficiary name in Katakana in the beneficiary name local language field as per the beneficiary bank records for best experience

5. Payment speed varies significantly depending on the beneficiary bank. The major banks in Japan process transactions near realtime except for downtimes after 9PM local time. However many banks in Japan have a daily cutoff of 3PM local time and also don't process all the transactions realtime

Mandatory data requirements

REMITTER

NameIdentification TypeIdentification NumberAddressCityPost CodeAccount TypeCountry Code

BENEFICIARY

NameName Local Language(Optional)Account NumberAccount Type

ROUTING

Code Type 1 - SWIFT/ Beneficiary Bank CodeCode Value 1Code Type 2 - Branch CodeCode Value 2

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

Remitter Name will be visible in the Beneficiary’s Account Statement.

Network participant

Partner

FX source

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

Channels

All banks in Japan supporting Zengin payments

Routing code

Zengin Code

Notes

1. The fields Beneficiary address, Beneficiary identification type & Beneficiary identification value are mandatory for transactions above 1Mn JPY

2. The identification value is expected to be the beneficiary's My Number. My number should be exactly 12 characters if the beneficiary is an individual

3. The beneficiary name in Latin characters is mandatory

4. However it is also advised to additionally send the beneficiary name in Katakana in the beneficiary name local language field as per the beneficiary bank records for best experience

5. Payment speed varies significantly depending on the beneficiary bank. The major banks in Japan process transactions near realtime except for downtimes after 9PM local time. However many banks in Japan have a daily cutoff of 3PM local time and also don't process all the transactions realtime

Mandatory data requirements

REMITTER

NameIdentification TypeIdentification NumberAddressCityPost CodeAccount TypeCountry Code

BENEFICIARY

NameName Local Language(Optional)Account NumberAccount Type

ROUTING

Code Type 1 - SWIFT/ Beneficiary Bank CodeCode Value 1Code Type 2 - Branch CodeCode Value 2

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

Remitter Name will be visible in the Beneficiary’s Account Statement.

Network participant

Partner

FX source

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

Channels

All banks in Japan supporting Zengin payments

Routing code

Zengin Code

Notes

1. The fields Beneficiary address, Beneficiary identification type & Beneficiary identification value are mandatory for transactions above 1Mn JPY

2. The identification value is expected to be the beneficiary's My Number. My number should be exactly 12 characters if the beneficiary is an individual

3. The beneficiary name in Latin characters is mandatory

4. However it is also advised to additionally send the beneficiary name in Katakana in the beneficiary name local language field as per the beneficiary bank records for best experience

5. Payment speed varies significantly depending on the beneficiary bank. The major banks in Japan process transactions near realtime except for downtimes after 9PM local time. However many banks in Japan have a daily cutoff of 3PM local time and also don't process all the transactions realtime

Mandatory data requirements

REMITTER

NameIdentification TypeIdentification NumberAddressCityPost CodeAccount TypeCountry Code

BENEFICIARY

NameName Local Language(Optional)Account NumberAccount Type

ROUTING

Code Type 1 - SWIFT/ Beneficiary Bank CodeCode Value 1Code Type 2 - Branch 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

Remitter Name will be visible in the Beneficiary’s Account Statement.

Network participant

Partner

FX source

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

Channels

All banks in Japan supporting Zengin payments

Routing code

Zengin Code

Notes

1. The fields Beneficiary address, Beneficiary identification type & Beneficiary identification value are mandatory for transactions above 1Mn JPY

2. The identification value is expected to be the beneficiary's My Number. My number should be exactly 12 characters if the beneficiary is an individual

3. The beneficiary name in Latin characters is mandatory

4. However it is also advised to additionally send the beneficiary name in Katakana in the beneficiary name local language field as per the beneficiary bank records for best experience

5. Payment speed varies significantly depending on the beneficiary bank. The major banks in Japan process transactions near realtime except for downtimes after 9PM local time. However many banks in Japan have a daily cutoff of 3PM local time and also don't process all the transactions realtime

Mandatory data requirements

REMITTER

NameIdentification TypeIdentification NumberAddressCityPost CodeAccount TypeCountry Code

BENEFICIARY

NameName Local Language(Optional)Account NumberAccount Type

ROUTING

Code Type 1 - SWIFT/ Beneficiary Bank CodeCode Value 1Code Type 2 - Branch CodeCode Value 2

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.

Network participant

Bank

BANK

FX source

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

Channels

All SWIFT enabled banks in the country

All major banks enabled with SWIFT CODE

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

BANK

FX source

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

Channels

All SWIFT enabled banks in the country

All major banks enabled with SWIFT CODE

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

BANK

FX source

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

Channels

All SWIFT enabled banks in the country

All major banks enabled with SWIFT CODE

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

BANK

FX source

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

Channels

All SWIFT enabled banks in the country

All major banks enabled with SWIFT CODE

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

← All Asia markets