wallet
browser-session

Record that you signed and sent a payment your agent prepared

Called by the approval page (/floor10/wallet/approve/{id}) after the member's own embedded wallet signed the payment in their browser. Clerk-session only, same-site, application/json, and refused outright for an agt_ bearer: an agent can prepare a payment (ic_wallet_prepare_payment) but can never complete one. Only the request's owner may call it; anyone else's id answers the same 404 as an unknown or expired one. The hash is format-checked for the request's chain and stored as REPORTED (status submitted); IC does not verify it on-chain. A second report is a 409. 404 unless wallets are enabled.

post/api/wallet/requests/{id}/complete

Request

  • Base URL: https://www.immersivecommons.com
  • URL: https://www.immersivecommons.com/api/wallet/requests/{id}/complete
  • Auth: API key in cookie __session

Path parameters

idstring required

The payment request id.

Request body

tx_hashstring required

Base: 0x + 64 hex. Solana: the base58 transaction signature.

user_op_hashstring

Base only: the ERC-4337 user operation hash, 0x + 64 hex.

Response

The request, now submitted.

okboolean required

Changes

No recorded changes to this operation across all 1 revision of this API.