Choose an integration
July 30, 2026
Decision guide to FlowAlp Pay integrations: compare pay links and QR codes, shop plugins, hosted checkout via API, and full REST API integration.
FlowAlp Pay offers four integration paths, ordered here from zero code to full control: pay links and QR codes, plugins, the hosted checkout driven by the Merchant API, and a full API integration. All paths share the same account, payment methods, dashboard, and reporting — and you can combine them freely. This guide helps you pick the right starting point.
Comparison at a glance
| Integration | Coding effort | Best for | Where it runs |
|---|---|---|---|
| Pay links and QR codes | None | Invoices, donations, sales via e-mail or social media, in-person QR payments | Created in the dashboard, shared as a link or QR code |
| Plugin | Minimal (install and configure) | Shops on supported e-commerce, CMS, or business platforms | Inside your shop system |
| Hosted checkout via API (Gateway) | Backend integration | Custom carts and apps that need dynamic amounts and controlled redirects | Your backend creates it; customers pay on the hosted page |
| Full API integration | Highest | Tokenization, pre-authorization, subscriptions, and custom post-payment operations | Your backend drives the whole lifecycle |
Pay links and QR codes — no code
Create a payment link or QR code in the dashboard, set amount and purpose, and share it by e-mail, chat, invoice, or printout. The customer pays on your hosted payment page at your tenant domain. This is the fastest way to accept your first payment. See Pay links and QR codes.
Plugins — low code
If your platform is supported, prefer a plugin over a custom build: the payment flow is already implemented and maintained, and setup is limited to connecting your instance and API key. Start with these overviews:
- E-commerce integrations — including the WooCommerce guide
- CMS integrations
- Business software
- Other integrations
Hosted checkout via the Merchant API (Gateway)
Use a Gateway when your backend generates orders with dynamic amounts and you want controlled success, failed, and cancel redirects — while FlowAlp Pay still hosts the payment page for you. The typical flow:
- Your backend creates a Gateway (Create a Gateway) with amount, currency, and your order reference.
- The customer pays on the hosted payment page — as a redirect, or embedded via iFrame or modal (Checkout embedding overview).
- Your server receives a webhook and verifies it (Configure webhooks).
- You update the order only after server-side confirmation.
Full API integration
Beyond the hosted checkout, the Merchant API also lets you charge saved payment methods (tokenization), reserve and capture amounts (pre-authorization), run recurring billing (subscriptions), and manage refunds and cancellations through the Transaction API (charge, capture, refund and cancel). Start from the Merchant API overview.
How to decide
- No developer available, or occasional payments only: use pay links and QR codes.
- You run a standard shop platform: use a plugin.
- You have your own checkout, cart, or app: create Gateways via the API.
- You need saved cards, reservations, or subscriptions: plan a full API integration.
A browser redirect to your success page is not proof of payment. Whatever path you choose, confirm every payment server-side via webhooks (with signature verification) or an API retrieve before fulfilling an order.
Decided? Set up your instance name and API credentials, then send your first API request. No-code merchants can go straight to pay links and QR codes.