Choose an integration

FlowAlp Pay offers several integration modes. The choice depends on the platform you use and how much control you need over checkout.

Prerequisites

• FlowAlp Pay merchant account (sign up (https://signup.pay.flowalp.com) or login (https://login.pay.flowalp.com))
• At least one payment provider configured on the account
• Access to site / shop / app code if you integrate via API or embedding

Quick decisions

Scenario | Recommended approach | Where to go
You use a supported e-commerce, CMS, or business software | Plugin / official or third-party integration | Integrations
You already have a payment page in the back office and want to show it on your site | iFrame or modal window | iFrame, Modal window
You need a custom checkout (dynamic amount, redirect, cart, app) | Merchant API — Gateway | Accept a payment

TODO FlowAlp: creare e collegare le pagine citate se non ancora presenti

Third-party plugins

If a plugin exists for your platform, prefer it over a custom integration: less maintenance and a flow that is already tested. Guides:

• E-commerce
• CMS
• Business software

In some technical screens, packages, or plugin names you may still see Payrexx, because FlowAlp Pay uses that technology as the payment infrastructure.

Embedding an existing page

If the payment page is already configured in the merchant backend and you do not need a dynamic API flow:

• generate or retrieve the page URL / snippet;
• embed it via iFrame or open it in a modal window;
• for mobile, see Mobile apps.

A browser redirect to the success URL does not replace server-side verification of payment status.

Gateway via Merchant API

Use a Gateway when:

• order amount and metadata are generated by your backend;
• you want controlled success / failed / cancel redirects;
• you manage subscriptions, tokenization, or pre-authorization;
• you integrate a custom checkout or an app.

Typical flow:

• backend creates a Gateway (POST /Gateway/);
• customer completes payment on the FlowAlp Pay page (redirect or embed);
• you receive a webhook and/or query the Merchant API;
• you update the order only after server-side confirmation.

Details: Create a Gateway and Configure webhooks.

Next steps

• Instance name
• API credentials
• First API request