Skip to main content

Provider Method Profiles

A Provider Method Profile is where we store and manage the configuration for Payment Service Providers (PSPs) — services like Stripe, TWINT, or RaiseNow Reconciliation. These profiles allow us to customize payment processing for every RaiseNow account by setting up one or more PSP accounts and configuring how each payment method (like credit cards or SEPA Direct Debit) should work under each.

This structure gives us flexibility and control, letting us create different setups for different situations, such as a test environment vs. a live campaign, or demo setups vs. real donor flows.

What Does a Provider Method Profile Consist Of?​

A Provider Method Profile is made up of two main parts:

1. Provider Profile​

This contains the base configuration for a payment service provider (PSP) and it helps RaiseNow make a call to the payment provider securely.

Payment Profile includes:

  • The name of the provider (e.g. Stripe, TWINT, RaiseNow)
  • Whether it’s in test mode or live
  • Important credentials like:
    • API keys
    • Merchant IDs
    • Signing keys

2. Method Profile​

This defines the specific setup for a particular payment method (like SEPA Direct Debit, Credit Card, Sofort, etc.) under a Provider Profile.

Each Method Profile may include:

  • Which payment method it refers to
  • Special configuration values just for that method (e.g. a specific bank account, currency options, or region-specific rules)

So for example:

  • You may have one Provider Profile for Stripe.
  • Under it, you can have Method Profiles for:
    • Credit Card payments
    • SEPA Direct Debit
    • Sofort payments

This structure allows one provider profile to support multiple methods, each with its own behavior.

Connection Between Payments and Provider Method Profiles​

When a payment is created, it always uses:

  • A specific payment provider (e.g. TWINT, Stripe, RaiseNow)
  • A specific payment method (e.g. credit card, SEPA DD)

To make this work, RaiseNow uses the Provider Method Profile to load the correct configuration. For example, an organisation might charge a donors bank account using a direct debit payment method such as SEPA Direct Debit. For that charge, a specific creditor bank account must be defined. In this example:

  • The provider for the payment would be: raisenow_reconciliation
  • The payment method would be: sepa_dd
  • The Provider Method Profile used would be the configuration assigining the correct creditor account to the combination of payment provider and payment methods.

This ensures the correct setup is used during processing — from authentication and security, to routing the payment to the right account.