Skip to main content

Fundraise Up to iPaaS.com Donation Mapping Documentation

How Fundraise Up Donation records are transferred to iPaaS.com as Transactions with their payment and lines, by Fundraise Up webhook within seconds, on the poll schedule you create, or by Manual Sync.

Summary

Fundraise Up Donation records are transferred to iPaaS.com as Transaction records (Add or Update), each with a Transaction Payment and a designation Transaction Line, plus a fee line when the donor covers the processing fee and the Surcharge As Line Item setting is on. Donations arrive by the Fundraise Up webhook (usually within seconds), on the poll schedule you create, or by Manual Sync. When the donor is not yet linked to an iPaaS.com Customer (in practice, with the donor's first donation), the transfer sends the Supporter first, so the Customer exists before the Transaction is written.

ID Format

Manual Sync ID Format

Enter the Fundraise Up Donation ID, the system record ID of the donation (example: DFQLCFEP). The integration reads the donation, with its payment, from Fundraise Up and sends it to iPaaS.com with its Payment and lines.

External ID Format (saved after sync)

After a successful transfer, iPaaS.com saves the Fundraise Up Donation ID as the external ID of the iPaaS.com Transaction, on a dedicated external-ID record. That link is how later transfers of the same donation find and update the same Transaction. The children are linked the same way:

  • Transaction Payment: the payment ID the payment processor reports (example: ch_3TWrpcPNSR8EaKLj01UtGPDw). When one charge paid several donations (a multi-designation checkout), the Payment's external ID is the donation ID, a pipe, then the payment ID (example: DNQQPUVD|ch_3TWrpcPNSR8EaKLj01UtGPDw), so each donation's Payment has its own ID.

  • Designation Transaction Line: the donation ID, a pipe, then the designation ID (example: DFQLCFEP|EUBZFRFW). A donation with no Designation gets the donation ID followed by a pipe and nothing after it (example: DFQLCFEP|).

  • Fee Transaction Line: the donation ID followed by :fee (example: DCXHGLRE:fee).

The default template also maps the Donation ID into the Transaction's TransactionNumber, so you can find a donation's Transaction by its Fundraise Up ID. See Duplicate or Conflicting Mappings for how that number lets the integration link a donation whose link is missing.

Deleted Record Support

Inbound Delete is not supported. Fundraise Up is the system of record for Donations, and the integration only sends data to iPaaS.com, so a donation deleted in Fundraise Up is not deleted in iPaaS.com. A refund is not a delete: it updates the original Transaction. The Status mapping sets the Transaction's status to Refunded, the Payment's status becomes Refunded, and the refund date is written to the Refunded At custom field. No separate offsetting Transaction is created. With the Fundraise Up webhook set up, the refund usually reaches iPaaS.com within seconds; without it, it arrives on the next scheduled poll. See Fundraise Up Known Limitations for details.

Custom Field Support

This mapping collection can read Fundraise Up donation custom field values and write them to iPaaS.com custom fields on the Transaction. In Fundraise Up a custom field is added to each campaign that should record it, and every donation made through that campaign carries the field's value. The default template maps no Fundraise Up custom field: add a mapping for each one you want to keep.

Configuring custom fields in Fundraise Up

A custom field is created once for the Fundraise Up account and then added to each campaign that should record it:

  1. In the Fundraise Up dashboard, go to Settings > Custom fields and click Create custom field.

  2. Enter the field's Name: the identifier used by Fundraise Up and by the iPaaS.com mapping (for example utm_partner). Under Value input, choose Text line or Predefined options. Optionally enter a Default value.

  3. To add the field to campaigns created later, tick Auto-add to new campaigns. Click Create field.

  4. For each existing campaign that should record the field, add it from the campaign's Settings tab.

Fundraise Up Create custom field form with the example name utm_partner, the Value input choice, an empty optional Default value and the Auto-add to new campaigns option.

Fundraise Up states that custom field names "can only include alphanumeric values, and no spaces", and the form asks for "a name without spaces". A name can be up to 50 characters, and a custom field can't be named Element. Fundraise Up's own examples join words with an underscore (for example member_number), and the examples in this article do the same.

Donors do not type custom field values. A donation records the value set on its donation link, for example ?utm_partner=spring-mailer (use & instead of ? if the link already has parameters), or the field's Default value. Subscribers should validate in a staging environment which value is recorded when both the Default value and the link set one before relying on it in production.

Pattern 1: Direct 1:1 Mapping (Field Type)

Typically the simpler choice when the iPaaS.com destination is a Transaction custom field that takes the value as it is. Steps:

  1. In iPaaS.com, create a custom field on the Transaction collection to map to (or use an existing custom field). The iPaaS.com custom field name does not need to match the Fundraise Up Name, though using the same name simplifies operations.

  2. In this mapping collection, add a mapping of type Field.

  3. Set the Source table to Custom, the Source field to the Name entered in Fundraise Up (for example utm_partner), and the Destination to the iPaaS.com custom field from step 1. If the source field does not yet exist in the picker, click + Add Custom Field to add it.

At transfer time, the integration finds the Fundraise Up custom field by its Name and transfers the value Fundraise Up sends for it on that donation.

Pattern 2: Dynamic Formula Mapping

Choose this pattern when a direct 1:1 mapping does not fit: for example, when you need to transform the value (change its case, strip formatting, add a prefix or suffix), combine several Fundraise Up values into one iPaaS.com field, or apply conditional logic before writing.

The integration provides the GetValueFromCustomField function, which reads a Fundraise Up custom field's value from the donation by the field's Name. On a donation, the custom fields are available to a formula as CustomFields. The simplest Pattern 2 mapping returns one custom field's value:

return GetValueFromCustomField(CustomFields, "your_field_name");

The second argument is the Name you entered when you added the custom field to the campaign in Fundraise Up. It is matched exactly, including case. See Fundraise Up Mapping Functions for the full reference.

Steps to configure:

  1. Create (or identify) an iPaaS.com Transaction custom field to receive the value. Click + Add Custom Field in the destination picker if you need to create one inline.

  2. On this mapping collection, add a mapping of type Dynamic Formula.

  3. Set the Destination to the iPaaS.com Transaction custom field from step 1.

  4. In the Source editor, enter the formula. The bare function call (above) returns the value as it is. To transform it before writing, add formula code around the call, for example:

    • Change the case: return GetValueFromCustomField(CustomFields, "campaign_code")?.ToString().ToUpper();

    • Substitute a default when blank: var v = GetValueFromCustomField(CustomFields, "donor_type")?.ToString(); return string.IsNullOrEmpty(v) ? "Individual" : v;

    • Combine fields: return GetValueFromCustomField(CustomFields, "first_initial") + "." + GetValueFromCustomField(CustomFields, "last_name");

Behavior at transfer time:

  • If the donation carries a value for the field, the function returns it as text.

  • If the donation has no field with that name, or Fundraise Up sends it with no value, the function returns an empty value (not an error) and the destination iPaaS.com field is set to empty. Use ?. before calling a method on the result, as in the examples above.

  • True and false arrive as lowercase "true" and "false". If the destination expects another form, convert it in the formula, as in the example below.

return GetValueFromCustomField(CustomFields, "your_field_name")?.ToString() == "true" ? "Yes" : "No";

Shared Behavior and Limitations

  • Custom fields are added per campaign. A custom field added to Campaign A is not automatically on Campaign B, unless it was created with Auto-add to new campaigns and Campaign B was created afterwards. If your subscription receives donations from several campaigns and you want a custom field on every donation, add that field to each campaign.

  • First match wins on duplicates. If a donation carries two custom fields with the same Name, only the first one's value transfers.

  • Donation questions are separate. The answers a donor gives to a campaign's checkout questions are not custom fields. Read them with the GetQuestionAnswer function (see Fundraise Up Mapping Functions).

Mapping Collection Status

  • Status: Enabled

  • Trigger Events: Fundraise Up webhook, scheduled poll, or Manual Sync.

Trigger

Behavior

Fundraise Up webhook

Your Fundraise Up admin creates the webhook by hand in the Fundraise Up dashboard (see the Installation Instructions); nothing needs to be turned on in iPaaS.com. Deliveries usually reach iPaaS.com within seconds. Donation created is accepted and ignored: the Transaction for a new donation is written by Donation successful. Every other donation event (for example a refund) adds or updates the donation's Transaction. Every recurring plan event sends the plan's latest donation again. Tribute, Supporter and other events are accepted and run nothing. A delivery with a wrong or missing webhook key is refused and runs nothing.

Scheduled poll

Subscribing creates no schedule: create a Webhook Poll Request event with the scope transaction/poll under iPaaS.com Dashboard / Integration Monitoring / Events. Each poll reads the donations created since the previous poll, and reads Fundraise Up's event log to send again the donations that changed (refunds, recurring plan changes). It does not send again a new donation the webhook already brought. The poll keeps working when the webhook is off, so keep it as the backstop.

Manual Sync

Available from the iPaaS.com Manual Sync page at any time, using the Fundraise Up Donation ID.

Every trigger reads the donation again from Fundraise Up before it is transferred, so the Transaction always gets the donation's current data.

Duplicate or Conflicting Mappings

This mapping transfers Donations from Fundraise Up to iPaaS.com. Fundraise Up is the system of record for Donations, and the integration sends data to iPaaS.com only: there is no mapping collection that writes Donations back to Fundraise Up.

Collision Handling

This collection and its child collections have no Collision Handling Method setting. Duplicates are prevented in these ways instead:

  • External ID link. Once a donation is transferred, its saved external ID routes every later transfer to the same Transaction, Payment and lines.

  • Automatic matching when a link is missing. When a donation has no saved link (for example after the link was removed), the integration looks for the iPaaS.com Transaction whose TransactionNumber is the donation ID. When it finds one, it links that Transaction's existing children again, then links the Transaction and updates it, rather than create a second Transaction. The children are found by their mapped fields: the Payment by its checkout_transaction_id custom field, the designation line by its designation_id custom field (only when the donation has a Designation), and the fee line by its unit price and the absence of a designation_id. Keep these mappings; without them, a re-send can add a second Payment or line.

  • The match always uses the donation ID. The integration looks for the donation ID whatever is mapped to TransactionNumber. If you map another value to TransactionNumber, a donation whose link is lost can't be matched, and a re-send adds a second Transaction.

  • Two Transactions with the same number stop the transfer. When more than one iPaaS.com Transaction has the donation ID as its TransactionNumber, the integration can't tell which one to link, and the transfer stops with FUUP-BIZL-1001. Remove or renumber the duplicates in iPaaS.com, then re-send the donation.

Unmapped Field Overwrite Risk

Warning: The iPaaS.com API uses PUT (full record replace) when updating Transaction records. The following Transaction fields are not mapped in the default template mappings for Add/Update Fundraise Up Donation TO iPaaS.com. Any existing values on the iPaaS.com Transaction will be overwritten with empty values each time an inbound transfer runs, unless additional mappings are added to keep them:

  • CompanyId

  • ParentId

  • DiscountAmount

  • TaxAmount

  • ShippingAmount

  • Subtotal

  • TransactionUpdatedDateTime

If you use any of these fields on the iPaaS.com side, keep their values during inbound updates. The recommended approach is to split this mapping collection into separate Add and Update collections, then use the DestinationValue function in the Update collection's mapping formulas to carry forward the existing iPaaS.com value for each unmapped field. For example, to keep the existing TaxAmount during an update, add a Dynamic Formula mapping with the source formula DestinationValue.TaxAmount mapped to the iPaaS.com TaxAmount field. This reads the current value from the iPaaS.com record and writes it back, so the PUT does not clear it. Repeat for each field you need to keep.

Supported Child Collections

  • Add/Update Fundraise Up Payment TO iPaaS.com (Child of Donation): Transfers the payment that produced the donation as an iPaaS.com Transaction Payment. It always runs with its parent Donation transfer, never on its own.

  • Add/Update Fundraise Up Designation TO iPaaS.com (Child of Donation): Transfers the donation's Designation as an iPaaS.com Transaction Line, with the Designation and Campaign written to line custom fields so you can report on donations by fund or program. Its filter keeps the designation line only. It always runs with its parent Donation transfer.

  • Add/Update Fundraise Up Surcharge TO iPaaS.com (Child of Donation): Transfers the processing fee the donor chose to cover as its own iPaaS.com Transaction Line, when the Surcharge As Line Item setting is on and the donor covered a fee. Its filter keeps the fee line only. It always runs with its parent Donation transfer.

Covered fees and the two line collections. Both line collections receive every line a donation yields, and their opposite filters make sure each line is written once. With a covered fee split out, the designation line holds the amount before the fee and the fee line holds the fee. Together they add up to the Transaction Total and the Payment amount, which stay at the amount charged. With the setting off, the donation has one designation line for the full amount.

System Caveats

Fundraise Up Caveats

  • Rate limit. Fundraise Up accepts at most 3 API requests at the same time per account, across all of the account's API keys, live and test. Keep the subscription's Concurrent Connections at 1 or 2. Every subscription that uses the same Fundraise Up account counts toward the same limit.

  • Position-based polling. The poll keeps its position: the last donation it read. Each poll reads only donations newer than that, page by page, until it has read them all. The first poll on a new subscription reads the donations created within the Donation Poll Days setting; no collection offers an Initialize Data step, so that first poll is the only way to bring in older donations. The position moves forward only, and it moves as soon as the poll has read the list, before the donations transfer. So a donation whose transfer failed is not read again by a later poll unless it changes in Fundraise Up: fix the cause, then re-send it from the error log or with a Manual Sync.

  • Recurring donations produce separate records. Each recurring installment is its own Fundraise Up donation and its own iPaaS.com Transaction. There is no separate Recurring Plan record in iPaaS.com. The default template writes the plan's details (id, status, frequency, installment number, start, end and next installment dates) to Transaction custom fields such as Recurring Plan Id, so you can group installments by plan in downstream systems.

  • Anonymous donations have no supporter. When a donor gives anonymously, the donation has no supporter. No Supporter is sent for that donation, and the EmailAddress mapping writes email@email.com so the Transaction still meets the iPaaS.com requirement below. See Fundraise Up Known Limitations for the keep-or-remove decision on that value.

  • Livemode and API key permissions must match. The subscription's Livemode setting decides whether the integration reads live or test data. The API key needs Read permission on Donations, Supporters, Recurring plans and Events in that mode (Live data or Test data); one key can hold both. If Livemode doesn't match the mode your API key was made in, donations don't transfer: each stops with FUUP-VALD-1006, which names the Livemode value to set. Make sure Livemode matches the key's mode before the first transfer.

  • Multi-designation checkouts produce several donations. Fundraise Up lets a donor split one checkout across up to 5 designations, and records each designation as its own donation. The integration therefore writes one iPaaS.com Transaction per designation, each with its own Payment and designation line. All the donations from one checkout share a grouped donation ID (format DGXXXXXXX), which the Designation collection writes to the line custom field grouped_donation_id, so you can roll the Transactions back up to the donor's single checkout.

iPaaS.com Caveats

  • Required API field group. iPaaS.com Transactions require at least one of customer_id, company_id or email_address. When the donor is linked to a Customer, the Transaction is linked through customer_id. Anonymous donations rely on the EmailAddress mapping's email@email.com value.

  • PUT semantics. Every transfer fully replaces the Transaction. If another integration also writes to the same Transactions, agree which side owns which field, and use DestinationValue keep-mappings (see Unmapped Field Overwrite Risk above) where needed.

  • Custom field destinations must exist. The Transaction and Transaction Line custom fields this collection writes must exist in iPaaS.com. Use + Add Custom Field in the mapping editor to add one inline.

  • Line SKUs must name existing Products. Both line collections write a Sku that must name an existing iPaaS.com Product before the first transfer (see Setup Requirements).

Setup Requirements

For full setup steps see the Installation Instructions and Connections and Settings. The integration-wide setup (the Fundraise Up API key, Livemode, the poll event and the webhook) is documented there and not repeated here.

Products for the two lines

Before the first transfer, create a donation Product and a surcharge Product in iPaaS.com (or use ones you already have), then set the Designation collection's Sku and the Surcharge collection's Sku to their SKUs. Until each names an existing Product, every donation with that line fails with the iPaaS.com error NFND-1003 - Product Id: [SKU] does not exist or can not be found.

Surcharge As Line Item setting

Set it to Yes to put a donor-covered processing fee on its own Transaction Line, or No to keep the fee inside the designation line. New subscriptions default to Yes. A subscription created before the setting existed has no value, which reads as off; iPaaS.com does not save a blank value. Any other value stops each transfer with FUUP-VALD-1002. Turning the setting off later keeps the split of a donation that already has a fee line when it is sent again.

Payment Method Other

Your iPaaS.com company must have a Payment Method named Other, or the FundraiseUp Payment Method -> iPaaS Method translation must be remapped to Payment Methods you have.

Integration Flow

When a webhook delivery arrives, the scheduled poll runs, or a Manual Sync is started, the integration processes each Donation in this order:

  1. Read the donation. For the poll, the integration reads the donations newer than its saved position, then saves the new position before any donation is transferred; it also reads Fundraise Up's event log and picks up the donations that changed since the previous poll. For a webhook delivery or a Manual Sync, the integration reads that one donation from Fundraise Up.

  2. Find the existing Transaction. If the donation is already linked, the transfer is an Update of the linked Transaction, and any child whose link was lost is found and linked again. If it is not linked, the integration looks for a Transaction whose TransactionNumber is the donation ID and links it with its children (see Collision Handling); if none is found, the transfer is an Add, and if more than one is found, it stops with FUUP-BIZL-1001. Delete is not supported.

  3. Send the Supporter first when needed. When the donation's supporter is not yet linked to an iPaaS.com Customer, the integration runs the Supporter mapping collection first, so the Customer exists before the Transaction is written. A supporter already linked is not sent again. Anonymous donations skip this step.

  4. Map the Donation fields. Each mapping in this collection builds the iPaaS.com Transaction, including any custom-field mappings you added.

  5. Map the Payment. The donation's payment goes through the Add/Update Fundraise Up Payment TO iPaaS.com child collection and becomes the Transaction Payment.

  6. Map the lines. Every donation yields a designation line, whatever its status (failed, pending and refunded donations too). When the Surcharge As Line Item setting is on and the donor covered the fee, it also yields a fee line, and the designation line holds the amount before the fee. Each line collection keeps its own line through its filter: the designation line goes through Add/Update Fundraise Up Designation TO iPaaS.com, and the fee line through Add/Update Fundraise Up Surcharge TO iPaaS.com.

  7. Send to iPaaS.com. The Transaction, linked to the Customer, with its Payment and lines, is sent to iPaaS.com as an Add or an Update.

Mappings

Add/Update Fundraise Up Donation TO iPaaS.com

iPaaS.com data type: Transaction

Description: Transfers Fundraise Up donations to iPaaS.com as Transactions. Maps the donation ID, total, quantity, status, created date and supporter email, and writes recurring plan, consent, benefit, tribute, refund, donor comment and covered-fee details to Transaction custom fields.

Mapping Filter: None. Every donation the integration reads is processed.

Field Mapping Table

Mapping Type

Source Field (Fundraise Up)

Destination Field (iPaaS.com)

Description

Dynamic Formula

SpaceportSystemId

SystemId

Required. Links the Transaction to this subscription.

Field

Id

TransactionNumber

Required. The Fundraise Up donation ID (for example DFQLCFEP), so you can find a donation's Transaction by its Fundraise Up ID. Later transfers find the Transaction through its saved external ID, not this field. Keep this mapping: when a donation's link is missing, the integration looks for the Transaction whose number is the donation ID and links it rather than create a second one, so a different value here stops a lost link being found again.

Static

"Order"

Type

Required. Sets the Transaction Type to Order.

Lookup Translation

Lookup Translation: FundraiseUp Donation Status -> iPaaS Order Status

Status

Required. Translates the Fundraise Up donation status into the iPaaS.com Transaction status. See the value table below.

Dynamic Formula

See the EmailAddress formula below.

EmailAddress

Recommended. The supporter's email. A donation with no supporter (an anonymous donation) gets email@email.com, so the Transaction still has a customer, company or email. See Fundraise Up Known Limitations for the keep-or-remove decision.

Field

AmountInDefaultCurrency

Total

Recommended. The amount charged, in the Fundraise Up account's default currency, so totals are comparable across donor currencies.

Static

1

TotalQty

Optional. Sets the Transaction's total quantity to 1.

Field

CreatedAt

TransactionCreatedDateTime

Recommended. The date and time the donation was made, for reporting.

Dynamic Formula

return RefundedAt?.ToString("o");

Refunded At (Custom Field)

Recommended. The date and time Fundraise Up refunded the donation, in ISO 8601 format. Empty until the donation is refunded. A downstream system (for example a donor database) can mark the gift as refunded from it.

Field

Comment

Donor Comment (Custom Field)

Recommended. The comment the donor wrote at checkout, as entered. Empty when there is none.

Dynamic Formula

return SupporterCoveredFeeInDefaultCurrency.HasValue && SupporterCoveredFeeInDefaultCurrency.Value > 0 ? SupporterCoveredFeeInDefaultCurrency.Value.ToString(System.Globalization.CultureInfo.InvariantCulture) : null;

Donor Covered Fee (Custom Field)

Recommended. The processing fee the donor chose to cover, in the account's default currency (for example 0.70). Empty when the donor did not cover a fee. Written whatever the Surcharge As Line Item setting, so a downstream system can record the fee even when it is not on its own line.

Dynamic Formula Documentation: EmailAddress

if(string.IsNullOrEmpty(SupporterEmail)){
    return "email@email.com";
}
return SupporterEmail;

Transaction custom fields for plan, consent, benefit and tribute details. Each is empty when the donation has no such detail. All are Recommended: a downstream system (for example Raiser's Edge NXT) reads them by name.

Mapping Type

Source Field (Fundraise Up)

Destination Field (iPaaS.com)

Description

Field

RecurringPlanId

Recurring Plan Id (Custom Field)

The recurring plan's ID. Empty for one-time donations.

Field

RecurringPlanStatus

Recurring Plan Status (Custom Field)

The plan's status when this installment was recorded (for example active, paused, canceled).

Field

RecurringPlanFrequency

Recurring Plan Frequency (Custom Field)

The plan's frequency (for example monthly, quarterly, annual).

Field

Installment

Recurring Installment (Custom Field)

The installment number of this payment within its plan.

Dynamic Formula

return RecurringPlanCreatedAt?.ToString("o");

Recurring Plan Start Date (Custom Field)

The date the plan was created (ISO 8601).

Dynamic Formula

return RecurringPlanEndedAt?.ToString("o");

Recurring Plan Ended Date (Custom Field)

The date the plan ended, if it has (ISO 8601).

Dynamic Formula

return RecurringPlanNextInstallmentAt?.ToString("o");

Recurring Next Installment Date (Custom Field)

The plan's next installment date (ISO 8601).

Dynamic Formula

return !string.IsNullOrWhiteSpace(ConsentCustomizedEmail) ? ConsentCustomizedEmail : ConsentGeneral;

Consent Email (Custom Field)

The donor's email consent: opted_in, opted_out or not_submitted.

Dynamic Formula

return ConsentCustomizedPhoneCalls;

Consent Phone (Custom Field)

The donor's phone-call consent.

Dynamic Formula

return ConsentCustomizedPostalMail;

Consent Mail (Custom Field)

The donor's postal mail consent.

Dynamic Formula

return ConsentCustomizedSms;

Consent SMS (Custom Field)

The donor's SMS consent.

Dynamic Formula

return ConsentCustomizedSocialMedia;

Consent Social (Custom Field)

The donor's social media consent.

Dynamic Formula

return BenefitState;

Benefit State (Custom Field)

Whether the donor was offered and took the thank-you gift: selected, shown_not_selected or not_shown.

Dynamic Formula

return BenefitFairMarketValue.HasValue ? BenefitFairMarketValue.Value.ToString(System.Globalization.CultureInfo.InvariantCulture) : null;

Benefit Fair Market Value (Custom Field)

The benefit's fair market value, for example 25.00.

Dynamic Formula

return BenefitFairMarketValueCurrency;

Benefit Fair Market Value Currency (Custom Field)

The currency of that value, as a lowercase ISO code.

Dynamic Formula

return BenefitName;

Benefit Name (Custom Field)

The benefit's name, for example Tote bag.

Dynamic Formula

return string.IsNullOrWhiteSpace(BenefitOptionValue) ? null : (string.IsNullOrWhiteSpace(BenefitOptionName) ? BenefitOptionValue : BenefitOptionName + ": " + BenefitOptionValue);

Benefit Option (Custom Field)

The variant the donor chose, as "name: value" (for example Size: M).

Dynamic Formula

return BenefitShipTo;

Benefit Ship To (Custom Field)

Where the benefit ships, on one line.

Dynamic Formula

return TributeType;

Tribute Type (Custom Field)

in_honor or in_memory.

Dynamic Formula

return TributeHonoree;

Tribute Honoree (Custom Field)

The person the donation honors or remembers.

Dynamic Formula

return TributeSharingFrom;

Tribute From (Custom Field)

Who the tribute is from.

Dynamic Formula

return TributeSharingMessage;

Tribute Message (Custom Field)

The donor's message for the tribute notification.

Dynamic Formula

return TributeRecipientName;

Tribute Notify Name (Custom Field)

The person to notify about the tribute.

Dynamic Formula

return TributeSharingRecipientEmail;

Tribute Notify Email (Custom Field)

Their email address.

Dynamic Formula

return TributeRecipientAddress;

Tribute Notify Address (Custom Field)

Their postal address, on one line.

Lookup Translation Table: FundraiseUp Donation Status -> iPaaS Order Status

Source Value (Fundraise Up)

Destination Value (iPaaS.com)

Notes

succeeded

Complete

The donor's payment cleared.

failed

Cancelled

The payment failed.

refunded

Refunded

The donation was refunded after a successful payment.

pending

Pending

The payment is awaiting confirmation.

retrying

Pending

A failed payment is being retried by Fundraise Up.

scheduled

Pending

A recurring installment is scheduled for a later date.

These are the six donation statuses Fundraise Up publishes at the time this documentation was written. If Fundraise Up adds a status, add a row for it to the translation collection.

Add/Update Fundraise Up Payment TO iPaaS.com (Child)

iPaaS.com data type: Transaction Payment

Description: Transfers the payment that produced each donation as an iPaaS.com Transaction Payment. It runs only with its parent Donation transfer.

Mapping Filter: None. The payment of every transferred donation is processed.

Field Mapping Table

Mapping Type

Source Field (Fundraise Up)

Destination Field (iPaaS.com)

Description

Lookup Translation

Lookup Translation: FundraiseUp Payment Method -> iPaaS Method

Method

Required. Translates the Fundraise Up payment method into the iPaaS.com Payment Method. The shipped translation maps every Fundraise Up method to Other, so your iPaaS.com company must have a Payment Method named Other, or you must remap each method to one of your own Payment Methods (for example credit_card to Credit Card). See the value table below.

Dynamic Formula

Parent.AmountInDefaultCurrency

Amount

Required. The amount charged, from the parent donation, in the account's default currency. Matches the Transaction Total.

Field

Method

Description

Optional. Writes the Fundraise Up payment method (for example credit_card, ach) to the Payment's description, so the original method stays visible while the Method maps to Other.

Dynamic Formula

See the Payment Status formula below.

Status

Required. The Payment's status follows the donation's: succeeded gives Completed, refunded gives Refunded, failed gives Failed, and pending, retrying or scheduled give Pending. It is set again each time the donation is sent, so a refund updates it. A system that receives payments from iPaaS.com should take only Completed payments as money received.

Field

Id

checkout_transaction_id (Custom Field)

Recommended. The payment ID the payment processor reports, so you can reconcile iPaaS.com records against the processor's reports. Keep this mapping: the integration also finds an existing Payment by this field when it links a donation again, and without it a re-send can create a second Payment.

Dynamic Formula Documentation: Payment Status

// The payment follows the donation: only a succeeded donation is money received.
return Parent.Status == "succeeded" ? "Completed" : Parent.Status == "refunded" ? "Refunded" : Parent.Status == "failed" ? "Failed" : "Pending";

Lookup Translation Table: FundraiseUp Payment Method -> iPaaS Method

The shipped translation covers all 25 payment methods Fundraise Up publishes at the time this documentation was written, each to Other. The raw method stays on the Payment's Description. A method Fundraise Up adds later has no row and arrives blank: add a row for it. Remap a method to one of your own Payment Methods when you need it in iPaaS.com.

Source Value (Fundraise Up)

Destination Value (iPaaS.com)

credit_card

Other

apple_pay

Other

google_pay

Other

click_to_pay

Other

ach

Other

paypal

Other

venmo

Other

becs_direct_debit

Other

bacs_direct_debit

Other

nz_becs_direct_debit

Other

pad

Other

sepa_direct_debit

Other

ideal

Other

crypto

Other

stock

Other

link

Other

twint

Other

mobile_pay

Other

swish

Other

wero

Other

revolut_pay

Other

cash_app_pay

Other

pix

Other

eps

Other

daf

Other

Add/Update Fundraise Up Designation TO iPaaS.com (Child)

iPaaS.com data type: Transaction Line

Description: Transfers the donation's Designation as a Transaction Line on the parent Transaction, with the Designation and Campaign written to line custom fields. It runs only with its parent Donation transfer.

Mapping Filter

// Keeps the designation line; the donor-covered fee line goes to the Surcharge collection.
return !IsSurcharge;

Filter Description. Each donation yields a designation line and, when its fee is split out, a fee line. This filter passes the designation line (IsSurcharge is false) and skips the fee line, which the Surcharge collection writes. Every donation produces a designation line, whatever its status. A donation with no Designation still produces one, with the donation's amount and no designation values.

Field Mapping Table

Mapping Type

Source Field (Fundraise Up)

Destination Field (iPaaS.com)

Description

Static

"Product"

Type

Required. iPaaS.com requires a Type on every Transaction Line; a donation line is a Product line.

Static

"REPLACE with your donation product SKU"

Sku

Required. Placeholder value — replace during implementation: enter the SKU of an existing iPaaS.com Product for donations (for example a generic Donation product) before the first transfer. Until you do, every donation fails with NFND-1003 - Product Id: [SKU] does not exist or can not be found.

Static

"Complete"

Status

Required. iPaaS.com requires a Status on every Transaction Line. The line is always Complete; the donation's own status is on the parent Transaction.

Static

"1"

Qty

Required. One designation line per donation, so the quantity is always 1.

Field

UnitPrice

UnitPrice

Required. The amount given to this designation, in the account's default currency. With a donor-covered fee split onto its own line, it is the amount before the fee; otherwise it is the full amount charged. Either way, the lines add up to the Transaction Total.

Field

ExtendedPrice

ExtendedPrice

Required. Qty times UnitPrice, so it equals UnitPrice.

Static

"Designation of the donation"

Description

Recommended. The line's label in iPaaS.com reports and downstream systems. Change it to match your organization's wording (for example Donor-designated gift).

Dynamic Formula

Parent.Designation.Id

designation_id (Custom Field)

Recommended. The Designation's ID in Fundraise Up (for example EUBZFRFW), the most reliable key for reporting by designation. Keep this mapping: the integration also finds an existing designation line by this field when it links a donation again.

Dynamic Formula

Parent.Designation.Code

designation_code (Custom Field)

Recommended. The Designation's code, if you set one in Fundraise Up. Empty otherwise.

Dynamic Formula

Parent.Designation.Name

designation_name (Custom Field)

Recommended. The Designation's name as donors see it (for example General designation).

Dynamic Formula

Parent.Campaign.Id

campaign_id (Custom Field)

Recommended. The Campaign's ID in Fundraise Up, so reports can slice lines by Campaign and Designation.

Dynamic Formula

Parent.Campaign.Code

campaign_code (Custom Field)

Recommended. The Campaign's code, if you set one in Fundraise Up.

Dynamic Formula

Parent.Campaign.Name

campaign_name (Custom Field)

Recommended. The Campaign's name as donors see it (for example Year-End Appeal 2026).

Dynamic Formula

Parent.GroupedDonationId

grouped_donation_id (Custom Field)

Optional. The grouped donation ID Fundraise Up gives every donation from one multi-designation checkout, so you can roll the Transactions back up to the donor's checkout. Empty for an ordinary donation.

Static

"Donation"

Line Type (Custom Field)

Recommended. Marks the designation line as Donation; the fee line carries Fee. Keep this mapping: a system that receives the gift through iPaaS.com (for example Raiser's Edge NXT) takes only lines with Line Type Donation as gifts.

Add/Update Fundraise Up Surcharge TO iPaaS.com (Child)

iPaaS.com data type: Transaction Line

Description: Transfers the processing fee the donor chose to cover as its own Transaction Line on the parent Transaction. It writes a line only when the Surcharge As Line Item setting is on and the donor covered a fee. It runs only with its parent Donation transfer.

Mapping Filter

// Keeps only the donor-covered fee line; the designation line goes to the Designation collection.
return IsSurcharge;

Filter Description. This filter passes only the fee line (IsSurcharge is true) and skips the designation line, which the Designation collection writes. A donation with no covered fee, or a subscription with the setting off, yields no fee line, so this collection writes nothing for it.

Field Mapping Table

Mapping Type

Source Field (Fundraise Up)

Destination Field (iPaaS.com)

Description

Static

"REPLACE with your surcharge product SKU"

Sku

Required. Placeholder value — replace during implementation: enter the SKU of an existing iPaaS.com Product for the fee (for example a Surcharge product) before the first transfer. Until you do, every donation with a covered fee fails with NFND-1003 - Product Id: [SKU] does not exist or can not be found.

Static

"Product"

Type

Required. iPaaS.com requires a Type on every Transaction Line; the fee line is a Product line.

Static

"Complete"

Status

Required. iPaaS.com requires a Status on every Transaction Line. The fee was charged with the donation, so the line is Complete.

Field

Quantity

Qty

Required. Always 1: one fee line per donation.

Field

UnitPrice

UnitPrice

Required. The processing fee the donor chose to cover, in the account's default currency.

Field

ExtendedPrice

ExtendedPrice

Required. Quantity times UnitPrice, so it equals the fee.

Field

Description

Description

Recommended. Donor-covered processing fee, so the line reads clearly in reports and downstream systems.

Static

"Fee"

Line Type (Custom Field)

Recommended. Marks the fee line as Fee. Keep this mapping, so a system that receives the gift can post the fee apart from the gift or skip it. A fee line never becomes a gift in Raiser's Edge NXT.

Don't add a designation_id mapping to this collection: the integration tells the fee line apart from the designation line by the absence of that field when it links a donation again.

Error Handling

Errors from this mapping collection appear in iPaaS.com Dashboard / Integration Monitoring / Error Logs. An error from a Fundraise Up call includes Fundraise Up's Request-Id: quote it when you contact your MiSP or iPaaS.com support about that error.

For the full catalog of error messages, descriptions, and resolution steps, see Fundraise Up Error Messages.

Testing & Validation

Test Scenarios

  1. Make a new donation in Fundraise Up (an individual donor with an email) and check that, after the webhook delivery or the next poll, an iPaaS.com Transaction exists with the correct TransactionNumber, Status, Total, EmailAddress and TransactionCreatedDateTime, linked to a Customer, with a Transaction Payment whose checkout_transaction_id holds the processor's payment ID.

  2. Make an anonymous donation and check that its Transaction has the email email@email.com and no Customer.

  3. Refund a succeeded donation in Fundraise Up and check that the same Transaction's status becomes Refunded, its Payment's status becomes Refunded, and Refunded At holds the refund date, with no second Transaction.

  4. Manually sync a donation by its Donation ID from the iPaaS.com Manual Sync page and check that the transfer completes, including the Payment and lines.

  5. Add a Fundraise Up custom field (for example appeal_code) to a campaign with a Default value, and map it to a Transaction custom field. Make a donation through the campaign and check that the custom field receives the value.

  6. Remap one method in the FundraiseUp Payment Method -> iPaaS Method translation (for example credit_card to Credit Card) and check that a new donation paid that way gets the remapped Method instead of Other.

  7. Make a donation to a campaign with a Designation and check that the Transaction has one designation line with Type Product, your donation Product's Sku, Status Complete, Qty 1, the donation's amount, Line Type Donation, and the designation and campaign custom fields filled in.

  8. On a campaign with multiple designations, make a checkout split across two or more designations and check that iPaaS.com receives one Transaction per designation, each with one designation line, and that every line's grouped_donation_id holds the same value.

  9. With Surcharge As Line Item set to Yes and the Surcharge Sku set to an existing Product, make a donation where the donor covers the fee. Check that the Transaction has a designation line for the amount before the fee and a fee line with Description Donor-covered processing fee, Qty 1, the fee as its unit price and Line Type Fee; that the two lines add up to the Total and the Payment amount; and that Donor Covered Fee holds the fee. Repeat with the setting at No and check for one designation line at the full amount.

  10. Remove the external ID link of a transferred Transaction, send the donation again, and check that the same Transaction and Payment are linked again, with no second Transaction or Payment. For a donation with a Designation, check that its designation line is linked again too, and for a donation with a fee line, that the fee line is.

Validation Checklist

  • The Fundraise Up API key in the subscription settings is active and has Read permission on Donations, Supporters, Recurring plans and Events in the mode the Livemode setting selects, and Livemode matches the mode the key was made in.

  • A Webhook Poll Request event with scope transaction/poll exists under Dashboard / Integration Monitoring / Events, at a frequency that suits how soon you need donations in iPaaS.com.

  • If you want donations within seconds, the Fundraise Up webhook has been created in the Fundraise Up dashboard.

  • Your iPaaS.com company has a Payment Method named Other, or the FundraiseUp Payment Method -> iPaaS Method translation has been remapped to Payment Methods you have.

  • The Designation collection's Sku and the Surcharge collection's Sku name existing iPaaS.com Products.

  • The Transaction and Transaction Line custom fields the template writes exist in iPaaS.com.

  • The defaults listed in Fundraise Up Known Limitations (including the EmailAddress fallback and the line Description) have been reviewed.

  • Every campaign that should record a particular custom field has that field added to it in Fundraise Up.

Additional Notes

Operational Notes

  • API unavailability. If Fundraise Up is unavailable when a transfer runs, the transfer fails and the error appears in Dashboard / Integration Monitoring / Error Logs. If the poll could not read the list of donations, the next poll reads the same donations again. If one donation's transfer failed, a later poll does not read it again unless it changes in Fundraise Up: re-send it from the error log or with a Manual Sync once Fundraise Up answers.

  • Refunds. A refund updates the original Transaction: its status and its Payment's status become Refunded, and the refund date goes to Refunded At. See Fundraise Up Known Limitations.

  • Existing subscriptions. Template changes are not applied to subscriptions created on an earlier version: each addition to these collections (for example the Transaction custom fields, the Line Type mappings and the Surcharge collection) is added by hand. Nothing is required to keep the integration working, but a downstream system that reads these custom fields or Line Type gets empty values until they are added. The steps are in the Fundraise Up Version 1.0.3 Upgrade Guide.

Related Documents

Related Mapping Documentation

Did this answer your question?