Domain forwarding (sometimes called connecting, pointing or redirecting) lets you automatically direct your domain’s visitors to a different location on the web. This can be done within the DNS settings of the registrar hosting your website. You can forward your domain to a site you’ve created with Wix, WordPress or any other URL.
Domain forwarding has two options: forwarding only and forwarding with masking. Both options will redirect your visitors, but forwarding with masking has additional features you can use.
- Redirects visitors to a destination URL of your choosing
- Keeps the destination URL in the browser address bar
Example: Assign coolexample.com to forward only to coolwebsite.net. When a visitor types coolexample.com in a browser address bar, they will be redirected to the site for coolwebsite.net. The browser address bar will update to show coolwebsite.net.
Forwarding with masking
- Redirects visitors to a destination URL of your choosing
- Keeps your domain name in the browser address bar
- Allows you to enter meta-tags for search engine information
Example: Assign coolexample.com to forward with masking to coolwebsite.net. When a visitor types coolexample.com in a browser address bar, they will be redirected to the site for coolwebsite.net. The browser address bar will continue to show coolexample.com, effectively masking the destination URL.
This blog post will focus on switching portal to operate without any payment processing being done. Note that normally Stripe (when configured) handles all online payment processing for the portal.
Overriding to process manually is useful if you want for example to test the system out for the first time without seeing “Payment processing not setup” message or if you want to use the portal for manual (offline transactions) only.
To get started first go into Administration Panel -> Payment Settings. Then navigate to the option called “Payment Processing” and toggle it off as shown below and click “Save Payment Settings” button.
This will disable all payment processing. Now you should be able to create campaigns for testing or campaigns where you process online contributions or transactions in a different way.
Setting Per Campaign Transaction Fee
In this tutorial, we’ll show you how to set the Campaign Transaction Fee, per campaign during setup. Please note that only the ADMIN has access to this feature.
Step 1: Log in as the Admin of your portal and turn the option on in the Administrator Dashboard settings
Step 2a: Create a new campaign
During the first tab “Basics” of the campaign creation, if you scroll down you’ll see the Campaign Percentage Fee field. Here you can adjust this setting to apply exclusively for this campaign.
If this field is left blank, then the default portal Transaction Fee setting in the Payment Settings will be used instead.
Step 2b: As admin, you can also edit an existing campaign to change this percentage
Go to any campaign and hit EDIT. You’ll see the same field here.
Only admin can edit this field. Other users will see the number, but the field won’t be editable.
(As other users)
Step 3: Complete the campaign creation process
Just complete the campaign process and everything should be set and ready to go!
How Can I Troubleshoot My Payment Configuration?
Sometimes you may run into configuration issues with payment processing.
Please note that we do our best to help you with this including online help tutorials or assistance from our engineering team that can check or verify your payment configuration to ensure everything is correct.
Have you gone over the following tutorial below on how to configure the main Stripe account for your website instance?
Please make sure all the steps are followed in the above tutorial including creation of platform on Stripe.
Next, if you are planning to have project creator connect their stripe/bank account to campaign during campaign creation (like a kickstarter) for automatic distribution of funds, you will need to then follow the tutorial below.
Alternatively, you can use “Direct Transaction” feature if you will not be having project creators connecting their accounts and all money will go into portal account only as per below and you may handle distribution of funds manually.
That means you only need to do the connection once at the portal level and the funding step will be removed from campaign creation process.
Finally, if you are seeing customers created but not charges then your issue may reside with charge modes. Lite Tuition allows you to process payments in two charge modes.
1. Direct Charge Mode
2. Post Charge Mode
Defaults are for AoN type of campaign (All Or Nothing) that payments are processed in Post Charge Mode, and for KiA (Keep It All) type of campaigns that payments are processed in Direct Charge Mode.
These modes are configurable from the Administration Panel.
If you are indeed using AoN campaigns with Post Charges, then these should be tested as per tutorial below. Note that you will need to end the campaign so it can be tested (for this please refer to “Test Post Processing” option).
Direct Charges do not require this as they are processed immediately.
If you are still experiencing problems with your Stripe configuration, we will need to you to create a new support ticket on support.litetuition.com and invite our team to your Stripe account temporarily (you can remove us later). You can invite firstname.lastname@example.org and our engineer can examine both your Stripe and your Website Configuration to ensure there are no issues.
In order for this test to work, you must have an approved campaign with contributions/pledges.
STEP 1. Log in as the Portal Admin. Go to your ‘Administrator Dashboard’ and under the ‘Campaigns’ tab, select the campaign you want to test.
Checkmark the campaigns you want to edit with the check-boxes on the left of each campaign.
STEP 2. Click on the ‘Actions’ button at the top left to apply to the checked Campaigns. Click on ‘Test Post Processing’
- Approve Campaign: Approve campaigns which are “waiting for approval”.
- Disprove Campaign: Reject a campaign or undo campaign approval.
- Test Post Processing: End a campaign, setting end date to -7 days. This is only used to test the Stripe Post Processing Script. Click this to test pre-authorization. (Please note: In LIVE mode, there is a 5 minute delay for the contributions to be processed for testing Post Processing. If there are transfers which are declined, you need to set the campaign status to “Accepted for capture” manually as the portal admin to capture the funds.)
- End Campaigns: End a campaign by changing the campaign end date to current time ( will need to wait a couple of minutes to update ).
- Delete Campaigns: Delete a campaign.
- Feature Campaign: Feature a campaign on the front page.
- Un-feature Campaigns: Remove a campaign from the Features List.
- Hide Campaigns: Hide the campaign from /explore and front page. To access the campaign, you will need a direct link.
- Un-hide Campaigns: Show the campaign again.
STEP 3. The system will automatically process the ended campaign and you will receive email notifications for each processing stage of the campaign.
STEP 4. You will now see your transactions on your Stripe dashboard.
As a project creator you are now ready to create a campaign and connect your stripe account to your CrowdFunding campaign. Here are a few short steps showing how to do this.
STEP 1. Once you have created your campaign, head to the ‘Funding’ tab and click ‘Connect with Stripe’.
STEP 2. This will redirect you to Stripe, you will need to login if you haven’t done so or fill out the form. You can skip the form if you are in ‘Development Mode’ (you must be logged in to your stripe account as well).
STEP 3. Now you can select your stripe account in the drop down, based on the account email. Live and Test connections will be labelled.
STEP 4. Fill out the rest of the information for your campaign and after all fields are filled out, you can now send it for review.
Introducing Direct Transactions
“Direct Transactions” is a feature which allows for direct stripe connect transactions that portal admin can toggle.
Basically, this mode allows all the funds from campaigns to go to a single stripe account which is selected by the admin. Admin can then distribute the funds to campaign creators or managers manually.
By enabling this feature, campaign creators no longer need to go through the individual stripe setup (funding step) which greatly reduces the complexity for anyone who tries to setup a new campaign.
Following is a brief tutorial for helping site owners to locate and use the setting:
1. Go to ‘administration dashboard’ and then go to ‘Portal Settings’.
2. Under ‘Stripe Settings’, there is ‘Direct Transactions’. If that is toggled on, then all transactions will go to the main Stripe account configured on portal settings.
3. Save the settings and it’s good to go.
- Direct charge option will charge contributor’s credit cards and distribute the funds as contributions are received, (when using either Keep it All or All or Nothing raise modes).
- Post charge option will charge contributor’s credit cards and distribute the funds once the campaign end time is reached, (when using either Keep it All or All or Nothing raise modes). This option will not process charges when All or Nothing raise mode is in use and funding goal has not been met.
Please refer to the following articles for more information. New Raise Mode Payment Workflows (Direct/Post) and Post Processing Workflow Explained
Post Processing Workflow Explained
This post will try to explain post processing workflow in more detail and outline some differences in regard to direct processing.
Campaign Processing Workflow
The post processing workflow offers several advantages over direct processing. However, there are always cases when either post or direct processing workflows make more sense. KiA campaigns can certainly benefit from Direct Processing and AoN campaigns are better suited for Post Processing. That is why these are the sensible defaults.
Imagine the following scenario. You had AoN campaign that had 100 contributors running in direct processing mode. If project ended and did not reach its goal or reached its goal but creator decided to back out, then project creator would need to refund those 100 backers manually.
However, if post processing mode was used then creator would not need to handle the refunds manually due to how post processing and credit cards work.
In post processing workflow what happens is as follows:
- Campaign ends at a certain date.
- If the campaign is successful (AoN) or under KiA mode, it moves into the special 5 day post processing phase
- Backend will try then to pre-authorize all credit cards to determine success rate and put fund holds.
- If there is a 100% success rate, it will automatically put campaign into capture phase (that occurs at end of 5 days), if not project creator or admin has to explicitly accept the campaign for capture by following the link sent in email or by changing campaign status manually to “Accepted for Capture” in administration panel (if administration account is used)
- If there is less than 100% success rate for pre-authorizations, project creator will get notified and also backers will get notified so they can re-try their pledges with new credit cards
- At any point project creator can back out of the campaign, however backers are not allowed to back out once they contributed, only project creator can back out.
- On the fifth day all pre-authorizations will get automatically processed as captures if the campaign has entered capture state as per #4
- If the campaign is canceled, project creator backed out, etc. then all pre-authorizations will automatically fall off after 6 days, so there is no need for manual refunds to be performed.
- The 5-day period gives enough time to project creators to determine the fate of campaign and also allows the backers to re-submit credit card information to ensure higher success rates
- Post processing mode is always a recommended mode for AoN campaigns.
Note that 5-day time period is a default time period and can be adjust to lower value if desired in the administration panel for the website.
The post processing workflow can always be tested immediately without waiting for 5-days.
Campaign Processing States
Once the campaign leaves the Approved / Running state ( campaign run time is finished ), the campaign is then going to enter final states as described below.
|Finished – Processing Pre Authorization||This is when backend pledge processor will try to pre-authorize the pledges||Campaign will either be Accepted for Capture or Declined depending on 100% success of Pre-Authorization, Campaign Manager is notified|
|Finished – Accepted For Processing Capture||This is when backend pledge processor has pre-authorized the cards with 100% success rate||Pledge Processor will begin capture on all cards in 5 day period, Campaign Manager is notified and has option to cancel during this time|
|Finished – Declined For Processing Capture||This is when backend pledge processor has not been able to pre-authorize all cards with 100% success rate||Campaign Manager is notified and has option to cancel during this time or proceed with collection of whatever pledges are available in 5 day period|
|Finished – Processing Capture||This state is entered when pledges are ready to be captured, normally it occurs after 5 days of campaign being accepted for capture||Campaign Manager is notified that capture has started and status of campaign has changed accordingly|
|Finished – Capture Processing Complete||This is the final state of pledge processing which indicates that pledge capture phase is finished||Campaign Manager is notified that capture has finished and status of the campaign has changed accordingly|
New Raise Mode Payment Workflows (Direct/Post)
Due to demand from our users, we have introduced configurable payment workflows. Each Raise Mode (KiA or AoN) can now operate in either Direct or Post payment processing mode. This is configurable behavior from the portal admin UI.
With Direct payment processing mode contribution charges get processed immediately without any delays. This also means that the project or campaign creator needs to handle refunds manually.
Post payment processing mode (a sensible default) will process all contributions after the campaign has ended. It will first pre-authorize all credit cards used for contributions and then allow for those that failed to be re-tried. Additionally, it will give opportunity to the project creator to back out if success thresholds are not met. Refunds are handled automatically because if creators back out, pre-authorizations will fall off on their own. Finally, after a 5 day period those pre-authorizations will be captured if project creators did not back out.
Direct payment processing mode is preferred mode for KiA project or campaign creators. However, KiA can still be configured to use either Direct or Post payment processing mode.