Public Signup Pages in Maxio’s Advanced Billing platform allow you to create custom signup funnels with unique URLs, branding, and pre-configured Products. Each Public Signup Page links directly to a specific Product and can be embedded or shared with potential Customers, enabling fast, secure, and optimized subscription creation.
Each product can have multiple Public Signup Pages, each with its own unique URL. This allows you, the merchant, to control specific signup funnels by creating a unique look and wording for each Public Signup Page.
You can get the URL for a specific Public Signup Page attached to an Advanced Billing Product by viewing the list of Public Signup Pages located on that same page.
The Public Signup Page URL is composed using your site’s subdomain, a generated token, and (optionally) the API handle for the Product. For example: https://acme-inc.chargifypay.com/subscribe/tr57wy2j/awesome-product.
View the version of the page and the URL of the exact signup page.
As you move through this series of articles, you’ll learn more about how Public Signup Pages work and how to customize them as needed.
Public Signup Page Layouts
When creating a Public Signup Page, Advanced Billing automatically uses the modern layout. We recommend using the modern layout as it is crisper, cleaner, and more responsive.
Example of the modern version of Public Signup Pages.
Both versions provide the same functionality. However, the modern (v2) layout is responsive, mobile-friendly, and offers an improved user experience. You can select the layout version for each Public Signup Page when creating or editing the page. To set the default layout version for API-created pages, navigate to Settings > Public Page Default Settings > Default Public Signup Page Version.
Modern Public Signup Page Webinar
For a brief overview of the features in modern Public Signup Pages, watch our archived webinar:
Public Signup Page Flow
- Provide your potential Customers with a link to the Public Signup Page for the Product you would like to offer. You can pass data to pre-populate the form or variables that are sent to Advanced Billing – see Pre-populating Data.
- The Customer fills out their credit card details and other requested or required information. The information collected is defined in your Public Page Default Settings.
-
If the Customer enters incorrect information or their credit card is declined, they are notified on the page and given a chance to correct it.
If reCAPTCHA validation fails during signup, the page displays a message explaining that the security check could not be completed. The customer should refresh the page and try again, or try signing up from a different browser.
- If the information is correct and the card is accepted (or not required), the Customer is redirected to:
- A Subscription Receipt Page;
- Or, the page specified in the Return URL within your Public Signup Page Settings.
-
- If you use a Return URL and return parameters, you can capture data about the signup and update your application state. However, it is recommended to verify the data using our API to prevent URL spoofing.
- The Return URL and parameters provide synchronous signup notifications. This is the best method for real-time updates from Public Signup Pages.
- You can also use webhooks to modify your application state. Webhooks are asynchronous, so do not block the user’s signup process while waiting for a webhook response. See Webhooks Are Asynchronous.
Card Scanning
Potential subscribers can use mobile devices to subscribe from your website. They’ll be redirected to a Public Signup Page optimized for their device.
In addition to providing their personal details and selecting a Product, subscribers can scan their credit card information using their device’s camera. Card swiping is not currently supported by Public Signup Pages.
Example of scanning a credit card using a mobile device.
Once the subscriber selects the scan option, their device’s camera is activated. The card number is captured from the scan. No images or card data are stored on Advanced Billing servers or the mobile device.
Comments
Article is closed for comments.