Wrong payTo used at settle time
Quirk · GET /api/x402/facilitator-wrong-payto-at-settle · Facilitator Dependency
The merchant calls /settle with a payTo address different from the one advertised in the challenge; the facilitator rejects it because the payment was signed for a different recipient.
Explanation
The merchant's code builds the /settle request using a hardcoded payTo address instead of the one it advertised in the challenge. The payment was signed by the client for the challenge's payTo, so the facilitator rejects the mismatched settle request. If the call had somehow succeeded, funds would have been routed to the wrong recipient. The merchant must pass the same payTo it advertised — or derive it from the same source — on every /settle call.
What to watch
Returns 402. The facilitator rejects the mismatched payTo — funds would have gone to the wrong address if the call had succeeded.
Facilitator
Settled against the live Radius testnet facilitator (https://facilitator.testnet.radiustech.xyz). A valid payment runs a real /verify and /settle on-chain.
Metadata
- Status: Quirk
- Method: GET
- Price: 0.0001 (100 atomic)
- Responsible party: Merchant