Android
- You have set up your Judopay account.
- Sign up for your sandbox account, to receive access to your Judopay dashboard and the sandbox environment.
- Your judoIds and tokens are configured and enabled as appropriate.
- You have the latest version of the Android SDK.
For Mobile apps, we recommend using payment session authentication.
- Android Studio and Build Tools - (We recommend you use the latest stable version).
- Your app targets API 32 or higher.
- Minimum Android SDK version 21 (Android 5.0).
The Mobile SDK is available for Android as a Gradle dependency. No need to clone a repository.
To add Judopay as a dependency to your current project:
- Navigate to your build.gradle file
- In the dependencies section add the latest com.judopay:judokit-android:{version} For the latest version, see Android Releases.
An example of how your build.gradle might look:
3. Ensure the Maven Central Repository has been added:
See Judopay's JudoKit for Android on Github.
The Judo builder is at the heart of the Android Mobile SDK. This class is responsible for:
- Setting all the required parameters
- Customising the payment flow
- Import some of the classes and properties from the com.judopay.judokit.android package as detailed below:
- Judo is the class used to build the payment flow.
- Amount and Reference: Classes used to set the amount and reference properties.
- PaymentWidgetType allows for multiple payment types:
- Card
- Google Pay™
- iDEAL
- Identifies the transaction result:
- PAYMENT_SUCCESS
- PAYMENT_ERROR
- PAYMENT_CANCELLED
- The JudoActivity class is used to start a payment intent.
- In the Amount object provide the Amount value and Currency type:
- In the Reference object provide the ConsumerReference string:
- Set the following required parameters:
- The token and secret values, OR create the authorisation object (Step 3 below).
- Set the SDK to run in sandbox mode
- Set the following objects:
- Judo ID
- JudoId format = 100100100
- Authorisation object (if using this method)
- Amount
- Reference
- Create the authorisation object:
4. Set the authorisation object when invoking Judo builder:
Field | Description |
---|---|
CARD_PAYMENT | Card Payment |
TOKEN_PAYMENT | Starts a token payment with optionally asking the user to enter their CSC and / or cardholder name. |
PRE_AUTH | Card PreAuth |
TOKEN_PRE_AUTH | Starts a pre-auth token payment with optionally asking the user to enter their CSC and / or cardholder name. |
CREATE_CARD_TOKEN | Save Card |
CHECK_CARD | Check Card |
PAYMENT_METHODS | Payment Method Selection |
PRE_AUTH_PAYMENT_METHODS | PreAuth Method Selection |
GOOGLE_PAY | Google Pay (Payment) |
PRE_AUTH_GOOGLE_PAY | Google Pay (PreAuth) |
SERVER_TO_SERVER_PAYMENT_METHODS | Server to Server |
The Judo object is now configured and you are ready to make a transaction.
Each transaction operation is represented as an Activity.
To make a transaction:
- Create an Intent to pass the JudoActivity class
- Add the Judo object to the Intent:
- Call putExtra
- Assign it to the JUDO_OPTIONS key
The Judo object holds all the payment configurations previously set up.
3. Pass the Intent and a request code to allow Judopay to handle the onActivityResult and the transaction response:
4. Implement the onActivityResult method and handle the transaction response:
Check the request code from the onActivityResult and see if it matches with JUDO_PAYMENT_WIDGET_REQUEST_CODE. If it does, the result is called from the JudoActivity.
This means the imported response codes can be used to check the following possible response type and handle each case respectively:
- success
- cancel
- error
To set a server-to-server transaction:
- On the Judo builder set the PaymentWidgetType to:
If you are building your own card wallet, and not using a UI you can make a preauth or payment using a stored card token.
Follow the steps for Making a Transaction and replace the PaymentWidgetType with:
- PaymentWidgetType.TOKEN_PRE_AUTH or
- PaymentWidgetType.TOKEN_PAYMENT
For more information on token payments, see the Android Sample App.
JudoKit-Android is enabled for 3D Secure 2 (EMV 3DS).
3D Secure 2 is available on JudoKit Android version 3.0.0 or higher, and is available on github.
The easiest way to integrate 3D Secure is to use the UI within JudoKit, as this handles the 3D Secure flow for you.
Using a 3D Secure Enabled credential*, follow the steps for Making a Transaction.
*We recommend using billingAddress and emailAddress fields for 3D Secure 2 transactions.
You can provide billingAddress and emailAddress in two ways: Add and populate billingAddress and emailAddress to the payment configuration object:
Or, to request this information from your customer:
- Enable the billingAddress and emailAddress fields to appear in the UI: .setShouldAskForBillingInformation(true)
Using a 3D Secure Enabled credential*, follow the steps for Token Payments.
Follow our suggested guidelines to simulate both positive / happy path scenarios, and negative scenarios in the sandbox environment to test your integration is working correctly. This will give you confidence for when your integration goes live.
See, Testing your Android SDK and generate:
- Successful payments
- Declined payments
- Unexpected errors
You will need to have your app approved by Google prior to using Google Pay™ in production.
- Ensure you have tested Google Pay™ on your mobile app. See, Testing Google Pay™ Wallet - via Mobile SDK.
- Ensure your Android Application Package is enabled for sandbox testing. This is to permit the Google Pay™ Support Team to run their review tests.
- Send your Android Application Package to the Google Pay™ Support Team so they can review your app and assist you with any of the Terms and Conditions that need to be agreed.
- The Google Pay™ Support Team will enable your app with production access to Google Pay™, once their review has been successfully completed.
You will then be able to accept Google Pay™ transactions from your mobile app.