Set up Tap to Donate

Before you begin, you need:

• The Organization Administrator role. Only Organization Administrators can set up Tap to Donate.
• A connected Stripe account, which Tap to Donate uses to process in-person payments. If you haven't connected one yet, see Stripe.

You can enable Tap to Donate by adding one address — the address where your team collects donations. Fundraise Up registers it with Stripe so your devices can take card payments. One address covers all your events, and you can edit it later. You can do this in the Dashboard or in the Fundraise Up app.

1. Go to Settings > In-Person Giving.
2. Click Set up location.
3. In the Set up your location window, enter your office address. In Location name, enter a name for this address, such as Main Office.
4. Click Set up location.

1. Install the Fundraise Up app on your phone or tablet, then log in with your Fundraise Up account.
2. Tap Enable.
3. On the Set up your location screen, fill in your address. In Location name, enter a name for this address, such as Main Office.
4. Tap Continue.

If your organization has not connected a Stripe account yet, the app asks you to connect one before you can continue.

Tap to Donate campaigns live in the Tap to Donate campaigns section of your Dashboard. Only these campaigns appear in Tap to Donate mode.

To create one:

1. Go to Tap to Donate campaigns.
2. Click New campaign.
3. Enter a name for the campaign. This name is internal, and supporters do not see it.
4. Under Default language, choose the language the campaign content appears in unless a supporter picks another one.
5. Click Create campaign.

After you create your first campaign, New campaign gives you two options:

• New Tap to Donate campaign with default settings — a fresh campaign you configure from the start. Use it when the new campaign is unlike the ones you already run.
• Clone an existing Tap to Donate campaign — a copy of a campaign you have already set up, carrying over its settings. Use it when the new campaign is close to an existing one — the same event at a different location, or a repeat in a later year — so you do not configure it again.

The campaign opens on the Overview tab, which shows its key details. Switch to the Settings tab to configure it.

You can also start from the Fundraise Up app. On the campaign list, tap New campaign, then tap Go to Dashboard. When you return to the app, pull down on the campaign list to refresh it.

The Settings tab is where you set how the app takes donations. The left-hand menu groups the options into sections. Start with General and work down.

The General section sets the campaign's name and how long it runs.

• Set a Campaign name for internal use — it appears in the Dashboard and your reports, but supporters never see it.
• Add an optional Campaign code to tag the campaign in reports, exports, and your CRM.
• Under Campaign end date, set a date to disable the campaign automatically and move it to the archive.

The Frequencies section sets which donation frequencies supporters can choose. Offer up to two frequencies, such as one-time and monthly. The station preselects the default, and supporters can switch to the second one if you add it. Only the frequencies enabled in your account's Dashboard settings (under Settings > Recurring plans) are available here.

The Donation amounts section sets the smallest gift the station accepts. You can choose different amounts for the frequencies you selected.

The Designations section sets what supporters' donations fund. Choose how donations are assigned to a designation:

• Assigned designation — every donation goes to the designation you select, and supporters cannot change it.
• Selectable designation — supporters choose from the campaign designations at the station.

The Supporter section sets what personal information supporters give with their donation, and when they give it.

Select Collect supporter information to ask for a first name, last name, and email address. The supporter can leave them blank unless you require them. Clear the checkbox to take donations without asking for anything — the app then won’t show supporter screens at all, and the donation will be recorded without a name or contact details.

With Collect supporter information selected, choose what else to ask for and what the supporter must give:

• Require full name — the supporter must enter a first and last name.
• Require email — the supporter must enter an email address.
• Phone number — select Make it required to require it. Select Show legal text to display Legal text under the field, such as consent to receive calls or text messages.
• Mailing address — set a Minimum amount to ask to request it only above a certain donation amount. Select Make it required to require it, and set a Minimum amount to require to enforce that only above a chosen amount.

A name, email address, and phone number are collected before the payment goes through, so the details can’t attach to someone else’s donation. Requiring one of them only decides whether the supporter can move on without it.

A mailing address and contact preferences are collected after the payment, where the supporter can skip them. A mailing address you require is collected before the payment instead.

For an organization in Canada, the Canada Revenue Agency requires a first name, last name, email address, and mailing address before the payment. The app always collects it before the payment.

Under Supporter options, choose whether supporters can:

• Allow to donate anonymously — keep their information out of any public use, such as reports or published lists.
• Allow donations on behalf of organizations — credit a company, club, or association for the donation.

Each required field can reduce completion, so require only what you need.

The Marketing consent section sets how the app asks supporters for permission to receive communications. Choose one of three options:

