Protected ReadonlycacheStaticinstanceThe process default: built from each dependency's own instance().
update for an operator, whoever owns the row: skips only the capability check.
OptionalaccountNumber?: string | nullOptionalaccountType?: "CHECKING" | "SAVING" | nullDeposit account type, defaulting to "CHECKING". Total here, optional
in storage and on the create request — see
SwiftWireDbInstrumentData.accountType.
OptionalbankAddress?: The bank's address as the customer entered it. Each field wins over the directories; its country is the BIC's.
Optionalcurrency?: string | nullISO-4217 currency the payout settles in, defaulting to SWIFT_WIRE_DEFAULT_CURRENCY. Immutable after create — see SwiftWireDbInstrumentData.
Optionaliban?: string | nullOptionalintermediaryRoutingNumber?: string | nullIntermediary bank BIC/SWIFT code, if any
OptionallocalAccountNumber?: string | nullThe Local Account Number (e.g. Cuenta Cliente in Costa Rica) in the beneficiary's bank.
OptionallocalBankCode?: string | nullLocal Bank Code For Account Number (e.g. BSB for AU, IFSC for IN, NCC for EU, institution-transit (CRN) for CA)
OptionalreferenceId?: string | nullOptionalroutingNumber?: string | nullBIC/SWIFT code
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.
The bank a BIC names, with the address an entity's instrument would store
for it and the bankAddress.* fields a customer must still supply.
ok(null) for a code the SWIFT directory does not know.
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.
Merge data into an existing instrument. Every field is optional — an
absent key is left untouched.
beneficiary is replaced wholesale rather than merged field-by-field, and
its type is immutable — it is a BUSINESS | PERSON discriminated union,
and a partial merge could assemble a member that satisfies neither arm.
The owning entity is read off the row, not supplied: it is what the
capability check and the derived providerId are built from, and an
instrument cannot move between entities.
Upserts currently-persisted beneficiary into AiPrise and runs a verification
Maintain the account and beneficiary details for sending international wires via SWIFT network.