Testing Google Pay™ Wallet - via Mobile SDK

testing google pay™ wallet via mobile sdk prerequisites before you can process google pay™ payments and preauths with judopay, you will need to https //support google com/googleplay/android developer/answer/7161426?hl=en gb to get your merchant ids to test google pay™ payments and preauths in sandbox, contact mailto\ developersupport\@judopay com to configure your wallet payments credentials google pay™ wallet scenarios (positive flow) depending on your use case and app configurations , some of the following scenarios may not be relevant to you follow our suggested guidelines to simulate positive / happy path scenarios, to test your integration is working correctly this will give you confidence for when your integration goes live important to consider for google pay™ (dpan) the google pay™ mobile wallet payment flow provides consumers with an extra layer of security, encrypting and decrypting the card details sent in the payload by replacing the consumer's card details with a device token this payment method is sca compliant by default for a successful end to end wallet payment testing journey, it is recommended to perform wallet test scenarios in a production environment use live cards to process test payments and preauths we do not recommend making merchant initiated transactions using card tokens that were generated by google pay™ dpan you may experience a lower transaction success ratio these images are from our dummy app, your interface may look different suggested test scenario process a google pay™ wallet payment preauth tip tip the app is using the payment / preauth flow, which has been set up in the payment configuration object we suggest checking the following options have been configured correctly merchant name billing address phone no shipping address shipping address phone no email address for more information on configuring your app, see docid\ it3yrnihegsketqtsxgi3 expected outcome you will be directed to a successful transaction completed page the below is a typical end user flow when making a google pay™ wallet payment google pay mobile flow suggested test scenario process a wallet payment preauth request to test the google pay™ payment method is correctly configured and supported tip tip your judopay account and your app have been configured to support the google pay™ payment method expected outcome the buy with g pay button will be displayed test card data to simulate a successful request, use live cards to process test payments and preauths in a production environment the card will not be charged when processing test payments in a production environment calling the mobile sdk functions for more information on integrating your android app, including calling the mobile sdk functions see docid\ it3yrnihegsketqtsxgi3 google pay™ wallet scenarios (negative flow) declines can occur for various reasons, it can be impossible to simulate all the negative flows depending on your use case and app configurations, some of the following scenarios may not be relevant to you follow our suggested guidelines to simulate negative scenarios, to test your app’s error handling this will give you confidence for when your integration goes live important to consider how your app handles negative flows your customer's experience should a negative flow occur logic to communicate error messages customise how your app responds how to maintain application consistency these images are from our dummy app, your interface may look different suggested negative test scenario to handle a decline scenario, attempt to perform a google pay™ wallet payment preauth request where the user cancels the payment expected error depending on how your app has been configured to respond, you may redirect the user to their cart an error page displaying an error message