Types of Models

Novalnet currently offers three different setups for managing operations and fund sharing between the main vendor and affiliates, based on the merchant's business use case. This section outlines the types of models available, helping merchants choose the one that best fits their operational needs.

Marketplace Model

Central platform with multiple affiliates and mixed cart support

Single Affiliate Model

One affiliate per cart/order with simplified transaction flow

Commission Based Affiliate Model

Main merchant owns products with affiliate commission structure

1. Marketplace Model

Central platform with multiple affiliates and mixed cart support

Recommended
A typical setup for platforms where the marketplace is centrally owned, and multiple affiliates (sellers) offer their products via contracts linked to the marketplace and facilitated by Novalnet. This model is iDEAL | Wero when customers can add items from multiple affiliates into one cart (Mixed Cart).

Responsibilities

  • Turnover: Belongs to the Affiliate
  • Invoicing: Liability with the Affiliate
  • Capture: Liability lies with the Affiliate
  • Refund: Liability lies with the Affiliate
  • Novalnet Costs: Can be borne by Main Merchant, Affiliate, or shared

Booking Structure

Transaction Flow Example

A reference transaction is created for the full order. For example, if a €100 cart includes:

  • Affiliate A (€40)
  • Affiliate B (€35)
  • Affiliate C (€25)

Then one main transaction (reference) is created for the marketplace, and three sub-transactions are created for each affiliate.

Bank Statement Reference

Includes the main reference transaction descriptor pointing to the marketplace. Individual descriptors (via multiple bookings) are supported upon request. However, multiple bookings may trigger multiple debits on the customer account and cause confusion with 3D Secure authentication.

2. Single-Affiliate Model

One affiliate per cart/order with simplified transaction flow

Simple
Used when only one affiliate is involved per cart/order. The marketplace offers the platform, but a single affiliate completes the sale.

Responsibilities

  • Turnover: Belongs to the Affiliate
  • Invoicing: Liability with the Affiliate
  • Capture: Liability lies with the Affiliate
  • Refund: Liability lies with the Affiliate
  • Novalnet Costs: Can be borne by Main Merchant, Affiliate, or shared

Booking Structure

Transaction Flow
  • Only one transaction is created for the affiliate
  • No reference transaction is needed
  • The affiliate assumes full turnover responsibility
Bank Statement Reference

Displays a single transaction descriptor for the affiliate. Custom descriptors can be configured depending on the acquiring setup, particularly for card-based methods like Credit Card, Apple Pay, and Google Pay.

3. Commission-Based Affiliate Model

Main merchant owns products with affiliate commission structure

Centralized
The main merchant owns the products/services. Affiliates contribute to the sale (e.g., referral, logistics, raw material supply) and receive a commission without being part of the turnover.

Responsibilities

  • Turnover: Belongs to the Main Merchant
  • Invoicing: Liability with the Main Merchant
  • Capture: Liability lies with the Main Merchant
  • Refund: Liability lies with the Main Merchant
  • Novalnet Costs: Borne by the Main Merchant

Booking Structure

Transaction Flow
  • Only one transaction is created under the main merchant
  • Affiliates are logically linked for commission
  • Affiliates do not control the transaction
Bank Statement Reference

Only the main merchant's descriptor appears. Affiliates are not shown in the transaction details visible to the customer.

Related Topics