Skip to content
CountdownFlow Help Sign in

Create reseller offers and connect payment events

Separate the plans you sell from your own platform subscription and verify the purchase workflow.

2 min read

Screenshots show the real application in an isolated demo environment with fictional example data. Setup notices and controls may differ by environment, plan and role. Click an image to view it full-size, and always use the values generated in your own workspace.

Your SaaS plan and your client offer are different

A reseller plan defines the capabilities and allowances you offer to eligible client workspaces. Your agency’s platform subscription sets an outer boundary; selling a plan does not automatically create features that your agency is not permitted to delegate.

Use the Reseller plans screen in the eligible owner context. Review feature switches and quotas individually, especially templates, buttons, offer cards, history, API/webhooks and branding.

Configure an offer

  1. 1Create a clearly named reseller plan and set the effective features and limits you intend to sell.
  2. 2Choose its billing type and the supported payment-provider mapping shown in the app.
  3. 3Connect the appropriate product/offer identifiers and configure the required verification settings according to the screen.
  4. 4Publish/share the supported purchase or signup link only after testing the complete verified flow.
  5. 5Review how the purchase record is associated with the intended client workspace and which access-assignment step is currently available.
Reseller plan management screen with its offer configuration controls
In the application Define your client offer and its allowed capabilities here. A browser checkout return is not proof of a verified purchase or access assignment. View full-size screenshot (opens in a new tab)

Never infer access from a redirect alone

A browser return or success-looking URL is not a verified purchase. Access must follow a trusted payment event and the app’s supported buyer/workspace association and entitlement-assignment workflow.

Do not promise that every provider automatically provisions access. Check the actual verified purchase and client assignment. If a workflow needs an owner action, complete it before asking the buyer to retry.

Provider support and honest scope

Only use provider options whose payment-event contract is supported by the current application. A brand name or page builder is not proof of a supported payment event. Avoid creating manual “paid” records to bypass missing verification.

Related articles

Plans, checkout, billing portal and cancellationFind your actual allowances, change billing safely and understand the difference between direct and agency-managed access. Receive and verify signed webhooksCreate an endpoint, validate signatures, handle retries and troubleshoot delivery failures. Manage an agency and its client workspacesKeep clients separated and understand hierarchy, delegated access and workspace switching. Explain and troubleshoot client plan accessUnderstand effective entitlements, agency-managed billing and changes to client allowances.