About Google Pay

What is Google Pay

Logo	Google Pay™
Info	Google Pay is the fast, simple way to pay on sites, in apps and in stores using the cards saved to your Google Account. It protects your payment info with multiple layers of security and makes it easy to send money, store tickets or cash in on rewards – all from one convenient place.
Type	Payments by eWallet

Notice: Regarding the liability shift in case of the card processing, please contact your Acquirer directly. Because Pay-Jet is not a direct contract partner, your Acquirer should specify the liability shift rules for each card brand.

When a user taps the Google Pay payment button, they see a payment sheet. It displays the payment methods they've saved to their Google Account and optional fields such as a shipping address. Users can then select a payment method quickly and provide a shipping address if required, or they can add new information.

In-app payment

The Google Pay API enables fast, simple checkout within your app, giving you convenient access to hundreds of millions of cards saved to Google Accounts worldwide.

These above screens represent a recommended Google Pay buy flow for a shopping cart experience.

These guidelines will help you implement Google Pay within your apps: https://developers.google.com/pay/api/android/guides/brand-guidelines.

Web payment

The Google Pay API enables fast, simple checkout on your website. This provides convenient access to hundreds of millions of cards that are saved to Google Accounts worldwide.

The above screens represent a recommended Google Pay buy flow for a shopping cart experience.

These guidelines will help you reference the Google Pay brand within your websites: https://developers.google.com/pay/api/web/guides/brand-guidelines.

Step by Step Set-Up Guide

Once you have decided to support Google Pay, there is a set of steps that need to be done. This guide is applicable for both, in-app and also web payments.

1. Verify if your Acquirer supports Google Pay, for the card networks supported and support for Android device tokens.

This information will be provided by Pay-Jet support team: Pay-Jet Support.

2. If you already do not have one, request creation of Pay-Jet Merchant ID, unique identifier that represents a merchant in Pay-Jet Cockpit platform. You need to use Pay-Jet Merchant ID also in Google Pay API.

Please contact Pay-Jet support team: Pay-Jet Support.

3. Integrate Google Pay API: https://developers.google.com/pay/api/.

Apps: https://developers.google.com/pay/api/android/overview

Web: https://developers.google.com/pay/api/web/overview

a. For payment tokenization method, choose “GATEWAY”, with following values:

