This is the official Software Development Kit (SDK) for Chargebee iOS. This SDK makes it efficient and comfortable to build an impressive subscription experience in your iOS app.
Post-installation, initialization, and authentication with the Chargebee site, this SDK will support the following capabilities.
-
Sync In-App Subscriptions with Chargebee: Integrate with Apple Store Connect to process in-app purchase subscriptions, and track them on your Chargebee account for a single source of truth for subscriptions across the Web and Apple App Store. Use this if you are selling digital goods or services, or are REQUIRED to use Apple's in-app purchases as per their app review guidelines. For SDK functions to work seamlessly, ensure that products configured in the Apple App Store and existing subscriptions are successfuly imported into Chargebee.
-
Tokenisation of credit card: Tokenize credit card information while presenting your own user interface. Use this if you are selling physical goods or offline services or are NOT REQUIRED to use Apple's in-app purchases as per their app review guidelines.
-
Note: This SDK doesn’t support Apps developed using Objective C. If your app is developed using Objective C then we can guide you to integrate Objective C with our SDK code. Please reach out to support@chargebee.com
The following requirements must be set up prior to installing Chargebee's iOS SDK
-
iOS 12+
-
Swift 5+
Choose from the following options to install Chargeee iOS SDK.
Add the following snippet to the Podfile to install directly from Github.
pod 'Chargebee', :git => 'https://github.com/chargebee/chargebee-ios', :tag => '1.0.28'
Add the following line to your Podfile to install using CocoaPods.
pod 'Chargebee'
Follow the step to install SDK using Swift Package Manager.
-
Select File > Swift Packages > Add Package Dependency
-
Add repository URL https://github.com/chargebee/chargebee-ios
This is an optional step that helps you to verify the SDK implementation using this example project. You can download or clone the example project via GitHub.
To run the example project, follow these steps.
-
Clone the repo - https://github.com/chargebee/chargebee-ios.
-
Run pod install from the Example directory.
There are two types of configuration.
-
Configuration for In-App Purchases
-
Configuration for credit card using tokenization
To configure the Chargebee iOS SDK for completing and managing In-App Purchases, follow these steps.
-
Integrate the App Store Connect with your Chargebee site.
-
On the Sync Overview page of the web app, click View Keys and use the value of generated App ID as the SDK Key.
-
On the Chargebee site, navigate to Configure Chargebee > API Keys to create a new Publishable API Key or use an existing Publishable API Key. Note: During the publishable API key creation you must allow read-only access to plans/items otherwise this key will not work in the following step. Read more.
-
Initialize the SDK with your Chargebee site, Publishable API Key, and SDK Key by including the following snippets in your app delegate during app startup.
import Chargebee
Chargebee.configure(site: "your-site",
apiKey: "publishable_api_key",
sdkKey: "SDK Key")
}
To configure SDK only for tokenizing credit card details, follow these steps.
-
Initialize the SDK with your Chargebee Site and Publishable/Full Access Key.
-
Initialize the SDK during your app startup by including the following snippets in your app delegate.
import Chargebee
Chargebee.configure(site: "your-site", apiKey: "publishable_api_key")
This section describes the SDK integration capabilities.
-
Integrating In-App Purchases
-
Integrating credit card tokenization
The following section describes how to use the SDK to integrate In-App Purchase information. For details on In-App Purchase, read more.
Every In-App Purchase subscription product you configure in your App Store Connect account can be configured in Chargebee as a Plan. Start by retrieving the Apple IAP Product IDs from your Chargebee account.
CBPurchase.shared.retrieveProductIdentifers(queryParams :["String": "String"], completion: { result in
switch result {
case let .success(products):
print("array of Products Id's \(products)")
case let .failure(error):
// Handle error here
}
})
For example, query parameters can be passed as "limit": "100".
The above function will automatically determine your product catalog version in Chargebee and call the relevant APIs to retrieve the Chargebee Plans that correspond to Apple IAP products and their Apple IAP Product IDs.
You can then convert the IAP Product IDs to Apple IAP Product objects with the following function.
CBPurchase.shared.retrieveProducts(withProductID : ["Product ID from Apple"],completion: { result in
switch result {
case let .success(products):
print("array of Products \(products)")
case let .failure(error):
// Handle error here
}
}
You can present any of the above products to your users for them to purchase.
Pass the CBProduct
and CBCustomer
objects to the following function when the user chooses the product to purchase.
CBCustomer
- Optional object. Although this is an optional object, we recommend passing the necessary customer details, such as customerID
, firstName
, lastName
, and email
if it is available before the user subscribes to your App. This ensures that the customer details in your database match the customer details in Chargebee. If the customerID
is not passed in the customer's details, then the value of customerID
will be the same as the SubscriptionId
created in Chargebee.
Note: The customer
parameter in the below code snippet is an instance of CBCustomer
class that contains the details of the customer who wants to subscribe or buy the product.
let product = CBProduct(product: SKProduct())
let customer = CBCustomer(customerID: "",firstName:"",lastName: "",email: "")
CBPurchase.shared.purchaseProduct(product: product,customer: customer) { result in
switch result {
case .success(let result):
print(result.status)
print(result.subscriptionId) // this will print the subscription ID
print(result.planId) // this will print the Plan ID
case .failure(let error):
// Handle error here
}
}
The above function will handle the purchase against App Store Connect and send the IAP receipt for server-side receipt verification to your Chargebee account. Use the Subscription ID returned by the above function, to check for Subscription status on Chargebee and confirm the access - granted or denied.
This function also returns the plan ID associated with a subscription. You can associate JSON metadata with the Apple App Store plans in Chargebee and retrieve the same by passing plan ID to the SDK function - retrievePlan(PC 1.0) or retrieveItem(PC 2.0).
When a user changes their subscription level from a lower price plan to a higher price plan, it's considered an upgrade. On the other hand, when a user switches from a higher-price plan to a lower-price plan, it's considered a downgrade.
In the case of the Apple App Store, you can arrange the subscriptions using the drag-and-drop option in Edit Subscription Order in App Store Connect. Learn more.
The showManageSubscriptionsSettings()
function is designed to invoke the upgrade/downgrade flow in your app using Chargebee's iOS SDKs.
Chargebee.shared.showManageSubscriptionsSettings()
, opens the App Store App subscriptions settings page.
Note: Upgrades and downgrades are handled through Apple App Store Server Notifications in Chargebee.
The purchaseNonSubscriptionProduct
function handles the one-time purchase against App Store Connect and sends the IAP receipt for server-side receipt verification to your Chargebee account. Post verification a Charge corresponding to this one-time purchase will be created in Chargebee. There are three types of one-time purchases consumable
, non_consumable
, and non_renewing_subscription
.
let product = CBProduct(product: SKProduct())
let customer = CBCustomer(customerID: "",firstName:"",lastName: "",email: "")
let typeOfProduct: productType = .non_consumable
CBPurchase.shared.purchaseNonSubscriptionProduct(product: withproduct,customer: customer,productType: typeOfProduct) { result in
switch result {
case .success(let success):
print(result.customerID)
print(result.chargeID ?? "")
print(result.invoiceID ?? "")
case .failure(let failure):
// Handle error here
}
}
The given code defines a closure-based function named purchaseNonSubscriptionProduct
in the CBPurchase
class, which takes three input parameters:
product
: An instance ofCBProduct
class, initialized with aSKProduct
instance representing the product to be purchased from the Apple App Store.customer
: An instance ofCBCustomer
class, initialized with the customer's details such ascustomerID
,firstName
,lastName
, andemail
.productType
: An enum instance ofproductType
type, indicating the type of product to be purchased. It can be either .consumable
, .non_consumable
, or .non_renewing_subscription
.
The function is called asynchronously, and it returns a Result
object with a success
or failure
case, which can be handled in the closure.
- If the purchase is successful, the closure will be called with the
success
case, which includes thecustomerID
,chargeID
, andinvoiceID
associated with the purchase. - If there is any failure during the purchase, the closure will be called with the
failure
case, which includes an error object that can be used to handle the error.
The restorePurchases()
function helps to recover your app user's previous purchases without making them pay again. Sometimes, your app user may want to restore their previous purchases after switching to a new device or reinstalling your app. You can use the restorePurchases()
function to allow your app user to easily restore their previous purchases.
To retrieve inactive purchases along with the active purchases for your app user, you can call the restorePurchases()
function with the includeInActiveProducts
parameter set to true
. If you only want to restore active subscriptions, set the parameter to false
. Here is an example of how to use the restorePurchases()
function in your code with the includeInActiveProducts
parameter set to true
.
CBCustomer - Optional object. Although this is an optional object, we recommend passing the necessary customer details, such as customerId, firstName, lastName, and email if it is available before the user subscribes to your App. This ensures that the customer details in your database match the customer details in Chargebee. If the customerId is not passed in the customer’s details, then the value of customerId will be the same as the SubscriptionId created in Chargebee. Also, the restored subscriptions will not be associate with existing customerId.
let customer = CBCustomer(customerID: "Test123",firstName: "CB",lastName: "Test",email: "cbTest@chargebee.com")
CBPurchase.shared.restorePurchases(includeInActiveProducts: true, customer: customer) { result in
switch result {
case .success(let response):
for subscription in response {
if subscription.storeStatus.rawValue == StoreStatus.Active.rawValue{
print("Successfully restored purchases")
}
}
case .failure(let error):
// Handle error here
print("Error:",error)
}
}
The restorePurchases()
function returns an array of subscription objects and each object holds three attributes subscription_id
, plan_id
, and store_status
. The value of store_status
can be used to verify subscription status.
In the event of any failures during the refresh and validation process or while finding associated subscriptions for the restored items, iOS SDK will return an error, as mentioned in the following table.
These are the possible error codes and their descriptions:
Error Code | Description |
---|---|
RestoreError.noReceipt |
This error occurs when the user attempts to restore a purchase, but there is no receipt associated with the purchase. |
RestoreError.refreshReceiptFailed |
This error occurs when the attempt to refresh the receipt for a purchase fails. |
RestoreError.restoreFailed |
This error occurs when the attempt to restore a purchase fails for reasons other than a missing or invalid receipt. |
RestoreError.invalidReceiptURL |
This error occurs when the URL for the receipt bundle provided during the restore process is invalid or cannot be accessed. |
RestoreError.invalidReceiptData |
This error occurs when the data contained within the receipt is not valid or cannot be parsed. |
RestoreError.noProductsToRestore |
This error occurs when there are no products available to restore. |
RestoreError.serviceError |
This error occurs when there is an error with the Chargebee service during the restore process. |
Note: These error codes are implemented in our example app. Learn more.
Receipt validation is crucial to ensure that the purchases made by your users are synced with Chargebee. In rare cases, when a purchase is made at the Apple App Store, and the network connection goes off, the purchase details may not be updated in Chargebee. In such cases, you can use a retry mechanism by following these steps:
- Add a network observer, as shown in the example project.
- Save the product identifier in the cache once the purchase is initiated and clear the cache once the purchase is successful.
- When the network connectivity is lost after the purchase is completed at Apple App Store but not synced with Chargebee, retrieve the product ID from the cache once the network connection is back and initiate
validateReceipt()
/validateReceiptForNonSubscriptions()
by passingCBProduct
andCBCustomer(Optional)
as input. This will validate the purchase receipt and sync the purchase in Chargebee as a subscription or one-time purchase. For subscriptions, use the functionvalidateReceipt()
; for one-time purchases, use the functionvalidateReceiptForNonSubscriptions()
.
Use the function available for the retry mechanism.
Function for subscriptions
CBPurchase.shared.validateReceipt(product,customer: nil) { result in
switch result {
case .success(let result):
print(result.status )
// Clear persisted product details once the validation succeeds.
case .failure(let error):
print("error", error.localizedDescription)
// Retry based on the error
}
}
Function for one-time purchases
CBPurchase.shared.validateReceiptForNonSubscriptions(product,type,customer: nil) { result in
switch result {
case .success(let result):
// Clear persisted product details once the validation succeeds.
case .failure(let error):
// Retry based on the error
}
}
The following are funtions for checking the subscription status of a subscriber who already purchased the product.
Use query parameters - Subscription ID, Customer ID, or Status for checking the Subscription status on Chargebee and confirm the access - granted or denied.
Chargebee.shared.retrieveSubscriptions(queryParams :["String" : "String"]") { result in
switch result {
case let .success(result):
print("Next offset \(result.nextOffset)")
print("Subscriptions: \(result.list)")
case let .error(error):
// Handle error here
}
}
For example, query parameters can be passed as "customer_id" : "id", "subscription_id": "id", or "status": "active".
Use only Subscription ID for checking the Subscription status on Chargebee and confirm the access - granted or denied.
Chargebee.shared.retrieveSubscription(forID: "SubscriptionID") { result in
switch result {
case let .success(result):
print("Status \(result.status)")
case let .error(error):
// Handle error here
}
}
The above functions return the plan ID associated with a subscription. You can associate JSON metadata with the Apple App Store plans in Chargebee and retrieve the same by passing plan ID to the SDK function - retrievePlan(PC 1.0) or retrieveItem(PC 2.0).
Use the Subscription ID for fetching the list of entitlements associated with the subscription.
Chargebee.shared.retrieveEntitlements(forID: "SubscriptionID") { result in
switch result {
case let .success(result):
print("Status \(result.status)")
case let .error(error):
// Handle error here
}
}
Note: Entitlements feature is available only if your Chargebee site is on Product Catalog 2.0.
The following section describes how to use the SDK to tokenize credit card information.
If your Chargebee site is configured to PC 2.0, use the following functions to retrieve the product or product list for purchase.
Retrieve the list of items using the following function.
CBItem.retrieveAllItems(queryParams :["String" : "String"], completion: { result in
DispatchQueue.main.async {
switch result {
case let .success(itemLst):
self.items = itemLst.list
debugPrint("items: \(self.items)")
self.performSegue(withIdentifier: "itemList", sender: self)
case let .error(error):
debugPrint("Error: \(error.localizedDescription)")
}
}
})
For example, query parameters can be passed as "sort_by[desc]" : "name" or "limit": "100".
Retrieve specific item details using the following function. Use the Item ID that you received from the previous function - Get all items.
CBItem.retrieveItem("Item ID"){ (itemResult) in
switch itemResult {
case .success(let item):
print(item)
self.itemName.text = item.name
self.itemStatus.text = item.status
case .error(let error):
print("Error\(error)")
self.error.text = error.localizedDescription
}
}
If your Chargebee site is configured to PC 1.0, use the relevant functions to retrieve the product or product list for purchase.
Retrieve a list of plans using the following function.
CBPlan.retrieveAllPlans(queryParams: ["String":"String" ]) { (result) in
switch result {
case .success(let plan):
print("Plan Array: \(plan)")
// Use plan details here
case .error(let error):
// Handle error here
}
}
For example, query parameters can be passed as "sort_by[desc]" : "name" or "limit": "100".
Retrieve specific plan details passing plan ID in the following function.
CBPlan.retrieve("planId") { (planResult) in
switch planResult {
case .success(let plan):
print("Plan Name: \(plan.name)")
// Use plan details here
case .error(let error):
// Handle error here
}
}
Retrieve specific addon details passing addon ID in the following function.
CBAddon.retrieve("addonId") { (addonResult) in
switch addonResult {
case .success(let addon):
print("Addon Name: \(addon.name)")
// Use addon details here
case .error(let error):
// Handle error here
}
}
Once the user selects the product to purchase, and you collect the credit card information, use the following function to tokenize the credit card details against Stripe. You need to have connected your Stripe account to your Chargebee site.
let card = CBCard(
cardNumber: "4321567890123456",
expiryMonth: "12",
expiryYear: "29",
cvc: "123")
let paymentDetail = CBPaymentDetail(type: CBPaymentType.Card, currencyCode: "USD", card: card)
Chargebee.shared.createTempToken(paymentDetail: paymentDetail) { tokenResult in
switch tokenResult {
case .success(let token):
print("Chargebee Token \(token)")
// Use token here
case .error(let error):
// Handle error here
}
}
After the customer's card data is processed and stored and a Chargebee token reference is returned to you, use the token in subsequent API calls to process transactions.
The following are some endpoints that accept Chargebee tokens for processing subscriptions.
Please refer to the Chargebee API Docs for subsequent integration steps.
Chargebee is available under the MIT license. For more information, see the LICENSE file.