Test your standard forms or custom self-hosted forms to make sure they appear correctly on your website and enter data correctly in Bloomerang CRM.
Step 1: Connect Your Processor to Bloomerang CRM
Stripe
You must have a Stripe processor set up in Bloomerang CRM. For information about how to set up a Stripe processor, view Add Stripe to Bloomerang CRM.
To connect to an existing Stripe processor in Bloomerang CRM:
Go to the Transaction Processors page. You must use this direct link: https://crm.bloomerang.co/Settings/Transaction/CreditCardProcessor
Click Stripe.
Warning: Stripe can process only live cards. Test with $1 transactions. You can refund the transaction to the donor, but the transaction fees are non-refundable.
Authorize.Net
To test your Authorize.Net connection and credentials, have an Administrator set your account to test mode.
When a processor is in test mode, it does not actually process any real transactions, but still lets you check that your form is working correctly. This also allows you to create donations for a fake constituent, who can be filtered out of reports if necessary.
Tip: Schedule testing for off-peak hours to prevent any confusion. Constituents will not be able to submit a donation on the form during testing.
Go to the Transaction Processors page. You must use this direct link: https://crm.bloomerang.co/Settings/Transaction/CreditCardProcessor
Click Authorize.Net.
In the API Login ID and API Transaction Key boxes, type in your keys from Authorize.Net.
Select Test Mode.
Click Save.
Step 2: Connect your Processor to the Form
Make sure your form is using the test processor:
Click Communications.
Click Forms.
On the Online Giving tile, click Select.
Click the form to test.
From the Transaction Processor drop-down list, select the processor to test.
Click Save.
Step 3: Publish the Form
Publish the form to the location on your website where it will be used.
Step 4: Make Donations Using the Form
Tip: Enter all test donations on the same constituent's account for easier clean-up.
Load your web page and visually check the form.
For Stripe, run the test transactions with a live card. For Authorize.Net, run test transactions using Spreedly test numbers:
One-time donation.
Recurring donation.
Donate with different credit card types.
Tip: See Test Forms with EFT Transactions to test EFT transactions.
Set the frequency and future start date of a recurring donation, if applicable.
Use different funds, if applicable.
Submit the form with custom fields, if applicable.
After each transaction, verify the following:
The success page appears.
Account is created in Bloomerang CRM, if applicable.
Donation is added to constituent's timeline.
Funds and custom fields are recorded correctly.
Other unique functionality works as expected.
If you are self-hosting the form, verify these additional items:
Test some scenarios that should not work, such as an incorrect card number, expired card, declined card, and so forth. Make sure the form fails correctly.
Make sure that the form correctly handles cases such as the user canceling out of the credit card dialog without entering a credit card number, or the user double-clicking rather than single-clicking the Submit button.
Step 5: Clean Up
When you are done testing, clean up the following:
Refund the test donations in Bloomerang CRM. This prevents your organization’s revenue from being incorrectly calculated in Bloomerang CRM.
Switch your Authorize.Net processor back to live mode by turning off test mode.
Run at least one transaction using the live processor and a real credit card, just to make sure everything is set up correctly. Refund this transaction if it isn't a real donation.
If you are completely finished testing, contact [email protected] to clean up the test transactions.