Skip to main content
Jp Morgan Wallet

Reference

Supported branches and their Business Identifier Codes (BICs)

The following table lists the branches that J.P. Morgan Wallet™ supports, along with information like their SWIFT BICs.

A BIC that identifies the branch is required for some types of transactions. For example, to execute a PayOut transaction (send funds from your Wallet DDA to a counterparty's external DDA), you must provide both the BIC of the bank branch where your Wallet DDA is located as well as the BIC of the bank branch where the counterparty's DDA is located.

Note: If there are leading zeros in a value, always include them in API requests.

Branches
ID Name Region Local time zone Type SWIFT BIC
0001 JPMORGAN CHASE BANK, N.A. - OHIO NAMR ET Affiliate CHASUS33XXX
0021 JPMORGAN CHASE BANK, N.A. - MICHIGAN/FLORIDA/GEORGIA NAMR ET Affiliate CHASUS33XXX
0034 JPMORGAN CHASE BANK, N.A. - KENTUCKY NAMR ET Affiliate CHASUS33XXX
0053 JPMORGAN CHASE BANK, N.A. - INDIANA NAMR ET Affiliate CHASUS33XXX
0111 JPMORGAN CHASE BANK, N.A. - ILLINOIS NAMR CT Affiliate CHASUS33XXX
0121 JPMORGAN CHASE BANK, N.A. - WISCONSIN NAMR CT Affiliate CHASUS33XXX
0201 JPMORGAN CHASE BANK, N.A. - TEXAS NAMR CT Affiliate CHASUS33XXX
0501 JPMORGAN CHASE BANK, N.A. - COLORADO NAMR MT Affiliate CHASUS33XXX
0552 JPMORGAN CHASE BANK, N.A. - LOUISIANA NAMR CT Affiliate CHASUS33XXX
0601 JPMORGAN CHASE BANK, N.A. - ARIZONA NAMR MT Affiliate CHASUS33XXX
0602 JPMORGAN CHASE BANK, N.A. - UTAH NAMR MT Affiliate CHASUS33XXX
0613 HONG KONG APAC HKT Regular CHASHKHHXXX
0655 LUXEMBOURG EMEA CET Regular CHASLULXXXX
0662 JPMORGAN CHASE BANK, N.A. - OKLAHOMA NAMR CT Affiliate CHASUS33XXX
0671 LONDON EMEA GMT Regular CHASGB2LXXX
0702 JPMORGAN CHASE BANK, N.A. - NORTHWEST NAMR PT Affiliate CHASUS33XXX
0703 JPMORGAN CHASE BANK, N.A. - SOUTHWEST (including CA) NAMR PT Affiliate CHASUS33XXX
0802 NEW YORK NAMR EST Regular CHASUS33XXX
0836 SYDNEY APAC AEST Regular CHASSGSGXXX
0883 SINGAPORE APAC SST Regular CHASSGSGXXX

Supported account currencies by branch

Each J.P. Morgan branch supports different currencies. Here are some examples of branches and accounts with different currencies that they might have:

  • NY: All accounts must use USD.
  • London: One account with GBP, one account with EUR, etc.
  • Singapore: One account with SGD, one account with JPY, etc.

It is important to check which branches support which currencies so you can plan your Wallet program accordingly. When you make a PayOut transfer from one branch to another, you must first confirm that the creditor branch supports the currency that you are sending.

The following table lists the currencies that each branch supports.

Supported account currencies by branch
Currency US London Luxembourg Singapore Hong Kong Sydney
AED
AUD
BGN
BHD
BWP
CAD
CHF
CNY
CZK
DKK
EUR
GBP
HKD
HRK
HUF
ILS
INR
JPY
KWD
KZT
MAD
MXN
NOK
NZD
OMR
PLN
QAR
RON
RSD
RUB
SAR
SEK
SGD
THB
TND
TRY
UGX
USD
ZAR

Allowed characters

Only characters in the Society for Worldwide Interbank Financial Telecommunication (SWIFT) X character set are allowed in Wallet API requests.

This applies to all parameters for all Wallet endpoints. If you enter an unsupported character in an API request, Wallet rejects the request.

Allowed characters
Characters Description
a-z 26 lowercase letters of the English alphabet
A-Z 26 uppercase letters of the English alphabet
0-9 10 digits
/ Forward slash
-

Hyphen/minus

Note: Cannot be in the first position of a field.

? Question mark
:

Colon

Note: Cannot be in the first position of a field.

( Opening/left parenthesis
) Closing/right parenthesis
. Full stop / period
, Comma
' Apostrophe
+ Plus
Space
@

At sign

Note: Only for email attributes.

{

Opening/left brace

Note: Can only be used to define a tag/field in the beginning of a line.

Example: {59} beneficiary account

}

Closing/right brace

Note: Can only be used to define a tag/field in the beginning of a line.

Example: {59} beneficiary account

CR Carriage return
LF Line feed

End-to-end ID

The end-to-end ID (endToEndIdentification) is a unique identifier that travels through the payment system and can be used to query a transaction.

Wallet integrates with multiple payment systems, and there are limitations to the end-to-end ID based on the system. If you provide an end-to-end ID that does not fulfill the requirements for the payment rail, Wallet rejects the request.

The following table lists the requirements for the end-to-end ID by payment rail.

End-to-end ID requirements by payment type
Payment rail Character limit Supported characters
US ACH 15 Alphanumeric
US ACH FX 35 Uppercase English letters and digits
US Wire 16 Alphanumeric
US RTP 35 Alphanumeric
US PayPal / Venmo 35 Alphanumeric
UK BACS 16 Alphanumeric
UK BACS FX 16 Uppercase English letters and digits
UK Wire 15 Alphanumeric
UK FPS 31 Uppercase English letters and digits
EU SEPA 16 Alphanumeric
EU SEPA FX 16 Uppercase English letters and digits
EU Wire 15 Alphanumeric
EU SEPA Instant 35 Uppercase English letters and digits

Debtor/creditor agent requirements for US payment rails

For US payment rails, your Wallet DDA must be at the J.P. Morgan Chase Bank, New York branch or any of its affiliate US branches.

This means that when you transfer physical funds between your Wallet DDA and an external DDA using a US payment rail, the debtor and creditor agents have certain requirements:

  • PayOut: The debtor agent must be the J.P. Morgan Chase Bank, New York branch or any of its affiliate US branches.
  • PayInto Collection: The creditor agent must be the J.P. Morgan Chase Bank, New York branch or any of its affiliate US branches.

The following table lists the supported bank identifiers for each US payment rail.

Supported bank identifiers for US payment rails
Payment rail Bank identifier
US ACH ABA: 028000024
US Wire
  • ABA: 021000021
  • BIC: CHASUS33XXX (for an affiliate US branch, replace "XXX" with the corresponding code for the branch)
US RTP ABA: 028000024 or 021000021