Custom Plans

When a user builds a custom plan by picking individual features, the receipt metadata contains the feature details directly.

How metadata is stored

Stripe limits metadata values to 500 characters. Cuprice splits the feature JSON across multiple keys:

{
  "customPlan": "true",
  "featureDetails_0": "[{\"name\":\"AI Prompt\",\"type\":\"Standard\",\"price\":10},",
  "featureDetails_1": "{\"name\":\"Dashboard\",\"type\":\"Standard\",\"price\":20}]"
}

Reconstructing the feature list

Join all featureDetails_* keys and parse the JSON:

const metadata = receipt.metadata;

let json = "";
Object.keys(metadata)
  .filter(k => k.startsWith("featureDetails"))
  .sort()
  .forEach(k => json += metadata[k]);

const features = JSON.parse(json);
// => [{ name: "AI Prompt", type: "Standard", price: 10 }, ...]

Feature object shape

Each feature in the array has:

string

required

Feature name (e.g. “AI Prompt”)

string

required

Feature type: “Standard”, “Limits”, or “Usage Based”

number

required

Price for this feature

number

For Limits/Usage Based features, the purchased quantity

Getting Started

Embed Widget

Payments

Feature Gating

Customization

AI Tools

How metadata is stored

Reconstructing the feature list

Feature object shape

​How metadata is stored

​Reconstructing the feature list

​Feature object shape

How metadata is stored

Reconstructing the feature list

Feature object shape