New here? This page is a configuration reference for teams implementing the Fundraise Up integration in iPaaS.com. It documents scope, design decisions, and settings to confirm before go-live. These are not product defects, and most items are handled during implementation by iPaaS.com or your Managed Integration Service Provider (MiSP). See Understanding Integration Scope & Known Limitations for how we document this for every integration.
This document describes the known limitations of the iPaaS.com integration with Fundraise Up, as they stood at the time this documentation was written. They are inherent to the current integration design and to the capabilities of the Fundraise Up API, and they apply to all subscribers using this integration.
For each limitation we explain what it is, why it exists, and what it means for you.
Platform Scope and Tested Versions
Remote Platform: Fundraise Up
API: the Fundraise Up API at https://api.fundraiseup.com/v1, the same address for live and test data
API Version: Fundraise Up API v1. Fundraise Up does not publish separate version numbers within v1; it lists its changes in the "Changes in API" section of its API documentation. The integration was built and tested against the unversioned production endpoints as of 2026-11-12.
Test Date: 2026-11-12 and 2026-11-13 (integration version 1.0.3), in Fundraise Up test mode.
Not built for: writing to Fundraise Up, or reading Fundraise Up campaigns, designation setup, fundraisers, subaccount management or Donor Portal links. The integration reads donations, the supporters who made them, their recurring plans and Fundraise Up's event log, for the one account and mode its API key and Livemode setting select. It is not built for any other donation platform. If Fundraise Up releases a new API version in the future, this integration does not support it automatically.
1. Data flows from Fundraise Up to iPaaS.com only
What: The integration only reads data from Fundraise Up into iPaaS.com. It does not create, update or delete anything in Fundraise Up.
Why: Fundraise Up is the system of record for donations. One-way capture keeps it clear which system owns each donation. The integration declares no FROM iPaaS.com data flow, so the iPaaS.com portal offers no collection that sends records to Fundraise Up.
What this means for you:
Create and change donations in Fundraise Up (its dashboard or campaign forms).
A change made in Fundraise Up, such as a refund, reaches iPaaS.com by the Fundraise Up webhook or on a later poll (see "Changes after a donation is created arrive by webhook or poll" below).
If you need two-way synchronization, discuss the design with your MiSP; it needs a different integration topology.
2. The Fundraise Up webhook is created by hand in Fundraise Up
What: Fundraise Up can notify iPaaS.com of donation and recurring plan events as they happen; a delivery usually reaches iPaaS.com within seconds. At the time this documentation was written, Fundraise Up offered no way for iPaaS.com to create the webhook, so you create it in the Fundraise Up dashboard, once for each iPaaS.com subscription (see Fundraise Up Installation Instructions). Once it exists, the integration fully supports it, and nothing needs to be turned on in iPaaS.com.
Why: Fundraise Up manages webhooks only in its dashboard (Settings > Webhooks); its API has no webhook endpoints. For each delivery, the integration reads the donation again from Fundraise Up, so what reaches iPaaS.com is always Fundraise Up's current record.
What this means for you:
The integration handles each Fundraise Up event as follows:
Donation created is accepted and does nothing; the donation enters iPaaS.com with its next event (for example Donation successful) or on the next poll. Ticking it does no harm.
Every other donation event (for example Donation successful, Donation updated or a refund) updates the same iPaaS.com Transaction.
Every recurring plan event sends the plan's latest donation again, so its Transaction carries the plan's current details.
Tribute, supporter and other events are accepted and do nothing.
The webhook's address carries your subscription's Webhook API Key, and that key is what iPaaS.com checks. A delivery with a wrong or missing key is refused and nothing runs. Treat the webhook address like a password.
Fundraise Up states that it switches a webhook off automatically when its endpoint goes 48 hours without a successful delivery, for example because the key in the address is wrong. Donations then arrive only on the poll until you fix the address and switch the webhook back on in Fundraise Up.
Fundraise Up states that it may deliver the same event more than once and does not guarantee the order. Each delivery reads the donation again and updates the Transaction already linked to it, so a repeat does not create a second Transaction.
Fundraise Up signs each delivery with its own signing secret. iPaaS.com does not check that signature, so you don't need to keep the secret.
There is no "test webhook" action on the iPaaS.com side. Fundraise Up sends webhooks for test-mode donations, so a test donation is the simplest way to check your webhook.
3. The poll runs on a schedule you create, and continues from the last donation it read
What: The poll is the backstop for the webhook and the only path when no webhook is set up. Subscribing creates no poll schedule: you create a Webhook Poll Request event yourself with the scope transaction/poll and a cron schedule (for example 0 0/15 * * * ? for every 15 minutes). The poll keeps its position as the last donation it read, not as a time, and each run continues from there.
Why: A position based on the last donation read never misses or repeats a donation, while a time window can miss donations created during a slow poll. The Donation Poll Days setting is read only on the first poll, when the subscription has no saved position yet.
What this means for you:
Without a poll event, nothing arrives by poll and nothing reports an error. The poll keeps working when the webhook is off.
No collection offers Initialize Data. History comes only from the first poll, which brings the donations created within Donation Poll Days (every donation when it is 0 or blank). A negative or non-numeric value stops the first poll with FUUP-VALD-1004; once a position is saved, the setting has no further effect. See Fundraise Up Connections and Settings for recommended values.
The poll does not send again a new donation the webhook already brought. A new donation the webhook missed is still sent.
The poll saves its position as soon as it has read the list of new donations, before it transfers them. A donation whose transfer fails is not read again by a later poll unless it changes in Fundraise Up. Fix the cause, then re-send the donation from Dashboard / Integration Monitoring / Error Logs or with a Manual Sync of its Donation ID.
When more than 100 donations arrive between two polls, the poll reads them all in the same run, 100 at a time.
With the webhook on, the poll can run less often (for example once a day); without it, new donations appear in iPaaS.com on the poll schedule, not in real time.
4. Changes after a donation is created arrive by webhook or poll
What: Refunds, status changes, edits and recurring plan changes made in Fundraise Up after a donation was created reach iPaaS.com by the webhook within seconds, and each poll also reads Fundraise Up's event log for them. The changed donation is sent again and updates its existing Transaction. A recurring plan change (for example paused, canceled or reactivated) sends the plan's latest donation again, which then carries the plan's current status and dates.
Why: The donation poll reads each donation once, when it is new. The event log is Fundraise Up's record of what happened afterwards, so the poll still catches a change when the webhook is off or missed a delivery.
What this means for you:
The re-sent donation updates the existing iPaaS.com Transaction (the Donation collection is Add/Update). Downstream collections see an update, not a new record.
The poll sends every change again, even one the webhook already brought, so a refund is never lost. The repeat writes the same values to the same Transaction; a subscription that sends Transactions on may receive that update once more.
The poll keeps its own position in the event log. Its first run starts from the newest event and does not replay older history.
The poll finds a plan's latest donation among the newest 500 donations. A plan whose latest donation is older than that is skipped until its next installment arrives. When the change comes by webhook instead, the error FUUP-NFND-1001 appears: re-send the plan's latest donation with a Manual Sync of its Donation ID (it starts with D), then dismiss the error.
If the API key cannot read Fundraise Up Events, new donations still transfer and one error, FUUP-AUTH-1003, appears in Dashboard / Integration Monitoring / Error Logs. Only the changes the poll reads from the event log are affected. In Fundraise Up, give the key Read permission on Events in the same mode (Live or Test) as Livemode, then dismiss the error; it is not removed automatically. Re-sending the error first confirms the fix: its text then says the key can read Events again. The next poll reads the changes made while the permission was missing, from where it last read Events. If it had never read Events, re-send the donations changed in that time with a Manual Sync of their Donation IDs.
Nothing on the Transaction marks a dispute. Check disputes in Fundraise Up.
5. Supporter data is sent with the donor's first donation
What: A supporter is transferred to iPaaS.com as a Customer as part of a donation transfer, while the supporter is not yet linked to an iPaaS.com Customer: in practice, with the donor's first donation. The integration reads the supporter's own current record from Fundraise Up, not the copy on the donation. Later donations link to the existing Customer and do not send it again, and supporter events from the Fundraise Up webhook do nothing.
Why: Sending the supporter on every donation would change downstream records (for example a donor's name in a donor database) without anyone deciding it should.
What this means for you:
Editing a supporter's name, email, phone or address in Fundraise Up does not reach iPaaS.com on its own, even when the supporter donates again. To bring the change across, run a Manual Sync of the supporter by its Fundraise Up supporter ID (it starts with S). You can also update the iPaaS.com Customer directly.
A donation from a new email creates an iPaaS.com Customer; later donations from the same email link to the same Customer.
6. Matching and duplicates are handled automatically, with no Collision Handling Method
What: None of the integration's collections offers a Collision Handling Method setting. Duplicates are prevented instead by the links iPaaS.com keeps between each Fundraise Up record and its iPaaS.com record, and by two automatic rules:
Customers match by email. iPaaS.com keeps Customer emails unique, so a supporter's email matches at most one Customer. When that Customer exists but is not yet linked (for example a Customer another system created), the integration links it instead of creating a new one. The Customer keeps its Customer Number, Company, Comment and its addresses; the supporter's first and last name are written to it, and the integration adds one address of its own.
A lost link is restored by Transaction Number. The default template maps the Fundraise Up donation ID to the Transaction's Transaction Number. When a donation is not linked yet and one Transaction already has its donation ID as the Transaction Number, the integration links the donation to that Transaction, with its Payment and lines, and updates it instead of adding a second one. Keep the Transaction Number mapping as shipped: the integration always looks the Transaction up by the donation ID.
Why: A donation and its supporter are always linked through iPaaS.com's own link records, which is how later updates find them. The two rules above cover the cases where no link exists yet.
What this means for you:
Do not look for a Collision Handling Method on these collections; there is nothing to set.
If two Transactions have the same donation ID as their Transaction Number, the transfer stops with FUUP-BIZL-1001. Remove or renumber the duplicates in iPaaS.com, then re-send the donation.
7. Supporter Address and Payment data come from the parent records
What: Supporter Address and Donation Payment have no records of their own in Fundraise Up. The integration takes them from the parent supporter and donation.
Why: Fundraise Up returns a supporter's address as part of the supporter record, and a donation's payment as part of the donation record.
What this means for you:
A supporter has at most one address in Fundraise Up, so the integration writes at most one Customer Address for it. If Fundraise Up has no address for the supporter, no Customer Address is written and nothing is reported as an error. If it has one, the Customer Address is written even when some of its fields are empty.
A donation has at most one payment. Its external ID is the payment ID the payment processor reports; when one charge paid several donations (see "Multi-designation checkouts produce separate Transactions" below), the donation ID is added in front so each Payment has its own ID. A donation with no payment produces no Transaction Payment and no error.
8. Recurring donations are captured as individual installment Transactions
What: Each installment of a recurring donation becomes its own iPaaS.com Transaction. There is no separate recurring plan record in iPaaS.com.
Why: Fundraise Up records each installment as its own donation. The plan's details are read from Fundraise Up each time an installment is transferred and carried on that Transaction.
What this means for you:
To group installments by plan, filter iPaaS.com Transactions by the Recurring Plan Id custom field. It is empty for one-time donations.
The default template writes the plan's status, frequency, installment number and dates to Transaction custom fields. The plan's amount, currency and cancellation reason are available to map from the source fields LiveRecurringPlanAmount, LiveRecurringPlanCurrency and LiveRecurringPlanCancellationReason.
When a plan changes without a new installment (for example it is paused or canceled), its latest installment is sent again with the new values (see "Changes after a donation is created arrive by webhook or poll" above).
Systems that create a recurring schedule downstream may need more than Fundraise Up provides. Some donor databases require a stored payment token for a recurring gift, and Fundraise Up's API does not provide one. Check with your MiSP before relying on recurring schedules downstream.
9. Livemode is set once for the life of a subscription
What: The Livemode setting selects whether the integration reads Fundraise Up's live data (True) or test data (False). It is a True/False setting, and iPaaS.com refuses any other value when you save the subscription.
Why: A subscription's poll positions and its links between Fundraise Up records and iPaaS.com records are built from the mode it has been reading. Changing the mode on a subscription that has already transferred donations would mix records from two separate sets of Fundraise Up data under one subscription. Fundraise Up lets a single API key hold permissions for both live and test data, so the key alone does not prevent this.
What this means for you:
Set Livemode at install (True for production, False for testing) and leave it unchanged for the life of the subscription.
Before the first transfer, make sure Livemode matches the mode the API key was created in (Live or Test). If they don't match, the subscription still connects, but each donation stops with FUUP-VALD-1006, which names the Livemode value to set. A key that reads both Live and Test data also reaches donations made in the other mode, such as test donations on a live subscription; each stops with FUUP-VALD-1006 to dismiss, so give a production subscription a key with Read on Live data only.
Use a separate iPaaS.com subscription for each mode: one with Livemode True for live donations and one with Livemode False for test donations.
If test and live Transactions share downstream systems, consider a mapping on the test subscription that marks its Transactions (for example a custom field set to Test), so downstream systems can filter them out.
If you think you need to change Livemode on an existing subscription, consult your MiSP first.
10. Refunds are reflected on the original Transaction
What: When a donation is refunded in Fundraise Up, the integration updates the existing iPaaS.com Transaction and its Transaction Payment to Refunded, and writes the refund date to the Transaction custom field Refunded At. No separate offsetting Transaction is created.
Why: Fundraise Up records a refund as a status change on the original donation, not as a separate donation. The integration reflects that shape in iPaaS.com.
What this means for you:
Downstream systems that treat a Transaction status of Refunded as the refund work without extra setup.
If your accounting workflow needs a separate offsetting Transaction, ask your MiSP to add a downstream step that creates it when a Transaction's status changes to Refunded. You can also submit a feature request through your iPaaS.com partner channel.
11. Donations are represented as a Transaction with a Payment and one or two lines
What: Every Fundraise Up donation becomes one iPaaS.com Transaction with at most one Transaction Payment (none when the donation has no payment) and a designation Transaction Line, whatever the donation's status. When the donor covered the processing fee and Surcharge As Line Item is on, the Transaction also gets a second line for the fee (see "A processing fee the donor covers can arrive as its own line" below). Every line carries the custom field Line Type: Donation on the designation line and Fee on the fee line.
Why: A Fundraise Up donation has at most one payment and at most one designation. The designation line carries the designation and campaign details as line custom fields, so you can report on donations by fund or program at the line level.
What this means for you:
The Payment's status follows the donation: succeeded becomes Completed, refunded becomes Refunded, failed becomes Failed, and any other status becomes Pending. A system that receives payments from iPaaS.com should treat only Completed payments as money received.
A donation with no designation still gets one designation line for its amount.
Downstream systems that create one record per line should read Line Type to tell the gift from the fee.
12. Multi-designation checkouts produce separate Transactions
What: Fundraise Up's Multiple designations feature lets a donor split one Campaign Page checkout across up to 5 designations. Fundraise Up creates a separate donation for each designation, and all of them share a Grouped Donation ID. The integration reflects that shape: a checkout split across 3 designations produces 3 iPaaS.com Transactions, each with its own Payment and designation line.
Why: Fundraise Up does not return one donation with several designations; it returns one donation per designation, paid by one charge.
What this means for you:
If your reporting needs to roll the Transactions back up to one checkout (for receipts or acknowledgements), use the grouped_donation_id line custom field the default Designation collection writes. To have it on the Transaction itself, add a mapping on the Donation collection from the source field GroupedDonationId.
If you don't use Multiple designations, every donation produces one Transaction with one designation line.
13. Country codes arrive lowercase
What: Fundraise Up provides country values as lowercase two-letter codes (for example us, ca, gb), and the integration writes them to the iPaaS.com Customer Address Country field as they are.
Why: This is how Fundraise Up records country values on supporters and donations.
What this means for you:
If a downstream system expects uppercase codes or full country names, replace the Country mapping on the Supporter Address collection with a Lookup Translation that converts the codes, or normalize the value in the downstream system.
14. Unmapped Field Overwrite Risk
What: When the integration updates an iPaaS.com record, iPaaS.com replaces the whole record. Fields that the default template does not map are cleared on every update, even if another system wrote them. The fields at risk are:
Transaction: DiscountAmount, TaxAmount, ShippingAmount, Subtotal, TransactionUpdatedDateTime
Transaction Payment: MethodInfo
Customer Address: FirstName, LastName, Company, Address3, IsPrimaryBilling, IsPrimaryShipping, Type
Why: Fundraise Up is the source of truth for the data it sends, and the template maps what Fundraise Up provides. The Supporter collection already keeps an existing Customer's Customer Number, Company and Comment with formulas of this kind.
What this means for you: If another system writes any of these fields on records this integration also updates, add a Dynamic Formula mapping for the field that keeps the existing value, using the DestinationValue function. For example, to keep the Transaction's tax amount, map TaxAmount from:
return DestinationValue != null ? DestinationValue.TaxAmount : null;
Repeat for each field you need to keep.
15. Fundraise Up allows 3 requests at a time per account
What: Fundraise Up limits each account to 3 API requests in parallel, across all endpoints and all API keys of the account, live and test together. Further requests are refused with HTTP 429 and the code concurrent_requests_limit_exceeded. Since June 2025 the limit counts the requests in progress at the same time, not requests per second or per minute. Parent accounts and subaccounts are counted separately. Source: Fundraise Up API documentation, Rate limits and its "Changes in API" entry for June 2025.
Why: This is Fundraise Up's published API policy.
What this means for you:
Set the subscription's Concurrent Connections to 1 (recommended) or 2, never higher. With higher values, Fundraise Up refuses some requests as too many at once; those transfers appear in Dashboard / Integration Monitoring / Error Logs with FUUP-EXTN-1005 and are retried. Concurrent Connections is an iPaaS.com setting on every subscription, so check its value after you subscribe.
The API Throttle Limit and API Throttle Seconds settings limit the request rate, not the number of requests in flight, so they do not prevent this limit.
If several iPaaS.com subscriptions read the same Fundraise Up account (for example one in live mode and one in test mode), keep the total of their Concurrent Connections at 3 or less.
When Fundraise Up refuses a request for this reason, the transfer is retried automatically after about 60 seconds, with the code FUUP-EXTN-1005.
16. Use one subscription per Fundraise Up account and mode in each iPaaS.com company
What: If two subscriptions in the same iPaaS.com company read the same Fundraise Up account in the same mode, both transfer every donation.
Why: Each subscription keeps its own poll position and its own links between Fundraise Up records and iPaaS.com records, so neither knows that the other has already transferred a donation. The second transfer does not add a duplicate: a donation that a subscription has not linked yet is matched to the iPaaS.com Transaction whose Transaction Number is the donation's ID, and that Transaction, its Payment and its lines are updated and linked. Each donation is still read and written twice, which doubles the requests to Fundraise Up and runs any iPaaS.com flows that react to a Transaction update twice.
What this means for you:
Keep one Fundraise Up subscription per Fundraise Up account and mode in each company. A live-mode and a test-mode subscription on the same account do not affect each other.
If you need a second subscription on the same account and mode for a while, give it no poll event and point no Fundraise Up webhook at it.
Two subscriptions on one Fundraise Up account share its limit of 3 requests at a time, so keep the total of their Concurrent Connections at 3 or less (see section 15).
17. A processing fee the donor covers can arrive as its own line
What: Fundraise Up lets donors add the processing fee to their gift. The Surcharge As Line Item setting decides how that fee reaches iPaaS.com.
Why: Some downstream systems need the gift and the fee apart (for example to post the fee to a different account), while others want one line for the whole charge.
What this means for you:
Yes: the designation line is the gift before the fee, and a second line carries the fee. The Transaction total and Payment stay at the amount charged, so the lines, total and Payment agree.
No: the donation is one designation line for the gross amount charged.
Any other value stops each transfer with FUUP-VALD-1002. iPaaS.com does not save a blank value (the previous value stays). A subscription created before the setting existed has no value, which reads as off.
Before you turn it on, create an iPaaS.com Product for the fee and set its SKU on the Add/Update Fundraise Up Surcharge TO iPaaS.com collection (see "Placeholder Values to Replace Before Go-Live" below). On a subscription created before the setting existed, also add that collection and its filter first, and add the filter to the Designation collection; the Fundraise Up Version 1.0.3 Upgrade Guide lists the steps.
Turning it off later: a donation already transferred with a fee line keeps that split when it is sent again (for example after a refund). Donations first transferred after the change arrive as one line.
The fee is always available on the Transaction custom field Donor Covered Fee, whatever the setting.
18. Donation question answers are reachable only through the GetQuestionAnswer function
What: The answers donors give to Fundraise Up checkout questions are not mapped by the default template and have no ready-made field. The only way to bring an answer into iPaaS.com is a Dynamic Formula mapping that calls the GetQuestionAnswer function with the question's code.
Why: Each organization defines its own questions in Fundraise Up, so the template can't know which questions exist or where their answers belong.
What this means for you:
Add one Dynamic Formula mapping on the Donation collection for each question you need, writing to a Transaction custom field. See Fundraise Up Mapping Functions for the arguments and an example.
19. Template changes are not applied to existing subscriptions
What: A subscription keeps the mapping collections it was created with. When the integration's default template gains new mappings, collections or translation rows, existing subscriptions do not receive them automatically.
Why: This is how iPaaS.com templates work for every integration: a subscriber's collections may have been customized, so iPaaS.com never overwrites them.
What this means for you:
If your subscription was created on an earlier version, add each new item by hand when you want it. Nothing is required to keep working on the current version. The Fundraise Up Version 1.0.3 Upgrade Guide lists the additions and the steps.
20. Downstream integrations may refuse data Fundraise Up accepts
What: Fundraise Up does not validate donor phone numbers, so a phone number is carried to the iPaaS.com Customer as the donor entered it. A downstream integration may refuse it: Blackbaud Raiser's Edge NXT refuses an invalid phone number, so that donor's gift does not reach Raiser's Edge NXT until the Customer's phone number is fixed. The Raiser's Edge NXT gift collection also takes only lines whose Line Type is Donation (a fee line never becomes a gift) and reads the Fundraise Up custom fields (consent, tribute, recurring plan, Donor Covered Fee, Refunded At, Donor Comment) by name.
Why: Each integration validates the data its own platform requires; this integration carries Fundraise Up's data as Fundraise Up provides it.
What this means for you:
When a downstream transfer fails on a donor's data, correct the Customer in iPaaS.com (or the supporter in Fundraise Up, then re-send it with a Manual Sync), then re-send the downstream transfer.
If your subscription was created on an earlier version, add the newer Donation mappings and Line Type mappings (see the "Template changes" limitation above), or gifts reach Raiser's Edge NXT with those fields empty.
21. Default mappings to review before go-live
The default template includes a few values that work as shipped but should be reviewed against your reporting conventions. Subscribers or their MiSP should decide on each one during onboarding.
What this means for you: review each default below before your first live transfer, and keep it or change it to suit your reporting.
Add/Update Fundraise Up Donation TO iPaaS.com
Donation Type (Static)
Donation Email Address (Dynamic Formula, anonymous-donation fallback)
Donation Total (Field)
Add/Update Fundraise Up Payment TO iPaaS.com (child of the Donation collection)
Payment Amount (Dynamic Formula)
Payment Method (Lookup Translation)
Add/Update Fundraise Up Designation TO iPaaS.com (child of the Donation collection)
Designation Description (Static)
Defaults in Add/Update Fundraise Up Donation TO iPaaS.com
Donation Type (Static)
Collection: Add/Update Fundraise Up Donation TO iPaaS.com
Shipped default: Order
Why to review: every donation becomes an iPaaS.com Transaction of type Order. You may prefer a type such as Donation or Gift.
Suggested action: confirm the value matches the Transaction Type your downstream reporting expects; change it if needed.
Donation Email Address (Dynamic Formula, anonymous-donation fallback)
Collection: Add/Update Fundraise Up Donation TO iPaaS.com
Shipped default: the supporter's email, or email@email.com when the donation has no supporter email (an anonymous donation)
Why to review: an iPaaS.com Transaction needs a customer, company or email. The fallback lets anonymous donations transfer, but it is not a real address.
Suggested action: keep the fallback and route anonymous donations to a "no donor" bucket downstream, or remove it so anonymous donations stop with an error and are handled by hand.
Donation Total (Field)
Collection: Add/Update Fundraise Up Donation TO iPaaS.com
Shipped default: source field AmountInDefaultCurrency
Why to review: every Transaction is recorded in the Fundraise Up account's default currency, which gives a uniform reporting basis. Organizations that want the donor's own currency need a different source.
Suggested action: keep the default for one reporting currency, or change the source to Amount for the donor's currency.
Defaults in Add/Update Fundraise Up Payment TO iPaaS.com (child of the Donation collection)
Payment Amount (Dynamic Formula)
Collection: Add/Update Fundraise Up Payment TO iPaaS.com (child of the Donation collection)
Shipped default: the parent donation's AmountInDefaultCurrency
Why to review: the same currency choice as the Donation Total mapping above.
Suggested action: keep it consistent with the Donation Total mapping.
Payment Method (Lookup Translation)
Collection: Add/Update Fundraise Up Payment TO iPaaS.com (child of the Donation collection)
Shipped default: each of the 25 payment methods Fundraise Up publishes translates to the iPaaS.com method Other; the Fundraise Up method itself is written to the Payment's Description.
Why to review: the specific payment method is not on the Payment's Method until the translation is updated. Your iPaaS.com company needs a payment method named Other (or the methods you translate to).
Suggested action: translate each Fundraise Up method you use to the matching iPaaS.com method (for example credit_card to Credit Card) and leave rare ones at Other.
Defaults in Add/Update Fundraise Up Designation TO iPaaS.com (child of the Donation collection)
Designation Description (Static)
Collection: Add/Update Fundraise Up Designation TO iPaaS.com (child of the Donation collection)
Shipped default: Designation of the donation
Why to review: this label appears on the Transaction Line in iPaaS.com reports and on anything downstream that reads the line.
Suggested action: change it to your organization's wording (for example Donor-designated gift), or map it from the designation's name with a Dynamic Formula.
Placeholder Values to Replace Before Go-Live
The default template ships two placeholder SKUs that match no product in your company. Each must name an existing iPaaS.com Product before the first transfer; otherwise every donation with that line fails with NFND-1003 - Product Id: … does not exist or can not be found.
Where | Placeholder value | Replace with |
Add/Update Fundraise Up Designation TO iPaaS.com, Sku (Static) | REPLACE with your donation product SKU | The SKU of your donation Product in iPaaS.com (for example a general Donations product). |
Add/Update Fundraise Up Surcharge TO iPaaS.com, Sku (Static) | REPLACE with your surcharge product SKU | The SKU of an iPaaS.com Product for the donor-covered fee. Needed when Surcharge As Line Item is Yes. |
This document covers the twenty-one known limitations of the Fundraise Up integration plus the two placeholder values above. For detailed technical documentation, see the Donation and Supporter mapping documentation.
