Registration & Packages

Pagestead allows administrators to create “membership packages” to which end-users can subscribe. In order to create paid packages, the administrator must first make sure their copy of Pagestead is connected to a functional Stripe or Paypal account. Stripe or Paypal is used to collect the package fees from your end-users.

To properly connect your Stripe account, you will need to log into your Stripe account and retrieve your secret key and publishable key . For more information regarding the retrieval of your Stripe keys, we suggest reading this article .

To connect your Paypal account, you will need to provide your API username, API password and API signature. For more information regarding these settings, please have a look at the following article. Additionally, you will need to make sure your Paypal account is a Business Account and is setup to receive Express Checkout payments for digital goods (you might need to contact Paypal customer support to get this enabled).

After entering your Stripe or Paypal details, you can now move onto creating the actual packages by navigating to the Packages panel (located on the main menu bar). There is no limitation on the number of packages you can create.

When creating a new package, you will be asked to provide the following details:

  • Package name – This is the name for your package. The end-user will see this name in the dropdown menu when creating his or her account.
  • Number of sites – This is the number of sites end-users subscribed to this package are allowed to create.
  • Hosting option(s) – These are the publishing options available to end-users subscribed to this package. Please note that more than one option can be selected.
  • Export site – This enables or disables the export functionality (ie allowing end-users to download sites/pages)
  • FTP Publishing – Enabled or disables the option to upload a site to a remote server using sFTP or FTP
  • Upload space (in MB) – This sets the maximum amount of MegaBytes the end-users is allowed to use for uploading images.
  • Templates – Define which pre-made page templates will be available to the end-user
  • Blocks – Determines which block  categories the end-user will have access to. If the “limit block access” switch is set to “OFF”, all blocks are available. If the “limit block access” switch is set to “ON”, the Administrator can then enable individual categories by checking the corresponding checkboxes. If all checkboxes are unchecked (while the “limit block access” switch is set to “ON”), the end-user will have no access at all and the blocks section will be hidden.
  • Price – The amount that the end-user will be charged for subscribing to this package. When no Stripe or Paypal details have been provided, only free packages can be created.
  • Currency – The currency in which the end-user will be charged.
  • Interval – The interval in which the user will be charged; this can be either weekly, monthly, every 3 months or every 6 months.
  • Status – Indicating wether or not the package is active. If a package is in-active, no new signups are allowed (changing the status does not affect existing users).

If you are using Stripe as the payment gateway, upon creating a new package, a corresponding “plan” will be created automatically within your Stripe account.

Updating existing packages

After a package has been created, it’s details can be changed. However there are some restrictions. Only the following details can be altered once a package has been created:

  • Package name
  • Allowed number of sites
  • Hosting options
  • Export
  • FTP Publishing
  • Upload space
  • Templates
  • Blocks
  • Status

Price, currency and interval can not be altered by Pagestead. Unfortunately, this is a restriction imposed by Stripe. If the administrator wants to alter price, currency and/or interval, we suggest he/she creates a new package and moves existing users over to that new package.

Test mode / live mode

Pagestead allows users to work in “test mode” allowing an administrator to test the payment system before allowing users to sign up. The switch to toggle the test mode can be found under Settings > Payment Settings. We suggest administrators run the payments in test mode first before allowing actual users to sign up.

Please note that in order to use the Paypal test mode, you will need to apply for a sandbox account.

In addition to turning on test mode, you will need to do the following to fully use the test mode:

For Stripe

  • Log into your Stripe account and turn on test mode from there
  • Grab your Stripe test keys and insert these into Pagestead

For Paypal

  • Sign up for a sandbox account
  • Grab the API credentials for that sandbox account

Please note that running test mode while using your live Stripe keys will not work!

Please note that packages created while in test mode, can not be used in live demo. When you have completed running your tests; we suggest you delete your packages (you can do this within Pagestead) and user accounts subscribed to the test packages before switching to live mode.

Packages will be connected to the payment gateway which was active when the package was created. If you switch from Stripe to Paypal, or the other way around, the packages created using the previous gateway will be hidden. It is not possible to switch packages from Stripe to Paypal or the other way around.

Was this article helpful?

Related Articles

Leave A Comment?

You must be logged in to post a comment.