Skip to main content
POST
Seller Financing is in beta and runs on Ethereum Sepolia instances only for now (DEVELOPMENT instances on Ethereum). A PRODUCTION instance, or one on another network, answers 503 SELLER_FINANCING_UNAVAILABLE. See Seller Financing.
Records a market your instance deployed. Send the hash of the mined deployMarket transaction built by Build Deployment. This is the only Seller Financing write with a confirm call. Everything after it is read from the chain. The API reads the receipt and checks, in order:
  1. The transaction is mined and succeeded.
  2. It calls deployMarket on your network’s Seller Financing factory, directly or wrapped in a smart-account call.
  3. The factory emitted MarketDeployed with the signing wallet as deployer.
  4. No other instance has recorded the market. A market recorded elsewhere answers 409 MARKET_RECORDED_ELSEWHERE, whatever wallet signed it. details.marketId names its record ID only when a verified wallet of your instance holds OPERATOR_ROLE or DEFAULT_ADMIN_ROLE on it, read on chain.
  5. The wallet that signed it is a verified wallet of your instance.
  6. The factory recognises the market as its own.
A deployment sent through a Safe, an EIP-7702 account or an ERC-4337 smart account is accepted. The API reads the wrapped call, and the signer is the smart account that called the factory, so that account must be the verified wallet of your instance. The wallet that broadcast the outer transaction is kept as outerSender on the role assignment record. The answer carries the market record, the role assignment record built from the same receipt, and the token-side setup the adapter still needs. A market is recorded once, on the instance whose wallet signed its deployment. An instance one of whose verified wallets holds OPERATOR_ROLE or DEFAULT_ADMIN_ROLE on a market another instance recorded does not record it again: every market route answers for it by its ID, and List Markets lists it when that wallet is the admin or operator named at deployment. See Which markets your instance reaches.

Body Parameters

string
required
Hash of the mined deployment transaction: 0x followed by 64 hex characters. A malformed hash answers the standard 400 VALIDATION_ERROR with the message “txHash must be a 32-byte hex hash” and details: [{ field: "txHash", message }], before anything is read.

Response Fields

The status is 201 when the market is recorded now and 200 when it was already recorded on your instance. Sending the same hash again is safe.
object
TX_NOT_FOUND is the expected answer when you confirm before the transaction is mined. Wait for one confirmation and send the hash again.
If the answer is an error after the market was already recorded, for example because the chain could not be read while the role record was built, send the same hash again. A recorded market answers 200 with created: false.

Error Codes