Pay with Google Pay

Prerequisites

As a prerequisite, you should understand:

Process Details

To set up for live transactions, you need two merchant IDs. One is received from Google, the other is from the payment gateway. You can receive the Google merchant ID, and request production access for particular Internet domains, at https://developers.google.com/pay/api/web/guides/test-and-deploy/request-prod-access. You bring the Google merchant ID to us then. We will register it at the payment gateway, and tell you also the gateway merchant ID. It is passed to the Google Pay button of your checkout solution.

The payment process itself works similar to other payment methods. When one operates the Google Pay button, the payment instrument is chosen and the necessary security checks are performed. The Google API returns a security token, that must be handed over to authorise the payment against the secuconnect API. The secuconnect API methods to authorise and capture the payment are the same like for credit card payment, except there are no callback URLs for there is no second interactive 3-D Secure check. And there is a special Payment Container type for Google Pay.

Google Pay Button Integration

The setup for the token generation is as follows:

JavaScript
const tokenizationSpecification = {
  type: 'PAYMENT_GATEWAY',
  parameters: {
    'gateway': 'aciworldwide',
    'gatewayMerchantId': '<gateway_merchant_id>'
  }
};

You must restrict the application to the following authentication method and card networks:

JavaScript
const allowedCardAuthMethods = ["CRYPTOGRAM_3DS"];
const allowedCardNetworks = ["DISCOVER", "MASTERCARD", "VISA"];

Authorise the Payment

In order to authorise the Smart Transaction for Google Pay payment, you need to call POST Smart/Transactions/STX_xxx/prepare/creditcard:

Request
POST /api/v2/Smart/Transactions/STX_33PXAW2YN2NJTPM5KPGMK7QF5PBVA2/prepare/creditcard HTTP/1.1
Host: connect-testing.secupay-ag.de
Authorization: Bearer qb56tjj1bcvo9n2nj4u38k84lo
Content-Type: application/json
Accept: application/json
 
{
"container": {
"type": "googlepay",
"private": {
"signature": "MEUCIQD4NF3Wh1Kjvxf12MsZ3iVf1eHZOU46l43gNMIxzHAq8QIgX3cGN3V2DSTUtGIwgdNjaXca4+Kpslx45nWgzcOmqag\u003d",
"protocolVersion": "ECv1",
"signedMessage": "{\"encryptedMessage\":\"6QrdO9Rm5wUO76YrgOFu4k/d42mAgYVtMMvpEybDQoFL5Wj...\",\"ephemeralPublicKey\":\"BEz07ptykA21w7ZhwDjB3Kn2558wR3xnM6y/iZUn5mfFMljm6ZHtBANF+L4yObcq1CfCnvRPR90Gid2+Myht5WA\\u003d\",\"tag\":\"9l5vnWtmGctNQvifh4qZggLR9gvzURj2EgobsR0oUDE\\u003d\"}"
},
  }
"customer": {
"id": "PCU_3M55SQZR42NSPDS8GGF4N55EZCDCAZ"
},
"merchant": {
"id": "MRC_WVHJQFQ4JNVYNG5B55TYK748ZCHQP8"
}
}

These are the parameters:

Parameter

Type

Meaning

container

object

Payment container data

container/type

string

Always "googlepay" for this payment method

container/private

object

Data taken from Google Pay token ( paymentData.paymentMethodData.tokenizationData.token )

customer

object

Customer. Only needed if not set before.

customer/id

string

Customer ID (PCU_xxx)

merchant

object

Merchant. Only needed if not identified by the contract.

merchant/id

string

Merchant ID (MRC_xxx)

The Smart Transaction is authorised immediately.

Response (3-D Secure Not Required)
HTTP/1.1 200 OK
Content-Type: application/json
...
 
{
"object": "smart.transactions",
"id": "STX_33PXAW2YN2NJTPM5KPGMK7QF5PBVA2",
// ...
"customer": {
"object": "payment.customers",
"id": "PCU_3M55SQZR42NSPDS8GGF4N55EZCDCAZ",
"contact": {
"forename": "Mike",
"surname": "Mustermann",
"name": "Mike Mustermann",
"address": {
"street": "Musterstr.",
"street_number": "42",
"additional_address_data": "App. 97",
"postal_code": "09999",
"city": "Dorianburgh",
"country": "DE"
},
"email": "Eunice.Spencer89@example.net",
"mobile": "+491775555555",
"phone": "+495555555555",
"dob": "1965-12-31T00:00:00+01:00"
}
},
"container": {
"object": "payment.containers",
"id": "PCT_SF9XGHPVC2NSQX03V86EREAMMET7AZ"
},
// ... // ...
"transactions": [{
"object": "payment.transactions",
"id": "PCI_4YN04HZ4Z705GMRSJ5EW4J4X0ZDPNW"
}],
"created": "2020-10-29T14:13:41+01:00",
"updated": "2020-10-29T14:13:50+01:00",
"status": "approved",
// ...
"payment_method": "creditcard",
"trans_id": "30093721",
// ...
}

Status approved means the payment is authorised and you should be able to capture it. Status failed means you must repeat the payment process. You must also repeat the payment process when you update the Smart Transaction. It is then set back to created.

If the option auto_capture is true, it would already capture the Smart Transaction. Status ok, received or collection means you can deliver. Status pending means you have to wait for one of these statusses. Status failed means the payment failed, and you must repeat the payment process.

Capture the Payment

The way to capture an authorised payment is the same for all payment methods. If you have already studied this for invoice or direct debit payment, you will not find any new details.

In order to start the authorized Smart Transaction, you only need to call POST Smart/Transactions/STX_xxx/start.

Request
POST /api/v2/Smart/Transactions/STX_33PXAW2YN2NJTPM5KPGMK7QF5PBVA2/start HTTP/1.1
Host: connect-testing.secupay-ag.de
Authorization: Bearer qb56tjj1bcvo9n2nj4u38k84lo
Accept: application/json

If everything is fine, the API responds with 200 OK:

Response
HTTP/1.1 200 OK
Content-Type: application/json
...
{
"object": "smart.transactions",
"id": "STX_33PXAW2YN2NJTPM5KPGMK7QF5PBVA2",
// ...
"transactions": [
{
"object": "payment.transactions",
"id": "PCI_FDBREW9ZS7P6FTN4ZY2ATC6NK0QWO7"
}
],
"created": "2020-03-27T10:55:23+01:00",
"updated": "2020-03-27T10:56:41+01:00",
"status": "ok",
// ...
}

Status ok, received or collection means you can deliver. Status pending means you have to wait for one of these statusses. Status failed means the payment failed, and you must repeat the payment process.

Note: You also need to mark the actual delivery. This is needed to determine the due date of the payment.