Testing Android SDK - Card Payments

testing android sdk card payments with judopay’s android mobile sdk solution, a minimal integration is all that is required to enable you to take a card payment take a card preauth take a card token payment take a card token preauth check the validity of a card, using checkcard save the card details, using savecard card payment 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, in the sandbox environment, using the docid obafnuc1umhk vihhs5d to test your integration is working correctly this will give you confidence for when your integration goes live these images are from our dummy app, your interface may look different suggested test scenario process a card payment preauth use the test card details docid obafnuc1umhk vihhs5d tip tip the app is using the payment / preauth flow, which has been set up in the payment configuration object expected outcome you will be directed to a successful transaction completed page suggested test scenario process a card token payment token preauth tip tip the app is using the token payment / token preauth flow, which has been set up in the payment configuration object if your app allows the consumer to save their card details, use the save card scenario and use the saved card token reference to make a payment expected outcome you will be directed to a successful transaction completed page suggested test scenario process a card payment prompting the consumer to enter their billing address expected outcome depending on your use case and app configuration the android sdk prompts the consumer to enter their billing details example flow prompting the consumer to enter their billing address prompt enter billing address suggested test scenario process a card payment without the billing address fields displayed expected outcome depending on your use case and app configuration the android sdk does not prompt the consumer to enter their billing details if you process a token payment, the billing details form will not be displayed in the payment flow this is due to the card token being used, which already has the cardholders details securely saved example 'no challenge' flow android no challenge flow suggested test scenario handle a 3d secure 2 flow tip tip it is useful to have an understanding of the full 3ds 2 payment flow, including the conditional steps, to verify how it relates to the user journey in your app for more information on the 3ds 2 flow, see docid\ k7fnzbol73ssctbct4nxm expected outcome depending on your use case and app configuration use the card holder name table to trigger any 3d secure 2 flow, see cardholdername table your app explicitly forces a challenge flow, so the consumer will be directed to the challenge page for the purpose of this exercise, below we have an example of a frictionless flow successful challenge flow unsuccessful challenge flow example 3d secure 2 'frictionless' flow android no challenge flow example successful 3d secure 2 'challenge' flow android successful challenge flow example unsuccessful 3d secure 2 'challenge' flow android payment failed test card data to simulate a successful card payments request, use the docid obafnuc1umhk vihhs5d calling the mobile sdk functions for more information on integrating your android app, including calling the mobile sdk functions see docid\ fyef n37tnl1c5dsscml3 card payment scenarios (negative flow) declines can occur for various reasons, it can be impossible to simulate all the negative flows in a sandbox environment 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 card payment preauth request decline using the following cardnumber 4221690000004963 cv2 452 expirydate 12/24 expected error and description card declined you will be re directed to an error page with an error message suggested negative test scenario to handle a decline scenario, attempt to perform a card payment preauth request decline using the following example use cases enter an invalid cvv user taps the cancel button on the 3ds 2 challenge screen expected error and description card declined you will be re directed to an error page with an error message suggested negative test scenario attempt to perform a card payment where the incorrect card details are entered this will perform the field validation checks expected error and description payment declined form validation error messages will be displayed in the form the pay now button will be greyed out