Custom Plans

A custom plan has no Cuprice plan to look up: cuprice_plan_id is 0, and the chosen features come with the checkout link. The custom plan card sends them like this:

Parameter	Example
`cuprice_custom_plan`	`true`
`cuprice_plan_id`	`0`
`selected_features`	`Team seats,Priority support`
`feature_usage`	`{"Team seats":3}`
`amount`	`44`
`interval`	`month` (always, for custom plans)

Step 1: Price the selection on your server

The query string can be edited by the buyer, so send the selection back to Cuprice and use the answer:

const params = new URL(req.url).searchParams;
const shareId = params.get("cuprice_share_id");
const names = (params.get("selected_features") ?? "").split(",").filter(Boolean);
const usage = JSON.parse(params.get("feature_usage") ?? "{}");

const res = await fetch(
  `https://app.cuprice.io/api/share/${shareId}/checkout-payload`,
  {
    method: "POST",
    headers: { "Content-Type": "application/json" },
    body: JSON.stringify({
      selectedFeatures: names.map((name) => ({ name })),
      featureUsageAmounts: usage,
      billingInterval: "month",
    }),
  }
);
const { payload } = await res.json();

const amount = payload.plan.amount; // charge this
const features = payload.features.map((f) => ({ name: f.name, limit: f.limit }));
// => [{ name: "Team seats", limit: 3 }, { name: "Priority support", limit: null }]

Use payload.features, not the names from the query string. Cuprice only lists features that exist in the project there, so a made-up name cannot sneak in.

Step 2: Keep the features with the payment

Save features and amount on a pending order in your database and pass the order ID to your payment provider. Provider metadata fields are often too small for a long feature list.

Step 3: Save on the customer after payment

When your provider confirms the payment, copy the order’s features onto the customer. From there, checks work the same as for regular plans.

Feature fields

Each entry in payload.features for a custom plan has:

string

required

Feature name, for example “Team seats”. Custom plan features carry no id (it is null).

string

The feature type, for example Limits or Usage Based

number

The amount the buyer chose for a limit or usage-based feature, or the feature’s default amount. null for on/off features.

object

model (flat, limits or usage_based), unitPrice and subtotal for this feature

Custom plans cannot be reported to Cuprice with Report Subscription Event, because that endpoint needs a Cuprice plan ID.

Getting Started

Embed Widget

Checkout

Feature Gating

Customization

AI Tools

Step 1: Price the selection on your server

Step 2: Keep the features with the payment

Step 3: Save on the customer after payment

Feature fields

​Step 1: Price the selection on your server

​Step 2: Keep the features with the payment

​Step 3: Save on the customer after payment

​Feature fields

Step 1: Price the selection on your server

Step 2: Keep the features with the payment

Step 3: Save on the customer after payment

Feature fields