ResponseMode

OID4VP: In this mode, the Authorization Response is sent to the Verifier using an HTTPS POST request to an endpoint controlled by the Verifier. The Authorization Response parameters are encoded in the body using the application/x-www-form-urlencoded content type. The flow can end with an HTTPS POST request from the Wallet to the Verifier, or it can end with a redirect that follows the HTTPS POST request, if the Verifier responds with a redirect URI to the Wallet.

OID4VP: The Response Mode direct_post.jwt causes the Wallet to send the Authorization Response using an HTTPS POST request instead of redirecting back to the Verifier. The Wallet adds the response parameter containing the JWT as defined in Section 4.1. of JARM and Section 6.3 in the body of an HTTPS POST request using the application/x-www-form-urlencoded content type.

OAuth 2.0: In this mode, Authorization Response parameters are encoded in the fragment added to the redirect_uri when redirecting back to the Client.

Any not natively supported Client ID Scheme, so it can still be parsed

OAuth 2.0: In this mode, Authorization Response parameters are encoded in the query string added to the redirect_uri when redirecting back to the Client.