Skip to content

Last Updated: 15 July 2025 | Change Log

Google Pay

Make a Google Pay payment by providing the encrypted payload (wallet token) in the payments request.

Google Pay is not yet supported when setting up a recurring payment.

1. Basic Request

application/json

Provide the encrypted Google Pay payload

{ "transactionReference": "Memory265-13/08/1876", "merchant": { "entity": "default" }, "instruction": { "method": "googlepay", "paymentInstrument": { "type": "encrypted", "walletToken": "{\"protocolVersion\":\"ECv1\",\"signature\":\"MEQCIH6Q4OwQ0jAceFEkGF0JID6sJNXxOEi4r+mA7biRxqBQAiAondqoUpU/bdsrAOpZIsrHQS9nwiiNwOrr24RyPeHA0Q\\u003d\\u003d\",\"signedMessage\":\"{\\\"tag\\\":\\\"jpGz1F1Bcoi/fCNxI9n7Qrsw7i7KHrGtTf3NrRclt+U\\\\u003d\\\",\\\"ephemeralPublicKey\\\":\\\"BJatyFvFPPD21l8/uLP46Ta1hsKHndf8Z+tAgk+DEPQgYTkhHy19cF3h/bXs0tWTmZtnNm+vlVrKbRU9K8+7cZs\\\\u003d\\\",\\\"encryptedMessage\\\":\\\"mKOoXwi8OavZ\\\"}\"}" }, "narrative": { "line1": "trading name" }, "value": { "currency": "GBP", "amount": 42 } } }

2. Add additional features

Note: 3DS (for Googlepay) and FraudSight are not yet available for wallets

3. Response

Features that change the API flow

Certain features add additional requests and responses:

  • Auto Settlement - automatic 202 - sentForSettlement following authorization.
    • If any of the AVS/CVC response riskFactors are marked as notMatched the payment will be sentForCancellation automatically by default but can be disabled.
application/json
No response example