> For the complete documentation index, see [llms.txt](https://solutions.fundraisingbox.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://solutions.fundraisingbox.com/knowledge-base/feature-set.md).

# Feature Set

### Platform Solutions – Feature Set

The Platform Solutions follows a modular, building-block architecture.&#x20;

### **Multi-Channel Fundraising Touchpoints**

**Donation Forms**

* Real-time transfer of one-time and recurring donations, as well as contact data, from any number of FundraisingBox forms
* Integration of FundraisingBox duplicate detection, enhanced by preconfigured duplicate rules within the target system
* Synchronization of standard information (see standard mapping table), such as email opt-ins, donation receipt preferences, donation purposes, etc.
* Transfer of data from custom form fields

**Fundraising Campaigns**

* Automatic synchronization of fundraising campaigns, including all relevant campaign data and the campaign creator, as campaign records
* Incoming donations are directly linked to the corresponding campaign
* Campaigns can be managed from within the target system, e.g. adjusting fundraising goals, modifying campaign duration, or controlling publication and deactivation

**Charity Shop**

* Synchronization of individual donation products from the digital shopping cart of the charity shop connected to the donation forms, including associated donation data

**Custom Applications**

* Synchronization of data collected via organization-specific applications connected to the donation forms

**Bundled Raw Data**

* In addition to standard information, custom fields and metadata of a donation are automatically transferred as bundled JSON datasets per object
* Enables flexible, connector-independent downstream processing without requiring additional requests

**Contact/Account Data Management**

* Thanks to bidirectional synchronization, updates to contact data submitted via FundraisingBox online forms are automatically written back
* Ensures that duplicate detection continues to function reliably for future donations, helping prevent duplicate records

***

### **Payment Operations**

**Support for Multiple Payment Methods**

* Integration of various payment options, including PayPal, direct debit, credit cards, Apple Pay, Google Pay, TWINT, and others
* Payments are processed directly by the payment provider and transferred to the organization’s account, ensuring fast fund availability

**Recurring Payment Management**

* Cancellation, pausing, reactivation, and adjustments (e.g. amount or interval) of recurring donations can be managed directly within the system
* Bidirectional synchronization ensures that updates are transmitted to the original payment provider and executed accordingly

**Reconciliation**

* Automatic identification and allocation of payout batches to the organization’s account
* Mapping of individual transactions to their respective payouts
* Capture and linkage of payout data, including transaction-level and payout-level fee transparency

**Direct Debit Processing (Automated)**

* Fully automated handling of one-time and recurring direct debit donations
* Automatic generation of SEPA-compliant mandates
* Synchronization of direct debit donations and mandates for visibility and management within the system
* Ability to initiate direct debit collections directly from the system (e.g. for offline direct debits)
* Migration of existing recurring direct debit agreements to automated processing

**Manual Direct Debit Processing**

* Direct debit data can also be transferred and processed when handled manually or via third-party providers

**Bank Sync (Offline Donations)**

* Import of offline donations (e.g. bank transfers) via bank synchronization
* Donation data can be reviewed and transferred into the system with a single click

**SEPA Mandate Management**

* Structured storage of SEPA mandate information, including all relevant details
* Linking of mandates to payment instruments and associated transactions

**Error Logging and Chargeback Handling**

* Documentation of validation errors and troubleshooting information directly within the system
* Updates on failed or reversed payments, including chargeback reasons where provided by the payment provider

***

### **Customer Relationship Features**

**Donor Portal for Online Contacts**

* Donors submitting data via FundraisingBox forms gain access to a personal overview of their donations and recurring contributions
* Visibility into donation details such as amount, date, and purpose
* Ability to manage existing recurring donations
* Direct access to issued donation receipts for transparency
* Self-service updates of personal data (e.g. name, address)
* Simplified process for making additional donations with just a few clicks

**Email Communication**

* Synchronization of email communications sent via FundraisingBox (e.g. transactional thank-you emails) into the system


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://solutions.fundraisingbox.com/knowledge-base/feature-set.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
