How long does it typically take for an international wire sent *to* Chase using its BIC to settle?

When sending an international wire *to* a Chase Bank account using its BIC (Bank Identifier Code), settlement times typically range from 1 to 5 business days. Factors influencing speed include the origin country, correspondent banking relationships, time zones, and compliance checks—especially for larger or unusual transfers.

Chase does not process incoming international wires on weekends or U.S. federal holidays, so delays often occur if the transfer initiates late in the week or near a holiday. While some corridors (e.g., USD transfers from major financial centers like London or Toronto) may settle in as little as one business day, others—particularly those involving currency conversion or less-connected jurisdictions—can take the full 3–5 days.

For remittance businesses, transparency around these timelines is essential. Clearly communicating realistic settlement expectations helps reduce customer support queries and builds trust. Proactively advising clients to verify Chase’s current BIC (CHASUS33), correct routing details, and provide complete beneficiary information minimizes rejections and delays.

While Chase doesn’t offer real-time tracking for incoming wires, partnering with fintech platforms that provide end-to-end visibility can significantly enhance your service level. Always remind senders to retain their SWIFT confirmation number for dispute resolution—and recommend initiating transfers early in the week to avoid weekend holdups.

Are there fees associated with receiving international wires at Chase using its BIC—and who bears them (sender/receiver/both)?

When sending money internationally to a Chase Bank account, understanding wire fee structures is essential for cost-effective remittances. Chase uses its BIC (Bank Identifier Code)—CHASUS33—for incoming international wires, but fees apply regardless of the routing method.

Chase charges a $15 fee for each incoming international wire transfer. This fee is automatically deducted from the recipient’s account upon receipt—meaning the receiver bears this cost. However, the sender may also incur fees: their bank or intermediary banks often levy outgoing or processing fees, which vary by institution and country.

Additionally, currency conversion fees may apply if the transfer is made in a foreign currency. Chase uses its own exchange rate (which includes a margin above the mid-market rate), potentially reducing the final amount received. To maximize value, senders should confirm whether their provider offers transparent FX rates and low or no intermediary fees.

For remittance businesses partnering with U.S. recipients using Chase accounts, advising clients about these layered costs improves transparency and trust. Encouraging senders to request “SHA” (shared) fee allocation—or “BEN” (beneficiary-borne) clarity upfront—helps avoid surprises. Optimizing for total landed cost—not just the headline transfer fee—delivers better client outcomes and competitive differentiation.

Does Chase publish its BIC on official regulatory filings (e.g., FFIEC, SWIFT), and where can it be independently verified?

For remittance businesses sending funds to JPMorgan Chase accounts, verifying the correct Bank Identifier Code (BIC) — also known as SWIFT code — is critical for transaction accuracy and compliance. Chase does publish its official BIC (CHASUS33) in multiple authoritative regulatory and industry sources.

The BIC CHASUS33 is listed on the SWIFT directory (swift.com), the definitive global registry for financial institution identifiers. It’s also disclosed in Chase’s FFIEC Call Reports and Thrift Financial Reports, publicly accessible via the FFIEC’s Data Download Program and the Federal Reserve’s public filings — all independently verifiable by regulators, auditors, and licensed money transmitters.

Remittance providers must ensure their systems use CHASUS33 — not outdated or generic variants — to avoid delays, returns, or AML red flags. Cross-checking against SWIFT’s official site or the FFIEC database adds a layer of due diligence required under FinCEN guidelines and state MSB licensing rules.

While Chase’s website displays the BIC prominently in its wire instructions, regulatory filings provide third-party validation essential for compliance documentation. Always confirm live status via swift.com/BIC or FFIEC.gov before onboarding new payout corridors involving Chase.

Can Chase customers request a *custom* or *sub-BIC* for treasury or corporate payment processing?

Chase customers—especially treasury and corporate clients—often ask whether they can request a *custom* or *sub-BIC* for streamlined payment processing. The short answer is: **no**, Chase does not assign custom or sub-BIC codes to individual clients. BIC (Bank Identifier Code), also known as SWIFT code, is standardized globally by SWIFT and assigned per legal entity or branch—not per client or department. Chase’s official BIC is CHASUS33, with possible branch-specific extensions (e.g., CHASUS33XXX), but these are pre-defined and not customizable.

For remittance businesses supporting corporate clients using Chase, this means payments must route through Chase’s central BIC infrastructure. However, Chase offers robust alternatives—including structured payment references (ISO 20022 fields), unique account numbering, and API-driven treasury platforms—to enhance traceability and reconciliation without needing sub-BICs.

Understanding this limitation helps remittance providers set accurate client expectations and design compliant, efficient workflows. Leveraging Chase’s supported identifiers—like UETR (Unique End-to-End Transaction Reference) and enriched remittance data—ensures faster settlement, better compliance, and improved cash flow visibility for global corporate clients.

How does Chase handle intermediary bank routing when a sender uses `CHASUS33` but doesn’t specify a correspondent bank?

When sending international wire transfers to JPMorgan Chase, using the SWIFT/BIC code `CHASUS33` is standard—but what happens if no correspondent (intermediary) bank is specified? Chase automatically routes payments through its preferred correspondent network to ensure swift, compliant processing. Unlike some banks that require manual intermediary selection, Chase leverages pre-established relationships with major global custodians and settlement banks—such as Citi, BNY Mellon, or HSBC—to optimize clearing paths based on destination currency and jurisdiction.

This intelligent routing minimizes delays, reduces rejection risk, and enhances traceability—critical advantages for remittance businesses handling high-volume, time-sensitive cross-border payments. Chase’s internal systems evaluate factors like regulatory requirements, FX settlement efficiency, and real-time liquidity availability before selecting the optimal intermediary, all without sender intervention.

For remittance providers, this means greater predictability in settlement times (often same-day USD credits) and lower operational overhead. However, transparency matters: while Chase doesn’t disclose the specific intermediary in real time, MT103 confirmations include full routing details post-execution. Partnering with Chase via APIs or direct integration further enables automated reconciliation and audit-ready reporting—key for AML compliance and client trust.

 

 

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.