Troubleshooting

A 400 from any on-chain action — buying, transferring, approving, bidding on a contract-backed auction, confirming an offer transfer. The account has no user.walletAddress, and the column is a mirror that only the customer's own SIWE link flow at /user/profile?tab=wallet can write. It cannot be set from the admin panel or in SQL.

This is the single most common blocker on a fresh install. Full detail, and the other three ways money gets stuck, are in When money or an NFT is stuck.

The addon is not enabled, or the account lacks access.nft. Check Admin → System → Extensions first, then the role's permissions. A missing menu is almost always permissions, not a broken install.

Minting is an on-chain operation and needs the Ecosystem custody layer working underneath. Confirm the chain is enabled and its master wallet has gas — a mint that cannot pay its fee stalls rather than reporting a clear error. Check the chain's own page under Blockchains for what "funded" means there.

The contract was never deployed, or deployment failed partway. Open Contracts and check the collection's deployment state before assuming the mint path is broken.

Token media is fetched from wherever its metadata points. If that is an IPFS gateway, the platform's image loader only permits the gateways on its allowlist — an off-allowlist host is refused at render time and cannot be caught by a fallback. Host media on an allowed gateway or your own domain.

Anti-snipe extends an auction when a bid lands near the close. Check whether nftEnableAntiSnipe is on and what nftAntiSnipeExtension is set to — see Settings. This is working as designed, and it is worth stating on your terms page.

A bid must clear the current highest ACTIVE bid by the listing's own nft_listing.minBidIncrement, which was fixed when the auction was created and validated then against nftBidIncrementPercentage. There is no platform-wide minimum increment setting — see Settings. A bidder entering the exact current price is refused.

The listing carries settlementBlockedAt and shows a Settlement blocked badge. No money was ever escrowed, so nobody is owed a refund — but the flag cannot be cleared from the admin console. See When money or an NFT is stuck.

An ACCEPTED offer stamped flaggedAt, with an open NOT_RECEIVED dispute against it. The escrow release failed and the offer status toggle will not release it either. See When money or an NFT is stuck.

Creators go through onboarding before they can list. Check their state on the creator screen — an incomplete onboarding looks identical to a permissions problem from the customer's side.

Check the sale record before assuming a payout bug. Royalties and platform fees come out of the sale amount, so the seller receives less than the headline price. Fees and royalties explains the split.

Disputes need an admin with edit.nft.dispute to resolve them. access.nft.admin alone opens the queue but cannot settle anything, so the queue appears to work and nothing can be actioned.