Mobile SDKs and Wrappers
Chargebee hosted page solutions are designed to provide an optimal experience on mobile devices. All hosted pages are mobile responsive, delivering a smooth experience for users who reach your website or web app from a mobile browser.
If you also have mobile apps, Chargebee offers SDKs and wrappers that give you more control over the checkout experience inside those apps. Each solution carries a different level of PCI, App Store, and Google Play responsibility, so pick the one that matches what you sell and how much of the payment flow you want to own. Every solution ships with an example app you can run before you integrate.
Choose a solution
What you sell determines which solution you can use.
| What you sell | Use | Why |
|---|---|---|
| Digital goods and services | React Native SDK, Flutter SDK, or native SDKs | Apple and Google require in-app purchases for digital goods. These SDKs process in-app purchase subscriptions and sync them to Chargebee. |
| Physical goods and services | React Native Wrapper, or the card tokenization in the native SDKs | Physical goods fall outside the in-app purchase rules, so you can charge through any gateway Chargebee supports. |
Note
The React Native SDK 2.x supports in-app purchases only. To sell physical goods through the React Native Wrapper, use the 1.x version.
How the solutions differ
Card tokenization with the native SDKs
The native SDKs tokenize card details and create subscriptions in Chargebee from within your app, charging through the Stripe payment gateway. They handle the sensitive data and the Chargebee calls; your app owns the payment form and the rest of the UI.
Because card details travel directly from your customer to the gateway, your PCI compliance scope stays small. Use these SDKs when you would rather not open a WebView or send the user out to a mobile browser.
Hosted checkout with the React Native Wrapper
The React Native Wrapper renders Chargebee-hosted checkout pages inside a WebView component in your app. You get a prebuilt checkout UI with branding, color, and step customization, plus access to every payment gateway and method Chargebee supports.
This solution requires the lowest level of PCI compliance of the three, which is why Chargebee recommends it for mobile apps that sell physical goods.
Before you integrate
Syncing in-app purchases requires configuration on the Chargebee side and in the app stores. Set these up first:
- Connect App Store Connect to Chargebee and configure your Apple products.
- Connect Google Play to Chargebee and import your Play products.
Get help
- To request support for another gateway or payment method in an SDK, contact support.
- To use in-app purchases in Chargebee for digital subscriptions, email eap@chargebee.com.
Was this article helpful?