Get Started
Choose your Plexy integration path
This is the documentation for API v2 and SDK integration. Looking for the more stable legacy version? See the API v1 documentation.
Pick speed or pick control.
Plexy gives you two ways to integrate: the Sessions Flow — one API call and Plexy handles everything — or the Advanced Flow, which trades effort for complete control over the checkout UI and payment lifecycle.
Pick your server flow
| Sessions Flow | Advanced Flow | |
|---|---|---|
| Best for | Fastest path to live payments | Fully branded custom checkout |
| API calls required | One (POST /v2/sessions) | Three+ (/paymentMethods → /payments → /payments/details) |
| Who handles 3DS + redirects | Plexy | You |
| Time to first payment | Minutes | Days |
| Good fit examples | SMB checkout, invoicing, subscription billing | Marketplaces, custom-branded flagship apps, multi-step checkouts |
Not sure which to pick?
Start with the Sessions Flow — it covers most merchants and gets you to your first live payment fastest. Choose the Advanced Flow when you need a fully branded payment form or custom orchestration that the Sessions Flow can't accommodate.
Continue with your flow
Sessions Flow →
Create a session, mount the checkout, handle the result via webhook.
Advanced Flow →
Render payment methods, submit payments, handle 3DS yourself.
Next steps
- Explore SDK guides for your platform
- Browse the API reference for all endpoints
Pick how to render Plexy on the client
Two ways to mount Plexy in your app.
Drop-in is one pre-built component that renders the entire checkout — payment-method selection, forms, and 3DS prompts. Components are individual payment-method pieces (Card, Apple Pay, Google Pay, ...) that you place and style in your own UI. Both work with either the Sessions Flow or the Advanced Flow — this choice is about client-side rendering, not flow.
| Drop-in | Components | |
|---|---|---|
| Best for | Fastest client integration | Composable, custom layouts |
| What you render | One <Dropin /> mount — full checkout | Individual payment-method components you place yourself |
| Payment-method UI ownership | Plexy renders all methods (Card, Apple Pay, Google Pay, ...) | You pick and arrange each method component |
| Bundle size | Larger — includes all registered payment methods | Smaller — tree-shake to only the methods you use |
| Time to integrate | Minutes | Hours |
| Good fit examples | Standard single-page checkout, MVP, quick launch | Multi-step flows, custom layouts, selective payment methods |
Start with Drop-in — it's the fastest way to ship a working checkout. Move to Components when you need custom layout, selective payment methods, or want to minimize bundle size.