@Pay Help Center
Welcome to @Pay!
There are a few things you should do to get started using @Pay.
1. Fill out your Organization Info
Navigate to Settings > Organization Information on the dashboard. Make sure your organization name and contact info are correct.
If you are using the @Pay Gateway, then it is also crucial that you fill out every field on this page in order to fully configure the gateway. These fields include the Address fields, Organization Representative information, and the Transfer Information. If these fields are not completed within 2 weeks of signing up or before you raise more than $1,000, we will not be able to process any more payments.
Visit the @Pay Gateway section of the Help Center for more information.
2. Upload your logo
Navigate to Settings > Messaging & Theme on the dashboard. In the Your Logo section of the page, upload the image from your computer by selecting the Browse button.
3. Update your Sender Settings
Navigate to Settings > Messaging & Theme on the dashboard. Review the information in the Sender Settings section. The Reply To Address is pre-populated with whatever email was given during the signup process. This is the address that will appear on receipts, so you may want to update the email address to a generic email your company uses, such as firstname.lastname@example.org.
4. Update your Receipt Template Colors
Navigate to Settings > Messaging & Theme on the dashboard. In the Template Colors section choose your color scheme that you want displayed on the receipts your customers receive.
Once you have complete these 4 steps you are ready to start fundraising with @Pay! Visit the Web Giving, Email Giving, and Text Giving sections of the Help Center to learn more about using our different products.
@Pay organizations are provided a dashboard to manage donations and access transaction and donor data.
The @Pay Help & Resource Center contains tutorials on how to use the @Pay dashboard, roll @Pay out to donors, and implement fundraising best practices.
If you have any questions, contact us any time or reach out to your account manager.
When a new user is granted access to the @Pay dashboard, they are sent a confirmation email with a link to set up the account.
Click the link in the email to set up a password for the account (yeah, we know…passwords suck! But even we can’t escape them completely).
For security reasons, the link expires after 7 days. If you aren’t able to activate your account in that timeframe, we can send you a new confirmation email. Simply email us at email@example.com.
Once your account is activated, log in anytime at https://dashboard.atpay.com/
The Dashboard homepage provides a snapshot of fundraising totals per month for the current year as well as the 5 most recent live transactions. It also has quick links to the most visited sections of the dashboard.
Navigating the Dashboard
The Dashboard is divided up into categories for each fundraising method, reporting, as well as general settings that affect the whole platform. Use the menus at the top to navigate through the dashboard. There is a guide for each section in this help center.
@Pay’s 2-click buttons create the ability to donate or pledge directly from an email. Include @Pay buttons in all of your organization’s newsletters and fundraising emails.
- Place the 2-click buttons near the top of the email
- Give donors 4-6 different donation amount options. Too many options can make the email cluttered.
- On average, donors opt for the mid-level donation amounts, so keep that in mind when setting the highest donation amount.
How 2-click buttons work
When a donor clicks on an @Pay button in an email, a confirmation email response automatically opens. Simply review the email to verify that the donation amount and sender are correct, and then press Send to complete the transaction.
2-Click Donor Experience:
If the donor has previously saved their payment information, the donation is complete and a receipt is sent.
1st-Time Donor Experience:
If the donor is new to @Pay, they are sent an email thanking them for the pledge with a link to a mobile optimized payment capture page.
What about Other buttons?
It isn’t possible to have an Other button that allows donors to enter a custom donation amount directly in the email. Instead, @Pay can create an Other button that links to the Giving Portal allowing the donor to fill out whatever donation amount they prefer in the web form.
If you would like an Other button, contact your @Pay account manager. Provide them with your preferred button colors and they will send you back a button that links to your giving portal.
Introducing @Pay to Donors
When introducing donors to @Pay 2-click buttons, it is helpful to provide some information on how @Pay works. @Pay is the only platform that allows donations through SMTP, so this will likely be a new experience for them.
There are 4 different methods that we recommend organizations use. Many organizations choose to implement one or a combination of these options:
- Build up a list of 2-click enabled donors
- Link buttons directly to the PCP for first few email campaigns
- Add a short @Pay tutorial to the bottom of the email
- Send an introduction to @Pay email to your donors
Build up list of 2-click enabled donors
There are lots of ways to build up the number of donors with a payment method on file. If you are using @Pay’s Giving Portal or Text-to-Give features, they will also be 2-click enabling your donors. For example, if a donor gives through your website utilizing the @Pay giving portal (or you include the @Pay SDK on your payment capture page) they will now be able to donate in just 2-clicks using email buttons.
When you are ready to send your email buttons, the donors that are already 2-click enabled will be able to donate directly from the email. First-time donors will receive the further action required (FAR) email to capture their payment method. It is also possible to use list segmentation (see the Customer List section under Reporting) to separate your emails. For example, send an email with 2-click buttons to all of your @Pay enabled donors while sending an email with buttons that link to a PCP to donors that don’t have a credit card on file.
Begin with Buttons that link directly to Payment Capture Page
If a donor has never used @Pay before, their donation cannot be processed after they send the confirmation email because there is no payment method on file to charge. In the standard workflow, @Pay automatically sends them a further action required (FAR) email with a link to a payment capture page (PCP).
Most organizations see a very high conversion rate of donors from FAR emails. However, there is always a chance that the FAR email will get forgotten about in the donor’s inbox or sent to the spam folder. Therefore, some organizations choose to create buttons for their email that link directly to a PCP, bypassing the FAR email.
After a few email campaigns, your organization will build up a list of donors that now have a payment method on file, meaning that they are 2-click enabled. At that point, you can switch to sending donors the 2-click email buttons and make donating a breeze!
If you would like to use buttons that link directly to a PCP, get in touch with your @Pay account manager. Just send them your button color and the button amounts that you need, and they will send you back the button set.
Add @Pay Tutorial to emails
We recommend adding a short blurb about @Pay 2-click giving at the bottom of every email you send that has @Pay buttons. This is especially important in your first few campaigns.
Below is a sample to help you craft what will work best in your emails.
Send @Pay Introductory Email
Some organizations send an email to their donors, introducing them to @Pay. This provides an opportunity to explain the donation experience for both first-time and recurring donors. If your organization uses text-to-give, you can also explain that process in this email. However, there is the danger of sending too many emails, so each organization should decide what is best for their donor base.
The @Pay Giving Portal makes accepting web donations easy!
Review the “Giving Portal Settings” and “Manage Campaigns” guides below for help setting up your donation forms. The giving portal is fully optimized for desktop, tablet, and smartphone displays, making it a great tool for connecting with donors in a variety of ways.
Giving Portal Settings
The Giving Portal comes out of the box with several defaults enabled, but everything is easily customizable.
The default title is “Giving Portal.” This is not a required field, so you can choose to leave it blank or change it to something else.
Some title suggestions are “Give to [Organization Name] Today!” or “Thank you for giving!”
This appears just below the Title, in white text. It is not required, but provides a space to tell the donor details about this particular campaign or mission statement. This field is limited to 255 characters.
In the description you can enter more text about this specific campaign, put in html code to create a banner graphic, or just leave it blank. When using a banner, consider leaving the Title and Header blank above it, to keep the giving portal from becoming cluttered.
You have the option to add designations to the Giving Portal. Designations give donors the chance specify what fund they want their donation to contribute to. They can also be used to allow donors to express their reason for giving.
Enter the options you want to give donors and separate the options by a comma to create a new element in the drop down list.
Tithe, Offering, Building Fund
General Needs, Southern Branch, Eastern Branch
The donor is not required to choose a designation in order to donate.
Designation List Name
You may choose to use the designation drop down list for something other than choosing the specific fund. For example, if you create a campaign for ticket sales, this field could be used to select the entree type. Or if you mail out t-shirts to your donors, it could be used for collecting t-shirt sizes.
Rename the field in the Designation List Name to whatever will make sense to donors.
What is your t-shirt size?
Choose your entree
Optional Custom Fields
If there is additional information that you need to collect, you can create custom fields. Optional custom fields DO NOT have to be completed by the donor for them to submit their donation.
If you would like to make more than one custom field, simply separate the fields with a comma. The comma indicates that a new field should be created.
For example, if you set the Optional Custom Fields up like this in the dashboard:
It will look like this on the giving portal:
Required Custom Fields
Required fields have the same set up as optional custom fields, but they required the donor to fill out the field before the donation can be submitted. An asterisk will appear next to the field name to indicate that it is required.
Only use required custom fields when absolutely necessary. You don’t want to create any friction in the donating process.
The advanced settings allow customization of the color scheme used in the giving portal. The color palette below highlights how changes in the settings affect the giving portal display.
The background color can be replaced by an image. With the correct image, this can really make the donation page pop.
It is generally best to avoid images that have a central focus in the middle of the image, because that is where the form is placed.
Don’t be afraid to go through a bit of trial and error to find the correct background image. Upload the image and then view the giving portal to see how it looks. Make sure to view the giving portal on a variety of screen sizes (smartphone, tablet, computer, external computer monitors).
You have the option to enable Google reCAPTCHA. CAPTCHA provides an extra layer of protection to protect your giving portal from spam and abuse. Unlike other CAPTCHA methods that require donors to type in values based on a distorted picture, this method is just a simple click.
If you enable reCAPTCHA on your giving portal, it will be displayed at the bottom of the form, just above the Submit button.
If you enable the email opt-in, a check box will display on the giving portal, allowing donors the option of whether they want to receive future email communications from your organization.
The check box defaults to checked. It is grouped with the opt-in for saving payment information for future transactions.
The giving portal comes with 4 customizable buttons (the defaults are $10, $25, $50, and $100) as well as an Other button.
Enter in the dollar amounts you decide on into the Amount fields to set the gift options.
Tip: Donors tend to donate the mid-range amount, so don’t be shy about setting a high amount as one of the options.
To add descriptions to the donation amounts (e.g. number of meals that amount provides or number of families helped), enter the text into the description field for each button.
Button descriptions don’t work in every scenario, but they can be a great way to help donors make a personal connection to their contribution, and encourage their generosity.
Decrease button options
Buttons can be easily removed from the giving portal. Leaving the Amount and Description fields blank will automatically remove the button from the donation form.
If you don’t want to provide an Other button, just select the check box to Disable Other Button.
The flexibility to remove buttons is helpful when creating a campaign for ticket sales or membership which require a set of specific amounts.
Giving Portal URL
The URL associated with your giving portal is displayed at the top of the Giving Portal Settings page.
Copy this link and then begin to socialize it!
Navigate to Manage Campaigns on the @Pay dashboard to see all of the Giving Portals that have been created. The first Giving Portal in the list is the default. Edit this either from the dashboard menu option Giving Portal Settings or by clicking the Edit link on the right side of the list.
The default giving portal can be used for your general giving needs. However, sometimes you need to set custom amounts or change the messaging for specific campaigns. To accomplish this without changing your default giving portal, create a new giving portal campaign.
Select Add Campaign to create a new version.
When you add a new campaign, all of the fields will be pre-populated to mirror the default giving portal. Customize the fields for this particular campaign and then hit Update.
After you have saved the new giving portal, it will appear in the campaign list, so you can manage it in the future.
The URL associated with your campaign giving portal can be viewed after the campaign has been created.
In the table that displays all the campaigns created for your organization, there is a column called Slug. This is the unique identifier that is appended to your default Giving Portal URL to create a new URL. You can view the full url at the top of the settings page if you hit Edit for a specific campaign. Selecting View will also open up the campaign in a new window, and you can see the URL in the address bar.
The slug is configured based on the Title given to the campaign when the campaign is first created. We do not allow you to change the slug after it is set (changing the title of the campaign after it has been saved the first time will have no affect on the slug).
If you made a mistake on the title and want to update the slug, we recommend that you simply create a new campaign. If this option doesn’t work for you, then contact your account representative and they can put in a ticket to have the slug changed.
Beta: QuickPay Mobile Web Giving
@Pay is excited to release the beta version of QuickPay mobile web giving. This beta release adds 2-click giving to mobile web and also features a simplified design on both mobile and desktop.
The old version of the @Pay giving pages are still available for use. If you would like to begin using the beta version, then you will need to change the url that you direct your donors to. The URL for both version of the giving page are at the top of the campaign settings page in the dashboard.
Since the new features are only in beta, we will be fine-tuning the donor experience and design over the coming months. We welcome any feedback you may have. Email us at firstname.lastname@example.org with any questions or comments.
What are the new features?
- QuickPay for Mobile Web – If the giving page is opened on a mobile device, the donor can give in just 2-clicks using SMTP authentication.
- Simplified Design – If the giving page is opened on a computer, the donor will check out by entering their payment information using a streamlined form.
- Pass on the fees – Organizations have the option to pass credit card processing fees onto the donor.
How do I use the new giving pages?
To use the new giving portal, you will simply need to direct your donors to the new URL that @Pay has provided. Depending on how your organization socializes your giving page, you should take some or all of the steps below.
- Update your website’s donation link to direct to the new giving page.
- All future Facebook, Twitter, and other social media fundraising posts should reference the new URL.
- If your donation page has been widely circulated you should consider creating a redirect so that anyone clicking on a link to your old giving page will be automatically redirected to the new page. Please contact your @Pay account representative or email email@example.com if you would like to set up a redirect.
Refer to the giving portal settings section of the help center for information about how to configure giving pages. The settings for the beta giving portal are the same as the old version, with one exception. The simplified design has led to fewer color settings. Only the Background Color and Primary Color will affect the new design.
The back ground color of the page behind the payment form. The primary color affects the color of the buttons and the payment form headings.
QuickPay Mobile Web
If the giving page is opened on a mobile device, we have made the checkout process as simple as possible. The donor simply needs to complete these 4 steps:
- Chose the amount they want to give
- Click the @Pay button that is generated, which opens a confirmation email.
- Press send on the confirmation email
- Check their email for a receipt. If the donor does not have a payment method on file, @Pay will send them an email with a link to a payment capture page, enabling the donor to enter in their credit card and complete the donation.
Custom Fields and Designations
Although mobile web donating has been streamlined, it still enables donors to enter in custom field data and designations. After the donation amount is selected, the custom fields appear below the 2-click button.
If there are required fields, the donor will not be able to push the 2-click button unless it is filled out.
Donors that do not want to use the QuickPay option, can press the link on the page that says “Use payment form instead of quickpay.” Selecting this option will direct the donor to a payment capture for them to enter their credit card information.
New Desktop Design
Although QuickPay isn’t available when the giving page is opened on a computer, the form has been simplified to make it easy to fill out.
Pass on Processing Fees to Donors
If your organization would like to pass credit card processing fees onto donors, contact your @Pay account representative or email us at firstname.lastname@example.org and we can turn this feature on. This feature is only available on the new giving pages. It is not currently available on the old version.
The Giving Widget is a small version of the @Pay giving page that is contained within an iframe. The iframe can be added directly onto your website. So, instead of adding a Donate button that redirects the donor to the giving portal (which is hosted by @Pay) the widget can be displayed on your homepage.
Here is an example of the giving widget on a university foundation’s homepage.
The giving widget is great for organizations that have already invested a lot of time and resources into building a website. Not only does the widget allow donors to stay on your website, it also ensures that the call to action has lots of visibility.
How to implement the Giving Widget
Every giving campaign created in the Web Giving section of the dashboard automatically generates the HTML for a widget that is available for use. The code can be found at the bottom of the settings page for any campaign.
Here is an example of the full HTML:
<iframe src=’https://dashboard.atpay.com/giving_portal/widget/org_ZFuPr5tCTZs23aDqWnd2Hg/giving_portal’ scrolling=’no’ frameBorder=’0′ width=’281′ height=’306′>Browser not supported</iframe>
Your webmaster can simply copy and paste the HTML into your website and then arrange on the page wherever it you want.
If you want to preview what the widget looks like within the iframe, copy the URL contained within the HTML and paste it into a browser.
Since the widget is a simplified version of the complete giving page, it only pulls from certain settings from the campaign. The color scheme is set based on the color of the Header Color. If you have included a background image in the campaign, it will not be included in the widget (you website becomes the background image).
Designations and Custom Fields will be included in section 2 of the widget.
Since the widget is not a full sized giving page, you are limited to 3 fields in step 2 of the donation process. If you aren’t using designations or recurring giving, this could be 3 custom fields. If you are using both designations and recurring giving, then you are limited to 1 custom field.
Web Giving Use Cases
On your website
When people come to your website, they need an easy way to give. A link on the homepage leading donors directly to the giving portal is a great way to accomplish that. The link should be eye-catching and clear so that donors don’t have to spend a lot of time searching for it.
Tweets and Facebook posts can include a link to the giving portal. The link will give your supporters an easy way to contribute.
In most uses cases, text-to-give is set up with a dynamic trigger. This means that donors can text in any amount that they want to give. However, sometimes donations need to be pre-set amounts (e.g. membership drives, ticket sales). This can be accomplished by using a trigger word to initiate the text-to-give experience. When creating a text campaign based off a trigger word rather than a dynamic donation amount, the giving portal is a great resource.
An example setup works like this:
- Supporter texts the trigger word, such as “Membership” to the text-to-give number.
- @Pay sends a response text message with a link to a campaign specific giving portal.
- The supporter clicks on the link to bring up the giving portal on their smartphone, selects their membership level option (e.g. bronze supporter $50, silver supporter $75, gold supporter $100), and then completes the payment process.
There is nothing built into the @Pay dashboard relating to text giving, because there isn’t that much that needs to be configured. Everything is ready to go when you sign up!
However, throughout 2016 there will be new features released for text-to-give that will include dashboard customizations, so stay tuned!
In the mean time, if you need any help setting up your text-to-give number, just contact your @Pay account manager.
How Text Giving Works
Step 1: Text an amount to the text-to-give number (example: “10 Tithe” or any numeric value). The text response will ask the donor to confirm the gift. Click the link.
Step 2: An email will open. Verify that the “from” address is the correct email and press send. First-time donors will be directed to a payment capture page rather than a MAILTO link.
Step 3: The donation is complete! A receipt is emailed.
With a static trigger, we set up a trigger word for donors to text, rather than an amount. In this scenario, the donor cannot select their donation amount directly in the text message, so they are sent a link to a giving portal in the reply SMS.
Static triggers are great in scenarios where donors should only give a predefined amount, such as memberships and ticket sales.
Step 1: Supporter texts the trigger word, such as “Membership” to the text-to-give number. Response email includes a link to the giving portal that was set up for that trigger word.
Step 2: Supporter clicks the link, selects their donation amount (e.g. bronze supporter $50, silver supporter $75, gold supporter $100), and enters their credit card information.
Step 3: The donation is complete! A receipt is emailed.
Contact your @Pay account manager if you would like to configure static triggers.
Text Use Cases: NonProfits
There are lots of ways for nonprofits to use text-to-give in their fundraising campaigns.
Text-to-Give provides donors another option to give besides mailing in a check or credit card information.
People come to your events because they believe in your cause. However, long lines at a donation table or not enough cash in the wallet can discourage people from donating while at the event. Fliers and signs with your text-to-give number at the event can facilitate generosity.
If your event requires tickets, use @Pay’s giving portal for ticket sales, ensuring that all attendees already have a credit card on file. Then they won’t have to take out their wallet at the event!
Also consider displaying your text-to-give number at sporting events or benefit concerts.
One of today’s most effective fundraising mediums is social media. The majority of Facebook and Twitter views are from mobile devices. Add your text-to-give number to your organization’s posts to give donors and easy way to give on their phones.
Do you advertise in magazines or other print media? If so, add your text-to-give number to your ads to make a direct call to action.
If you give out T-shirts at your annual fundraising marathon, include the text-to-give number directly on them. The number can be included on all types of swag, including coffee mugs, frisbees, and tote bags.
Billboards and signs can be a great way to promote your text-to-give number. Places like bus and train stops, where people spend a lot of time waiting, eager for distractions, can provide a great opportunity for new donor acquisition.
The possibilities go on and on. We always love to hear about the different ways organizations promote their text campaign. Share your story with us at email@example.com.
Text Use Cases: Faith-Based
Churches that sign up with @Pay receive a welcome packet that includes posters and fliers that help introduce @Pay to the congregation.
We recommend that you hang posters in visible locations and either hand out fliers to members or slip them into the pews.
If your church has a display screen during services, it can also be helpful to display the text-to-give number and instructions.
Remember, text-to-give isn’t only for services! Socialize the number on social media and your website to allow your members to tithe anytime.
For more information, download these tutorials:
The Pledge Thermometer is a great way to motivate the attendees at your next event. Display it on a big screen at the event so donors can see how their generosity contributes to the goal.
The thermometer is very easy to set up. When you make your web giving campaigns you will see a section at the bottom of the settings page for the thermometer. The thermometer for that campaign will track all pledges made using that particular web donation form. Just set your goal and save the settings. Then copy and paste the url into a new browser window to view the thermometer.
The thermometer provides huge value as a tool for using text-to-give at your event. Whatever slug is associated with that campaign is also the text-to-give keyword for that campaign. For example, the keyword for the above campaign is “gala.” That means a donor texts a donation amount and the word gala to your organization’s text-to-give number, and then the thermometer will show that pledge (example: 50 gala).
The slug is determined by the title you give the campaign the first time you save it. The title can be changed later, but that will not change the slug, so make sure you know what you want the keyword to be before you save it.
- Make it one word. Multiple words will have to be combined with a dash, making it harder to text in.
- Make it simple
- Avoid acronyms. It can be tempting to use an acronym, but most phones have an autocorrect feature, which can lead to errors.
Donation vs Pledge
The thermometer is based off of a pledge, rather than a donation. Not everyone wants to get their credit card out while attending an event, but they are willing to pledge an amount and will enter their payment info later. The thermometer is designed include these pledges. So the moment a person texts in an amount, it will be included in the thermometer total even before they finish the transaction.
Recurring donations are an important feature of the @Pay platform. It allows donors to regularly contribute to the causes they care about an make budget planning much easier for your organization.
Recurring giving is enabled by default for organizations (if your organization does not have recurring giving, contact your account representative). Donors will have the option to make a donation one-time, weekly, monthly, or annual on all web giving campaign forms. Recurring options are also listed on payment capture pages that first time text and email donors are sent to. All donations default to one-time.
Options for recurring donations are not meant for every situation. For example, if you make a campaign to sell tickets to an event, it doesn’t make sense to offer the donor the option give monthly. In the Advanced Settings sections, when editing a campaign, there is a checkbox that says Enable Recurring. This checkbox is selected by default, but you can deselect it for any campaign if you don’t want the appear on the form.
We know how important data is to your organization! That is why the @Pay gives you complete and easy access to all of your donor data.
Simply navigate to the Reporting section of the dashboard and follow the instructions in this guide.
View Transactions In Dashboard
In Transaction History, you can view all of the donations made to your organization. The transaction table shows a snapshot of some of the most relevant data: date, offer name, tag (for text transactions only), donor email, donation amount, gateway used to process the payment, and whether the donation was successful.
There is also a field for Net Amount. This column will only be populated if you use the Stripe gateway. The amount displayed is the donation amount minus the gateway processing fees.
Note that if a donor doesn’t have a payment method on file during their initial donation attempt, the status of the transaction will be “Further Action Required.” If they respond to the FAR email and enter in a payment method, the transaction status does not change to Successful, instead a second transaction is registered, this time as Successful.
If you click on the Details link to the right of any donation listed in the table, more information is displayed for that particular donation.
There is a lot of data displayed in this view, but there are some key things to be aware of.
Source: This will indicate what platform the donation was made from: SMS (text), Email, or the Giving Portal.
Offer Details: If this donation was made with an email button you created, then these fields will match up with what you filled out when creating the button. Offer Details for text and web donations will be filled out with @Pay defaults for that particular method.
Resend Receipt: If the donor contacts your organization claiming they have not received a receipt or that they deleted it, click the Resend Receipt link in the top right corner of the transaction details. This will send a new copy of the email receipt to the donor.
Transaction ID: This is the unique identifier of the transaction in the @Pay database. If there are any issues with the donation, send us the transaction ID and donor email address for us to troubleshoot.
Export all Transaction Data
Export transactions from your dashboard into whatever format fits your reporting and record keeping needs.
This provides an export of all of your transaction data into a csv spreadsheet. Save-as an xlsx file once it has been exported to your computer if you prefer the functionality that xlsx spreadsheets have over csv files.
All of the data in the csv export is contained in the Transaction details viewable in the dashboard as well as some additional data. Optional fields such as Shipping Address and Custom Fields are included in this export.
The Salesforce format exports the data into a csv formatted to be uploaded directly to the Salesforce NonProfit Starter Pack import tool. You won’t have to make any changes to column headings or the order the fields are displayed!
If you use a different CRM that you would like a custom export for, contact your @Pay account manager and we can help!
Filter what transactions to display in the dashboard or that you want to export.
The top filter row displays the most commonly used filtering options. You can toggle more option to show advanced filtering options, including searching on fields specific to when the Email Button or Giving Portal was made or looking up all of the donations for a particular donor’s email address.
Only the data fitting the current search criteria will be exported out of the @Pay dashboard. If you want to export all of your data, reset the filters and then export.
View and Export your Donor List
The customer list is a table of all of your donors that have donated with @Pay and have opted to save their payment information, making them 2-click enabled.
This table can be viewed directly in the dashboard, or you can export it to a csv file. To export, click the Export link at the bottom left of the list. Once the list is opened as a csv, you can always save it as an xlsx file if you need to add formatting.
Only customers that have registered their payment method through a Payment Capture Page (PCP) will be 2-Click Enabled. Customers will receive a FAR email with a link to the PCP if they are NOT 2-Click Enabled. Email segmentation is an option that can help prevent potential abandonment during the FAR process. To prevent FAR’s from occurring, you can send new donors a link directly to the Payment Capture Page instead of the @Pay Mailto. To do this, use the exported Customer List from the Dashboard or configure a hook to update your mailing lists.
Read more about ways to use list segmentation in the Email Donating section of this help guide.
In settings, you can make updates that affect your entire @Pay platform. This includes managing access to the dashboard, setting contact info, and uploading your organization’s logo.
The Your Login section is the place to manage the email address attached to your @Pay credentials as well as your password.
In order to change your password, you must also provide your current password.
In the Manage Access section, you can see all of the users that have access to the dashboard and add new users.
To add a new user, click Add Account at the bottom of the list.
Enter in the email address and Save Settings. A confirmation email will be sent to the address.
If the user has not yet confirmed the account login, a Send link will be displayed in the right column. Clicking the link will resend the account confirmation email to them. The activation link on a confirmation email is only valid for 7 days. If more than 7 days pass, the Send link is an easy way to give the new user another activation email.
Enter your organization name. This name will be used for all of the branded messaging (receipts, confirmation emails, payment capture pages) that is sent to donors, so make it reflects exactly how you want the organization to be represented.
The best number for @Pay to contact you.
The best number for @Pay to contact you.
Minimum transaction amount
This is the minimum donation that your organization wants to accept. The default is $0.00 which means all donation amounts are accepted. However, if you have overhead costs that make accepting donations below a certain amount not worth it, then you can set that amount here. Common thresholds are $5 or $10.
If a donor enters an amount less than the minimum on one of your web donation forms, they will see an error on the form stating what the minimum donation amount is.
The mailing address for your organization. We may use this to send resources (such as posters and fliers to distribute to donors).
Messaging & Theme
This section sets the defaults for communications that @Pays sends to donors on an organization’s behalf.
These check boxes are always checked by default. Only uncheck these boxes if you are connecting to our web hooks and sending your own receipts, Further Action Required notifications, and failed transaction notifications. If you uncheck these boxes, @Pay WILL NOT send these notifications to your donors.
View our Developer Documentation for more information about our APIs and Web Hooks.
Upload your organization’s logo here. This will display at the top of your giving portal, payment capture page, receipts, and any other messaging viewable to your donors.
All of the fields in Sender Settings will be visible to your donors, so make sure you provide information that you want to be public.
Make sure to select Save Message Settings after making any changes.
Reply to Address
This is the “From” address used by @Pay when we send email on your organization’s behalf (receipts, failed transaction notifications, and further action required notifications). This email address will also appear in the contact information at the bottom of email messages and payment capture pages.
This field is REQUIRED for @Pay to function.
Service Phone Number
This phone number will appear in the contact information at the bottom of email messages and payment capture pages.
This field is not required.
This phone number will appear in the contact information at the bottom of email messages and payment capture pages.
This field is not required.
Organization/DBA Name/Reply-To Name
This name will appear in emails when referring to the organization. This name will also be a part of the “From” field in emails sent from @Pay. It defaults to the Organization Name (from the Organization Info section) but you can change it here.
This text will appear as small print at the bottom of every receipt and payment capture page. This is a great place to put any relevant tax information or other instructions you may have for your donors.
This field is not required.
Set the color scheme for receipt template that will be emailed to your donors. All changes save automatically and will be viewable in the receipt template in the dashboard.
A gateway is a service that allows you to process payments on the Visa, Mastercard, Discover, and American Express networks. With all of our standard packages, @Pay handles credit card processing for your organization. If you already have a gateway that you would like to use with @Pay, contact us and we can provide you a custom package that will allow you to integrate with over 90 different gateways.
@Pay also provides a test gateway. If you would like to test you can use test credit cards to simulate donations:
|Type||Card Number||Decline/Failed Card|
|Visa||4111 1111 1111 1111||4012 8888 8888 1881|
|MasterCard||5555 5555 5555 4444||5105 1051 0510 5100|
|Discover||6011 1111 1111 1117||6011 0009 9013 9424|
|American Express||3782 8224 6310 005||3714 4963 5398 431|
Understanding gateways can be tricky and @Pay is here to help! Contact us if you have any questions.
If you signed up through our website, you are automatically set up with an @Pay gateway account. If you signed up with a sales representative, contact them if you would like to use our gateway.
When you initially sign up for an @Pay account, the gateway account is also automatically created, but only a provisional basis. In order to begin receiving payments, we require additional information for verification purposes.
- Tax ID or Employer Identification Number – EIN
Organization Representative Details
- First and Last Name
- Date of Birth
- Last for digits of Social Security Number
If you only provide the name and date of birth for a company representative, you can begin receiving payments up to a couple thousand dollars. However, the account will be suspended if more than 2 weeks pass or more than a couple thousand dollars are collected if you have not provided the last four digits of the SSN. This SSN must match up with the name of the individual provided. Make sure the name provided is the full legal name as it appears on their social security card. If the name and SSN do not match, the verification will not process and we may have to request additional information.
Who should the organization representative be?
The organization representative can be anyone within your organization who has been given authorization to set up an account. The representative is not responsible or liable for any activity that happens on the organization’s account. So in other words, it can be anyone who works for your organization. We recommend providing the information for the individual responsible for maintaining the @Pay account or someone from your finance department.
Reporting and Deposits
If you use the @Pay gateway, there are some additional reporting features available on the @Pay dashboard. In the transaction reports, the Net column will be filled out with the donation amount minus the credit card processing fees.
There is also a separate report type called Deposits. This shows you each deposit made into your bank account and what transactions are associated with that deposit. Once a deposit shows on your deposit screen, it should show up in your bank account by the next business day. At that point the status should be updated from “in_transit” to “paid.”
Deposits are done on a two-day rolling basis. This means deposits are made daily and are composed of the donations that were processed two days prior. So, generally, you’ll see the money in your account two days after a donation is made. However, while deposits are posted every day of the week, most banks will only post deposits on business days.
Add Your Own Gateway
In addition to providing an @Pay gateway, @Pay also connects with over 90 other gateways. If your organization prefers to connect your existing gateway to your @Pay account, follow the steps below.
Note that this service is only available to organizations with a custom subscription package. All of our standard packages must use the @Pay gateway.
In the dashboard, click on Manage Gateways under the Settings tab.
This will bring you to a page that shows all of your gateway connection. Every account comes with a Test gateway, and you may also see a Stripe gateway configured if you signed up from our website.
To add your existing gateway, click Add Gateway at the bottom left of the table.
This will bring up a dropdown list where you can select the your gateway provider. If your gateway isn’t on the list, contact your account manager and they can set you up with the @Pay gateway. We can also discuss an integration with your existing gateway, but this may include some implementation costs.
Depending on which gateway you select, different credentials will appear for you to fill out. If you need help accessing these credentials, contact your gateway provider.
The requested credentials are usually some combination of username, password, API key, Merchant ID, etc. @Pay has a lot of experience working with different gateways, so if you run into any issues at this step, contact us at firstname.lastname@example.org.
Once the gateway is configured, make sure it is set up as your default gateway. Just click on the gateway and check the Default box. Click the Save Settings button, and you are done!
@Pay has a partnership with Paperless, which offers blended processing rates depending on the interchange rates. This averages out to about 1.75% + $0.22. If you would like to to sign up for this gateway, you must have an @Pay starter plan (or higher) and then go through the underwriting process with Paperless. Contact us to learn more.
Once you have an active gateway from Paperless, there are just a few steps to getting it connected to @Pay.
Navigate to Settings > Manage Gateways in the @Pay dashboard. Select Add Gateway. Click here for more info about connecting gateways to @Pay.
Select First Data e4 from the gateway type drop down list. The credentials you will need are:
To retrieve these credentials, you will need to log in to your Paperless (Payeezy) account. Navigate to the Administration tab and then select Terminals.
Select the terminal (click anywhere on the row) in the table to see the details of that terminal. In the details, you will see a field called Gateway ID, which is the first credential you need.
There is also a field for Password. If you don’t already know what the password is, then generate a new one and copy it. Then Update the page settings, otherwise the new password you generated will not be saved.
If you return to the terminal settings page, the password will be hidden with asterisks. If you did not copy the password when it was first generated, you will need to generate a new one. However, be aware that this will affect any other accounts that you have connected to this gateway.
Enter the credentials into the @Pay gateway setup page and select Add Gateway.
@Pay 2-Click Enabled – A donor is 2-Click Enabled if they have registered their card with an organization to make payments. Any transaction request that is made with an @Pay Button or @Pay Mailto by a 2-Click Enabled donor will automatically process through the gateway.
@Pay 2-Click Button – A mobile and platform optimized HTML button that is placed into an email campaign or mobile webpage. These link to an @Pay Mailto or directly to a payment capture page. @Pay 2-Click Buttons are generally created and available when an offer is generated.
@Pay Mailto – A mail-to link that contains specific tokenized details that are used to process a transaction when sent to the @Pay platform.
@Pay Offer – An offer can be generated manually from the Organization Dashboard or dynamically using one of our SDK’s. Transactions are processed against offers. An offer can be tied to an @Pay 2-Click Button, a Payment Capture Page, or even a QR code. When an offer is created, an @Pay Mailto is generated. When configuring an Offer you can set the price, expiration date, offer details, and a variety of additional options. A list of created Offers can be seen from within your Organization Dashboard.
Gateway – @Pay connects with a variety of different gateways or payment processors. Every organization is provided with a “Test” gateway for development purposes. Gateways are added in the Organization Dashboard. An offer can be tied to a specific gateway when being created. If a specific gateway is not selected, the default gateway will be used.
FAR (Further Action Required) – If a customer submits a transaction and @Pay needs further details, the transaction will be marked as FAR. By default @Pay will send an email specifying what is required. A customer will receive a FAR message if they are attempting to make a payment with your organization for the first time. On rare occasions, a FAR will also be generated to authenticate the transaction if certain security checks aren’t met.
CAPTCHA – Stands for “Completely Automated Public Turing Test to Tell Computers and Humans Apart.” Enabling CAPTCHA on web forms provides an extra layer of security to protect your donation forms from spam and attacks. It validates that the form is filled by a person rather than a bot.