API changelog
November 2026: Server-assigned funding deadlines and Instant cancellation
TBMC assigns payment-order funding deadlines: Standard orders receive 24 hours and Instant orders receive 15 minutes
from creation. Omit expiresAt from payment and offramp creation requests. The response still includes the deadline.
Existing orders and idempotent retries retain their original deadline. Quote expiry remains the deadline to accept a
quote; a funded order does not expire while awaiting payout.
Instant orders can request cancellation while AWAITING_FUNDS. A 202 response records intent; poll the order for
completion. Cancellation waits for in-flight deposits and compliance clearance. If funding wins before cancellation is
processed, payment continues. A canceled Instant order can register a late deposit for return.
November 2026: Account default fee collection
TBMC can set your account to deduct fees by default. Quotes, payment orders and Auto Routes that do not send
feeCollection then use deducted, and the response shows the collection applied. Sending feeCollection still sets
it per request, and a payment that cites a quote keeps the quote's collection. On a deducting account, a request that
uses the legacy amountUsd without feeCollection: "invoiced" returns 400; send fundingAmountUsd or
payoutAmountUsd. Accounts TBMC has not changed keep invoicing.
November 2026: Explicit quote settlement modes
POST /quotes accepts mode: "instant", "standard", or "auto". Instant requests return an Instant quote or
serviceable: false; they never fall back to Standard. Standard requests price the next netting window. Auto requests
allow automatic selection and Standard fallback. The response mode remains instant or standard; pass it and the
quote id when creating the payment.
New integrations must send a mode. Omitted mode returns 400 unless TBMC has enabled legacy compatibility for the
account. Compatible integrations retain their existing automatic selection and can migrate by sending mode: "auto".
Explicit modes work independently of that compatibility setting. Existing quotes and payments are unchanged. See
Getting started for an example and response handling.
Parents can retrieve a direct child's quote through GET /quotes/{quoteId}?subaccountId={id}, matching quote creation
and rate lookup scope. Foreign child scope returns 403; a quote outside the selected account returns 404.
November 2026: Standard Quotes without a separate capability
Standard Quotes and Instant settlement no longer need their own account capabilities: each is available for the assets
and chains enabled for it on your account. An account without Instant settlement gets a Standard Quote from
POST /quotes. Quote, rate, and supported-asset responses include only the assets, chains, and settlement modes enabled
on your account. Quotes now expire 5 minutes after issue.
GET /account/limits adds maxInstantPaymentUsd, the largest payment that settles Instant, as a decimal string with
four decimal places ("10000.0000"). A larger Auto quote is priced Standard, and a larger Instant quote returns
serviceable: false. The field is absent when the account has no cap.
November 2026: Auto Route payout wallet coins
Creating an Auto Route checks that toAddress is an ACTIVE wallet registered on deliveredChain. It does not check
which coins that wallet can receive. Confirm the wallet accepts deliveredAsset before you create the Auto Route, or
payouts may not arrive. The console now asks for this confirmation before it creates an Auto Route. The API request and
response are unchanged.
November 2026: Payment order payout wallet coins
Creating a payment order checks that toAddress is an ACTIVE wallet registered on toChain. It does not check which
coins that wallet can receive. Confirm the wallet accepts asset before you create the order, or the payout may not
arrive. The API request and response are unchanged.
November 2026: Archive a wallet
POST /users/id/{userId}/wallets/archive retires a registered wallet. Send chain and walletAddress; include
subaccountId for a direct subaccount. The response is 200 { "status": "ARCHIVED" }. Repeating the request succeeds
without another change. Activation in progress or a queued wallet update returns 409; retry after it finishes.
Archived wallets cannot authorize new payments or refunds. Existing ownership and payment history stay available.
Transfers already submitted to a provider can still complete. Re-registering the address under the same user restores it
as PENDING and restarts activation. It must become ACTIVE before it can move funds again. Ownership stays with the
same user.
User reads hide archived wallets by default. GET /users?includeArchived=true includes wallets with status ARCHIVED.
The user remains listed when its last wallet is archived.
November 2026: Account asset permissions
Asset access is configured per account, asset, chain and settlement mode, with separate funding and payout permissions.
GET /supported-assets returns the pairs available to your account. Pass subaccountId to check a direct subaccount. A
subaccount inherits its parent's permissions unless it has separate permissions. Newly supported pairs require account
enablement; contact support@bettermoney.com to request access.
Access changes apply to new requests and deposits that have not yet been accepted. Accepted work continues processing. See Getting started for integration guidance.
November 2026: Funding and payout support by settlement mode
Each GET /supported-assets entry now carries funding and payout, each with instant and standard booleans. They
report whether your account can fund a payment with the pair, or deliver it to a recipient, in each settlement mode.
instant is false throughout for an account without Instant payments.
October 2026: Update a user by id
PATCH /users/id/{userId} updates a user's label, location, or returnWallets. Omitted fields keep their values,
and the changes apply together or not at all. The user keeps its id, wallets, and payment history. location and
returnWallets follow the rules of POST /add-user-record, which still registers and updates users by label. Pass
subaccountId to update a subaccount user. The response has the same shape as GET /users/{label}.
A new label must be unique in the account; a label already in use returns 409, as does an update still processing for
the user. Labels starting with sandbox- are reserved, and sandbox users cannot be renamed: both return 400.
GET /users/id/{userId} reads a user by id. GET /users/{label} is unchanged.
A label may be empty. Address a user with an empty label as /users/, and pass label= to GET /external-accounts.
Registration, reads, and bank-account routes accept the empty label.
October 2026: Sandbox payment limit
A sandbox account cannot make a single payment above $1,000. Quotes and payment orders above that amount return 403.
An Auto Route deposit above it is held. GET /account/limits reports a maxTxUsd of $1,000 or lower for a sandbox
account.
October 2026: Travel Rule beneficiary collection
Enabled accounts provide beneficiary when creating payments of $3,000 or more between different users, and when
creating Auto Routes. Individual and business beneficiaries use location.country and location.subdivision for
residence and registration respectively. Hosted wallets require the wallet provider's legalEntityIdentifier.
Use GET /travel-rule/requirements to check the account policy and GET /travel-rule/vasps to search wallet providers.
Payment order details include the saved beneficiary and information-sharing status under travelRule. See the
Travel Rule guide.
October 2026: Subaccount rates
GET /quotes/rates accepts an optional subaccountId query parameter naming a direct subaccount. The list then uses
that subaccount's own capabilities, asset entitlements, and fees. An id that is not one of your subaccounts returns
403. Requests without the parameter are unchanged.
October 2026: Receive instant settlement
POST /rulesets accepts an optional forceInstant boolean when mode is INSTANT. The default is false. When it is
true, a deposit waits for instant settlement if the corridor or pool is unavailable. The Auto Route create, list, and
by-id responses return the stored setting. Creating any INSTANT Auto Route requires a configured delivery asset and an
operational wallet on its delivery chain.
GET /rulesets/:id/deposits can return PENDING for a deposit waiting for instant settlement. Clients that validate
status values against a fixed list must accept PENDING.