TypeScript SDK — Account Services: Banking & Payments
Link bank accounts and manage payment methods. All methods are on client.accountServices.
See the API specifications for full request/response schemas and the authentication guide for setup.
Methods
addBank
POST /v1/payments/addbank · Authenticated
Links a US bank account for fiat deposits and withdrawals. The request body is validated client-side. The SDK enforces:
accountnumber— required stringrouting— required stringname— required string (account holder name)type— required enum:"checking"or"savings"
Code
This is a POST mutation — never automatically retried. Double-check account details before submitting; linking an incorrect account requires manual correction.
addBankCAD
POST /v1/payments/addbank/cad · Authenticated
Links a Canadian bank account for CAD deposits and withdrawals. The request body is validated client-side. The SDK enforces:
swiftcode— required stringaccountNumber— required stringname— required stringtype— required enum:"checking"or"savings"institutionNumber,branchnnumber— optional strings
Code
Note: The field name
branchnnumber(with double "n") matches the API specification exactly.
listPaymentMethods
POST /v1/payments/methods · Authenticated
Returns all payment methods linked to the account. The response is a wrapper object with balances and banks arrays — not a bare array.
Code
This is a POST mutation — never automatically retried.
listCustodyFeeTransfers
POST /v1/custodyaccountfees · Authenticated
Returns custody fee transfers for custody accounts. The request body accepts an optional timestamp field (bigint or number) for filtering. The response is a bare array.
Code
Tip: Fee amounts are decimal strings. Pass
timestampas a bigint or number to filter results — the API returns records on or after the given timestamp (lower bound, forward paging), not backward.
What's next
- Balances & Account — account details and balance queries
- Withdrawals & Transfers — moving funds
- Request Validation — how client-side validation works