Get a ledger account transfer by ID. Admin function does not lock down to a customer.
OptionalcreatedAt?: DbTimestampCriteriaOptionalentityId?: string[]OptionalorderBy?: DbOrderByCriterion<Optionalpage?: numberDefaults to 1
OptionalpageSize?: numberDefaults to 10
OptionalsourceCustomerId?: stringOptionalsourceLedgerAccountId?: string[]Optionalstatus?: ("PENDING" | "FAILED" | "CANCELLED" | "SUCCEEDED")[]OptionaltargetCustomerId?: stringOptionaltargetLedgerAccountId?: string[]OptionalupdatedAt?: DbTimestampCriteriaUpdate the transfer details in DB and publish an event if required
Caller-supplied dedupe token (required — the service never mints its own; the caller owns idempotency). Submitting the same key twice returns the EXISTING transfer (no second insert, no workflow re-kick), making network-level retries safe.
Stored in
idempotency_key, which also seeds the on-chain Mintfx transfer PDA (read back byledgerAccountTransferWorkflowActivities). Verified safe: mintfx-client'sdeterministicUUIDByteshashes the key (sha256 → UUIDv5 → 16 bytes) before deriving the PDA seed, so length and charset are unconstrained.