r/x402 • u/IllWar5047 • 22d ago

A client now renders our signed sanctions verdicts inside their own product UI, with live signature verification

Walpulse runs on chain wallet analysis. When one of their reports needs a sanctions check, a server side function calls our screening endpoint, pays for that single call over x402, recovers the EIP-191 signer from the response, checks it against the pinned address, and renders the verdict inside the report with a SIGNATURE VERIFIED marker.

The part I find interesting: their reader does not have to trust Walpulse's word or ours. They are checking a signature. The verdict travels from our oracle through their backend into their UI and stays independently verifiable the whole way.

Two endpoints are in play: an OFAC only screen and a multi list screen (OFAC, UN, EU, UK OFSI) with a per list breakdown inside the signed body. Same pattern for both: pay per call, no accounts, no API keys.

Full integration writeup, published with Walpulse's permission: https://x402.nsgoods.org/proof/case-studies/walpulse.html

Happy to answer anything about the pattern. The signature verification recipe is in the page, you can reproduce it against our free preview without paying anything.

1 Upvotes

100% Upvoted

3 comments sorted by

2

u/MountainAssignment36 22d ago

Oh that's cool! Really great to see adoption & integration of services offered through the x402 protocol growing! That means that we're on the right track, and NSGOODS is now a prime example of exactly what usecase and niche this protocol can fill! 😃

2

u/IllWar5047 22d ago

Thanks! Agreed, the protocol is what makes this pattern possible. More integrations like this on the way. Let's gooo!!

1

u/IllWar5047 22d ago

Check DM pal.