When a page or part is recently created, it's possible the secure payment template updater has not been run yet. This will need to be run in order to dynamically pull the design of the event page onto the secure payment page. You should also run this as the first troubleshooting measure for when the secure payment page is not showing as expected. You will need to run the updater any time a change is made.
Run the Secure Payment Template Updates
Run the Secure Payment Template Updates
Page Shows Inaccurate Information on Step 3
Typically, when the payment page shows information for a different or previous event, or text in a newly created formatted text and images part that should be hidden, this is due to the page or part being copied, instead of creating a new page and part. A new page and part will need to be created, and then run the template updater.
If after creating a new page, new part and running the updater, the default BBSP page displays, as shown below
This typically indicates there is a design element preventing the correct design from being displayed properly.
Please refer to our BBSP design guide. You may need to consult a qualified designer or web developer.
Please refer to our BBSP design guide. You may need to consult a qualified designer or web developer.
The incorrect or old template shows on the payment page on a mobile device ONLY
We may see this issue if the template does not have a set layout for mobile devices. To resolve this issue, we can set the layout for mobile devices. Similarly, if there is an issue with the desktop template, but not the mobile device template, the payment page might display as a mobile view on a desktop. The desktop view issues should be present in the Secure Payment Template Update process exceptions.
Verify the Targeting & Security of the part, page, template and style sheet is set to View Everyone
Confirm the Primary Site URL
Confirm the Primary Site URL
If NetCommunity is on an older version of the product, you may need to upgrade in order to allow the secure payment templates to work properly. Previous items which conflicted with the BBSP templates:
- Page name cannot have single quote or apostrophe
- Page name cannot have double quote
- Page name cannot have a colon ":"
- Page name cannot contain an "&" symbol
- Page name cannot have a "-"
See article: What are items to consider when designing the secure payment page. When the design of the payment page doesn't match step 1, this indicates there may be design elements conflicting with the Blackbaud Secure Payment Page that do not allow the design to render correctly. You may need to work with a qualified web developer to follow the design guide in order to resolve the behaviors. How do I fix design issues with my site?
What are items to consider when designing the secure payment page?
FAQs Regarding Upgrading to Blackbaud Secure Payments 2.0
Disabling Secure Payment template update does not use generic template for secure payment pages
Communications Consent
Error: Completed with Exceptions - when running the secure payment template for a part with Communications Consent