Google Pay™ Android

Google Pay™ Android

Google PayTM Android offers an easier, more secure way to pay and facilitate the checkout process by using a mobile device access code or other physical recognition system during an online payment.

Android Process

In order to start accepting Google PayTM Android in your App, you will need to use our SDK for Google PayTM. SDKs are ready-to-install kits containing APIs as well as additional tools for development.

During a transaction, the merchant sends the Google PayTM encrypted payload to PayFacto gateway. The PayFacto gateway will then decrypt the payload and process the transaction.

With Google PayTM, PayFacto supports: Purchase and Pre-Authorization. PayFacto also supports Refund, Pre-Authorization Completion and Void, and no interaction is required with Google PayTM for these transactions.

PayFacto supports all the major card brand networks (Visa, Mastercard, Amex) in either 3DS or PAN only mode.


Important

By using Google Pay in your application, you agree to follow Google's Pay APIs Acceptable Use Policy and accept the terms defined in the Google Pay API Terms of Service.

Overview

1) The merchant application requests and receives the encrypted payload from Google Pay API.

2) The payload is sent to the merchant's server.

3) The PayFacto payment gateway receives the encrypted payload from the merchant's server and decrypts it.

4) PayFacto processes the transaction with the host.

Google Pay™ Android

Building a Demo App of the Solution

1) Git clone Google Pay Android Demo app repository https://github.com/google-pay/android-quickstart
2) Update the Demo App for PayFacto payment gateway
3) Build and run the Demo App
4) Validate the transaction in PayFacto Gateway Payment Manager

Customizing the Demo App for PayFacto Payment Gateway

1) In the file Constants.java,

  • Set the PAYMENT_GATEWAY_TOKENIZATION_NAME to 'payfacto'
  • Set the exampleGatewayMerchantId to your PayFacto gateway merchant ID


2) In the file CheckoutActivity.java in the method handlePaymentSuccess

  • Add the code to call PayFacto gateway Payment API
  • Make sure to specify “GooglePay” in the OEMWalletType
  • The Payment method token (paymentData.paymentMethodData.tokenizationData.token) is sent in the OEMWalletData

PayFacto Payment API Endpoints

The payload is transmitted to PayFacto's servers via the payment API

The following endpoints are available for Android.

APIEndpoint
IAP - Purchasehttps://test.api.payfacto.cloud/v1/iapPurchase
IAP - Preauthorizationhttps://test.api.payfacto.cloud/v1/iapPreAuthorization
Completionhttps://test.api.payfacto.cloud/v1/completion
Refund Without Cardhttps://test.api.payfacto.cloud/v1/refundWithoutCard
Voidhttps://test.api.payfacto.cloud/v1/void


Acknowledgment Process

Each transaction requires the merchant to send an acknowledgment (Ack) to the PayFacto gateway. The ACK transaction is used to confirm that the response was successfully received and the transaction is set to COMPLETED.

Transaction expiration delay

Transaction delay timeout

The merchant has 3 minutes to send the acknowledgement to our platform. Otherwise, PayFacto will automatically reverse the transaction. The transaction is set to VOIDED after the delay expiration.



The ACK transaction result can be either true or false. If you receive “false”, you can try to send the ACK transaction again for 2 more times. If the result is still “false”, the transaction was NOT successful.

APIEndpoint
Ackhttps://test.api.payfacto.cloud/v1/ack

Google Pay - API and Merchant Capabilities

Google Pay API json request object is documented here https://developers.google.com/pay/api/android/reference/request-objects#PaymentMethodTokenizationSpecification

Make sure to review the Google Pay developer documentation to specify your supported capabilities



In Constants.java

  public static final List<String> SUPPORTED_NETWORKS = Arrays.asList(
      "AMEX",
      "MASTERCARD",
      "VISA");

References

Android merchant

    • Related Articles

    • Apple Pay™ In-App

      Apple Pay™ In-App is integrated to applications in order to facilitate the checkout process by using a mobile device access code or other physical recognition system during an online payment with Apple Pay™. Edit Advantages The main advantages of the ...

    • SPL - Secure Pay By Link

      Secure Pay By Link Secure Pay By Link (SPL) is a new offering from PayFacto that allows a merchant to defer a SHC session to another time. It does that by creating a link that the cardholder can follow to a hosted page. When the cardholder navigates ...

    • Android PayFacto Error Codes

      This page lists the meaning of error codes if the application rejects the transaction. Error code value Description -1 No extra data -2 Amount or the Invoice sent is invalid -3 Transaction type is invalid -4 Invoice sent is already used or do not ...

    • Recurring Payments (Tokens)

      dit Introduction The recurrent payment module allows to merchant to execute transactions according to criteria established with the client and without the presence of the cardholder. It also allows to automatically making payments at regular ...

    • API v1.0 - SHC - Secure Hosted Checkout

      About SHC What is Secure Hosted Checkout? Secure Hosted Checkout (SHC) is a JavaScript library that allows merchants to collect and send cardholder information to PayFacto for verification without needing to access that information directly. When ...