Skip to main content
POST
Tokenize raw bank account data

Authorizations

Authorization
string
header
required

Basic authentication header of the form Basic <encoded-value>, where <encoded-value> is the base64-encoded string username:password.

Body

application/json

Raw bank account details to tokenize. The endpoint rejects any field not listed here.

subMerchantId
string
required

Submerchant that owns the bank account. Must be active, belong to your product, and have bank account tokenization enabled.

Maximum string length: 100
Pattern: ^[a-zA-Z0-9\-_'.,@&:#%() ]+$
Example:

"jpt-sim-md-1"

accountType
enum<string>
required

Bank account type.

Available options:
checking,
savings
Example:

"checking"

accountHolderName
string
required

Name on the bank account, up to 100 characters. The holder can be a person or a business. Allowed characters: letters, digits, spaces, and - _ ' . , @ & : # % ( ). Accents and look-alike characters are normalized before validation (for example, José becomes Jose).

Maximum string length: 100
Pattern: ^[a-zA-Z0-9\-_'.,@&:#%() ]+$
Example:

"John Doe"

accountNumber
string
required

Bank account number, 4 to 17 digits only.

Required string length: 4 - 17
Pattern: ^[0-9]+$
Example:

"12312311"

routingNumber
string
required

9-digit ABA routing number. Must pass the ABA checksum.

Pattern: ^[0-9]{9}$
Example:

"122187238"

Response

Bank account tokenized.

success
boolean

Whether the request was processed successfully.

Example:

true

code
string

Machine-readable result code. See the Error Codes reference.

Example:

"0"

message
string

Human-readable result message.

Example:

"Tokenization success"

data
object

The response payload.