Check a payee before money moves.

Use PayeeProof immediately before an autonomous machine payment when endpoint identity and payment destination consistency matter.

Workflow

  1. Discover the target service and obtain its public payment challenge.
  2. For GET or HEAD, PayeeProof can perform a bounded anonymous HTTPS probe. For POST, PUT, PATCH, or DELETE, supply an already-observed 402 response.
  3. Call payeeproof.check_payee or POST /v1/payee/check.
  4. If the request is safe and answerable, PayeeProof returns a $0.01 stablecoin payment challenge. No substantive assessment is revealed before settlement.
  5. After settlement, read the result class, individual checks, provenance, continuity, limitations, next step, and digest.
  6. Apply your own spending policy before paying the target.

Never send

Do not send the target merchant's payment credential, private keys, bearer tokens, cookies, card data, or arbitrary request bodies. PayeeProof does not need them and will not forward them.