const tokenizationSpecification = {

type: “PAYMENT GATEWAY”,

parameters: {

'gateway': 'computop',

'gatewayMerchantId': 'yourComputopMerchantID'

}

b. For supported payment card networks, choose the ones your acquirer is supporting:

const allowedCardNetworks = ["AMEX", "DISCOVER", "JCB", "MASTERCARD", "VISA"];

c. The Google Pay API may return cards on file on Google.com (PAN_ONLY) and/or a device token on an Android device authenticated with a 3-D Secure cryptogram (CRYPTOGRAM_3DS).

Please make sure that you define CRYPTOGRAM_3DS only if your acquirer is supporting this functionality. Please contact Pay-Jet Support to verify this point if needed.

const allowedCardAuthMethods = ["PAN_ONLY", "CRYPTOGRAM_3DS"];

If you are operating in EEA region, please define CRYPTOGRAM_3DS only, as these payments are already Strong Customer Authenticated in Google Pay wallet and therefore compliant with PSD2 SCA regulation.

Note: If you receive Soft Decline in Response, you need to restart the payment with 3-D Secure authentication.

d. In response from Google Pay API, you should receive Token similar to this:

You need to Base64 encode the whole token string and include it in Cockpit parameter TokenExt.

Process flow chart

Google Pay process flow

Cockpit interface

Definitions

Data formats

Format	Description
a	alphabetical
as	alphabetical with special characters
n	numeric
an	alphanumeric
ans	alphanumeric with special characters
ns	numeric with special characters
bool	boolean expression (true or false)
3	fixed length with 3 digits/characters
..3	variable length with maximum 3 digits/characters
enum	enumeration of allowed values
dttm	ISODateTime (YYYY-MM-DDThh:mm:ss)

Abbreviations

Abbreviation	Description	Comment
CND	condition
M	mandatory	If a parameter is mandatory, then it must be present
O	optional	If a parameter is optional, then it can be present, but it is not required
C	conditional	If a parameter is conditional, then there is a conditional rule which specifies whether it is mandatory or optional

Notice: Please note that the names of parameters can be returned in upper or lower case.

Calling the interface

Two transactions are created when making a credit card payment via Google Pay. In the Google Pay transaction the required credit card data are determined first and the actual credit card transaction is then carried out automatically. This takes place via a server-to-server connection and supports all usual credit card transaction options. The difference here, however, is that you don't transmit the credit card information, which you don't know. Instead, you transmit the Token generated by Google Pay, which contains the required credit card data in encrypted form.

In order to make a credit card payment with Google Pay, please use the following URL:

https://www.payjet-cockpit.de/googlepay.aspx

Notice: For security reasons, Pay-Jet Cockpit rejects all payment requests with formatting errors. Therefore, please use the correct data type for each parameter.

The following table describes the encrypted payment request parameters:

In addition you can submit any parameters that are applicable or required for a credit card payment (without credit card data). More information about this you can find within Card processing.

Oops, it seems that you need to place a table or a macro generating a table within the Table Filter macro.

Key	Format	CND	Description	Beschreibung
MerchantID	ans..30	M	MerchantID, assigned by Pay-Jet. Additionally this parameter has to be passed in plain language too.	HändlerID, die von Pay-Jet vergeben wird. Dieser Parameter ist zusätzlich auch unverschlüsselt zu übergeben.

Key	Format	CND	Description	Beschreibung
TransID	ans..64	M	TransactionID provided by you which should be unique for each payment	Ihre eigene TransaktionsID, die für jede Zahlung eindeutig sein muss

Key	Format	CND	Description	Beschreibung
refnr	ns..30	O	Merchant’s unique reference number	Eindeutige Referenznummer des Händlers

Key	Format	CND	Description	Beschreibung
Amount	n..10	M	Amount in the smallest currency unit (e.g. EUR Cent). Please contact the Pay-Jet Support, if you want to capture amounts <100 (smallest currency unit).	Betrag in der kleinsten Währungseinheit (z.B. EUR Cent). Bitte wenden Sie sich an den Pay-Jet Support, wenn Sie Beträge < 100 (kleinste Währungseinheit) buchen möchten.

Key	Format	CND	Description	Beschreibung
Currency	a3	M	Currency, three digits DIN / ISO 4217, e.g. EUR, USD, GBP. Please find an overview here: A1 Currency table EN	Währung, drei Zeichen DIN / ISO 4217, z.B. EUR, USD, GBP. Hier eine Übersicht: A1 Währungstabelle

Key	Format	CND	Description	Beschreibung
MAC	an64	M	Hash Message Authentication Code (HMAC) with SHA-256 algorithm. Details can be found here: HMAC Authentication (Request) HMAC Authentication (Notify)	Hash Message Authentication Code (HMAC) mit SHA-256-Algorithmus. Details finden Sie hier: HMAC-Authentisierung (Anfrage) HMAC-Authentisierung (Notify)

Key	Format	CND	Description	Beschreibung
UserData	ans..1024	O	If specified at request, Cockpit forwards the parameter with the payment result to the shop.	Wenn beim Aufruf angegeben, übergibt das Cockpit die Parameter mit dem Zahlungsergebnis an den Shop.

Key	Format	CND	Description	Beschreibung
RTF	a1	O	Establishment of Credential on File Agreement (Cardholder agrees that his card data can be stored for further transactions).	Einrichtung der Vereinbarung für hinterlegte Zugangsdaten (Karteninhaber stimmt zu, dass seine Kartendaten für weitere Transaktionen gespeichert werden dürfen).

Key

Format

CND

Description

Beschreibung

Capture

an..6

OM

Determines the type and time of capture.

Capture Mode	Description
AUTO	Capturing immediately after authorisation (default value).
MANUAL	Capturing made by the merchant. Capture is normally initiated at time of delivery.
<Number>	Delay in hours until the capture (whole number; 1 to 696).

Bestimmt Art und Zeitpunkt der Buchung (engl. Capture).

Buchungsart	Beschreibung
AUTO	Buchung sofort nach Autorisierung (Standardwert).
MANUAL	Buchung erfolgt durch den Händler - in der Regel die Buchung zum Zeitpunkt der Warenauslieferung bzw. Leistungserbringung.
<Zahl>	Verzögerung in Stunden bis zur Buchung (ganze Zahl; 1 bis 696).

Key	Format	CND	Description	Beschreibung
OrderDesc	ans..64	M	Description of purchased goods, unit prices etc.	Beschreibung der gekauften Waren, Einzelpreise etc.

Key	Format	CND	Description	Beschreibung
URLNotify	ans..256	M	Complete URL which Cockpit calls up in order to notify the shop about the payment result. The URL may be called up only via port 443. It may not contain parameters: Use the UserData parameter instead. Common notes: We recommend to use parameter "response=encrypted" to get an encrypted response by Cockpit However, fraudster may just copy the encrypted DATA-element which are sent to URLFailure and send the DATA to URLSuccess/URLNotify. Therefore ensure to check the "code"-value which indicates success/failure of the action. Only a result of "code=00000000" should be considered successful.	Vollständige URL, die das Cockpit aufruft, um den Shop zu benachrichtigen. Die URL darf nur über Port 443 aufgerufen werden. Sie darf keine Parameter enthalten: Nutzen Sie stattdessen den Parameter UserData. Allgemeine Hinweise: Wir empfehlen, den Parameter "response=encrypted" zu verwenden, um eine verschlüsselte Antwort von Cockpit zu erhalten Betrüger könnten das verschlüsselte DATA-Element kopieren, welches an URLFailure gesendet wurde, und betrügerisch dasselbe DATA an URLSuccess/URLNotify senden. Überprüfen Sie daher unbedingt den "code"-Wert des DATA-Elements. Nur eine Antwort mit "code=00000000" sollte als erfolgreich angesehen werden.

Key	Format	CND	Description	Beschreibung
TokenExt	ans..1024	M	Google Pay Token as JSON string in the Base64 format	Google Pay Token als JSON-String im Base64-Format
Channel	a..10	O	Channel over which the order is processed. Allowed values are WEBSITE and MOBILE_APP.	Kanal, über den die Bestellung abgewickelt wird. Erlaubt sind die Werte WEBSITE und MOBILE_APP.

Parameters for Google Pay

The following table describes the result parameters with which the Pay-Jet Cockpit responds to your system

pls. be prepared to receive additional parameters at any time and do not check the order of parameters

the key (e.g. MerchantId, RefNr) should not be checked case-sentive

Oops, it seems that you need to place a table or a macro generating a table within the Table Filter macro.

Key	Format	CND	Description	Beschreibung
MID	ans..30	M	MerchantID, assigned by Pay-Jet	HändlerID, die von Pay-Jet vergeben wird

Key	Format	CND	Description	Beschreibung
PayID	an32	M	ID assigned by Cockpit for the payment, e.g. for referencing in batch files This ID refers to the credit card transaction unless an error occurs already at the Google Pay transaction.	Vom Cockpit vergebene ID für die Zahlung, z.B. zur Referenzierung in Batch-Dateien. Diese ID bezieht sich auf die Kreditkarten-Transaktion, es sei denn, es kommt bereits bei der Google-Pay-Transaktion zu einem Fehler.

Key	Format	CND	Description	Beschreibung
XID	an32	M	ID for all single transactions (authorisation, capture, credit note) for one payment assigned by Cockpit	Vom Cockpit vergebene ID für alle einzelnen Transaktionen (Autorisierung, Buchung, Gutschrift), die für eine Zahlung durchgeführt werden

Key	Format	CND	Description	Beschreibung
TransID	ans..64	M	TransactionID provided by you which should be unique for each payment	Ihre eigene TransaktionsID, die für jede Zahlung eindeutig sein muss

Key	Format	CND	Description	Beschreibung
refnr	ns..30	O	Merchant’s unique reference number	Eindeutige Referenznummer des Händlers

Key	Format	CND	Description	Beschreibung
UserData	ans..1024	O	If specified at request, Cockpit forwards the parameter with the payment result to the shop.	Wenn beim Aufruf angegeben, übergibt das Cockpit die Parameter mit dem Zahlungsergebnis an den Shop.

Key	Format	CND	Description	Beschreibung
Status	a..50	M	OK (URLSuccess) or FAILED (URLFailure)	OK (URLSuccess) oder FAILED (URLFailure)

Key	Format	CND	Description	Beschreibung
Description	ans..1024	M	Further details in the event that payment is rejected. Please do not use the Description but the Code parameter for the transaction status analysis!	Nähere Beschreibung bei Ablehnung der Zahlung. Bitte nutzen Sie nicht den Parameter Description, sondern Code für die Auswertung des Transaktionsstatus!

Key	Format	CND	Description	Beschreibung
Code	n8	M	Error code according to Cockpit Response Codes (A4 Error codes)	Fehlercode gemäß Cockpit Antwort-Codes (A4 Fehlercodes)

Key	Format	CND	Description	Beschreibung
schemeReferenceID	ans..64	C	Card scheme specific transaction ID required for subsequent credential-on-file payments, delayed authorizations and resubmssions.	Kartensystemspezifische Transaktions-ID, die für nachfolgende Zahlungen mit hinterlegten Daten, verzögerte Autorisierungen und Wiedereinreichungen erforderlich ist.

Result parameters for Google Pay

Capture / Credit / Reversal

Captures, credits and reversals do not refer to the Google Pay transaction but directly to the credit card transaction. More information about this you can find within Card processing.

Batch processing via the interface

Captures, credits and reversals via batch do not refer to the Google Pay transaction but directly to the credit card transaction. More information about this you can find within the document Card processing.

Page tree