Client SDK

Plexy offers flexible SDK integration options that can be combined to match your specific needs. You'll need to make two key decisions:

Client-side integration type - How you want to display payment methods in your app

Server-side integration type - How you want to handle payment processing on your backend

Client-Side Integration Options

Choose how you want to present payment methods to your users:

Drop-in Integration

Best for: Quick implementation with minimal customization needs

The Drop-in component is a pre-built UI that displays all available payment methods in a single list. It's the fastest way to start accepting payments.

Key features:

Pre-built UI with all payment methods in one view

Minimal development time

Automatic support for new payment methods

Built-in 3D Secure 2 support

Basic UI styling customization

Supported payment methods: Cards, Apple Pay, Google Pay

Use Drop-in when:

You want to get to market quickly

You prefer a standardized payment UI

You want automatic updates when new payment methods are added

You need a simple, unified payment experience

Available for: Flutter

Components Integration

Best for: Custom payment UI with full control over layout and user experience

Components give you individual UI elements for each payment method, allowing you to create a completely custom checkout experience.

Key features:

Individual components for each payment method

Full flexibility in layout and positioning

UI styling customization per component

Built-in 3D Secure 2 support

Render payment methods anywhere in your app

Supported payment methods: Cards, Apple Pay, Google Pay

Use Components when:

You need a custom-designed checkout flow

You want to position payment methods in specific locations

You require granular control over the user experience

You want to match your brand's unique design language

Available for: Flutter

Server-Side Integration Options

Choose how your backend will communicate with Plexy's API:

Session Flow (Recommended)

Best for: Most implementations - simple, secure, and efficient

The Session flow creates a payment session on your server with a single API call. The session contains all the information needed to complete the payment, making it ideal for most use cases.

How it works:

Your server creates a payment session with a single /sessions API call

Pass the session ID and session data to your client application

Drop-in/Components handle the entire payment flow

Receive payment results via webhooks

Key advantages:

Simplified integration - Only one server API call needed

Enhanced security - Payment details stay on Plexy's servers

Less maintenance - Plexy handles payment flow complexity

Faster development - Minimal backend code required

Parameters required:

merchantAccount

amount (currency and value)

returnUrl

reference

countryCode

channel (Web/iOS/Android)

shopperEmail (recommended)

shopperLocale (optional)

Use Session flow when:

You want the simplest backend integration

You're building a new integration

You prefer less server-side code to maintain

You want Plexy to handle payment flow complexity

View Session Flow Documentation →

Advanced Flow

Best for: Complex requirements, custom payment flows, or existing integrations

The Advanced flow gives you complete control over the payment process with direct API calls for each step. You manage payment methods retrieval, payment submission, and handling additional actions.

How it works:

Your server calls /paymentMethods to get available payment options

Your server calls /payments to process the payment

Handle additional actions (3D Secure, redirects) through your server

Receive payment results via webhooks

Key advantages:

Maximum flexibility - Full control over every payment step

Custom logic - Implement complex business rules

Advanced scenarios - Handle unique payment flows

Granular control - Manage each API interaction

API calls required:

POST /paymentMethods - Retrieve available payment methods

POST /payments - Submit payment

Handle additional actions as needed

Use Advanced flow when:

You need custom payment logic or workflows

You want fine-grained control over the payment process

You're integrating with complex existing systems

You have specific compliance or business requirements

You need to modify payment data before submission

View Advanced Flow Documentation →

Choosing Your Integration

Quick Decision Matrix

Your Requirement	Client-Side	Server-Side
Fastest implementation	Drop-in	Session Flow
Custom UI design	Components	Session Flow
Complex business logic	Components	Advanced Flow
Minimal maintenance	Drop-in	Session Flow
Maximum flexibility	Components	Advanced Flow
Standard checkout	Drop-in	Session Flow

Common Integration Combinations

1. Quick Start (Recommended for most)

Client: Drop-in

Server: Session Flow

Best for: Getting to market quickly with a standard, reliable checkout

2. Custom Experience

Client: Components

Server: Session Flow

Best for: Branded checkout experience with simplified backend

3. Enterprise Solution

Client: Components

Server: Advanced Flow

Best for: Complex requirements with full control over payment logic

4. Rapid Prototype

Client: Drop-in

Server: Session Flow

Best for: POC or MVP development

Requirements for All Integrations

Before you begin, ensure you have:

Plexy Account Setup

Merchant account credentials

API key (for server-side calls)

Client key (for client-side authentication)

Webhook Configuration

Set up webhook endpoints to receive payment outcomes

Configure webhook URLs in your Plexy account

Platform-Specific Setup

Configure return URL handlers

Add custom URL schemes for redirects

Apple Pay: Complete certificate setup and add capability (iOS/Web)

Photo Library: Add usage descriptions for voucher payments (mobile)

SDK Requirements

Check minimum version requirements for your chosen platform

Ensure compatibility with your development environment

Platform-Specific Documentation

Select your platform to view detailed integration guides:

Web - Browser-based integration

iOS - Native iOS SDK

Android - Native Android SDK

React Native - Cross-platform JavaScript SDK

Flutter - Cross-platform Dart SDK (Drop-in | Components)

Next Steps

Choose your platform (Web, iOS, Android, React Native, or Flutter)

Choose your integration approach using the decision matrix above

Review the platform-specific documentation for your chosen client and server integration types

Complete the prerequisites listed in the requirements section

Follow the step-by-step guides in the detailed documentation

Test your integration in the test environment

Set up webhooks to receive payment outcomes

Go live by switching to the production environment

Support

For additional help:

Review the detailed documentation links above

Contact Plexy support for integration assistance

Check for code examples in the platform-specific integration guides

Ready to integrate? Start by selecting your platform and reviewing the documentation links for your chosen client and server integration types.

Client-Side Integration Options#

Drop-in Integration#

Components Integration#

Server-Side Integration Options#

Session Flow (Recommended)#

Advanced Flow#

Choosing Your Integration#

Quick Decision Matrix#

Common Integration Combinations#

Requirements for All Integrations#

Platform-Specific Documentation#

Next Steps#

Support#

Client-Side Integration Options

Drop-in Integration

Components Integration

Server-Side Integration Options

Session Flow (Recommended)

Advanced Flow

Choosing Your Integration

Quick Decision Matrix

Common Integration Combinations

Requirements for All Integrations

Platform-Specific Documentation

Next Steps

Support