Sign Transactions

Sign Transactions captures non-repudiable consent for every high-risk transaction.

Sign Transactions binds a verified person's identity to the terms of a specific transaction. The wallet shows the terms exactly as provided. The person signs, and the signature covers both their identity and the terms themselves. Any modification to the terms after the fact invalidates the signature.

While Verify Identity answers who is on the other end, Sign Transactions answers what specifically that person agreed to.

When to use it

Sign Transactions fits situations where signed evidence of consent is needed and the consent has to cover specific terms rather than a generic agreement.

  • Wire transfers. Authorize a wire with evidence of amount, beneficiary, and source account.
  • Recurring payment mandates. Capture consent for recurring or future-dated charges on a card or bank account.
  • Itemized purchases. Confirm a specific basket of items at checkout, with each line item part of the signed record.

Templates

The following Transaction Templates are supported.

  • Wire Instructions. Binds recipient, source, amount, and reference of a wire transfer to a Verifiable Credential.
  • Payment Mandate. Binds a payment mandate authorization, such as a recurring charge, to a Verifiable Credential.
  • Itemized Payment. Binds an itemized basket of line items to a Verifiable Credential.

Each template is documented in Transaction Data Templates.

How it works

Sign Transactions sequence

The Verifier performs the following checks on the response:

  • Hash match. Recompute the hash of the original terms and confirm it matches the one in the signed presentation.
  • Holder signature. Verify the signature on the presentation with the Holder's public key, confirming the legitimate Holder consented.
  • Certificate chain. Walk the certificate chain from the credential's issuer up to Proof Root CA R1, the trust anchor in your trust store.

Together, those checks ensure the response is cryptographic proof that the named verified person consented to the specific terms shown.

For the technical specifics of building the request and validating the response, see Verify a Credential (OID4VP).

Custom templates

📘

Need a template not in the catalog? Reach out to our Product team at [email protected].


See also: Use Cases · Transaction Data Templates · Verify a Credential