SusuFinance Verify — Live Demo

A vendor registers the addresses and payment links they publish to customers. They prove ownership by placing a short file on their web server or adding a verification code to their DNS record. Once proven, those addresses appear in the public registry. Any customer can check an invoice against them before sending.

Large institutions — exchanges, payment processors, licensed VASPs — often manage hundreds of receiving addresses across multiple chains. Instead of registering them one by one, they host a canonical list at an endpoint on their own domain and provide SusuFinance a read-only API key. SusuFinance uses that key to pull the list, hashes and verifies each address, and mirrors them in the public registry under the institution's domain name. The key is stored encrypted and is never exposed. Every six hours SusuFinance re-pulls, re-hashes, and compares. If any address appears, disappears, or changes without notice, SusuFinance alerts the institution and the affected badges lapse within twenty-four hours.

// Option A — objects with chain label (recommended)
{
  "addresses": [
    { "address": "0xce000000000000000000000000000000000000ce", "chain": "ethereum" },
    { "address": "bc1qdemoexchange00000000000000000000000000", "chain": "bitcoin" }
  ]
}

// Option B — plain address strings
{ "addresses": ["0xce000…", "bc1qdem…"] }

// Option C — bare array
["0xce000…", "bc1qdem…"]

These addresses were pulled from demo-exchange.io's hosted list, hashed, verified, and added to the public registry. Any investor can check one before sending.

Before sending funds, paste the address from the invoice or payment screen. The checker runs it against scam blacklists, sanctions lists, mixer activity, honeypot token patterns, and the verified publisher registry — in seconds.

Try a demo exchange address: 0xce000000000000000000000000000000000000ce