PaymentMethod objects represent the bank account payout methods that offramp orders settle fiat to. Save one with the Create Payment Method endpoint, then reference its paymentMethodId as the recipient when creating an offramp order.
type names the account identifier (the capture schema Crossmint collects and validates) — never the payment rail, scheme, or clearing house. The same saved account can be paid over multiple rails; rail selection happens at payout execution time.
Value
Description
bank-account-us
US bank account (routing number + account number).
bank-account-mx-clabe
Mexican bank account, identified by an 18-digit CLABE (Clave Bancaria Estandarizada).
bank-account-co
Colombian bank account (bank code + account number + national document).
bank-account-sepa-iban
Bank account identified by an IBAN within the supported SEPA scope.
bre-b
Colombian Bre-B key: an @handle, a mobile number, an e-mail, an identity document, or a commerce code.
The person or company that owns the account. Always the value the client sent, never the bank’s record of the holder. Derived from billing when the record predates this field.
Holder address, without a country: the account’s own country is the bank’s jurisdiction. Present only on types that collect one. Never on bank-account-mx-clabe.
Display-only name of the institution holding the CLABE. Absent until the destination lookup answers. Not bankName: a large share of CLABEs are issued by STP and the fintechs that ride on it.