Yes! The following fees will be applied to your RaiseDonors plan.
- $499 one-time setup fee (service)
- $105/month fee for service
- $100/year fee for SSL
Please make note that an annual agreement is required to implement the white-label solution (i.e. domain masking).
What is included with this solution?
- Full end to end SSL encryption on your custom white-label domain.
- Automated SSL renewals each year.
- Your organizations domain will be protected with ALL of our proprietary fraud monitoring services, cache layers, encryption services, and many other security features, ensuring you have the same security and performance metrics found under the domain of RaiseDonors.com.
- At this time, the donor portal does not support custom domain names.
Note, you may also embed a donation form on your website.
Ok, back to using your domain name,
Assume your organization name is Acme, Inc. By default, your RaiseDonors donation pages will be configured like this:
By enabling your own domain name, it will be configured like this:
Please note: you'll likely need to use a sub-domain for this setup. If you choose not to, everyone visiting your primary website (ie: acme-inc.com) will be sent to RaiseDonors. By using a sub-domain (ie: donate.acme-inc.com), only visitors landing on the sub-domain will be sent to RaiseDonors.
To do this, you need to have access to the DNS records for your domain name. There are a variety of places where your DNS records can be hosted, so these instructions will be non specific.
To get started, open a support ticket inside of your account, and inform us that you wish to get started with this solution. We'll then follow up with the appropriate next steps.
** RaiseDonors can make use of a pre-existing SSL certificate that you have already purchased and manage. However, you will be responsible for the renewal process and ensuring the SSL does not expire.
You are also responsible for notifying the RaiseDonors help desk -- at least 30 days prior to the expiration date -- so that expiring certificate can be replaced.
We must receive the SSL in a .pfx format along with the associated pfx password to decrypt the SSL certificate. Read more about .pfx formatting.