Skip to content

Clarify terminate/reject/return error behaviours including for unsupported transaction_data - #790

Open
jogu wants to merge 1 commit into
mainfrom
clarify-terminate-reject-error
Open

Clarify terminate/reject/return error behaviours including for unsupported transaction_data#790
jogu wants to merge 1 commit into
mainfrom
clarify-terminate-reject-error

Conversation

@jogu

@jogu jogu commented Aug 27, 2026

Copy link
Copy Markdown
Collaborator

The spec used "terminate", "reject", and "return an error" without defining how they differ, and stated the unsupported transaction_data requirement twice in different words (sections 5.8 and 8.4).

  • Define that terminating request processing means no response is returned to the Verifier, as no authentic request (and hence no trusted response endpoint) was obtained.
  • Harmonize the unsupported transaction_data wording: section 5 now defers to the Transaction Data section, which specifies that the Wallet must not return a VP Token and that any response returned is an invalid_transaction_data error response. Aborting without a response remains possible per the privacy considerations, resolving the tension between the previous unconditional "MUST return an error" and the SHOULD NOT in the Error Responses privacy section.
  • List the unsupported parameter case under invalid_transaction_data.

Fixes #454
Fixes #757

The spec used "terminate", "reject", and "return an error" without
defining how they differ, and stated the unsupported transaction_data
requirement twice in different words (sections 5.8 and 8.4).

- Define that terminating request processing means no response is
  returned to the Verifier, as no authentic request (and hence no
  trusted response endpoint) was obtained.
- Harmonize the unsupported transaction_data wording: section 5 now
  defers to the Transaction Data section, which specifies that the
  Wallet must not return a VP Token and that any response returned is
  an invalid_transaction_data error response. Aborting without a
  response remains possible per the privacy considerations, resolving
  the tension between the previous unconditional "MUST return an
  error" and the SHOULD NOT in the Error Responses privacy section.
- List the unsupported parameter case under invalid_transaction_data.

Fixes #454
Fixes #757
@jogu jogu changed the title Clarify terminate, reject, and return an error behaviors Clarify terminate/reject/return error behaviours including for unsupported transaction_data Aug 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Clarification Request: Interpretation of terminate, reject, and return an error in OpenID4VP Clarify unsupported transaction_data error

1 participant