How to set up Koalect for OM P2P Integration

Activation requirements and current limitations

To enable the automatic creation of OM P2P campaigns from Koalect projects, RaiseNow might need to activate the project creation notification from Koalect to the backend.

Please also note that the transfer of the beneficiary’s reference into the payment data is not yet supported. This means that even if a benefiting_reference is set on the beneficiary, it will not automatically appear in the payment (donation) sent to OM. This feature is planned but currently not available.

From Koalect project to OM P2P campaign

To create a P2P campaign in OM, a campaigner first creates a project under a specific Koalect campaign. In OM, each P2P campaign is a segment under a defined OM campaign, so Koalect must supply the necessary OM campaign reference when the project is created.

There are two possible ways to provide this campaign reference in Koalect:

1. Inherited from the beneficiary: The Koalect campaign may inherit an OM campaign reference from the associated beneficiary via the benefiting_reference field (labelled Reference in the UI).

2. Set via the project creation form: Alternatively, the OM campaign reference can be defined explicitly in the project creation form using the external_reference field (labelled Main Reference in the UI).

When the project is created, its unique project_id in Koalect will be used to generate a corresponding segment in OM under the given OM campaign. This forms the OM P2P campaign structure.

From Koalect project contribution to OM P2P Donation

When a donor makes a contribution to a Koalect project, this payment must be recorded in OM as a donation, linked to the P2P campaign that was previously created.

To achieve this, Koalect must again provide the relevant OM campaign and segment references. These are determined in the following way:

1. Inherited from the beneficiary: The same benefiting_reference may be used if it was already set on the beneficiary level.
2. Set via the contribution form: The project contribution form should include the same main reference (campaign_id) that was used when the project was created. This ensures the donation is properly linked to the correct OM segment.

Fallback values

To ensure data integrity and continuous delivery to OM, fallback mechanisms are in place:

1. If no OM campaign reference is set on the Beneficiary or in the project creation/contribution forms, the backend will apply a predefined fallback campaign reference (fallback-p2p-campaign-number).
2. If the segment (P2P campaign) could not be created in OM or is invalid, the system will always deliver the donation using a customer-configured generic OM campaign and segment via fallback-campaign-number and fallback-campaign-segment-id.

This guarantees that every donation reaches OM, even if the initial linkage fails.

Field mapping & resolution order

The following table outlines the order in which campaign and segment references are resolved during project creation and contribution processing

Project Creation → OM P2P Campaign

Priority	Source	Field Label	API Field	OM Field
1	Beneficiary	Reference	benefiting_reference	OM Campaign
2	Project Form	Main Reference	external_reference	OM Campaign
3	Backend	Final Fallback	fallback-p2p-campaign-number	OM Campaign

Project Contribution → OM Donation

Priority	Source	Field Label	API Field	OM Field
1	Beneficiary	Reference	benefiting_reference	OM Campaign & Segment
2	Contribution Form	Main Reference	campaign_id	OM Campaign & Segment
3	Backend	Fallback	fallback-p2p-campaign-number	OM Campaign & Segment
4	Backend	Final Fallback	fallback-campaign-number, fallback-campaign-segment-id	OM Campaign & Segment