Tenth Step
Words of Caution
If you are reading this guide, then you are likely a spicy content creator.
Please keep in mind that this website is "open" to the full internet. It would not be appropriate to have explicit nudity on this page any more than it would to have explicit nudity in your shop window in a busy neighborhood. Adult content should always be kept behind a password protected page, like the password protected blog we created.
Note that on the bottom left hand corner of ALL of your pages, there is a little bubble that says, "report abuse." As your webpage is being hosted on a free service, there are conditions. Use your common sense to make sure that button never gets pushed.
In the worst case scenario where your site was shut down through that report abuse button somehow, you would still be OK. Thanks to the "compartmentalization" that we have employed. Remember that new gmail account we created? THAT is where the complaint goes. The remainder of your web services would be unaffected. We can use short.io to instantly redirect your domain to a backup website.
This section will review those compartmentalization protocols and how to recover from a shutdown.
Payment Links
Whenever linking to payment pages or using embedded checkout buttons, make sure that when the client is at the point where they are entering their card information, they are at the correct URL. Unless you have taken special steps to connect a web checkout, or another type of app that has built in payment processing (like a forms app,) clients should never see YOUR URL above. Generally those payment buttons are designed to "pop out," so that the person is at square.com or whatever payment platform you are using at that point.
In other words, don't try to "embed" payment pages into your website unless they are specifically designed for that. Because their card information would then be going through YOUR server, even though it is encrypted, that can trigger fraud alerts.
Here's an example of a simple payment link using this concept. Below is an example of the same payment link, except using the "Embed code" option. Here's an option of a bad example. Note how I used the URL shortening service so that the payment page shows Werk.Baby at the top. Do not do that.