Read more
Learn about Adyen Giving on adyen.com.
A donation campaign gives the shoppers of your users the option to donate to a nonprofit organization when they make a purchase, either online or at the point of sale. The donation is charged to the same payment method that was used for the purchase, but is processed as a separate transaction. Donations are settled directly to the nonprofit's bank account. Adyen covers all fees and the donation amount is transferred to the nonprofit in full.
As a platform, you can set up and manage donation campaigns on behalf of your users in the Customer Area. Or you can use API calls to build an integrated solution on your platform that lets users set up and manage donation campaigns themselves.
Donation campaigns for account holders
In the Customer Area, under Giving > Campaigns, you can create donation campaigns for your users and manage the lifecycle of the various campaigns. Alternatively, you can do that using Management API calls. These API calls also enable you to build an interface yourself on your platform, to let users self-serve their donation campaigns.
Regardless of how you approach it, in an Adyen for Platforms integration, donation campaigns are always created for your account holders. And regardless of the sales channel, shoppers are only asked for a donation if the shopper's region, currency, and payment method support that.
Campaign creation
A donation campaign defines how and when shoppers can donate during a transaction. To set up such a campaign, the following information is needed:
- The nonprofit organization to collect donations for.
- The account holder(s). If you set up a campaign on behalf of your users, the maximum number of participating account holders is 400.
- The channels: online payments, in-person payments, or both.
- At least one store per channel. A store can only be part of one active campaign at a time.
- Donation options. For example, fixed donation amounts to choose from, or a round-up option.
Campaign lifecycle management
When a campaign is created, it starts out as inactive. This gives a chance to edit or delete the campaign. Starting a campaign is a separate action. Once a campaign is active, it is still possible to make edits. Ending a campaign is another separate action; campaigns do not have an expiry date. Keep in mind that a campaign that was ended cannot be re-started.
When the campaign details change or the campaign transitions to a different status, those updates happen right away for online payments. For in-person payments, the terminals pick up the updates when they run their next maintenance call. This usually happens overnight.
Nonprofit organizations
For a list of pre-approved nonprofit organizations to choose from, you can consult the Nonprofit library in your Customer Area or make an API call. The list shows the United Nations Sustainable Development Goals (UN SDG), regions, and languages that the nonprofits support.
Nonprofits are only included in the list if they are compatible with the legal entity country and industry of the account holder. In the Customer Area it can happen that the list of available nonprofits changes while you add more account holders to the campaign. If you use API calls, the list in the response differs depending on the account holders specified in the request.
Nonprofits that are not yet pre-approved must go through an onboarding process. You can contact us to propose a new nonprofit, or for some regions you can do that from your Customer Area:
- In your Customer Area, go to Giving > Campaigns.
- Select Request nonprofit and follow the prompts to provide the details of the new nonprofit.
The step Select nonprofit country shows the regions where you can propose a new nonprofit in this way.
Supported regions and currencies
Giving is available in the following countries/regions and currencies.
Supported currencies may vary between nonprofits depending on where they are registered.
| Country/region | Currencies |
|---|---|
| Asia-Pacific 1 | AUD, JPY, HKD, NZD, SGD |
| Europe | CHF, CZK, DKK, EUR, HUF, ISK, NOK, PLN, RON, SEK |
| United Arab Emirates | AED |
| North America | CAD, USD |
| Mexico | MXN |
| United Kingdom | GBP |
1Fundraising in Singapore is only possible for local nonprofits.
Supported payment methods
Payment method | In-person donations | Online donations | |
|---|---|---|---|
| Two step flow | One step flow | ||
| American Express | ![]() |
![]() |
![]() |
| Apple Pay 1 | ![]() |
![]() |
![]() |
| Bancontact | ![]() |
||
| Cartes Bancaires In-person only for French non-profits. |
![]() |
![]() |
![]() |
| China UnionPay | ![]() |
![]() |
![]() |
| Diners | ![]() |
![]() |
![]() |
| Discover | ![]() |
![]() |
![]() |
| eftpos | ![]() |
![]() |
|
| girocard | ![]() |
![]() |
|
| Google Pay 1 | ![]() |
![]() |
![]() |
| iDEAL | ![]() |
||
| Interac | ![]() |
||
| JCB | ![]() |
![]() |
![]() |
| Mastercard | ![]() |
![]() |
![]() |
| Maestro | ![]() |
||
| Maestro USA | ![]() |
||
| Visa | ![]() |
![]() |
![]() |
| Visa Debit | ![]() |
![]() |
|
Supported terminals
The following table shows the payment terminal models that support Giving, and the donation options that are supported on those terminals. The payment terminals must be on software version 1.109 or later, and some terminals or features require software version 1.110 or later. A combination of Round up and Fixed amounts in the one-step flow is only available for terminals on software version 1.124 or later.
| Model | Fixed amounts | Round up | Two step | One step |
|---|---|---|---|---|
| AMS1 | ![]() |
![]() Requires 1.110 or later |
![]() |
![]() |
| P630 | ![]() |
![]() |
![]() |
![]() |
| e280 | ![]() |
![]() |
![]() |
![]() |
| e285p | ![]() |
![]() |
![]() |
![]() |
| M400 | ![]() |
![]() |
![]() |
![]() |
| M450 Requires 1.110 or later |
![]() |
![]() |
![]() |
![]() |
| P400 Plus | ![]() |
![]() |
![]() |
![]() |
| S1E | ![]() |
![]() Requires 1.110 or later |
![]() |
![]() |
| S1E2L | ![]() |
![]() Requires 1.110 or later |
![]() |
![]() |
| S1F2 | ![]() |
![]() Requires 1.110 or later |
![]() |
![]() |
| S1U2 | ![]() |
![]() Requires 1.110 or later |
![]() |
![]() |
| SFO1 Requires 1.110 or later |
![]() |
![]() Requires 1.110 or later |
![]() |
![]() Requires 1.125 or later |
| V240m Plus | ![]() |
![]() |
![]() |
![]() |
| V400c Plus | ![]() |
![]() |
![]() |
![]() |
| V400m | ![]() |
![]() |
![]() |
![]() |
