For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
RegisterLoginSandbox Login
GuidesRecipesAPI Reference
GuidesRecipesAPI Reference
  • Getting Started
    • Getting Started with Checkout
    • Account Setup
    • Card Checkout with Credits
    • Card Checkout
    • Direct USDC Settlement
    • Fiat/Crypto Pay-ins
    • Secure Marketplace Checkout
    • EVM Checkout
    • How to Enable Checkout with Credit Cards
    • Quick Start Marketplace Implementation
    • Payouts
    • Common FAQs
  • Checkout
      • Getting Started with Implmentation
      • Mobile App Payments
        • Swift SDK
        • Android SDK
        • Flutter SDK
        • React Native SDK
        • Browser Redirect Checkout
    • Settlement Locations
  • Payouts
    • Payout Overview
    • What is a Payout
  • Subscriptions
    • Subscriptions Overview
  • Marketplaces
    • Marketplace Overview
    • How Marketplaces Work
    • How to Withdraw USDC
    • Countries Eligible for USDC Withdraw
    • Marketplaces Webhooks
    • Marketplaces Implementation
  • Developer Resources
    • Custom Branding
    • Checkout Implementation
    • Webhooks
  • Merchant Dashboard
    • Login & Account Access
    • Users and Roles
    • Rate Limits
    • Developer Contact
LogoLogo
RegisterLoginSandbox Login
On this page
  • Overview
  • When to use a mobile SDK
  • What the SDK does
  • Available SDKs
  • Common concepts
  • Merchant ID
  • Environment
  • Variants
  • Theming
CheckoutImplementation Overview

Mobile SDK Overview

Embed the Coinflow card form natively in your iOS, Android, or Flutter app using a first-party SDK.

Was this page helpful?
Previous

Swift SDK

Embed the Coinflow card tokenization form natively in a SwiftUI app.
Next
Built with

Overview

Coinflow publishes first-party SDKs for Swift, Android (Kotlin), Flutter, and React Native that embed the card tokenization form directly into native mobile apps. Every SDK renders the same PCI-compliant card form used on the web, surfaces a single tokenize() call, and returns a payment token your backend can charge.

Use a mobile SDK when you want the card entry experience to stay inside your app — no redirect out to a browser, no WebView wiring you have to maintain yourself.

When to use a mobile SDK

Mobile SDK (embedded)
Browser redirect

Renders the card form directly inside your app. You control the surrounding UI and the moment tokenization happens.

Best for:

  • Apps that need full control over checkout UI/UX
  • Subscription sign-up, card-on-file capture, replacing a saved card
  • Tokenization flows where you charge later server-side

View the Swift, Android, and Flutter guides below

What the SDK does

  1. Renders the Coinflow card form inside a native view.
  2. Captures the card data inside Coinflow’s PCI scope — sensitive data never touches your app code.
  3. Exposes a single tokenize() call you invoke when the user taps your Pay button.
  4. Returns a TokenizeResponse containing the payment token (and optionally expMonth / expYear).
  5. You forward that token to your backend, which calls Coinflow’s checkout API to charge the card.

The SDK only handles card capture and tokenization. The actual charge happens server-side via the standard Coinflow checkout API using the returned token.

Available SDKs

Swift (iOS)
Android (Kotlin)
Flutter
React Native

SwiftUI SDK for iOS 15+. Distributed via Swift Package Manager.

  • Package: coinflow-swift
  • Integration guide →

Common concepts

Merchant ID

Every SDK takes a merchantId string. This is issued by Coinflow when you sign up and is visible in the merchant dashboard. The same value works for both sandbox and production.

your-merchant-id is an example placeholder. Contact the Coinflow integrations team or check the merchant dashboard for your actual merchant ID before going live.

Environment

Every SDK takes an env enum that selects which Coinflow backend the form talks to:

  • Sandbox — test cards, no real money. Use during integration and QA.
  • Prod — live cards, real money.

Variants

Each SDK exposes three form variants:

VariantCapturesUse case
cardFormNumber, expiry, CVVStandard one-shot card entry
cardNumberFormNumber + expiryStep 1 of a two-step flow; returns a token used later with cvvForm
cvvFormCVV onlyRe-collecting CVV for a saved card-on-file token

Theming

Each SDK accepts an optional MerchantTheme that styles the form to match your app — colors, fonts, input shape, and placeholder text. All fields are optional. See each platform’s integration guide for the full field list.