- [JSON representation](https://developers.google.com/pay/e-wallets-v1/payment-integrator-e-wallets-api/Response#SCHEMA_REPRESENTATION)

Object sent during authentication response.

Here's an example of a clear text JSON response:


    {
      "associationId": "88ydEE-ioiwe==",
      "requestId": "375dhjf9-Uydd="
    }

The `AuthenticationResponse` is encrypted and signed using PGP or JWE+JWS. 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(
    {
      "associationId": "88ydEE-ioiwe==",
      "requestId": "375dhjf9-Uydd="
    }
      )
    )

or

    Base64UrlEncode(
      JWSignAndEncrypt(
    {
      "associationId": "88ydEE-ioiwe==",
      "requestId": "375dhjf9-Uydd="
    }
      )
    )

| JSON representation |
|---|
| ``` { "associationId": string, "requestId": string, "authenticationResult": { object (`https://developers.google.com/pay/e-wallets-v1/payment-integrator-e-wallets-api/simulateRedirectAuthentication#AuthenticationResult`) } } ``` |

| Fields ||
|---|---|
| `associationId` | `string` **OPTIONAL**: Reflected back by the payment integrator to Google. This allows Google to check that the associationId passed back is the same associationId passed in. This is required if it is present on the request. |
| `requestId` | `string` **REQUIRED**: Reflected back by the payment integrator to Google. This allows Google to prevent replay attacks. |
| `authenticationResult` | ``object (`https://developers.google.com/pay/e-wallets-v1/payment-integrator-e-wallets-api/simulateRedirectAuthentication#AuthenticationResult`)`` **OPTIONAL**: The result of the authentication. For flows where there is no subsequent call to the Payment Integrator after the authentication has taken place, the result must be included in the response to ensure the integrity of the result. |