Online Donation

Prev Next

Overview

You can use the Online Donation Page in PowerWorker Engage to collect Once Off and Monthly donations from supporters through a secure online form.

The donation form can be embedded on a charity's public website, allowing supporters to enter their details and securely submit a donation. Stripe is used to process the payment details.

When a donation is successfully submitted, an Once Off donation creates a Transaction record, while a Monthly donation creates a Payment Schedule record in PowerWorker Engage.

Submit an Online Donation

Supporters can submit a donation using the Online Donation Page.

    • Visit the charity website and open the Online Donation Page.

    • Select the Donation Frequency:

      • Once Off for a single donation.

      • Monthly for an ongoing monthly donation.

    • Enter the required supporter details, including name, email, address and phone number.

    • Enter the donation amount.

    • Enter the required payment details through the secure Stripe payment component.

    • Submit the donation.

    • After a successful submission, review the confirmation containing the donation summary and relevant receipt or next-step information.

What happens in PowerWorker Enagage

When a supporter successfully submits an online donation, PowerWorker Engage creates a record based on the selected Donation Frequency.

Once Off donation

For an Once Off donation, PowerWorker Engage creates a Transaction record containing the required information, including:

  • Donor

  • Amount

  • Campaign/source

  • Payment method reference

  • Status of In Progress

Monthly donation

For a Monthly donation, PowerWorker Engage creates a Payment Schedule containing the required:

  • Donor

  • Amount

  • Frequency

  • Payment method reference

The donor does not need to select a Start Date. The Monthly donation starts from today.

Validation and mandatory details

The Online Donation Page validates required information before the donation can be submitted.

Mandatory and validated information includes:

  • First name

  • Last name

  • Email address

  • Address

  • Phone number

  • Donation amount

  • Payment details

If required information is missing or invalid, the submission is blocked and a field-level validation message is displayed.

Duplicate prevention

If the same donation submission is retried because of a refresh, timeout or double-click, PowerWorker Engage creates only one Transaction or Payment Schedule and does not process the donation twice.

Payment processing

Stripe is used to securely process payment details submitted through the Online Donation Page. Raw card data is not stored in Power Pages or Dataverse.

Donation confirmation

After a donation is successfully submitted, a confirmation is displayed containing the donation summary and relevant receipt or next-step information.

Failure handling

If Stripe tokenisation or authorisation fails, or the donation cannot be saved to Dataverse, the donation is not processed. The supporter is shown a friendly error message with a support reference, and the failure details are logged for operational review.

Administration and configuration

Administrators should confirm the payment processor configuration before the Online Donation Page is used.

  1. Navigate to Configuration area.

  2. Navigate to Payment Processors table.

  3. Create or open the Stripe Payment Processor record.

  4. Confirm the Payment Gateway Type is set to Stripe Payment Intents.

  5. Confirm the required Stripe keys are stored against the Payment Processor record.

  6. Navigate to Configuration table.

  7. Open the active Configuration record.

  8. Confirm the correct Payment Processor record is selected.

  9. Select Save.

PowerWorker Engage supports payment processing through Stripe payment gateways, and Stripe supports all currencies in the product guidance.

Security and compliance

The Online Donation Page is designed to support secure donation capture.

  • Card data is handled only by approved payment components.

  • Raw card numbers are not stored in Power Pages or Dataverse.

  • API keys and secrets are server-side only.

  • Page and API access enforce configured permissions, anti-forgery and audit logging.