Each account can have multiple account and routing numbers. We recommend that you use a set per vendor. This is similar to how you use different passwords for different websites. Account numbers can also be used to seamlessly reconcile inbound payments. Generating a unique account number per vendor ensures you always know the originator of an incoming payment.
Fields
id- The Account Number identifier.account_id- The identifier for the account this Account Number belongs to.account_number- The account number.created_at- The ISO 8601 time at which the Account Number was created.idempotency_key- The idempotency key you chose for this object. This value is unique across Increase and is used to ensure that a request is only processed once. Learn more about idempotency.inbound_ach- Properties related to how this Account Number handles inbound ACH transfers.inbound_checks- Properties related to how this Account Number should handle inbound check withdrawals.name- The name you choose for the Account Number.routing_number- The American Bankers' Association (ABA) Routing Transit Number (RTN).status- This indicates if payments can be made to the Account Number.type- A constant representing the object's type. For this resource it will always beaccount_number.
Summary
Types
@type t() :: %Increase.AccountNumbers.AccountNumber{ account_id: String.t(), account_number: String.t(), created_at: DateTime.t(), id: String.t(), idempotency_key: String.t() | nil, inbound_ach: Increase.AccountNumbers.AccountNumber.InboundACH.t(), inbound_checks: Increase.AccountNumbers.AccountNumber.InboundChecks.t(), name: String.t(), routing_number: String.t(), status: String.t(), type: String.t() }