The Bank Account object 

Attributes

• idstring

  Unique identifier for the object.

• account_holder_namenullable string

  The name of the person or business that owns the bank account.

• account_holder_typenullable string

  The type of entity that holds the account. This can be either individual or company.

• bank_namenullable string

  Name of the bank associated with the routing number (e.g., WELLS FARGO).

• countrystring

  Two-letter ISO code representing the country the bank account is located in.

• currencyenum

  Three-letter ISO code for the currency paid out to the bank account.

• customernullable stringExpandable

  The ID of the customer that the bank account is associated with.

• fingerprintnullable string

  Uniquely identifies this particular bank account. You can use this attribute to check whether two bank accounts are the same.

• last4string

  The last four digits of the bank account number.

• metadatanullable associative array

  Set of key-value pairs that you can attach to an object. This can be useful for storing additional information about the object in a structured format.

• routing_numbernullable string

  The routing transit number for the bank account.

More attributes

Collapse all

• objectstring

  String representing the object’s type. Objects of the same type share the same value.

• accountnullable stringExpandableAvailable conditionally

  The account this bank account belongs to. Only applicable on Accounts (not customers or recipients) This property is only available when returned as an External Account where controller.is_controller is true.

• account_typenullable string

  The bank account type. This can only be checking or savings in most countries. In Japan, this can only be futsu or toza.

• available_payout_methodsnullable array of enums

  A set of available payout methods for this bank account. Only values from this set should be passed as the method when creating a payout.

  Possible enum values

  instant

  standard

• statusstring

  For bank accounts, possible values are new, validated, verified, verification_failed, or errored. A bank account that hasn’t had any activity or validation performed is new. If Stripe can determine that the bank account exists, its status will be validated. Note that there often isn’t enough information to know (e.g., for smaller credit unions), and the validation is not always run. If customer bank account verification has succeeded, the bank account status will be verified. If the verification failed for any reason, such as microdeposit failure, the status will be verification_failed. If a payout sent to this bank account fails, we’ll set the status to errored and will not continue to send scheduled payouts until the bank details are updated.

  For external accounts, possible values are new, errored and verification_failed. If a payout fails, the status is set to errored and scheduled payouts are stopped until account details are updated. In the US and India, if we can’t verify the owner of the bank account, we’ll set the status to verification_failed. Other validations aren’t run against external accounts because they’re only used for payouts. This means the other statuses don’t apply.