Getting Started - Payment

Kenkai SDK Payment Module consists of events for rewarding platforms. You need to implement this module if your app offers users some rewards, points on completing certain actions or achieving a certain milestone by using your app. To use the payment module you need to include the respective dependency in your project but make sure you have the Core Module already integrated.

This documentation covers the steps to integrating SDK in your app. We’ll also discuss a few fundamentals of how the dashboard works in tandem with your app usage to view your users and engage them with contextually personalized messages.

Initialization

To use the SDK, Core is mandatory to include as it contains the elements regarding the basic app navigation and workflow including nudges. Moreover, all the modules require the core to be integrated to successfully log the events. If you have already integrated the core, you don't need to repeat initialization steps for this and can start using the SDK after including the dependency.

Android (Java/Kotlin)

    implementation 'io.kenkai.android.sdk:payments:<version-number>'

For version-number please refer to Maven Repository

iOS (Swift)

You can directly get the SDK as a Swift package since the SDK is as OpenSource Repo on GitHub OR you can use the SDK as a Cocoapod. Add the following line in your Podfile.

    pod 'KenkaiSDKPayments', '~> <version-number>'

React Native (JS/TS)

For React Native Apps you don't need any new NPM package but can use the already existing one. The only thing required to import the correct module in your files.

 import { CFPayment } from '@kenkai-io/react-native-sdk'

Web Application (JS/TS)

For Web Apps you don't need any new NPM package but can use the already existing one. The only thing required to import the correct module in your files.

    import { Payments } from '@kenkai-io/js-sdk'

---

As per the SDK structure, content blocks are further divided into 2 main categories: Ingest Events and Catalog Events.

• Ingest Events helps with time sensitive elements such as when an event is happening.
• Catalog Events helps with static content that provide details about the elements in the events.

For Payment Content Block, there are only ingest events currently.

---