insimbi

Docs · Agent protocols

Visa Trusted Agent Protocol

HTTP message signatures prove the agent before checkout.

Mm

Designed. Protocol support is designed. The flow follows the protocol's published specification, with insimbi on the merchant side. Every check and every settlement is written to the record.

Visa Trusted Agent Protocol Designed. HTTP message signatures (RFC 9421) prove the agent before checkout.
Visa Trusted Agent ProtocolSequence diagram with 4 lanes (Agent, Merchant edge, Agent key directory, insimbi) and 8 numbered steps. The same steps are listed in text below the diagram.AgentMerchant edgeAgent keydirectoryinsimbi1Sign the request: Signature-Input andSignature over the authority and path,with created time, nonce and keyid2Request the page orcheckout with thesignature headers3Fetch the public keyfor the keyid4Public key5Verify the signature, the domain andpath, the time window and the nonce6Pay, with the verified agent attached7Record the agent verification with thepayment8Result

Steps in text

  1. Agent: Sign the request: Signature-Input and Signature over the authority and path, with created time, nonce and keyid
  2. Agent to Merchant edge: Request the page or checkout with the signature headers
  3. Merchant edge to Agent key directory: Fetch the public key for the keyid
  4. Agent key directory to Merchant edge: Public key
  5. Merchant edge: Verify the signature, the domain and path, the time window and the nonce
  6. Merchant edge to insimbi: Pay, with the verified agent attached
  7. insimbi: Record the agent verification with the payment
  8. insimbi to Merchant edge: Result

Request access

insimbi is in early access with design partners.