Concepts

Stableyard has one anchor object, the account, and everything else attaches to it. Each concept page covers one resource: what it is, its states, the calls that create and read it, and its errors.

Objects

Everything attaches to an account. IDs are prefixed, stable and opaque.

Object	ID prefix	The rule to know
`Account`	`acct_`	`subjectType` is fixed at creation and constrains every rail the account can use.
`PaymentHandle`	`handle_`	Immutable once claimed and never reused. `name@namespace` can resolve to another partner’s account.
`ConnectedWallet`	`wallet_`	`ownershipVerificationStatus` starts `unverified`.
`SettlementProfile`	`settle_`	`status` is `draft`, `active`, `inactive` or `failed`. A new account’s profile is `draft`.
`SettlementDestination`	`destination_`	Bank and rail destinations stay `pending_verification` until verified and cannot be selected before.
`BankAccount`	`bank_account_`	A linked off-ramp destination. Fields vary by country.
`OnrampBankAccount`	`onramp_acct_`	Issued in the customer’s name. Requesting again for the same wallet and asset returns the existing account.
`DepositAddress`	`deposit_addr_`	Reusable, no amount, no expiry. Each inbound transfer becomes a `Deposit` (`deposit_`).
`Payment`	`payment_`	`intent` is `receive` or `send` and never changes.
`Refund`	`refund_`	Each refund is its own record. `refundSummary` on the payment is an aggregate.
`Transaction`	`txn_`	The durable record. Reporting, not a spendable balance.
`Vault`	`vault_`	A charge that breaks the policy fails at the contract, not at a backend check.

Mistakes that cause most integration bugs

Treating a webhook as current state. An event says something changed. Read the resource for what is true now.
Treating provider success as collection. Money is credited only when the expected receipt is independently verified.
Creating a payment to get an address. Use a deposit address for repeated top-ups and a receive payment for one order.
Reading status alone. operationalState says whether a payment needs a retry or a person. See Status codes.
Showing recorded activity as a balance. Transactions and balances are reporting views, not spendable funds.

Accounts

The object every flow starts with.

Lifecycle and status codes

Payment, deposit and refund states, and which are terminal.

Onboarding

Money movement

Automation

Webhooks

Reference data

Concepts

Objects

Mistakes that cause most integration bugs

Accounts

Lifecycle and status codes

​Objects

​Mistakes that cause most integration bugs

Accounts

Lifecycle and status codes

Objects

Mistakes that cause most integration bugs