Compliance issuers this sandbox trusts

When a payment requires a compliance capability (e.g. attests:kyc:v1 or attests:sanctions:v1), the payer attaches a signed attestation from an issuer. This deployment’s verifier accepts that attestation only if its signer is one of the keys below and it uses the matching schema. Any one trusted issuer per capability is enough.

Issuers trusted here

How to get attested

Pick a trusted issuer above for the capability you need and follow its link to request an attestation for your payer address. Attach it to the payment; the verifier confirms the issuer is trusted here and that the attestation covers the required capability.

Run your own issuer

Building a real compliance issuer? Sign attestations with the canonical HSP schema (@hsp/core → issueKyc / issueSanctions — the wire format schemaId, claims codec, signature scheme must match), then send the organizer your signing address and project name. We add it to this sandbox’s trust set and it appears here. Trust is pinned per verifier: anyone can also choose to trust your issuer independently — see the developer guide. The settlement-attestation side — the adapter operators — is the symmetric other half of what a verifier pins.