Skip to main content
A plan is your recurring commercial offer in ArcenPay. It defines the price, billing cadence, and the set of features or entitlements that become available to a customer once they activate a subscription against it. Plans are the central object that connects your pricing catalog to access control in your application.

​
What a plan contains

Each plan holds four core pieces of information:
  • Customer-facing name and description — shown in ArcenEmbed checkout and portal surfaces.
  • Price and billing interval — the recurring amount and cadence (for example, monthly or annual).
  • Feature and entitlement mapping — the specific features, usage limits, or flags that activate for a customer on this plan.
  • Published status — only published plans are available for new subscriptions.

​
Where plans are configured

Plans are created and published exclusively from the ArcenPay dashboard Catalog. You do not define plans in code. Your application consumes the published plan IDs and resolves entitlement results from the SDK rather than reconstructing billing logic locally.
Make sure a plan is in the Published state before using its ID in any SDK call or embedding it in a checkout flow. Unpublished plans are not available to customers.

​
How plans are used at runtime

Once you have published a plan, its ID flows through the platform in several places:
  • ArcenEmbed checkout flows — published plans appear automatically in the billing surface when the customer selects or upgrades a plan.
  • Server-side subscription activation — you pass the plan ID to client.activateSubscription() to activate a subscription programmatically.
  • Entitlement and flag resolution — after a subscription is active, the React and Node SDKs resolve access against the entitlements attached to that plan.
Copy the plan ID from the dashboard Catalog page and store it as a constant or environment variable in your integration. Avoid hardcoding plan-specific logic in your UI — let the entitlement resolution layer handle access decisions.

​
Next steps

  • Subscriptions — understand how a subscription is created and managed after a plan is activated.
  • Add-ons — extend plans with extra products
  • Credits — attach prepaid usage packs to plans
  • Entitlements — learn how to check the access granted by a plan
Last modified on May 15, 2026