A donation form, or the Console page you use to process gifts or pledges, can refuse an attempt for several reasons. Work through the sections below in order, from the most common issue to the least common.
The Form or Page Will Not Open at All
If a Portal donation form stays on its loading message, or the Console gift or pledge page shows an error before any fields appear, your Rhythm account probably does not have a Fundraising settings record yet.
- On the Portal, the donor sees Unable to load gift form info, with a message that Fundraising has not been configured and giving cannot occur until it is.
- In the Console, staff see You have not configured fundraising settings. Please configure Fundraising settings before continuing.
Fix. Save a Fundraising settings record before you open giving to donors, including a default giving process and a default fund. See Set Up Fundraising for the full setup order.
Warning
This check only confirms that the settings record exists. It does not confirm that every value in the record is still valid. For example, if someone later deletes the default giving process in that settings record, this check still passes, and giving can fail later for a different reason.
A few other giving-form issues can look more serious than they are, but they come from the same setup area.
Tip
On a microsite, a missing donation landing page or a broken-looking Fundraising tab can have the same root cause: your Rhythm account's Fundraising settings are not fully set up yet. The page or tab itself is not necessarily broken.
Tip
Both Organization fields on a public giving page are plain text entry fields, not dropdowns. If one seems to spin instead of accepting input, type the organization name directly; there is no list to wait for.
"This Giving Process Does Not Allow Pledges"
In the Console, staff processing a pledge see IllegalOperation: Specified giving process <name> does not allow pledges. Pledge processing cannot continue., and the pledge wizard does not open.
Cause. The selected giving process does not allow pledges. If staff did not choose a process, Rhythm checks your Rhythm account’s default giving process instead. This check runs only in the Console’s browser. On the Portal, Rhythm handles the same situation by hiding Make a Pledge instead of showing an error.
Fix. Choose a giving process that allows pledges, or turn on pledges for the process you need to use.
A Recurring Gift's End Date Is Too Soon
Rhythm refuses a gift with a recurring end date less than one month away and shows IllegalOperation: The recurring gift end date must be at least 1 month in the future.
Fix. Set the end date at least one month ahead of today. This check applies only to gifts, not pledges.
A Gift Was Refused for Exceeding a Fund's Annual Limit
When a fund has an annual contribution limit turned on, Rhythm refuses a gift to that fund with IllegalOperation: Gift exceeds annual contribution limit.
Warning
This limit counts the donor’s gifts to that fund over the rolling twelve months from today, not since the start of the calendar year, even though the fund setting describes it as an annual limit. Rhythm accepts a gift that exactly reaches the limit and refuses only a gift that would exceed it. This check applies only when a gift is processed through the standard gift order flow. Pledges and gifts recorded through other paths are not held to it.
Fix. Lower the gift amount so the donor’s total to that fund over the past twelve months does not exceed the limit, or direct the excess to a different fund.
"Too Many Payment Attempts" (Anonymous Givers Only)
On the Portal, an anonymous donor sees Too many payment attempts have been made. Please wait a little while before trying again. after their fourth attempt from the same email address within an hour.
Warning
This limit slows attempts to test stolen card numbers through your public donation form. Rhythm tracks the email address the giver types and treats common address variations, such as an address with a "+" tag or minor formatting differences at some providers, as the same mailbox. The limit applies only to anonymous gifts; anonymous pledges are not limited this way. A genuine donor who mistypes their card several times in a row can hit this same limit and needs to wait before trying again.
Fix. Ask the donor to wait before retrying, or have a signed-in staff member process the gift for them in the Console. The Console is not subject to this limit.
A Signed-In Member Cannot Give for Someone Else
Rhythm refuses a signed-in Portal member’s gift or pledge when they name a different person as the donor, or when they name an organization they are not linked to. This check applies only to signed-in members. An anonymous visitor, or a staff member processing a gift, is not restricted to naming themselves as the donor.
Fix. Have the member submit the gift or pledge under their own name or their own linked organization, or have staff process it for the intended donor in the Console.
A Declined Card Gives No Reason
Warning
When an anonymous donor’s card is declined on the public donation form, Rhythm shows only this generic message: We could not process this payment. Please check your card details and try again, or use a different card. Rhythm never shows the payment processor’s specific decline reason in this case. This protects against card testing, because a specific reason, such as an invalid security code, would tell an attacker which part of a stolen card is wrong. Signed-in members and staff processing a gift in the Console see the processor’s actual reason. Rhythm changes this message only for the gift route; an anonymous pledge decline is not rewritten the same way.
Fix. You cannot see the specific decline reason for an anonymous gift decline from the donation form itself. Ask the donor to try a different card or payment method, have them give again while signed in, or have staff process the gift for them in the Console, where the actual reason is shown.
A Saved Card or Bank Account Causes a Problem
Several gift and pledge issues trace back to saving a payment method for later use.
A donor who is not signed in never sees the option to save a card. Saving a card or bank account for future giving, including for a monthly gift, is tied to a signed-in account. An anonymous donor has no account to save a payment method to, so Rhythm does not offer the option at all, and it will not work if it is somehow reached.
Fix. Ask the donor to sign in before giving if they want to save a card for a future or recurring gift.
A signed-in donor does not see the save-card option, even though it should be available. When your Rhythm account's Fundraising settings allow donors to securely save a credit or debit card, and the giving process being used does not override that checkout setting, a signed-in donor should see the option and be able to use it successfully.
Fix. Confirm both settings before assuming the option is broken: saving a card is turned on in Fundraising settings, and the giving process in use does not override checkout settings.
A card already on file fails without an explanation. The stored card details may no longer be valid or usable for that payment, even when the error does not say so.
Fix. Delete the saved card, add it again, and try the payment once more.
A pledge fails with "Forbidden: Access Denied," even with a valid saved card. A signed-in donor submitting a pledge with a saved, valid card may see Unable to process gift - Forbidden: Access Denied. This message has pointed to a problem processing the pledge itself on the Portal, not to the card, so trying a different card is unlikely to help.
Fix. Have the donor try the pledge again later, or process it for them in the Console instead.
A Bank-Account (ACH) Gift Fails or Never Appears
Your payment processor may not have ACH turned on. Turning on bank-account or electronic-check checkout in your Rhythm account is not enough by itself. Your connected payment processor account must also have ACH or eCheck enabled, separately from that setting. If a bank-account gift fails and the transaction never appears in your processor's own account, instead of appearing there as a decline, that points to this missing prerequisite rather than something the donor entered wrong.
Fix. Confirm with your payment processor that ACH or eCheck is turned on for your merchant account, then try the gift again.
Tip
If saving the bank account for later use seems to be part of the failure, having the donor submit the gift without saving it for later use has helped in some cases. This option to skip saving is not available on every checkout flow, so it may not be there to turn off.
Warning
If bank-account or electronic-check gifts fail for every donor at once, rather than for one donor with one payment method, that pattern by itself points to a broader processing issue rather than anything specific to that donor. Contact Support rather than troubleshooting each attempt separately.
A Payment Went Through, but No Gift Appeared
Occasionally an order's invoice shows payment applied, but no matching gift record appears.
| What You See | Likely Cause | What to Do |
|---|---|---|
| Store credit paid the invoice, but no gift record appears, and the order may stay open | Store credit applied as payment on a donation can, in some cases, leave the gift record uncreated | Open the order to confirm. If the gift is still missing, contact Support with the order or invoice number. |
| A "pay later" order's invoice was paid some time after checkout, but the gift never showed up, even though gifts paid at checkout populate normally | In some cases, a gift's record has not appeared automatically once a later payment posts to its invoice | Check the donor's gift history. If the gift is still missing, contact Support or record it by hand. |
When to Contact Support
Contact Support if the refusal does not match any message above, or if a gift or pledge keeps failing after you have ruled out these causes. Include the exact error message, whether the attempt was anonymous, signed in, or made by staff, and the giving process and fund involved.