Skip to main content

Getting started

Welcome to RaiseNow Connect — a powerful integration framework that allows you, as a SaaS partner, to embed RaiseNow functionality directly into your platform.

With Connect, you can initiate onboarding flows, receive donation and subscription data, and even embed donation forms via Touchpoint solutions — all while giving your users a seamless and secure experience.

Prerequisites​

Get in touch with RaiseNow to ensure your platform is registered as a RaiseNow Connect Partner

To receive your partner onboarding configuration UUID, Client ID and Client Secret from the RaiseNow team, please provide the following information:

FieldDescription
Logo (130×48, SVG)Used in the Connect UI (horizontal layout)
Square Logo (75×75, SVG)Used in compact views or cards
Return LabelThe label for the button shown to users after onboarding (e.g. "Return to {Return Label}")
Description (DE, FR, IT, EN)Short description shown to organisations during onboarding (max 150 characters per language)
Base URLBase URL used to validate dynamic redirect URLs in the Connect flow
Self Disconnect OptionShould RaiseNow Hub allow users to disconnect on their own?
- If yes, users can self-disconnect
- If no, provide a support/disconnect URL (e.g., FAQ or contact form)

Step 1: Authenticate​

Follow our authentication guide to securely access our API with your partner credentials.

Step 2: Initiate the Onboarding Flow​

This endpoint will initiate the connect process of an organisation. In the request body you will specify all the information needed for organisation onboarding, as well as event_subscriptions so you can get notified about the organisation status and other actions that the organisation might take.

The response body will contain the url to redirect the user to. The user will continue with the onboarding process on the given url.

Rules of redirecting:​

  1. Make sure that the token is included as a URL parameter https://connect.raisenow.com?token=bff2d9d348920368c8094a2d72d3fbdb. If you’d like to redirect the user to a different URL than the configured Base URL after the connection is completed, you can do so by providing a base64 encoded URL as the redirect_url parameter. https://connect.raisenow.com?token=bff2d9d348920368c8094a2d72d3fbdb&redirect_url=aHR0cHM6Ly9odWIucmFpc2Vub3cuY29tLyMv
    1. Make sure you specify the protocol (https://) inside the encoded URL.
    2. Make sure the encoded URL has the same host as the one you provided to us when we configured your organisation as a partner.
      • If you provided https://www.some.example.com, your dynamic redirect URL has to start the same https://www.some.example.com/some/path?param=123.
      • If your base redirect URL starts with www, your dynamic URL has to start with www as well.
      • If your base redirect URL is a subdomain make sure your redirect URL is a subdomain as well.
  2. Once the user is connected, a button will be displayed that redirect them to the url you provided.
  3. If your dynamic redirect URL does not pass the validation, the user will be redirected to your base redirect URL.

Merchant Category Codes​

RaiseNow supports the following Merchant Category Codes (MCC). Please ensure that the MCC code you pass corresponds accurately to the classification of the customer’s business. Use '"0000": Other' only for non-charity organisations, as this code is specifically for entities outside the non-profit sector and may result in different pricing with our payment providers.

  • 8699: Membership Organisations (Not Elsewhere Classified)
  • 7997: Membership Clubs (Sports, Recreation, Athletic)
  • 8398: Charitable and Social Service Organisations
  • 8641: Civic and Social Associations
  • 8651: Political Organisations
  • 8661: Religious Organisations
  • 0000: Other

Events​

Based on the partner’s use case and the type of data they wish to receive via webhooks, here is an overview of the currently supported events that can be added during the onboarding call.

This ensures partners can tailor event subscriptions to meet their specific requirements effectively.

User Locale​

Based on the language of the user, RaiseNow accepts the locales:

  • fr_CH
  • en_GB
  • de_CH
  • it_CH

Step 3: Check Onboarding Status​

Once you have initiated the onboarding process you might be interested in the status of the onboarding process. The best way to get the status of the onboarding process is to subscribe to the below events.

To subscribe to the events login to Hub and go to Settings > Webhooks > Create a Webhook. Alternatively, you can subscribe to an event through our API, here is the documentation.

Possible statuses:

StatusDescription
pendingWaiting for the user to connect.
startedThe user has chosen the flow (register/connect).
failedTechnical error.
abandonedThe onboarding has expired or canceled
succeededThe onboarding has succeeded, next steps are up to the partner

Step 4: Check Organisation Status​

Once you have initiated the onboarding process you might be interested in the approval status of the organisation. The best way to get the status of an organisation is to subscribe to organisation events.

To subscribe to the events you can also add a event subscription to the POST /onboarding/processes request body. Example:

{
  "onboarding_configuration_uuid": "",
  "initialisation_data": {
    "organisation": {
      ...
    },
    "user": {
      ...
    },
    "event_subscriptions": [
      ...
      {
          "event_name": "raisenow.organisations.organisation.approval_requested",
          "endpoint": "https://myapi.com/organisation/approval/requested",
          "username": "someone",
          "password": "password",
          "hmac_key": "******"
      }
    ]
  }
}

Next steps

Once you are successfully onboarding organisations, you can continue with the integration, and provide your users with RaiseNow functionality in your own Portal:

  • Access data like transactions, payouts, and supporter info (depends on your permissions)
  • Use Touchpoints to embed donation forms natively in your product