SDK downloads

Both SDKs are distributed as direct downloads to merchants under integration. Public registry distribution (Maven Central / CocoaPods) is on the roadmap but not yet available.

How to request the SDK

Request the latest SDK package from [email protected]. Include:

• Your Scan to Pay merchant ID
• The platform(s) you need — Android, iOS, or both
• Your app bundle ID / package name (the SDK is tied to your API key, which is in turn tied to your merchant profile)

Support typically responds within one business day with a signed download link.

Android — Lib Lite AAR

Required dependencies (declare in your build.gradle):

implementation 'com.googlecode.libphonenumber:libphonenumber:8.10.2'
implementation 'com.google.android.gms:play-services-auth:16.0.1'
implementation 'com.google.android.gms:play-services-auth-api-phone:16.0.0'

Install steps walked through in Android — Installation.

iOS — Scan to PayKit XCFramework

Required Info.plist keys:

<key>NSLocationWhenInUseUsageDescription</key>
<string>Your location will be used to prevent fraud</string>
<key>NSCameraUsageDescription</key>
<string>Used to scan QR codes during card registration</string>

Install steps walked through in iOS — Installation.

Verifying you have the latest version

The version number is printed on first launch in the SDK's debug log. Match it against the Android changelog or iOS changelog to confirm you're current.

For security patches we'll notify your tech lead directly. Minor releases ship every 3-4 months; major releases every 18-24 months with a migration guide and 6-month overlap.

Versioning policy

You're expected to be on a supported version. Security patches and major versions have upgrade obligations defined in your integration agreement.

What's next

• Install on Android → Android — Installation
• Install on iOS → iOS — Installation
• First payment → Android — Payments or iOS — Payments
• Support → [email protected]