Create an Account
Accounts must be pre-registered to transact on the Tesser platform. Registering accounts in advance of transacting enables wallet risk assessment and helps meet regulatory requirements.
Account creation
To create an account, submit a request to create a bank, wallet, ledger, or generic account and populate the appropriate fields. Accounts will always belong to the workspace they are created in and can also optionally belong to a tenant or counterparty. See the Accounts overview for more details.
Bank account creation request
Code
The response will provide a unique identifier for the account that can be used when requesting payments or transfers:
Code
Generic Account
A generic account records an account identifier that Tesser stores but does not interpret, such as a customer id at an exchange or an account number at another institution. It has no network, currency, or balance, so it never holds assets.
Create one with POST /v1/accounts/generic:
Code
Code
- Owner: exactly one of
tenant_idorcounterparty_idis required. Sending neither (accounts-3027) or both (accounts-3000) returns400. - Number:
generic_account_numberis required, up to 256 characters. Tesser trims surrounding whitespace and keeps the case, soACC-778andacc-778are different numbers. - One account per number: an owner has at most one generic account per number. A duplicate returns
409(accounts-3028), and the error message carries the existing account's id. The existing account may be one Tesser created from an inbound payment's travel-rule data (created_by: "SYSTEM"); use that account instead of creating another. - Immutable number:
PATCH /v1/accounts/:idchanges only thename. Sendinggeneric_account_numberreturns400. To record a different number, create a new generic account. - Funding only: a generic account can be a payment's
funding_account_id, but never the source or destination of a funds movement. Using it as a payment'sfrom_account_idorto_account_id, or as the account of a deposit, withdrawal, or rebalance, returns400(accounts-3029). See Funding Account vs. From Account.
Generic accounts appear in GET /v1/accounts (filter with type=generic) and GET /v1/accounts/:id, with generic_account_number and no assets.
Associating wallets and ledgers with a tenant or counterparty
A wallet or ledger can optionally belong to either a counterparty or tenant in addition to the workspace.
- Do not specify a tenant or counterparty if you want the wallet or ledger to be used in a fully omnibus manner, where funds are commingled across all of your customers. Upon onboarding, your organization will be provisioned with a wallet or ledger that only belongs to your workspace. You may create additional wallets or ledgers that only belong to the workspace as needed.
- Create a wallet or ledger that belongs to a tenant to manage proprietary funds belonging to that tenant, or to commingle funds belonging to that tenant's customers (e.g. originators and/or beneficiaries).
- Create a wallet or ledger that belongs to a counterparty to fully segregate funds only for that counterparty.
For more information on the relationship between accounts and counterparties, see the Accounts overview.