> 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/testing-the-data-flow.md).

# Testing the Data Flow

This section describes how to execute test scenarios to verify the data flow between FundraisingBox and the CRM system.

### **Creating Test Donations via FundraisingBox**

{% hint style="info" %}
The test donations described here use the payment method 'direct debit'. If additional payment methods are to be tested, they must be enabled for the FundraisingBox donation forms in sandbox mode. More information can be found [here](https://support.fundraisingbox.com/de/support/solutions/folders/79000086061).
{% endhint %}

**Procedure for testing a direct debit donation**

* Log in at: [https://secure.fundraisingbox.com/login](https://secure.fundraisingbox.com/login?lan=en) using your credentials. These must be requested from the account admin.
* Select the menu item 'Forms' in the left navigation bar and choose or create a donation form.&#x20;
* Open the form preview via 'Preview' and complete the form using the following sample data:
  * Payment method: SEPA direct debit
  * Test IBAN: 121212 (identifies a test donation) or alternatively use a sample IBAN (and BIC if required)
* Submit the form
* The success page will be displayed
* Verify the transaction via the 'Transactions' menu item and enable the toggle 'Show test transactions only' when using the test IBAN 121212

**Result:**\
The transaction is created in the CRM system as a 'Gift Transaction'. Changes to relevant fields (e.g., first name or last name) in the CRM system are synchronized back to FundraisingBox.

***

### **Creating a Peer-to-Peer Fundraising Campaign**

* Navigate to the menu item 'Fundraising campaigns' and, under 'Settings', select a preconfigured fundraising campaign tool
* Open the preview, select 'Create a new campaign', and complete and save the form

**Result**:

* The campaign appears immediately in FundraisingBox.
* Shortly thereafter, a corresponding Campaign is also created in the CRM system.
* The campaign creator is linked as a CampaignMember, and incoming donations through this campaign are automatically assigned.
* Changes in the CRM system are synchronized back to FundraisingBox, provided they are defined as bidirectionally syncable in the Standard Mapping table.
* Non-syncable properties (e.g., image, description) can be edited via the edit link or directly in FundraisingBox. In test mode, login is required for this.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://solutions.fundraisingbox.com/knowledge-base/testing-the-data-flow.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
