Using Google Pay™ with Transact Campus

What is Google Pay?

Google Pay makes checkout easier, allows customers to pay with any payment method stored in their Google account. Google Pay is supported on all major browsers. When your customer clicks on it, they will be presented with a list of payment methods stored in their Google account. Your customer will select a payment method and Google will return a payment token to be used for payment. You can use this Google Pay payment token as you would the card detail fields. For example, you can create a subscription for recurring payments.

Note: At this time Transact Campus does not support Android integrations, only Google Pay for Web is supported.


How to Enroll

Contact Transact Campus Support to enable Google Pay for your Client.
By using the Google Pay API, you accept the Google Pay API Terms of Service.
Payment Gateway API

a) Review the Google Pay Web Documentation.

b) Follow the steps in this Guide, making the below modifications to the steps described.

c) Modification to Step 2:

const tokenizationSpecification = {
  parameters: {
  gateway: 'transactcampus',
   gatewayMerchantId: {clientCode-merchantCode}


d) Modification to Step 3:

Note: Only include the card types enabled on your client credit card terminal.
const allowedCardNetworks = ["AMEX", "DISCOVER", "JCB","MASTERCARD", "VISA"];
const allowedCardAuthMethods = ["PAN_ONLY". "cryptogram_3ds"];

e) Once you have completed the request, Google will respond with a Payment Token. Capture the Payment Token and include it in your Payment API Request in the googlePayTokenfield along with any other data you would like to include in the request. POST the encrypted google payload for a payment request using REST API. The API expects valid token to authenticate requests. Requests and responses are in JSON format.

f)  Before going live with Google Pay on your website, make sure you have completed the Google Pay Web integration checklist and followed Google Pay Web Brand Guidelines.



Using Google Pay™ with Transact Campus
Document Version 1.0 ∙ December 2022