rejectTransferOffer refuses counterpart proposals surfaced listTransferOffers—receiver persona executes POST rejecting counterpart obligations atomically without settling funds.
Setup
import { Canton } from '@fairmint/canton-node-sdk';
const canton = new Canton({
network: 'devnet',
provider: '5n',
partyId: 'OWN_PARTY_ID',
});
Import and receiver
import { Canton } from '@fairmint/canton-node-sdk';
Receiver: canton.validator.rejectTransferOffer.
Minimal example
const res = await canton.validator.rejectTransferOffer({
contractId: '<offer-contract-id>',
});
console.log(res.rejected_offer_contract_id);
Parameters
contractId(required, string) — Offer contract identifier awaiting rejection responses referencing inbound ledger workflows.
Returns
rejected_offer_contract_id(string) — Echo correlating rejection transitions surfaced explorers referencing ledger instrumentation.
Errors and pitfalls
- Double-reject attempts behave undefined—guard UI transitions referencing ACS watchers verifying terminal states beforehand.
Auth and party
Bearer token binding receiver wallet identity exercising Canton authorization rejecting counterpart obligations referencing ACS visibility rules.
See also
Source
src/clients/validator-api/operations/v0/wallet/transfer-offers/reject.ts on GitHub.