SDK Overview

Use this page as the entry point for Client SDK documentation on developer.plexy.money. It explains which integration path belongs in which section and links to the platform-specific guides.

Plexy provides client-side SDKs for Web, iOS, Android, React Native, and Flutter. Use them when you want Plexy to render payment UI or payment-method components inside your checkout while your backend creates sessions, payment methods, payments, and payment details.

For server-side request orchestration, API authentication, sessions, payment methods, result handling, endpoint reference, and live setup, use the Server Integration section.

Default APSE region

SDK quickstarts and integration examples use APSE by default. Client SDKs select APSE with live-apse, Environment.apse, Environment.APSE, or Environment.liveApse, depending on platform. Keep this SDK environment live/APSE for both test and production runs. To run test transactions, use a test API key on your backend, as described in Test and Live Payments. Server-side /v2/sessions requests still use https://api.plexypay.com/v2/sessions; do not add live-apse to the request body. The clientKey in the SDK and the x-api-key on your backend must belong to the same merchant account and mode.

Shopper locale and currency

shopperLocale / locale controls checkout language and regional formatting, for example ru-KZ, en-US, or kk-KZ. It is not a currency setting. Currency is configured only in amount.currency, for example KZT.

Choose your integration path

Path	Use it for	Start here
Web	Browser checkout, React, Next.js, Drop-in, individual Web Components, custom styling	Web SDK
iOS	Native Swift apps, UIKit or SwiftUI checkout, iOS Drop-in and Components	iOS SDK
Android	Native Kotlin apps, Jetpack Compose or Views checkout	Android SDK
React Native	Shared JavaScript API over the native iOS and Android SDKs	React Native SDK
Flutter	Cross-platform mobile checkout using the Flutter plugin	Flutter SDK
Wallet	Shared Apple Pay and Google Pay setup that applies across SDKs	Apple Pay, Google Pay
Server Integration	Backend flows, API authentication, sessions, advanced payments, result handling, endpoint reference	Server Integration Overview

Platform SDKs

Web

Browser, React, Next.js, Drop-in, Components, and customization.

iOS

Native Swift SDK with Drop-in, Components, SwiftUI, and Apple Pay support.

Android

Native Android SDK for Jetpack Compose and Views.

React Native

One JavaScript API backed by the native mobile SDKs.

Flutter

Flutter plugin for Drop-in and Components on iOS and Android.

Wallet

Apple Pay and Google Pay setup shared by platform integrations.

How SDK and server integration fit together

Create a session or payment on your backend

Your server authenticates with Plexy, creates sessions, fetches payment methods, or submits payments through the Server Integration APIs.

Render checkout on the client

The platform SDK renders Drop-in or individual Components and collects payment details in the app or browser.

Handle redirects, wallets, and final status

The SDK handles client-side actions while your backend verifies final payment state with webhooks and API calls.

Server-side guides

Use these when implementing the backend part that every SDK integration depends on:

Authentication

Test and Live Payments

Sessions Flow

Advanced Flow

API Reference

SDK Overview

Choose your integration path#

Platform SDKs#

How SDK and server integration fit together#

Server-side guides#

Choose your integration path

Platform SDKs

How SDK and server integration fit together

Server-side guides