Skip to content
In the marketplace today

Crowdfunding

Funding campaigns run end to end.

From small raises to large real-estate offerings: campaigns, investor onboarding, regulated fund flows through PSP wallets, and a portal where investors see what they hold.

A crowdfunding campaign open in the panel.
30,000+
Investors at delivery, on the Dutch rails
2
Live markets
0
Card checkouts in the money flow

Campaigns, end to end

A fundraising project moves from draft through review to a live marketplace listing, carrying the full offering record.

  • Create, review and publish fundraising projects
  • A marketplace list of live campaigns
  • Campaign detail: description, financials, location, media, specifications
  • Category and quick-scan assessment steps
The campaign marketplace.

Onboarding before money moves

A new investor walks a task chain where each step unlocks the next — and nothing moves until the chain is green.

  • Complete the profile, accept the legal documents
  • Identity verification: KYC for people, KYB for businesses
  • Suitability questionnaires in the flow
  • Open a wallet, verify it, connect an IBAN
  • Tasks close themselves from provider webhooks
The investor onboarding checklist.

Regulated money, not a card form

Investments flow through wallets at a regulated payment institution, via the PSP provider modules — the shape these offerings legally need.

  • Investor wallets with balance and history
  • Deposits, withdrawals and direct-debit mandates
  • Payouts from campaign proceeds through the provider's settlement flow
  • Works with whichever PSP provider the tenant has licensed
An investor's wallet view.

The investor's own portal

Investors see what they hold without asking anyone.

  • A dashboard and portfolio view
  • Holdings per campaign, positions and prices
  • Self-service re-verification when compliance requires it
The investor portfolio.

Worth knowing: Any real fund flow needs a configured PSP provider module underneath — the module never moves money over a plain card checkout.

What every module inherits.

  • Installs from the marketplace with no redeploy — the menu and the permission list update immediately.
  • Creates its own tables, in its own schema, inside that customer's database.
  • Packages are cryptographically signed when they are built, and the signature is checked before the host unpacks one.
  • Uninstall switches a module off and keeps its data. Dropping the tables is a separate, deliberate choice.

Want to see Crowdfunding running?

Thirty minutes, a live workspace, and an honest answer about what each module does and doesn't do yet. Missing a module? A custom build is a fixed-scope project, from €25.000.

Book a call