Skip to main content

Hosted Flows

Use a published FloKit Flow URL for the hosted web experience and checkout. Follow the payment-provider and domain setup guides. Linking to a hosted Flow does not require embedding a separate checkout library.

React Native

Use @flokitai/subscriptions-sdk for App identity, entitlement reads, receipt submission, and web-to-app handoff. Obtain package access from your FloKit contact and follow the setup instructions for your selected package version. Prepare the App credential, a stable pseudonymous user reference, and the purchase or handoff experience you are integrating. Connect your App’s native Apple or Google purchase UI to the SDK’s receipt submission interface. Use the current entitlement interface to display access. Your backend must authenticate its own user session before granting protected resources. Neither a publishable App key nor a browser checkout callback proves who the user is or that a payment succeeded. For web checkout, direct the user to the published Flow from your React Native application.

Custom web integrations

Hosted Flows include their checkout experience. For checkout embedded in your own web application, agree the integration method with your FloKit contact. Keep provider prices and account credentials out of browser-authored payment requests.

Other native applications

Use the documented App API for native applications that do not use React Native. Follow its authentication and entitlement guidance and coordinate identity handoff with your FloKit contact. For subscription notifications to your backend, see outbound webhooks.