Skip to main content

Checkout

Core concepts and available systems​

The Riseact checkout is the donation form that guides the donor through the steps needed to complete a donation: personal details, amount, payment method.

You can use the one we provide or build your own custom checkout, using our APIs.

Ways to use it​

The choice depends on where the organization's website lives.

1. Checkout URL - designed for those using the Riseact website​

For organizations that use the website built with Riseact as their main website, the checkout is already integrated. Just share the campaign URL via email, social, QR code, or from any page of the site.

https://tua-org.riseact.site/campaigns/nome-campagna/donate

Upon completion, the donor is redirected to the thank-you page: https://tua-org.riseact.site/thankyou/{token}.

2. Donation Button - for external websites​

For organizations that have their own website and want to keep the user on the page during the donation. An embedded script opens the checkout in an overlaid modal, without a redirect.

Upon completion, the modal closes. If configured, the page is redirected to a custom URL (redirectUrl) - typically a thank-you page on the organization's website. Alternatively, the checkoutCompleted event can be intercepted via postMessage to handle completion with custom code.

See Donation Button for the full documentation.

3. Custom checkout - for advanced integrations​

For those who want to build a fully custom donation form, integrated into their own site or application. The backend calls Riseact's authenticated APIs to create the donation directly; the frontend never interacts with the Riseact checkout.

Upon completion, the flow and the thank-you page are managed entirely by the organization.

→ See Build your own custom checkout.

How the Riseact checkout form works​

When a user accesses the checkout URL, for example /campaigns/nome-campagna/donate, the backend creates a checkout with a unique token and redirects to the form URL with the ?co=<token> parameter. The frontend then loads the campaign configuration from the server (for example shown/required fields, enabled payment methods, etc.), populates the fields in case of prefilling or previously entered data (the token in the URL indeed allows the checkout state to persist across a refresh or when the link is shared).

  1. User accesses /campaigns/nome-campagna/donate
  2. Backend creates a token → 302 redirect to /campaigns/nome-campagna/donate?co=<token>
  3. The form loads in four steps: amount → personal details → payment → completed

The token allows the state to be saved at each step: the data survives a refresh or sharing of the link.

Upon completion, the donor is redirected to the thank-you page: https://tua-org.riseact.site/thankyou/{token}.

Campaign configuration​

The checkout adapts to the campaign configuration: fields shown, required fields, suggested amounts, enabled payment methods. These settings are managed from the Riseact panel or through the authenticated APIs.