Troubleshooting - Reference

DocsLimited

Last updated: Apr 10th, 8:03pm

If there's a problem with your integration, errors are shown in the response to your request. You can troubleshoot the problem based on the issue code or HTTP code in the response.

Google Pay issue codes

PayPal’s Google Pay on the Web integration includes issue codes for 2 additional error responses. These issue codes show up in the response.body.details[].issue parameter of the JSON response:

Issue Code Description
INVALID_GOOGLE_PAY_TOKEN PayPal can't decrypt the Google Pay token or can't find the necessary data in the token after decryption.
GOOGLE_PAY_MERCHANT_ID_MISMATCH The payee in the order doesn't match the merchant ID that the payer authorized on Google Pay.

400 Bad Request

A 400 Bad Request response can mean:

  • Google Pay token value is empty.
  • payment_method parameter is missing in the Google Pay decrypted_token.

Sample error response: Token value empty

    1HTTP status: 400 Bad Request
    2
    3HTTP headers:
    4{
    5 "Content-Type":"application/json"
    6}
    7
    8Response payload:
    9{
    10 "name": "INVALID_REQUEST",
    11 "message": "Request is not well-formed, syntactically incorrect, or violates schema.",
    12 "debug_id": "ef34461651e34",
    13 "details": [
    14 {
    15 "field": "/payment_source/google_pay/token",
    16 "value": "",
    17 "issue": "INVALID_PARAMETER_VALUE",
    18 "description": "The value of a field is invalid.",
    19 "location": "body"
    20 }
    21 ],
    22 "links": [
    23 {
    24 "href": "https://developer.paypal.com/api/orders/v2/#error-INVALID_PARAMETER_VALUE",
    25 "rel": "information_link"
    26 }
    27 ]
    28}

    Sample error response: Missing payment parameter

      1HTTP status: 400 Bad Request
      2
      3HTTP headers:
      4{
      5 "Content-Type":"application/json"
      6}
      7
      8Response payload:
      9{
      10 "name": "INVALID_REQUEST",
      11 "message": "Request is not well-formed, syntactically incorrect, or violates schema.",
      12 "debug_id": "f17abde1a8de8",
      13 "details": [
      14 {
      15 "field": "/payment_source/google_pay/decrypted_token/payment_method",
      16 "issue": "MISSING_REQUIRED_PARAMETER",
      17 "description": "A required field or parameter is missing.",
      18 "location": "body"
      19 }
      20 ],
      21 "links": [
      22 {
      23 "href": "https://developer.paypal.com/api/orders/v2/#error-MISSING_REQUIRED_PARAMETER",
      24 "rel": "information_link"
      25 }
      26 ]
      27}

      422 Unprocessable Entity

      A 422 Unprocessable Entity response can mean:

      • Google Pay token value is incorrect.
      • cryptogram value is missing from the decrypted_token object.

      Sample error response: Incorrect token value

        1HTTP status: 422 Unprocessable Entity
        2
        3HTTP headers:
        4{
        5 "Content-Type":"application/json"
        6}
        7
        8Response payload:
        9{
        10 "name": "UNPROCESSABLE_ENTITY",
        11 "details": [
        12 {
        13 "field": "/payment_source/google_pay/token",
        14 "location": "body",
        15 "issue": "INVALID_GOOGLE_PAY_TOKEN",
        16 "description": "The google pay token is invalid. PayPal was not able to decrypt the googlepay token or PayPal was not able to find the necessary data in the token after decryption."
        17 }
        18 ],
        19 "links": [
        20 {
        21 "href": "https://developer.paypal.com/api/orders/v2/#error-INVALID_GOOGLE_PAY_TOKEN",
        22 "rel": "information_link",
        23 "method": "GET"
        24 }
        25 ],
        26 "debug_id": "0ee3837653a79",
        27 "message": "The requested action could not be performed, semantically incorrect, or failed business validation."
        28}

        Sample error response: Missing cryptogram

          1HTTP status: 422 Unprocessable Entity
          2
          3HTTP headers:
          4{
          5 "Content-Type":"application/json"
          6}
          7
          8Response payload:
          9{
          10 "name": "UNPROCESSABLE_ENTITY",
          11 "details": [
          12 {
          13 "field": "/payment_source/google_pay/decrypted_token/authentication_method",
          14 "location": "body",
          15 "issue": "INCOMPATIBLE_PARAMETER_VALUE",
          16 "description": "The value of the field is incompatible with other fields in the order. Please refer to the documentation of the field for details on compatibility with other fields in the order."
          17 },
          18 {
          19 "field": "/payment_source/google_pay/decrypted_token/cryptogram",
          20 "location": "body",
          21 "issue": "INCOMPATIBLE_PARAMETER_VALUE",
          22 "description": "The value of the field is incompatible with other fields in the order. Please refer to the documentation of the field for details on compatibility with other fields in the order."
          23 }
          24 ],
          25 "links": [
          26 {
          27 "href": "https://developer.paypal.com/api/orders/v2/#error-INCOMPATIBLE_PARAMETER_VALUE",
          28 "rel": "information_link",
          29 "method": "GET"
          30 }
          31 ],
          32 "debug_id": "0ee3837653a79",
          33 "message": "The requested action could not be performed, semantically incorrect, or failed business validation."
          34}