Mobile Integration
The Mobile Software Development Kit (SDK) helps you develop a mobile app that accepts digital payments through the ANZ eGate payment gateway. The Mobile SDK supports both the iOS and Android platforms. This ensures that you can cater to a wide range of customers, regardless of the device they use.
Supported payment methods and operations
| Payment methods | Operations |
|---|---|
|
|
The actual payment transaction and any subsequent transactions are handled as normal API requests from your server. For details, see Subsequent Operations and Making a Server API Request .
To learn about mobile integration, see the following:
- For instructions on how to download the Mobile SDK and integrate it to your solution, see Integration Steps.
- To understand the steps needed to test your integration, see Testing Steps.
- For an overview of taking your integration live, see Go Live Checklist.
Prerequisites
Before implementing a Mobile SDK solution, check that you meet the following prerequisites:
- iOS:
- The Mobile SDK requires a minimum of iOS 11+ and is compatible with Swift 5 projects.
- To use the Mobile SDK for iOS, you must be familiar with Xcode. To download the tool and access its documentation, see the Xcode site.
- Android:
- The Mobile SDK requires a minimum of Android 21+.
- To use the Mobile SDK for Android, you must be familiar with Android Studio. To download the tool and access its documentation, see the Android Studio site.
Key benefits
Mobile integration has the following key benefits:
- It provides a seamless payment experience for users.
- It supports 3D Secure (3DS) authentication, which reduces fraudulent transactions.
- Mobile integration can be achieved through a hosted session or a payment session.
- As the Mobile SDK flow is based on the concept of a session, it offers the benefits of the Hosted Session integration method:
- It may reduce PCI compliance costs as you do not handle or store any payment details.
- Facilitates ease of integration as you do not need to directly handle the values for the request fields stored in a session.
- Reduces internal fraud as your staff has limited access to payer’s details.
- Allows you to update the request fields and values stored against a session. This is useful when a credit card expires or other payer details change.
- Allows you to retrieve request fields and values contained in a specific session ID.
Mobile payment process
When using the Mobile SDK, you need to take the following steps during the payment process:
- In your server, create a session in the gateway and update it with the basic details about the order the payer wants to make.
- In your mobile app, based on your PCI compliance level:
- You can collect the card details manually.
- You can use Apple Pay or Google Pay payment methods to retrieve a payment token from the payer without having to handle payment details manually.
- In your mobile app, authenticate the payer with 3DS, if you use 3DS authentication.
- If you get the payment details from the payer and the payer is successfully authenticated, send the payment transaction request from your server.
For more details, see Integration Steps.