What is a Parent/Child Dynamic in NoFrixion?

Parent and Child Merchant Structure

To make account setup faster and reduce ongoing admin, NoFrixion uses a parent and child merchant structure for certain customer setups, such as insolvency practitioners managing multiple companies.

This structure groups related merchants together while keeping each company’s accounts separate and secure.


What is a Parent Merchant?

A parent merchant acts as the main control point for users and access.

  • It represents the individual or team (for example, an insolvency practitioner)
  • Users and roles are managed once, at the parent level
  • Changes made at the parent level automatically apply to all linked child merchants

You won’t use the parent merchant for day-to-day transactions - it’s there to simplify access and administration.


What is a Child Merchant?

A child merchant represents an individual entity, such as:

  • A company in liquidation
  • A specific case or engagement

Each child merchant:

  • Has its own accounts and balances
  • Appears separately in the platform
  • Automatically inherits users and roles from the parent merchant

How This Works in Practice

When a new child merchant is created and approved:

  • It automatically appears in your merchant list
  • All users and roles from the parent merchant are copied across
  • No invitations or manual user setup are required

This means teams can access new company accounts immediately once they’re live.


Managing Users and Roles

User access is controlled at the parent merchant level.

  • Add, remove, or change a user’s role once on the parent merchant
  • The same change is automatically applied to all linked child merchants
  • A user can belong to multiple parent merchants, giving them access to multiple groups of child merchants where required

This ensures consistent access while avoiding repeated admin work.


Why We Use This Structure

The parent/child setup is designed to:

  • Speed up access to newly onboarded entities.
  • Eliminate repeated user invitations.
  • Reduce the risk of missing or inconsistent access.
  • Make managing multiple entities simpler and more scalable.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.