Is the BIC for Chase Bank’s custody services (e.g., J.P. Morgan Securities LLC) the same as its retail banking BIC?

When sending international wire transfers to Chase Bank’s custody services—such as J.P. Morgan Securities LLC—it’s critical to use the correct BIC (Bank Identifier Code). The BIC for Chase’s custody and institutional services is *CHASUS33*, while its retail banking division uses *CHASUS33XXX* or other branch-specific suffixes. Though both fall under JPMorgan Chase & Co., custody operations require distinct BICs to ensure funds route accurately through correspondent networks and avoid costly delays or returns.

Misusing the retail BIC for institutional custody accounts often triggers rejection by intermediary banks or extended processing times—especially for securities-related settlements, fund transfers, or pension disbursements. Remittance providers must verify the exact BIC with the beneficiary or consult Chase’s official institutional wire instructions before initiating payments.

For compliance and speed, always confirm whether the recipient is using Chase’s Custody & Fund Services division versus a standard checking or savings account. Using *CHASUS33* (without suffix) is typically correct for J.P. Morgan Securities LLC transactions, whereas *CHASUS33XXX* applies to general retail wires.

Double-checking BICs reduces failed transfers, lowers correction fees, and strengthens client trust—key advantages in competitive remittance markets. Stay precise, stay compliant, and optimize cross-border settlement efficiency.

How frequently does Chase Bank update or re-register its BIC with SWIFT, and where is that published?

For remittance businesses relying on Chase Bank for international transfers, understanding BIC (Bank Identifier Code) updates is critical to ensuring transaction accuracy and compliance. Chase Bank’s BIC—CHASUS33—is registered with SWIFT and remains stable unless significant corporate or structural changes occur.

Chase does not routinely “re-register” or update its BIC with SWIFT on a fixed schedule. Instead, SWIFT updates BIC records only when the bank formally requests a change—such as after mergers, rebranding, or branch network adjustments. Historically, Chase’s BIC has remained unchanged for over two decades, reflecting its operational consistency.

