Difference between revisions of "Google Pay"

From Barion Documentation
Jump to navigation Jump to search
(Implementing the Google Pay button)
 
(8 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
{{PageTitle|title=Google Pay integration}}
 
{{PageTitle|title=Google Pay integration}}
 
+
__NOTOC__
{{IncompletePage}}
 
 
 
 
Google Pay™ is a payment option for the customer. Google securely stores the customer's card information and hands it over to the merchant for processing. The process ensures that the card information stays secure and encrypted, the merchant does not know the details of the card.
 
Google Pay™ is a payment option for the customer. Google securely stores the customer's card information and hands it over to the merchant for processing. The process ensures that the card information stays secure and encrypted, the merchant does not know the details of the card.
  
Line 39: Line 37:
 
== Implementing the Google Pay button ==
 
== Implementing the Google Pay button ==
  
First read through the [https://developers.google.com/pay/api/web/overview introduction] in Google's documentation to see what you need to do to accept payments via Google Pay. If your system is ready, follow [[https://developers.google.com/pay/api/web/guides/tutorial this Google tutorial]] to create the JS code that renders the Google Pay button.
+
First read through the [https://developers.google.com/pay/api/web/overview introduction] in Google's documentation to see what you need to do to accept payments via Google Pay. If your system is ready, follow [https://developers.google.com/pay/api/web/guides/tutorial this Google tutorial] to create the JS code that renders the Google Pay button.
  
 
To identify the request towards Google you have to provide two IDs:
 
To identify the request towards Google you have to provide two IDs:
* '''gateway id''', the ID that identifies the gateway you are using to process the cahrgess. This is <code>barion</code>  
+
* '''gateway id''', the ID that identifies the gateway you are using to process the charges. This is <code>barion</code>  
 
* '''the gateway merchant id''', the ID that identifies your webshop. This can be copied from the detail page of your shop (in Barion) <br/> [[File:Merchantid.png]]
 
* '''the gateway merchant id''', the ID that identifies your webshop. This can be copied from the detail page of your shop (in Barion) <br/> [[File:Merchantid.png]]
  
 
These IDs must be set in your JS code, like this:
 
These IDs must be set in your JS code, like this:
  
<pre>
+
<syntaxhighlight lang="javascript" line='line'>
 
const tokenizationSpecification = {
 
const tokenizationSpecification = {
 
   type: 'PAYMENT_GATEWAY',
 
   type: 'PAYMENT_GATEWAY',
Line 55: Line 53:
 
   }
 
   }
 
};
 
};
</pre>
+
</syntaxhighlight>
 +
 
 +
We support four card types: American Express, Discover, MasterCard and Visa. You have to specify this in your JS code:
 +
<syntaxhighlight lang="javascript" line='line'>
 +
const allowedCardNetworks = ["AMEX", "DISCOVER", "MASTERCARD", "VISA"];
 +
</syntaxhighlight>
 +
 
 +
Currently we only support card that already been authenticated with 3DS, so you have to specify this as well
 +
 
 +
<syntaxhighlight lang="javascript" line='line'>
 +
const allowedCardAuthMethods = ["CRYPTOGRAM_3DS"];
 +
</syntaxhighlight>
 +
 
 +
To be able to get the e-mail address of the customer, please specify the <code>"emailRequired": true</code> in the [https://developers.google.com/pay/api/web/reference/request-objects#PaymentDataRequest PaymentDataRequest]. This will the the Google API to send back the e-mail address of the Google wallet int the [https://developers.google.com/pay/api/web/reference/response-objects#PaymentData PaymentData] object.
 +
 
 +
 
 +
Make sure to comply with the [https://developers.google.com/pay/api/web/guides/brand-guidelines Google Brand Guidelines] when you place the pay button on your webshop.
  
 
== Implementing the Barion API call ==
 
== Implementing the Barion API call ==
Line 61: Line 75:
 
To be able to pass on the encrypted token to Barion you have to implement a Barion API call. For the technical communication guide please read the this: [[Calling_the_API|Calling the API]].
 
To be able to pass on the encrypted token to Barion you have to implement a Barion API call. For the technical communication guide please read the this: [[Calling_the_API|Calling the API]].
  
The endpoint you have to implement is the [[Payment-StartPaymentWithGoogleToken-v3|v3/payment/startpaymentwithgoogletoken]]. The data that you have to provide here hase three key elements:
+
The endpoint you have to implement is the [[Payment-StartPaymentWithGoogleToken-v3|v3/payment/startpaymentwithgoogletoken]]. The data that you have to provide here has three key elements:
 
* all the information about the goods you want to sell
 
* all the information about the goods you want to sell
 
* the e-mail address of the customer (provided by Google)
 
* the e-mail address of the customer (provided by Google)
 
* the Google Pay token (provided by Google)
 
* the Google Pay token (provided by Google)
 +
 +
=== Possible error responses ===
 +
 +
The endpoint can result in any error described [https://docs.barion.com/Responsive_web_payment#Processing_the_error_response at the web payment scenario]. Besides those these are the specific error messages for this scenario
 +
 +
{| class="wikitable api-table"
 +
! Error code || Description
 +
|-
 +
| InvalidGoogleToken || The token provided was invalid. Either
 +
* malformed
 +
* or contained invalid structure
 +
|-
 +
| InvalidGoogleMessage || The content of the token was invalid. Either
 +
* contained data that was not recognized
 +
* or the message was expired
 +
|-
 +
|}

Latest revision as of 07:34, 24 November 2020

Google Pay integration

Google Pay™ is a payment option for the customer. Google securely stores the customer's card information and hands it over to the merchant for processing. The process ensures that the card information stays secure and encrypted, the merchant does not know the details of the card.

NOTE
We currently only support Google Pay for the web, android support is coming soon.

Payment Process

This picture describes the payment process:

Googlepay.png

  1. The customer clicks the Google Pay button. A window will pop up where the customer can choose a previously saved card to charge or even provide a new one.
  2. The JS code receives the encrypted card information.
  3. The JS code send the encrypted information to the merchant's server side
  4. The merchant's server side gathers all the information to start a payment and calls the Barion API
  5. The Barion API handles the request, decrypts the packages and charges the card. The result of the payment is sent back to the caller.
  6. The merchant's server communicates the result to the client side and the webshop renders the result of the payment.

Integration

IMPORTANT
To integrate this feature you have to develop the integration yourself! You need to understand Javascript code and is is also required to modify your webshop's server code!

These are the steps that you have to complete to use Google Pay on your website:

  1. Register a wallet in Barion and create a shop
  2. Implement the Google Pay button on your webshop's client side
  3. Implement the Barion API call on your webshop's server side

Creating a shop in Barion

To be able to use Barion as a Google Pay token processor you have to register a wallet and open a shop for your webshop.

  • You must register a Barion wallet at the Barion website or in the Sandbox environment. Learn more about the Sandbox environment here.
  • For this wallet you have to create a shop which should be approved by Barion.
  • For every currency you plan to conduct payments in you have to make sure there is an account created in your Barion wallet. This means that if you plan to have USD payments then there should be an USD account created in your wallet.
  • To make sure every corner case scenario works for your webshop it is best to topup that account with a small amount (approx. 5-10EUR or your choice of currency around the same value).

Implementing the Google Pay button

First read through the introduction in Google's documentation to see what you need to do to accept payments via Google Pay. If your system is ready, follow this Google tutorial to create the JS code that renders the Google Pay button.

To identify the request towards Google you have to provide two IDs:

  • gateway id, the ID that identifies the gateway you are using to process the charges. This is barion
  • the gateway merchant id, the ID that identifies your webshop. This can be copied from the detail page of your shop (in Barion)
    Merchantid.png

These IDs must be set in your JS code, like this:

1 const tokenizationSpecification = {
2   type: 'PAYMENT_GATEWAY',
3   parameters: {
4     'gateway': 'barion',
5     'gatewayMerchantId': 'PUT HERE YOUR SHOPS MERCHANT ID FROM BARION'
6   }
7 };

We support four card types: American Express, Discover, MasterCard and Visa. You have to specify this in your JS code:

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

Currently we only support card that already been authenticated with 3DS, so you have to specify this as well

1 const allowedCardAuthMethods = ["CRYPTOGRAM_3DS"];

To be able to get the e-mail address of the customer, please specify the "emailRequired": true in the PaymentDataRequest. This will the the Google API to send back the e-mail address of the Google wallet int the PaymentData object.


Make sure to comply with the Google Brand Guidelines when you place the pay button on your webshop.

Implementing the Barion API call

To be able to pass on the encrypted token to Barion you have to implement a Barion API call. For the technical communication guide please read the this: Calling the API.

The endpoint you have to implement is the v3/payment/startpaymentwithgoogletoken. The data that you have to provide here has three key elements:

  • all the information about the goods you want to sell
  • the e-mail address of the customer (provided by Google)
  • the Google Pay token (provided by Google)

Possible error responses

The endpoint can result in any error described at the web payment scenario. Besides those these are the specific error messages for this scenario

Error code Description
InvalidGoogleToken The token provided was invalid. Either
  • malformed
  • or contained invalid structure
InvalidGoogleMessage The content of the token was invalid. Either
  • contained data that was not recognized
  • or the message was expired