Event types reference
A reference for Fundraise Up REST API event types — when each event fires.
To filter events by type, use the types parameter in the Get events endpoint.
Donation events
Donation events cover the full lifecycle of a charge — from creation through success, failure, refund, or dispute.
| Event | When it fires |
|---|---|
donation.created | A donation record is created in the system. |
donation.success | A donation payment is successfully processed. |
donation.pending | A donation awaits payment processor confirmation. |
donation.failed | A donation payment attempt fails. |
donation.updated | A payment-related parameter on a donation is changed — such as the amount or payment method. Status changes do not trigger this event. |
donation.refunded | A donation is refunded. |
donation.benefit.updated | The benefit associated with a donation is updated. |
donation.personal_data_deleted | A supporter's personal data is removed from a donation record after a data deletion request. |
donation.pending_ach_verification_required | An ACH donation is pending because the supporter's bank account requires verification before the payment can proceed. |
donation.pending_incomplete | A payment is initiated but requires an additional action from the supporter before it can proceed — such as 3D Secure card verification (Stripe), PayPal authorization, or wallet verification (Gemini). An intermediate state between donation.pending and the final outcome (donation.success or donation.failed). |
donation.pending_paypal_action_required | A PayPal donation is pending because the supporter must complete an action in their PayPal account. |
donation.pending_retrying | A failed donation payment is retried. |
donation.pending_waiting_for_transfer | A donation is pending while a bank transfer completes. |
donation.pending_scheduled | A donation is scheduled for a future date and is not yet processed. |
donation.success_early_fraud_warning | The payment processor issues a fraud warning on a processed donation. |
donation.success_dispute_created | A supporter disputes a successfully processed donation (chargeback initiated). |
donation.success_dispute_won | A chargeback dispute is resolved in the organization's favor. |
donation.success_dispute_lost | A chargeback dispute is resolved in the supporter's favor. |
donation.success_dispute_in_review | A chargeback dispute is under review by the payment processor. |
Transaction attempt events
Transaction attempts are payment processing attempts tied to a donation. A single donation can generate multiple transaction attempts — for example, if an initial attempt fails and is retried.
| Event | When it fires |
|---|---|
transaction_attempt.pending | A payment attempt is submitted and awaits a response from the payment processor. |
transaction_attempt.success | A payment attempt is confirmed as successful. |
transaction_attempt.failed | A payment attempt is declined or rejected. |
Recurring plan events
Recurring plan events track changes to a plan's status, payment terms, and supporter preferences.
| Event | When it fires |
|---|---|
recurring_plan.activated | A recurring plan is created and the first installment is processed immediately. |
recurring_plan.scheduled | A recurring plan is created with a future date selected for the first installment. |
recurring_plan.failed | A recurring payment attempt fails. |
recurring_plan.completed | A recurring plan reaches its set limit — such as a total donation amount or end date — and ends. |
recurring_plan.cancelled | A recurring plan is cancelled. |
recurring_plan.paused | A recurring plan is paused. |
recurring_plan.retrying | A failed recurring payment is retried. |
recurring_plan.terms_updated | The payment terms of a recurring plan are updated. Applies to changes in installment amount, frequency, payment method, card expiration date, next donation date, end date, max plan amount, max plan installments, and cover transaction costs. |
recurring_plan.details_updated | Supporter preferences on a recurring plan are updated. Applies to changes in designation, campaign, email, phone, employer, on behalf of, anonymity, marketing consent, email receipt opt-in, custom fields, questions, comment, and tribute. |
recurring_plan.personal_data_deleted | A supporter's personal data is removed from a recurring plan record after a data deletion request. |
Tribute events
Tribute events track activity related to in-honor and in-memory donations.
| Event | When it fires |
|---|---|
tribute.created | A supporter completes a donation and enters an honoree name. This is the point of tribute creation — the honoree record exists, but no recipient has been notified yet. |
tribute.updated | Any field on an existing tribute is changed — honoree details, recipient contact information, or any other tribute data. |
tribute.shared | A tribute card or notification email send is initiated by the supporter or the organization. Fires at the moment the send process starts, not when the message is delivered. |
tribute.personal_data_deleted | A supporter's personal data is removed from a tribute record after a data deletion request. |
Supporter events
Supporter events fire when a supporter record is created, updated, or when personal data is removed from the system after a data deletion request.
| Event | When it fires |
|---|---|
supporter.created | A supporter record is created in the system. |
supporter.updated | A supporter's profile information is updated. |
supporter.personal_data_deleted | A data deletion request is submitted and the supporter's personal data is removed from the system. |