All official BIC information—including status, country code, and branch details—is published exclusively in the SWIFT BIC Directory (https://www.swift.com/bic-directory), accessible via subscription or limited free lookups. Remittance providers should verify BICs directly through SWIFT—not third-party sites—to avoid routing errors or delays.

For seamless cross-border payments, integrate real-time BIC validation into your remittance platform using SWIFT’s APIs or certified data feeds. Regularly auditing BICs against the official directory minimizes failed transactions and enhances customer trust. Staying informed ensures your business meets regulatory expectations and maintains high processing efficiency—key advantages in today’s competitive remittance landscape.

Can a wire be rejected solely due to BIC format errors (e.g., lowercase letters or spaces) when sending to Chase?

When sending wire transfers to Chase Bank, remittance businesses must adhere strictly to the Bank Identifier Code (BIC) format requirements. Chase explicitly mandates that BICs be submitted in uppercase letters only—no lowercase characters or extraneous spaces are permitted.

Even minor formatting deviations—such as “chaseus33” instead of “CHASEUS33”, or “CHASE US 33” with spaces—can trigger automatic rejection. Chase’s payment processing systems perform strict syntactic validation and do not normalize or auto-correct BIC entries. This means format errors are treated as invalid data, not just warnings.

Such rejections delay settlement, incur return fees, and damage sender credibility—especially critical for high-volume remittance providers serving time-sensitive international transfers. To prevent avoidable failures, integrate real-time BIC validation into your payment gateway or core remittance platform, ensuring case sensitivity and whitespace checks before submission.

Always verify BICs against SWIFT’s official registry and confirm Chase’s latest formatting guidelines via their Treasury Services documentation. Proactive validation not only reduces operational friction but also strengthens compliance posture and client trust in your remittance service.

Does Chase Bank support BIC-only identification for SEPA Instant Credit Transfers — and if not, why?

Chase Bank does not support BIC-only identification for SEPA Instant Credit Transfers (SCT Inst). As a U.S.-based bank, Chase is not a participant in the SEPA scheme and lacks a SEPA creditor identifier or direct connectivity to the Eurosystem’s TARGET Instant Payment Settlement (TIPS) platform.

This limitation stems from regulatory and infrastructural realities: SEPA requires banks to be established in the European Economic Area (EEA) or adhere to specific EU banking regulations—criteria Chase does not meet. Consequently, Chase customers cannot initiate SCT Inst payments using only a BIC; they must route transfers via correspondent banks or third-party fintech partners that *are* SEPA-compliant.

For remittance businesses serving U.S.-to-Eurozone corridors, this means additional processing steps, potential delays, and higher fees when leveraging Chase as an originator bank. To ensure true instant, low-cost EUR transfers, partnering with SEPA-licensed institutions—or using specialized cross-border platforms with embedded SEPA infrastructure—is strongly advised.

Staying informed about bank-specific SEPA capabilities helps remittance providers optimize speed, compliance, and cost. Always verify real-time payment eligibility directly with your banking partner—and consider integrating with SEPA-ready gateways to deliver seamless, sub-10-second EUR transfers to end beneficiaries.

How do fintechs or neobanks partnering with Chase (e.g., for sponsored banking) reference Chase’s BIC in their disclosures?

When fintechs or neobanks partner with JPMorgan Chase for sponsored banking—especially in cross-border remittances—they must comply with global payment standards, including accurate SWIFT/BIC referencing. Chase’s official BIC is CHASUS33, and it must be used *only* when funds are routed directly through Chase’s correspondent banking infrastructure.

However, most neobank-Chase partnerships operate under a program bank model, where the fintech is the regulated money transmitter, and Chase serves as the deposit-holding and settlement bank—not the originating or intermediary bank. In such cases, disclosing CHASUS33 as the “sending bank” BIC is misleading and non-compliant with SWIFT guidelines and FinCEN requirements. Instead, disclosures should clarify Chase’s role (e.g., “Funds held at JPMorgan Chase Bank, N.A., BIC: CHASUS33”) without implying Chase initiates or processes the remittance.

Accurate BIC usage builds trust with regulators and recipients—and avoids delays or returns from intermediary banks. Remittance businesses leveraging Chase-sponsored programs should audit all customer-facing disclosures, API documentation, and compliance manuals to ensure precise, transparent language around banking partners. When in doubt, consult Chase’s Sponsored Banking Compliance Team and retain legal counsel familiar with OFAC, FATF, and ISO 20022 standards.

In multi-currency accounts held at Chase, is the same BIC used regardless of the settlement currency (USD, EUR, GBP)?

When sending international payments to multi-currency accounts at JPMorgan Chase, remittance businesses often wonder whether the BIC (Bank Identifier Code) changes based on the settlement currency—USD, EUR, or GBP. The answer is clear: Chase uses the *same BIC*—CHASUS33—for all multi-currency accounts, regardless of the currency held or settled. This simplifies operational workflows and reduces reconciliation errors across cross-border transactions.

This consistency benefits remittance providers by eliminating the need to maintain separate routing instructions per currency. Whether funding a USD-denominated balance or settling in EUR or GBP, clients can rely on CHASUS33 as the universal identifier for Chase’s U.S. operations. Note that while the BIC remains constant, the corresponding account number and currency-specific details (e.g., IBAN for EUR/GBP) must still be accurately provided to ensure swift processing and avoid returns.

For compliance and efficiency, always verify recipient account details—including correct currency designation—before initiating transfers. Leveraging Chase’s unified BIC streamlines integration with payment gateways and ERP systems, supporting scalable, low-friction remittances. Partnering with banks offering such standardization helps remittance firms reduce overhead, improve SLA adherence, and enhance customer trust in global payout accuracy.

Where does Chase Bank list its legally registered BIC in official regulatory filings (e.g., FDIC certificate, OCC reports)?

For remittance businesses sending international wire transfers to Chase Bank, accurately identifying the bank’s legally registered BIC (Bank Identifier Code), also known as SWIFT code, is critical for compliance and transaction success. Chase Bank’s official BIC—CHASUS33—is consistently listed in its primary regulatory filings, including its FDIC Certificate of Deposit Insurance (Certificate #2647) and periodic reports filed with the Office of the Comptroller of the Currency (OCC). These documents are publicly accessible via the FDIC’s BankFind tool and the OCC’s Enforcement Actions & Reports portal.

Unlike internal routing numbers or ABA codes used for domestic transfers, the BIC CHASUS33 is the only code recognized globally under ISO 9362 standards for cross-border payments to JPMorgan Chase & Co. Remittance providers must use this exact code—not variants like CHASUS33XXX—to avoid delays, returns, or compliance flags from intermediary banks.

Verifying the BIC directly through official sources—not third-party directories—helps remittance firms meet FATF and FinCEN due diligence requirements. Always cross-check CHASUS33 against the FDIC’s active institution list and the OCC’s charter documentation to ensure real-time validity. Doing so reduces operational risk, enhances audit readiness, and supports seamless, compliant international payouts to U.S.-based beneficiaries at Chase.

 

 

About Panda Remit

Panda Remit is committed to providing global users with more convenient, safe, reliable, and affordable online cross-border remittance services。
International remittance services from more than 30 countries/regions around the world are now available: including Japan, Hong Kong, Europe, the United States, Australia, and other markets, and are recognized and trusted by millions of users around the world.
Visit Panda Remit Official Website or Download PandaRemit App, to learn more about remittance info.