To help you comply with the Payment Card Industry Data Security Standard (PCI DSS), Payment 2.0 parts use secure payment pages on a Blackbaud server to process credit card billing information and payment information. Use this setting to update your secure payment pages with the latest style sheet, layout, template, and page changes you make for your payment web pages. If you do not use this setting, the program holds your changes in a queue and pushes them to the secure payment page every five minutes. For more information about secure payment pages, see Secure Payment Page.
| 1. | Under Secure payment template update, to manually update secure payment pages so they include the latest template changes for desktop browsers and mobile devices, click Update templates. |
The update begins and the button disables. After it completes, the button enables again.
Note: When you click Update templates, all secure payment pages for all Payment 2.0 parts update. You cannot select to update a secure payment page for one Payment 2.0 part.
| 2. | To replace your organization's template for the secure payment page with a generic template, clear Enable secure payment template updates. The Update templates button disables so you cannot apply your template to the page. |
It is unlikely you want to use the generic template because it does not match the rest of your website. However, Flash and JavaScript content does not upload to the secure payment page for PCI DSS compliance. If your page, template, or layout includes this content and the absence of it heavily impacts the appearance of your secure payment page, you may want to use the generic template. You can also use the generic template if you need to temporarily revert your template updates to the page. When you are ready to use your template again, select Enable secure payment template updates and click Update templates.
| 3. | To save the setting, click Save. |