Is EBAYUS66 a valid SWIFT code?

Yes. EBAYUS66 has the right format and is in our directory for EBAY INC., SAN JOSE. Confirm with the beneficiary that it is the bank that holds their account.

What is the difference between EBAYUS66 and EBAYUS66XXX?

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

SWIFT/BIC · United States

EBAYUS66

EBAY INC. · Head office · SAN JOSE

Code details

SWIFT/BIC: EBAYUS66 (EBAYUS66XXX)
Institution: EBAY INC.
Office: Head office
Branch code: XXX · head office
Address: 2025 HAMILTON AVENUE, 95125 SAN JOSE
City: SAN JOSE
Country: United States

What EBAYUS66 means

EBAYUS66XXX

EBAYBank code
Four letters chosen by the institution.
USCountry code
United States (ISO 3166)
66Location 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 EBAYUS66 a valid SWIFT code?: Yes. EBAYUS66 has the right format and is in our directory for EBAY INC., SAN JOSE. Confirm with the beneficiary that it is the bank that holds their account.
What is the difference between EBAYUS66 and EBAYUS66XXX?: None. EBAYUS66 is the 8-character form of EBAYUS66XXX; XXX at the end means the head office. Either works.

Sending to EBAYUS66?

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 .