Enterprise ISOs

Bring your portfolio, partners and teams together.

For an ISO with 7,500 or more merchants, changing platforms affects teams across the business. Explore PilotOS across merchant operations, channel management and branded customer access, with your entity structure, integrations and controls included in the evaluation.

The channel in detail

Manage partner branding and commercial settings.

The partner controls shown here cover branding, subdomain, login copy and commission settings. Use the demo to examine how the built-in channel tools fit your network.

PilotOS / Enterprise ISOsInside the platform
Real partner configuration controls in the Meridian demonstration tenant. Values shown are illustrative.

Branding beside commercial terms

Review partner colours, login copy and commercial settings in the product.

Check the requirements of your network

Test your required access boundaries, reporting and integrations during the evaluation.

For your ISO

Choose the platform with the teams who will use it.

Teams, entities and access

Define how your entities and teams work together, who needs access and where records must remain separate.

Branded channel management

Review built-in partner management, branded web access and native app options for staff, partners and merchants.

Integrations and rollout

Agree integration requirements, data movement, acceptance checks and support arrangements before committing to the rollout.

Enterprise evaluation

Agree what must work before you switch.

Set clear acceptance criteria with your operational and technical teams. Use them to test the product and agree the implementation responsibilities.

Read the implementation guide
  1. Document your business structure

    List your entities, portfolios, teams and channel relationships, including who owns each part of the work.

  2. Review the controls

    Check staff access, governance, data handling and provider workflows against your requirements.

  3. Test complete workflows

    Test normal work and exceptions. Agree which results must be demonstrated before cutover.

  4. Agree the rollout plan

    Set the data migration, rollout sequence, support arrangements and responsibility for each stage.

Optional finance modules

Reconcile residuals and review commissions.

Compare expected and received residuals, investigate differences and review commission amounts, splits and statuses. Add the finance capabilities your team needs alongside sales and merchant management.

The Residuals Engine is an optional add-on. Check the residual and commission features and pricing for your chosen package.

Review optional modules
Optional residual reconciliation module. Real product screen with illustrative demonstration amounts.

Frequently asked questions

Getting started with PilotOS.

Ask us about your requirements
What qualifies as enterprise?

This offering is for portfolios of 7,500 or more merchants. Your entity structure, governance, integrations and rollout requirements also determine the implementation and commercial agreement.

Can we discuss multiple entities or brands?

Yes. Show us your entities, intended brands and access requirements. We will assess them against the platform and confirm what the proposed implementation covers.

What should our technical and operational teams prepare?

Bring your systems and providers, sample data structures, staff roles, key workflows and acceptance requirements. Include the people responsible for data, operations, security and commercial decisions.

Are bespoke integrations and service levels included?

Bespoke integrations, delivery responsibilities, support and service levels are agreed commercially and documented in your agreement.

Your next step

Book a demo for your enterprise requirements.

Bring your operational and technical teams. We will cover the portfolio, channel model, integrations and controls you need to evaluate.

Chat on WhatsApp