Using the Paysafe gateway, we can currently process donations from Visa, MasterCard, American Express or Discover credit cards.
Paysafe can also process UK Direct Debits as long as you bank with Barclays. Read this help article for the setup of PDDs with Paysafe.
In addition to supporting USD, CAD, EUR, GBP and AUD, Paysafe can support these currencies: https://developer.paysafe.com/en/rest-apis/reference-information/iso-country-and-currency-codes/currency-codes subject to your arrangements with Paysafe.
We strongly recommend that you explicitly confirm the payment methods and currencies available to you with Paysafe.
The currency is selected when you set up the gateway with Paysafe – it is not necessary to include a currency form field in your default supporter record, or on your donation pages. It is possible to take single and recurring payments through the same page by including the 'Recurring payment' field as a dropdown, radio button, or check box.
Before creating donation pages using the Paysafe gateway you will need to have arranged your merchant account with Paysafe. You will also need to decide what base URL you would like to use for your donation pages, and ensure that a certificate exists for it on our load balancer.
We currently have a certificate set up for the ‘wildcard’ domain ‘*.netdonor.net’. This means that you can use any value you like for the first part of the base URL, as long as it is followed by ‘.netdonor.net’, with no further DNS changes required. For example, if your organization were called ‘UK Charity’, you could choose the base URL ‘ukcharity.netdonor.net’. Your donation pages would then have URLs beginning ‘https://ukcharity.netdonor.net/…’.
If you would prefer to use a different base URL, eg. ‘donate.ukcharity.org.uk’, a security certificate will need to be set up on our load balancer for the relevant domain. Please contact us if you would like to do this.
It is recommended that you create and keep two separate gateway records in your account, one for testing and one linked to your live gateway. Donation pages should be linked to a test gateway initially, and then switched to a live gateway before launch. To create each one:
|
Field |
Description |
|
Reference name |
A unique name for the gateway. It is a good idea for the name to include the type of gateway (eg. Optimal Payments Live), the currency, and whether it is a live or test gateway. |
|
Select gateway |
Select the Optimal Payments gateway |
|
Username |
Your Paysafe account user name. |
|
API key |
Paysafe will provide this, along with your Account ID. |
|
Account ID |
See above. |
|
Currency |
Select the appropriate currency for the gateway, subject to what you have agreed with Paysafe. Note that changing this field in Engaging Networks will only change how currency is reported in our platform. The actual currency of donations is determined by the currency of your Paysafe account. |
|
Test mode |
Should be checked for a test gateway, but must be unchecked for a gateway that will accept live donations. |
The following fields should be set up in the default supporter record with the appropriate field ‘tag’ and added to your donation form.
|
Form Field |
Mandatory/optional |
Value type |
Comments |
|
Email Address |
Mandatory |
Alphanumeric |
Supporter’s email address |
|
First Name |
Mandatory
|
Alpha |
The cardholder’s first name. |
|
Last Name |
Mandatory |
Alpha |
The cardholder’s last name.
|
|
Address 1 |
Mandatory
|
Alphanumeric |
The first address line of the cardholder |
|
City |
Mandatory
|
Alpha |
The address city of the cardholder |
|
Region |
Mandatory
|
Alpha |
The address region of the cardholder. For the US and Canada, this should be a 2 character code for the state/province. For other countries, it is a free text field. |
|
ZIP/postal code/postcode |
Mandatory
|
Alphanumeric |
The post/postal/zip code of the cardholder |
|
Country |
Mandatory |
Alpha |
The country of the cardholder. This should be a 2 character code for the country. |
|
Donation Amount |
Mandatory
|
Numeric |
May be entered as a whole number, or with two decimal places. Eg. Twelve dollars may be entered as ‘12’ or ’12.00’. You may want to consider using the ‘select with input’ or ‘radio with input’ field types – see below. |
For credit card payments you will also need the following:
|
Form Field |
Mandatory/optional |
Value type |
Comments |
|
Credit Card Number |
Mandatory |
Integer |
Credit card number w/o spaces |
|
Credit Card Expiration |
Mandatory |
Date |
Format must be MM/YYYY. It is strongly recommended that you use the ‘split select’ field type for this form field. See below for details. |
For ACH/EFT payments you will also need the following:
|
Form Field |
Mandatory/optional |
Value type |
Comments |
|
Payment Type |
Mandatory |
Alpha |
ACH |
|
Bank Account Type |
Mandatory |
Alpha |
Checking or Savings |
|
Bank Account Number |
Mandatory |
Numeric |
The account number for the payment. |
|
Bank Routing Number |
Mandatory |
Numeric |
The routing number for the payment. Must be 9-digits. |
Additional Required Fields for Recurring Payments
If you want to accept recurring payments and have confirmed with Paysafe that you have this option enabled for your account, in addition to the credit card fields you will need to add the following:
|
Form Field |
Value |
Description |
|
Recurring Payment |
Alpha |
Submitting ‘Y’ will flag the transaction as a recurring payment. Any other value will result in a single payment. |
|
Recurring Frequency |
Alpha |
Permitted values are MONTHLY, QUARTERLY, SEMI_ANNUAL and ANNUAL. Please see the notes below on ‘select’ field types for details of ways of presenting these fields to supporters. |
|
Recurring Day |
Numeric |
The day of the month on which the recurring payment should be taken, from 1-28. |
© Engaging Networks | Company registered in England and Wales | Company number: 03848111