- The buyer picks a plan. Cuprice sends them to your checkout link with
cuprice_plan_id,cuprice_share_idand the billing interval. - Your checkout asks Cuprice for the plan’s price and features, creates the payment, and keeps the features with it, for example on a pending order in your database.
- Your payment provider confirms the payment, usually with a webhook.
- Your server copies the plan and its features onto the customer’s account.
- Your app checks that saved list before it shows a feature.
Where the feature list comes from
Both endpoints are public and need no API key:- Checkout Payload:
GET https://app.cuprice.io/api/share/{shareId}/checkout-payload?planId={cuprice_plan_id}returns one plan’s features withincludedandlimitalready worked out. A POST to the same address does the same for a custom plan. - Share API:
GET https://app.cuprice.io/api/share/{shareId}returns every plan on the page with its features. Theget-pricingtool of the MCP server returns the same data.
What you need
- A server route behind your checkout link that prices the plan and creates the payment
- A webhook or callback from your payment provider that confirms the payment
- A place to store each customer’s plan and features, such as a table in your database
Two kinds of purchase
Regular Plans
The buyer picks a plan like “Pro”. You look up its features by
cuprice_plan_id.Custom Plans
The buyer picks features one by one. The selection comes with the checkout link.
