Apto provides SDKs that wrap the Apto Mobile API so that you don’t need to deal with network requests. Convenient classes are exposed in these mobile SDKs, available for iOS (Swift and Objective-C) and Android (Kotlin and Java).
If you want to present PCI data in your mobile app or within your website, but your platform is not PCI certified, you can still show that information to your users by using the Apto PCI SDK. The Apto PCI SDK is a small package that’s available for iOS, Android, and Web, and contains a single UI component that can securely obtain the card’s PCI protected data and show it on screen within any UI of your application. The PCI SDK uses a secure user token, which can be obtained only by the card’s owner, to ensure that the PCI protected data is only delivered to the final user.
If you're PCI certified and don't want to use the PCI SDK, let us know.
Use the Mobile SDK (and optionally the PCI SDK) if you want to build your own UI. These SDKs wrap the API and they allow your mobile application to easily communicate with the Apto Platform.
White-label flows (UI SDKs)
For speed-to-market, we also offer a compiled version of the SDKs, which means you can take this white label mobile application and drop it into your existing application or you can distribute it as standalone mobile applications. The Android and iOS applications implement a standard cardholder experience but are configurable to match your branding look and feel.
To initialize and operate the white label flows, you'll pass your mobile API key. Two lines of code can present all the functionality that your users will need.
|Mobile SDK (Swift)|
|Mobile SDK (Objective-C)|
|UI SDK (Swift + Objective-C)|
|PCI SDK (Swift + Objective-C)|
|Mobile SDK (Kotlin + Java)|
|UI SDK (Kotlin + Java)|
|PCI SDK (Kotlin + Java)|