Google Pay Developer Guide
This section describes how to use this guide and where to find further information.
Audience and Purpose
This document is written for merchants who want to enable customers to use Google Pay to
pay for in-app purchases. This document provides an overview of integrating the Google API
and describes how to request the
National Australia Bank
API to process an
authorization.This document describes the Google Pay service and the
National Australia Bank
API. You
must request the Google API to receive the customer’s encrypted payment data before
requesting the National Australia Bank
API to process the transaction.Conventions
The following special statements are used in this document:
IMPORTANT
An
Important
statement contains information essential to
successfully completing a task or learning a concept.Recent Revisions to This Document
24.03
This revision contains only editorial changes and no technical updates.
24.02
Corrected URL to setting up Sandbox Account.
24.01
Fixed typo in Javascript sample. See Formatting Payment Blobs.
23.02
Updated the Google Pay authorizations required fields list. See Required Fields for a Google Pay Authorization.
Added follow-on transaction support to the Google Pay authorization section. See Google Pay Authorizations.
23.01
This revision contains only editorial changes and no technical updates.
VISA Platform Connect: Specifications and Conditions for Resellers/Partners
The following are specifications and conditions that apply to a Reseller/Partner
enabling its merchants through
Cybersource for Visa Platform Connect
(“VPC”) processing
. Failure to meet any of the specifications and
conditions below is subject to the liability provisions and indemnification
obligations under Reseller/Partner’s contract with Visa/Cybersource.- Before boarding merchants for payment processing on a VPC acquirer’s connection, Reseller/Partner and the VPC acquirer must have a contract or other legal agreement that permits Reseller/Partner to enable its merchants to process payments with the acquirer through the dedicated VPC connection and/or traditional connection with such VPC acquirer.
- Reseller/Partner is responsible for boarding and enabling its merchants in accordance with the terms of the contract or other legal agreement with the relevant VPC acquirer.
- Reseller/Partner acknowledges and agrees that all considerations and fees associated with chargebacks, interchange downgrades, settlement issues, funding delays, and other processing related activities are strictly between Reseller and the relevant VPC acquirer.
- Reseller/Partner acknowledges and agrees that the relevant VPC acquirer is responsible for payment processing issues, including but not limited to, transaction declines by network/issuer, decline rates, and interchange qualification, as may be agreed to or outlined in the contract or other legal agreement between Reseller/Partner and such VPC acquirer.
DISCLAIMER: NEITHER VISA NOR CYBERSOURCE WILL BE RESPONSIBLE OR LIABLE FOR ANY ERRORS
OR OMISSIONS BY THE VISA PLATFORM CONNECT ACQUIRER IN PROCESSING TRANSACTIONS.
NEITHER VISA NOR CYBERSOURCE WILL BE RESPONSIBLE OR LIABLE FOR RESELLER/PARTNER
BOARDING MERCHANTS OR ENABLING MERCHANT PROCESSING IN VIOLATION OF THE TERMS AND
CONDITIONS IMPOSED BY THE RELEVANT VISA PLATFORM CONNECT ACQUIRER.