Problem
During the Blackbaud authorisation process in Payments2Us, users may experience a blank screen or find that the authorisation does not complete after logging in successfully. In some cases, a CORS-related error may be visible in the browser’s developer console. This issue typically occurs immediately after authentication, before the success confirmation page is displayed, and can give the impression that the process has stalled or failed.
Excepted Screen/View:
Actual Screen/View:
Root Cause
This issue is commonly caused by High Assurance Session settings in your Salesforce organisation.
These settings are often enforced through:
- Multi-Factor Authentication (MFA)
- Session Security Level required at login
- Identity Verification policies such as “Raise session to high assurance”
When these settings are enabled, Salesforce may block the salesforce callback page used during the Blackbaud authorisation flow, resulting in a blank screen or CORS error.
Solution
Option 1: Exclude the User from MFA (Recommended)
This approach temporarily exempts the user from MFA using a permission set:
- Go to Setup → search for Permission Sets.
- Click New and create a permission set with a suitable name.
- Open System Permissions.
- Enable “Waive Multi-Factor Authentication for Exempt Users”.
- Save the permission set.
- Assign this permission set to the Salesforce user performing the Blackbaud authorisation.
- Log out and log back in.
- Confirm Salesforce no longer prompts for MFA.
- Retry Authorising with Blackbaud. (Step 6 of our our Blackbaud setup documentation)
- Verify that the success message appears (as shown in our Blackbaud setup documentation) and you are redirected back to merchant facility record.
Option 2: Update Session Settings at the Profile Level
If Option 1 does not work, you can adjust the session requirement at the profile level:
- Go to Setup → search for Profiles.
- Open the profile assigned to the user performing the Blackbaud authorisation.
- Locate “Session Security Level Required at Login”.
- Uncheck this setting and save.
- Log out and log back in.
- Confirm Salesforce does not prompt for MFA.
- Retry Authorising with Blackbaud. (Step 6 of our our Blackbaud setup documentation)
- Verify that the success message appears (as shown in our Blackbaud setup documentation) and you are redirected back to merchant facility record.
Important Notes
These changes are typically required only during the authorisation process. Once authorisation is successful, you may safely revert MFA or session settings if required by your organisation’s security policies. We are looking for a permanent solution to address this issue.