Skip to main content
Gr4vy offers two approaches for accepting payments in mobile apps. Both support the most common card and wallet payment flows. The right choice depends on how much UI control and native platform depth you need, and on how much PCI DSS scope you can take on.

Compare approaches

Embed SDKs

The Embed SDKs provide a drop-in payment sheet for iOS, Android, and React Native. The checkout UI is rendered in a web view, giving you access to all supported payment methods with minimal setup.

iOS

Drop-in payment sheet for iOS.

Android

Drop-in payment sheet for Android.

React Native

Cross-platform payments for iOS and Android.

Extend your Embed SDK integration

Apple Pay (iOS)

Enable Apple Pay for iOS Embed SDK integrations.

Google Pay (Android)

Enable Google Pay for Android Embed SDK integrations.

Apple Pay (React Native)

Configure Apple Pay for React Native checkouts.

Google Pay (React Native)

Configure Google Pay for React Native checkouts.

Native SDKs

The Native SDKs (Swift for iOS, Kotlin for Android) let you build card capture directly into your app’s native view hierarchy with no web view required. They support native 3DS authentication, giving you a smooth, fully in-app experience. The SDKs don’t include card entry UI, so your app collects the card details and is in scope for PCI DSS.

Swift (iOS)

Native card forms and 3DS for iOS with Swift.

Kotlin (Android)

Native card forms and 3DS for Android with Kotlin.

Extend your Native SDK integration

Native 3DS

Add and test native 3DS authentication in your app.

List payment options

Query available payment options for your mobile checkout context.

Apple Pay (iOS)

Add Apple Pay to native iOS checkouts outside the Embed SDK.

Google Pay (Android)

Add Google Pay to native Android checkouts outside the Embed SDK.

Not sure which to choose?

Start with the Embed SDKs if you want the fastest path to a working checkout with full payment method coverage, or if you want to keep card data out of your app. Choose the Native SDKs if you need complete UI control, a fully native 3DS experience, or want to avoid web view rendering in your app.