Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
developer:api_specification:xml_payment_features_googlepay [2018/05/25 11:26] thiago123 [Fixing] Release of version 5.2 |
developer:api_specification:xml_payment_features_googlepay [2019/06/04 11:13] vinayh [Availability] |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== Google Pay™ Using XML ====== | ||
| + | |||
| + | ~~TOC~~ | ||
| + | |||
| + | \\ | ||
| + | Google Pay helps users quickly and easily complete purchases in apps and on the web using payment methods saved to a Google account or Android device. | ||
| + | ===== Availability ===== | ||
| + | |||
| + | Google Pay is enabled on the %Gateway for **TSYS Saratoga** and **Elavon** Processors only, supporting the following card types: VISA, MasterCard, Discover/Diners, AMEX and JCB. | ||
| + | |||
| + | When it comes to being able to accept Google Pay transactions, the location of your business matters. Merchants in the following regions are eligible: | ||
| + | |||
| + | * - United States | ||
| + | * - Europe | ||
| + | * - Asia Pacific | ||
| + | * - Australia | ||
| + | |||
| + | Customer compatibility depends on where the customer stores their card details: | ||
| + | |||
| + | * **Card on Google Account** | ||
| + | * - Available worldwide | ||
| + | * **Card on Android Device** - Only customers in the following countries can make this type of payment: | ||
| + | * - United States | ||
| + | * - United Kingdom | ||
| + | * - Singapore | ||
| + | * - Australia | ||
| + | * - Hong Kong | ||
| + | * - Poland | ||
| + | * - New Zealand | ||
| + | * - Ireland | ||
| + | * - Belgium | ||
| + | * - Russia | ||
| + | * - Japan | ||
| + | * - Canada | ||
| + | * - Taiwan | ||
| + | * - Spain | ||
| + | * - Ukraine | ||
| + | * - Brazil | ||
| + | * - Czech Republic | ||
| + | * - Slovakia (Feb, 2018) | ||
| + | * - France (Coming Spring 2018) | ||
| + | * - South Korea (Late 2018) | ||
| + | ===== Integrating ===== | ||
| + | |||
| + | In this integration method you ned to implement a few steps: | ||
| + | |||
| + | **Step 01**: Setup | ||
| + | |||
| + | To process google pay payments, you will need to be sure that the terminals you want to use are configured for that, so: | ||
| + | |||
| + | * **First**, register with Google: In order to use the Google Pay API in Production, you must register with Google. To do this, simply navigate to the Google Payment API Support page. You will be asked to register the website you wish to make payments with, and Google will give you a Google Merchant ID which you will use during your Google Pay requests. | ||
| + | |||
| + | * **Then**, have your Google Pay details configured: Contact our support team and ask for Google Pay to be enabled on the desired terminals and then provide the Google Merchant ID that Google assigned to you. | ||
| + | |||
| + | \\ | ||
| + | |||
| + | **Step 02**: Integrate the Google Pay API to your website | ||
| + | |||
| + | The merchant’s developer team will need to implement the **[[https://developers.google.com/pay/api/web/setup|Google Payment API]]** to the merchant website in order to retrieve the customers (encrypted) card details (to be informed as **GOOGLEPAYLOAD**). | ||
| + | |||
| + | Note that during your **Google Pay API** Request, you will need to specify the following details: | ||
| + | |||
| + | * **merchantId** - The Merchant ID given to you by Google | ||
| + | * **gateway** - "Nuvei" (but all lower case) | ||
| + | * **gatewayMerchantId** - The Merchant ID given to you by the gateway | ||
| + | |||
| + | \\ | ||
| + | |||
| + | **Step 03**: Send Payment Request | ||
| + | |||
| + | After you’ve retrieved the Google Payload, convert the users Google Pay data to Hexadecimal, place it in the XML Payment Request in the GOOGLEPAYLOAD tag, and send the XML Payment Request to our servers as normal. | ||
| + | |||
| + | Consult the **[[developer:api_specification:xml_payment_features|XML Payment Features]]** for details on the URL for the request and other body fields too. Using the example below (change the data inside the tags) shows you how to perform a simple transaction using google pay. | ||
| + | |||
| + | <code xml> | ||
| + | <PAYMNET> | ||
| + | <ORDERID>123456</ORDERID> | ||
| + | <DATETIME>05-01-2017:11:04:55:055</DATETIME> | ||
| + | <TERMINALID>1234001</TERMINALID> | ||
| + | <GOOGLEPAYLOAD>7b0d0a2020227368697070696e67436f6e74616374223a207b0d0a2020202022656d61696c41646472657373223a20226578616d706c6540776f726c646e65747470732e636f6d222c0d0a202020202266616d696c794e616d65223a2022222c0d0a2020202022676976656e4e616d65223a2022222c0d0a202020202270686f6e6574696346616d696c794e616d65223a2022222c0d0a202020202270686f6e65746963476976656e4e616d65223a2022220d0a20207d2c0d0a202022746f6b656e223a207b0d0a20202020227061796d656e7444617461223a207b0d0a20202020276c6a59544d7559334a734d41344741315564447745422f775145417749486744415042676b71686b694739324e6b42683045416755414d416f4743437147534d343942414d4341306b414d4559434951446148474f75692b583254343452364756704e376d326e456372365436734d6a4f685a354e75536f316567774968414c31612b2f68703838444b4a3073763365543346785763733731786d624...... (etc it's quite long)</GOOGLEPAYLOAD> | ||
| + | <CARDTYPE>APPLEPAY</CARDTYPE> | ||
| + | <CARDHOLDERNAME>John Junior Jameson</CARDHOLDERNAME> | ||
| + | <HASH>2db545a97060c95c33bd2844418ff6e7</HASH> | ||
| + | <CURRENCY>USD</CURRENCY> | ||
| + | <TERMINALTYPE>2</TERMINALTYPE> | ||
| + | <TRANSACTIONTYPE>7</TRANSACTIONTYPE> | ||
| + | <POSTCODE>12345</POSTCODE> | ||
| + | </PAYMENT> | ||
| + | </code> | ||
| + | |||
| + | \\ | ||
| + | |||
| + | Variations of this request are possible, but for that, consult the complete reference for a payment at the **[[developer:api_specification:xml_payment_features|XML Payment Features]]** page and don't forget that the **GOOGLEPAYLOAD** tag replaces the **TRACKDATA** (for transactions using cards) or **CARDNUMBER** (for transctions using secure card) tags. | ||
| + | |||