• No consent — no consent checkbox appears.
• General consent — one checkbox covers all communication. Set the Checkbox text, and add Additional info to explain what the supporter agrees to.
• Customized consent — supporters opt in to each channel on its own. Under Channels, choose which to offer: Email, SMS, Phone, Postal mail, and Social media. Add Consent details to explain the choices.

Under Consent settings, select Show only in regions requiring explicit consent to show the request only where local law requires it. Preselect consent checkbox starts the checkbox selected. Preselection may not meet the requirements of some privacy laws, such as GDPR.

The Terms and conditions section adds a checkbox that supporters must select before they can complete a donation. Select Require supporters to accept terms, then set the Checkbox text. You can add links to your terms and privacy policy in the text.

Preselect checkbox starts the checkbox selected. In the European Union, supporters must give explicit consent, so preselection does not comply with GDPR.

The Custom fields section records extra information with each donation. Click Add field to choose a field from the list your organization keeps in Settings > Custom fields, or to create a new one, then set the value this campaign records. The values appear on the donation and in your exports.

The Localization section sets which languages the campaign content appears in. English and French are available.

To translate the campaign content into the other language, click Configure languages, select it, and click Save changes. An editor opens with your default-language content on the left and a field for each translation on the right.

A supporter sees your translated content when they give in that language. Anything you leave untranslated appears in the campaign default language.

The Campaign progress section shows how much the campaign has raised on the donation screen in the app.

Select Show total raised amount to display it. When the checkbox is clear, the app doesn't show campaign progress at all.

Under Raised amount settings, set what the amount is measured against:

• Add campaign goal — select it and enter a Goal amount. The app then shows the amount raised against the goal, with a progress bar. Without a goal, the app shows the raised amount on its own.
• Set end date — select it and choose an End date, the last day donations count toward the campaign.

The End date here is not the Campaign end date under General. The campaign end date disables the campaign and moves it to the archive; this date only sets which donations count toward the amount raised.

Switch to the Content tab to set what supporters see on the station's donation screen. Add a logo, an image, a title, and a message that explains the cause.

Switch to the Emails tab to configure the emails supporters receive after they give, such as the donation receipt. Customize each one or turn it off.

To send them in more than one language, open Localization on the Emails tab. It lists the email content you have customized — the sender name, the footer, and the subject and body of each email — with a field for each translation. A supporter receives the email in the language that was on screen when they donated.

An In-Person Giving Specialist is a staff member or volunteer who only collects donations on-site. The role carries no Dashboard permissions beyond personal profile settings. Organization Administrators, Campaign Administrators, and Configuration Managers can also collect donations in the app, but this role is built specifically for the people running events.

Only Organization Administrators can add In-Person Giving Specialists. When you invite one, you choose which campaigns they can use in the app — every active campaign, or a specific list.

To add an In-Person Giving Specialist:

1. Go to Settings > Team.
2. Click Invite user.
3. Enter the user's email address, first name, and last name.
4. Select In-Person Giving Specialist as the role.
5. Choose which campaigns the specialist can use:
   • To grant access to every active campaign, select All active campaigns. New campaigns you create later are added automatically.
   • To grant access to specific campaigns, select Selected campaigns only, click Add campaigns, and add one or more by name or ID.
6. Click Send invite.

You can add a specialist without assigning any campaigns; they can log in but see no campaigns until you grant access. Disabled or archived campaigns cannot be assigned, and disappear from the specialist's app automatically if a campaign is later disabled.

From a parent account, you can assign campaigns from your subaccounts as well. Campaigns from different accounts never appear in one list, so the specialist switches to the subaccount in the app to reach them.

Once specialists accept their invitations, they can set up the app and start collecting donations. See Accept in-person donations with Tap to Donate.

Any number of specialists can collect donations for the same campaign at once.

To change which campaigns an In-Person Giving Specialist can use:

1. Go to Settings > Team.
2. Find the specialist, click the three-dot menu (…), and click Edit role.
3. Update the campaign list:
   • To grant access to every active campaign, select All active campaigns.
   • To add a specific campaign, select Selected campaigns only, click Add campaigns, and add one or more.
   • To revoke access, remove the campaign from the selection.
4. Click Update.

The specialist sees the updated list the next time they open the app, or when they pull down on the campaign list to refresh it.

The Fundraise Up app uses the same SSO configuration as your Dashboard. If your organization already signs in with SSO, your team signs in to the app the same way. How users sign in follows your account setting under Settings > Security:

• Optional — users can sign in with SSO or with a password.
• Required — users must sign in with SSO. A password will not work.

Someone who belongs to more than one organization meets the rules of each one separately. Moving to an organization that requires SSO sends them through that organization's provider, and an organization that requires two-factor authentication asks for a code.

If you have not set up SSO yet, see Single sign-on (SSO).