Tovuti Administrators can build Courses and learning resources to be sold to their users.
Adding a Payment Gateway in Configuration makes it easy to apply collections directly to a Course, Subscription, Brand, and more.
This article outlines the following concepts:
Add Payment Gateway
Go to Configuration > Click Payment Gateways > Click Add
To allow admins to receive emails when something is purchased on the site click on the select button under the Admin email addresses.
Add any admins by filling out the admin name and email for those that need to receive purchase emails with the green "+" and remove any that are no longer needed with the red "-" buttons.
Select the gateway (Stripe or Authorize.net) then edit the rest of the fields for the Payment Gateway selected.
Click Save.
Sites
Also within this window, the Sites associated with this payment gateway are displayed.
When editing Brands, this Payment Gateway option is now selectable. Selecting this option automatically applies the settings you’ve saved by following the steps above.
Available Payment Gateways
View the Help Center Articles for our top Payment Gateways below:
If certain Users should be excluded from being able to use this Payment Gateway, this can be configured when editing the Brand.
Use Cases
The following are possible general use cases for utilizing this feature:
Selling paid courses or subscriptions within specific brands
An Admin wants to monetize premium content but only for a subset of users under a particular brand. They need a way to tie a payment system directly to that brand’s course catalog.
This feature is useful because:
-
Payment Gateways can be associated with individual brands
-
Each brand can have its own pricing model, audience, and currency rules
-
Admins avoid conflicts by isolating payment setups per business unit
Example Use Case
A training provider operates two brands: “Core Learning” (free content) and “Pro Academy” (paid certifications). The Admin adds Stripe as a Payment Gateway and links it only to “Pro Academy.” Users browsing that brand’s catalog can purchase courses, while “Core Learning” remains open-access.
Enabling frictionless checkout for paid learning paths
An eLearning business wants to simplify the purchase experience for users buying bundled content like course series, certifications, or annual subscriptions.
This feature is useful because:
-
Payment Gateways can be applied directly to courses, learning paths, or subscriptions
-
Users pay once and receive instant access to the appropriate content
-
Integrates with native checkout flows inside Tovuti
Example Use Case
A culinary school offers a “Pastry Certificate Program” composed of six courses. The Admin sets a one-time purchase price using an Authorize.Net gateway. Learners pay through a branded checkout page and are instantly enrolled in all six courses via a learning path.
Managing access restrictions based on payment gateway eligibility
A finance training organization wants to restrict access to a specific payment method (e.g., ACH-only) for certain clients while others can use standard credit card gateways.
This feature is useful because:
-
Admins can exclude certain user groups from using a payment gateway
-
Helps enforce custom pricing, billing agreements, or compliance needs
-
Provides flexibility for enterprise vs. public user experiences
Example Use Case
Corporate clients in the “Enterprise Access” group are under contract for invoiced billing. The Admin disables Stripe access for this group via Brand settings, ensuring they don’t see or use credit card checkout. Meanwhile, individual learners in public groups continue using Stripe for self-service purchases.