Regular Plans

When a buyer picks a regular plan like “Pro”, your checkout link receives its numeric ID as cuprice_plan_id. Use that ID, not plan_id, to look up features: plan_id is generated from the plan name and changes when you rename the plan, while cuprice_plan_id stays the same.

Step 1: Look up the plan when checkout starts

In the route behind your checkout link, read the IDs and ask Cuprice for the plan’s price and features:

const params = new URL(req.url).searchParams;
const shareId = params.get("cuprice_share_id");      // "YOUR_SHARE_ID"
const cupricePlanId = params.get("cuprice_plan_id"); // "768"
const interval = params.get("interval");             // "month" or "year"

const res = await fetch(
  `https://app.cuprice.io/api/share/${shareId}/checkout-payload?planId=${cupricePlanId}&billingInterval=${interval}`
);
const { payload } = await res.json();
if (!payload) throw new Error("Plan not found on the published page");

const amount = payload.plan.amount; // charge this, not the amount in the query string
const features = payload.features
  .filter((f) => f.included)
  .map((f) => ({ id: f.id, name: f.name, limit: f.limit }));
// => [{ id: 2279, name: "Team seats", limit: 5 }, { id: 2280, name: "Priority support", limit: null }]

limit is the plan’s limit for features that have one, and null for on/off features.

The Share API (or the MCP server’s get-pricing tool) returns every visible plan. A feature is in a plan when its multiplier is above 0. For features that have usage settings (countableData in the top-level features list), the multiplier is the plan’s limit.

const res = await fetch(`https://app.cuprice.io/api/share/${shareId}`);
const project = await res.json();

const plan = project.pricingPlans.find((p) => p.id === Number(cupricePlanId));
const countable = new Set(
  project.features.filter((f) => f.countableData).map((f) => f.id)
);

const features = plan.planFeatures
  .filter((pf) => pf.multiplier > 0)
  .map((pf) => ({
    id: pf.featureId,
    name: pf.feature.name,
    limit: countable.has(pf.featureId) ? Math.round(pf.multiplier) : null,
  }));

The Share API has no price for the chosen interval, so use the Checkout Payload endpoint when you also need the amount to charge.

Step 2: Keep the features with the payment

Save features, amount and cupricePlanId on a pending order in your database and pass the order ID to your payment provider as metadata. The customer then gets the plan as it was when they bought it, even if you edit or hide the plan later.

Step 3: Save on the customer and check

When your provider confirms the payment, copy the order’s features onto the customer. Then check that saved list in your app:

function hasFeature(customer, name) {
  return customer.features.some((f) => f.name === name);
}

function limitFor(customer, name) {
  return customer.features.find((f) => f.name === name)?.limit ?? null;
}

Feature names change if you rename a feature in Cuprice. If you expect renames, key your checks on the feature id instead. Custom plans only carry names, see Custom Plans.

Getting Started

Embed Widget

Checkout

Feature Gating

Customization

AI Tools

Step 1: Look up the plan when checkout starts

Step 2: Keep the features with the payment

Step 3: Save on the customer and check

​Step 1: Look up the plan when checkout starts

​Step 2: Keep the features with the payment

​Step 3: Save on the customer and check

Step 1: Look up the plan when checkout starts

Step 2: Keep the features with the payment

Step 3: Save on the customer and check