Relevant Listing: https://www.x402scan.com/server/63446f0c-9a8f-45a4-84a8-1098d117d150
Certain services / resources may implement rotating and/or ephemeral payment addresses in accepts[0].payTo. It seems that x402scan system currently pins whichever payTo address the initial probe happened to see. In these situations, payment settlements go to different per-request deposit addresses, so the listing reports zero transactions despite multiple successful payments went through (in the listing above, these were broadcast by facilitator 0x8D53dc3Bb085a1C26F9f48F669394A3c2dd84983 on Base).
Potential suggestions:
- Index transactions by the
from of transferWithAuthorization events (the facilitator / broadcaster) in certain cases.
- Add an OpenAPI extension like
x-discovery.facilitator for operators to declare their stable broadcaster address or a flag to declare the non-static destination address.
Relevant Listing: https://www.x402scan.com/server/63446f0c-9a8f-45a4-84a8-1098d117d150
Certain services / resources may implement rotating and/or ephemeral payment addresses in
accepts[0].payTo. It seems that x402scan system currently pins whicheverpayToaddress the initial probe happened to see. In these situations, payment settlements go to different per-request deposit addresses, so the listing reports zero transactions despite multiple successful payments went through (in the listing above, these were broadcast by facilitator0x8D53dc3Bb085a1C26F9f48F669394A3c2dd84983on Base).Potential suggestions:
fromoftransferWithAuthorizationevents (the facilitator / broadcaster) in certain cases.x-discovery.facilitatorfor operators to declare their stable broadcaster address or a flag to declare the non-static destination address.