Integration wtih page builder

Let’s walk through an integration example using FunnelFox.

FunnelFox allows you to build pages and steps in a sales funnel (landing → plan selection → payment → thank you). From this, we can derive two main stages of integration with our billing: displaying plans/prices and proceeding to payment (optionally, you can combine them on a single page).

At the step where the user chooses a plan, there are two approaches.

If you have a fixed set of plans and rarely change prices/descriptions, you can simply configure the following manually:

1. plan names,
2. prices,
3. currency,
4. duration etc.

If you want prices and product information to always be up to date, you can use our endpoint to retrieve:

1. current prices for plans,
2. product data (name, period, description),
3. additional attributes that you store on the billing side.

1. You (your backend or frontend) send a request to our API.
2. You receive a list of plans/prices.
3. You render the plans on the selection page.

This option is easier to scale and maintain: changes are made on the billing side, and you simply display the latest data on FunnelFox.

Once the user has selected a plan, you choose one of two UX scenarios.

After selecting a plan, the next FunnelFox step opens — a payment page where:

1. an iFrame with our checkout/payment interface is embedded,
2. the user completes the payment while staying inside the FunnelFox funnel.

1. you want to keep a seamless experience within FunnelFox,
2. it’s important that the user does not leave your flow.

After selecting a plan, you are open our hosted payment page, already tied to the user’s order:

1. an order is created,
2. you receive the order URL,
3. you redirect the user to our page and the user pays there,
4. after payment, we redirect the user back to your flow.

1. you want the simplest and most reliable option,
2. you want to avoid iFrame limitations,
3. you prefer to keep the entire payment experience on our side.