AI-generated Key Takeaways
-
The request body is an object sent during the authentication-authorization process, containing a request ID and desired authorizations.
-
This object is encrypted, signed (using PGP or JWS+JWE), and then encoded using web-safe base64 before being sent.
-
The
requestId
is a required field that uniquely identifies the request. -
The
authorizations
field lists the permissions requested, which are validated by Google for security.
Request body
Object sent during authentication-authorization request.
Here's an example of a clear text JSON request:
{
"requestId": "375dhjf9-Uydd="
"authorizations": ["LIST_ACCOUNTS", "ASSOCIATE_ACCOUNT"]
}
The AuthenticationAuthorizationRequest
is encrypted and signed using PGP or JWS+JWE.
Further, this value is web-safe base64 encoded. This encoding is referred to below as
Base64UrlEncode
. In other words, the clear text JSON version of the
AuthenticationRequest
must be passed through the following functions:
Base64UrlEncode(
PGPSignAndEncrypt(
'{"requestId": "375dhjf9-Uydd=",
"authorizations": ["LIST_ACCOUNTS", "ASSOCIATE_ACCOUNT"]}'
)
)
or
Base64UrlEncode(
JWSignAndEncrypt(
'{"requestId": "375dhjf9-Uydd=",
"authorizations": ["LIST_ACCOUNTS", "ASSOCIATE_ACCOUNT"]}'
)
)
JSON representation | |
---|---|
{ "requestId": string , "authorizations": repeated string } |
Fields | |
---|---|
requestId |
REQUIRED: Identifier for this request. |
authorizations |
REQUIRED: Reflected back by the payment integrator to
Google. This allows Google to check that the
|