Is HNBKUS3N a valid SWIFT code?

Yes. HNBKUS3N has the right format and is in our directory for HUA NAN COMMERCIAL BANK, LTD.. Confirm with the beneficiary that it is the bank that holds their account.

What is the difference between HNBKUS3N and HNBKUS3NXXX?

None. HNBKUS3N is the 8-character form of HNBKUS3NXXX; XXX at the end means the head office. Either works.

SWIFT/BIC · United States

HNBKUS3N

HUA NAN COMMERCIAL BANK, LTD. · Head office

Code details

SWIFT/BIC: HNBKUS3N (HNBKUS3NXXX)
Institution: HUA NAN COMMERCIAL BANK, LTD.
Office: Head office
Branch code: XXX · head office
Country: United States

What HNBKUS3N means

HNBKUS3NXXX

HNBKBank code
Four letters chosen by the institution.
USCountry code
United States (ISO 3166)
3NLocation code
Where the institution sits on the SWIFT network. A 1 in second place marks a passive participant.
XXXBranch code
XXX, or nothing at all, means the head office.

Paying an account at this bank

United States does not use IBAN: send the beneficiary’s local account number with this code. Check an IBAN →

Questions

Is HNBKUS3N a valid SWIFT code?: Yes. HNBKUS3N has the right format and is in our directory for HUA NAN COMMERCIAL BANK, LTD.. Confirm with the beneficiary that it is the bank that holds their account.
What is the difference between HNBKUS3N and HNBKUS3NXXX?: None. HNBKUS3N is the 8-character form of HNBKUS3NXXX; XXX at the end means the head office. Either works.

Sending to HNBKUS3N?

TrillioniPay shows the fee and the rate before you confirm, and the day the money should land.

Join the waiting list When will it arrive?

About this data

Codes are checked against our directory of banks on TrillioniPay corridors. Always confirm the code with the beneficiary’s bank before sending a payment. Last updated: 23 September 2026.

Institution names and addresses: Global Legal Entity Identifier Foundation (GLEIF) LEI data, available under CC0. The address is the legal entity’s registered or head-office address, which can differ from the office SWIFT lists.

SWIFT © and database rights August 2026. All rights reserved. This Mapping Table has been developed by SWIFT. Any use of the Mapping Table, in whole or in part, is subject to the BIC/LEI Mapping Table License Agreement as published with the Mapping Table available on GLEIF's website. The Mapping Table is updated monthly. For the latest BIC information and updates, always refer to www.swift.com/bic .