There are several important items to remember about the secure payment page for the Payment 2.0 part.
| • | When you use the same Payment 2.0 part on two web pages that use two different templates, the secure payment page renders using the template for the page the website user navigates from. For example, your payment page for an event registration uses a template with a red background and your payment page for a donation uses a template with a blue background. When a user navigates from the event registration payment page to the secure payment page, the page renders using the red template. When a user navigates from the donation payment page to the secure payment page, the page renders using the blue template. |
| • | Some parts, such as Formatted Texts & Image and Menu, appear on the secure payment page. Images also appear. However, you may notice that some parts do not appear on the page. |
| • | When you include targeted content on your page, be aware that it does not apply to the secure payment page. No matter the role the user is in, the secure payment page renders the view for an anonymous user the same way your page appears for anonymous users. Anonymous users are users not logged in to your website. |
| • | We recommend you remove parts that contain a Flash file. These files include JavaScript that the secure payment page removes for PCI DSS compliance. If you do not remove the part, an Adobe download message likely appears in its place on the secure payment page. |
| • | Likewise, we recommend you remove graphics that include JavaScript. The secure payment page removes these graphics for PCI DSS compliance. If you do not remove the graphic, the page likely renders incorrectly. |
| • | We recommend you remove third party social media sharing widgets from your page. These links typically include JavaScript that the secure payment page removes for PCI DSS compliance. |
| • | To enhance performance between your site and Blackbaud's server, the program holds updates you make to the style sheet, layout, and template for your payment page in a queue. When this content remains static for five minutes, the updates push to the Blackbaud server that checks for changes every five minutes. Altogether, it can take up to ten minutes to apply the updates to your secure payment pages. You cannot change this process. However, you can click Update templates in Sites & settings to manually update the changes for your secure payment page. For more information, see Secure payment page template update. |
| • | A generic template exists for the secure payment page. It is unlikely you want to use it because it does not match the rest of your website. However, if your template includes content such as Flash or JavaScript that you do not want to remove but that cannot be used on the 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, you select Enable secure payment template updates and click Update templates in Sites & settings. For more information, see Secure payment page template update. |