Method: echo

Stay organized with collections Save and categorize content based on your preferences.

Echos back the clientMessage passed in.

The purpose of this method is to test basic connectivity between the payment integrator and Google.

If the endpoint encounters an error while processing the request, the response from this endpoint will be of type ErrorResponse.

Responses to this query may be empty if this method does not return an HTTP 200. The response body is empty in situations where an ErrorResponse with a clear description could be used to help an attacker understand the payment integrator account identifier of other integrators. In these situations, where either the signing key doesn't match, the payment integrator identifier was not found, or the encryption key was unknown, this method will return an HTTP 404 with an empty body. If the request signature could be verified, additional information regarding the error will be returned in the response body.

An example request looks like:

  "requestHeader": {
    "protocolVersion": {
      "major": 1,
      "minor": 0,
      "revision": 0
    "requestId": "ZWNobyB0cmFuc2FjdGlvbg",
    "requestTimestamp": "1481899949606"
  "clientMessage": "client message"

An example response looks like:

  "responseHeader": {
    "responseTimestamp": "1481900013178"
  "clientMessage": "client message",
  "serverMessage": "server message"

HTTP request


Request body

The request body contains data with the following structure:

JSON representation
  "requestHeader": {
    object (RequestHeader)
  "clientMessage": string

object (RequestHeader)

REQUIRED: Common header for all requests.



REQUIRED: Message to echo in the response.

Response body

If successful, the response body contains an instance of ComplexEchoResponse.