Want a smoother checkout with Google Pay? Configure your payment options!

Integration of Google Pay into your app or web site is a good way to make checkout simpler and quicker to your clients. You can too modify the cost strategies that Google Pay supplies at checkout.

This put up guides you to configure the accepted cost strategies to your Google Pay integration. We discover the vary of choices, together with card networks, authentication strategies, and card varieties. You may discover ways to choose the perfect configuration to satisfy what you are promoting necessities and maximize safety for you and your clients.

Perceive the choices

You may arrange the Google Pay API to solely enable sure card varieties to be accepted by setting the CardParameters. It’s essential configure the next:

Authentication Strategies: Choose learn how to authenticate playing cards from the next:

PAN_ONLY: This refers to playing cards saved to the person’s Google Account.
CRYPTOGRAM_3DS: This is applicable to the tokenized playing cards added by means of the Google Pockets app on Android. It supplies enhanced safety with a device-generated 3D safe cryptogram for authentication.

Card Networks: Select card networks which you could settle for. AMEX, DISCOVER, INTERAC, JCB, MASTERCARD, and VISA are the supported networks.

^{Be aware for Brazil:}^{To supply assist for tokenized debit or credit score combo playing cards, the} ^countryCodeⁱⁿ ^{TransactionInfo}^{should be} ^BR^{and specify each the credit score and debit networks within the request.}

The next networks are supported:

VISA
ELECTRON
MASTERCARD
MAESTRO
ELO
ELO_DEBIT

Card Sorts (optionally available): You may select to permit or disallow pay as you go playing cards and bank cards.

Assurance Particulars (optionally available): You may select to request details about the validation carried out on the returned cost information. As a finest apply, we suggest you to request assurance particulars to differentiate between a Funding Main Account Quantity (FPAN) and a System Main Account Quantity (DPAN). DPAN is a tokenized model of the FPAN utilized in cell funds or digital wallets to assist stop fraud and bank card quantity publicity.

Make the perfect selections to your necessities

Authentication Strategies: PAN_ONLY is probably the most broadly supported choice, however CRYPTOGRAM_3DS supplies superior safety and may qualify for legal responsibility shift with sure card networks. It is extremely beneficial to allow each authentication strategies. Make certain to verify authentication choices together with your processor to see which of them are supported.

_Essential_{: Ensure that your current danger checks and controls for cost transactions are additionally utilized to Google Pay FPAN transactions recognized with assurance particulars. Google Pay validation and fraud checks aren’t meant to interchange your danger administration processes. For extra info, consult with} _{When to step-up your Google Pay transactions as a PSP}_.

Card Networks: Your selections rely in your cost processor’s capabilities. Just remember to assist the networks that align together with your processing setup.

Card Sorts: If you happen to’ve particular enterprise necessities to exclude pay as you go or bank cards, use the respective choices to regulate their acceptance.

Assurance Particulars: If you need assurance particulars, then you may get info on the account verification and the cardholder authentication. If each are true, you don’t need to step up the returned credentials.

Account Verified: True, if the cardholder possession is carried out
Card Holder Authenticated: True, if the identification and verification (ID&V) is carried out.

^Essential^{: If each aren’t true, we suggest you to run the identical danger checks and authentication checks together with 3D safe stream if relevant.}

Billing Tackle: It relies on what you are promoting requirement which billing handle fields you wish to return within the response. Nonetheless, to scale back person friction and drive most person conversions (incremental gross sales), we suggest you to solely request what is important.

Implementation

Following is the instance for CardParameters configuration. You should utilize values that meet what you are promoting necessities.

{
  "allowedPaymentMethods": [
    {
      "type": "CARD",
      "parameters": {
        "allowedCardNetworks": ["VISA", "MASTERCARD", "AMEX"],
        "allowedAuthMethods": ["PAN_ONLY", "CRYPTOGRAM_3DS"],
        "allowPrepaidCards": true,
        "allowCreditCards": true,
        "assuranceDetailsRequired": true,
      }
    }
  ]
}

^{Be aware}^{: This can be a simplified instance. Seek the advice of the Google Pay API documentation for the precise implementation particulars to your chosen platform (}^Android^or ^web^).

Coming quickly

Two new optionally available properties, allowedIssuerCountryCodes and blockedIssuerCountryCodes will likely be added to the CardParameters object. Each properties will settle for a listing of strings that comprises ISO 3166-1 alpha-2 nation codes. These properties will likely be accessible for testing by the tip of the 12 months.

These properties are relevant in PaymentDataRequest, IsReadyToPayRequest, and create button APIs on Android and web.

The 2 properties will likely be mutually unique, so just one might be set at a time. If neither property is specified, Google Pay customers can choose legitimate card cost strategies issued by issuers from any area.

Google Pay customers will likely be restricted to pick card cost strategies for playing cards issued by issuers based mostly both in one of many areas specified by the allowedIssuerCountryCodes allowlist or not in any of the areas specified by the blockedIssuerCountryCodes blocklist. If a card is not issued within the allowed nations, the cardboard will likely be grayed out with a message Not accepted right here on the Google Pay paysheet.

Following is an instance of allowedPaymentMethods configuration with the brand new allowedIssuerCountryCodes property specified.

{
  "allowedPaymentMethods": [
    {
      "type": "CARD",
      "parameters": {
        "allowedCardNetworks": ["VISA", "MASTERCARD", "AMEX"],
        "allowedAuthMethods": ["PAN_ONLY", "CRYPTOGRAM_3DS"],
        "allowedIssuerCountryCodes": ["US", "CA"],
        "allowPrepaidCards": true,
        "allowCreditCards": true,
        "assuranceDetailsRequired": true,
      }
    }
  ]
}

Conclusion

You may optimize your Google Pay integration for safety, comfort, and enterprise necessities with cautious configuration of your accepted cost strategies.

For extra help together with your implementation, sign up to the Google Pay & Wallet Console to create a assist ticket. As well as, you’ll be able to be part of the developer group within the #funds channel on Discord.

This text is written with AI-assistance from Gemini.

Source link