Protected ReadonlycacheProtected ReadonlydbStaticinstanceThe process default: built from each dependency's own instance().
Get instrument by ID or reference ID
It can be further narrowed down by type and entity ID.
Also clears payment-instrument.text. Every writer busts by customer alone,
which reaches no field tag, yet each write may change the text a cached
transaction q page matched on.
OptionalbankIds?: string[]Instruments used in a deposit or withdrawal at one of these banks: a per-row check, so a search with it is not cached (no write to a transaction busts this cache).
OptionalcreatedAt?: DbTimestampCriteriaOptionaldeleted?: booleanOptionalentityIds?: string[]Optionalids?: string[]Optionallinked?: booleanPHONE recipients with (true) or still without (false) a linked ledger account.
OptionalnameLike?: stringPartial match over the requested types' name-ish fields. Requires types.
OptionalnominisWalletScreenRequestIds?: string[]OptionalorderBy?: DbOrderByCriterion<Ties break on the row id, in the last criterion's direction.
Optionalpage?: numberDefaults to 1
OptionalpageSize?: numberDefaults to 10
OptionalpartialText?: stringPartial match over referenceId plus each requested type's searchable
fields. Requires types — the per-type field map is what keeps the query
indexable. Field map: internal/search.ts.
OptionalproviderIds?: string[]Provider-side account identifier. Kept in lockstep with the admin surface's filter of the same name (rules/service-pattern.md).
Optionalproviders?: (OptionalquilttConnectionIds?: string[]OptionalreferenceIdLike?: stringPartial match over the nickname: name on wallets, referenceId otherwise. Requires types.
OptionalreferenceIds?: string[]Optionalstatuses?: (Optionaltypes?: (OptionalupdatedAt?: DbTimestampCriteriaOptionalverificationProfileIds?: string[]Instruments holding one of these AiPrise profiles as their beneficiary's.
ProtectedsearchTags for a page: the scope its query searched (each customer's membership
tag, else the collection tag), so an empty page is bustable too, plus the
records it projects and the fields that chose or ordered its rows.
Query payment instruments across supported types