Adyen - Googlepay

Google Pay is the fast, simple way to pay with your phone and speed through checkout within apps, websites and in stores. There is no maximum transaction limit when you use your phone and card. Your payment info is also protected with multiple layers of security so you can pay with peace of mind – all the time.

Source: https://pay.google.com

Features

Integration type

Redirection

Tokenization

Yes

Payment Flow

1-step payment flow : Capture (direct debit)

2-step payment flow : Authorization + Capture

3-step payment flow : Pending Authorization + Authorization + Capture (asynchronous workflow)

Additional features

Information request and CIT

MIT

Server-to-server

How to test?

info

You have to create a Google developper account in order to test this payment method with a compatible device (minimum Android 5.0 or later + NFC supported).

Data Mapping & Mandatory Fields

Below is the mapping between your Create Session request and the fields expected by this payment method.

Purse Session field	Mandatory
amount	Yes
order.redirection	Yes
order.reference	No
customer.reference(Only for tokenization)	No
shipments.delivery_method_reference	No
shipments.shipping_address.first_name	No
shipments.shipping_address.middle_name	No
shipments.shipping_address.last_name	No
shipments.shipping_address.city	No
shipments.shipping_address.postal_code	No
shipments.shipping_address.country_code	No
shipments.shipping_address.phone	No

Payment Labels

Label	Method	Payment type
adyen	googlepay	primary (wallet)

Actions

Status

PSP status	State	Code	Description
MALFORMED_PARTNER_RESPONSE	ERROR	TECHNICAL_ISSUE_TO_CONTACT_PARTNER	Malformed partner response, partner HTTP response is not of json type.
SUCCESS	SUCCESS	SUCCEEDED	action done successfully
ERROR	ERROR	FAILED	An error occurred when calling adyen
NO_REDIRECT_RESULT	WAITING	WAITING_PARTNER_RESPONSE	No redirect result could be found, customer was not redirected to our redirection API. Awaiting for notification from Adyen
AuthenticationFinished	SUCCESS	SUCCEEDED	The payment has been successfully authenticated with 3D Secure.
AuthenticationNotRequired	SUCCESS	SUCCEEDED	The transaction does not require 3D Secure authentication, for example, the issuing bank does not require authentication or the transaction is out of scope. Check the authenticationNotRequiredReason parameter to know why authentication was skipped.
Authorised	SUCCESS	SUCCEEDED	The payment was successfully authorised.
Cancelled	ERROR	FAILED	The payment was cancelled (by either the shopper or your own system) before processing was completed.
ChallengeShopper	ERROR	FAILED	The issuer requires further shopper interaction before the payment can be authenticated. Returned for 3D Secure 2 transactions. WORKFLOW NOT IMPLEMENTED
Error	ERROR	FAILED	There was an error when the payment was being processed.
IdentifyShopper	ERROR	FAILED	The issuer requires the shopper's device fingerprint before the payment can be authenticated. Returned for 3D Secure 2 transactions. WORKFLOW NOT IMPLEMENTED
14_002	ERROR	FAILED	Required field 'paymentData' is not provided.
Pending
PresentToShopper	ERROR	FAILED	Present the voucher or the QR code to the shopper.WORKFLOW NOT IMPLEMENTED
Received
received
RedirectShopper
Refused	ERROR	FAILED	The payment was refused. You'll receive a refusalReason in the same response that indicates why it was refused.
ABANDONED	ERROR	ABORTED_BY_CUSTOMER	The customer abandoned payment after validate (should only happen with bancontact mobile as it displays a QR code that still needs to be used to pay)