Multi-Tenant Payment Architecture: How to Isolate Every Tenant on One Payment Platform

  • Home
  • Blog
  • Multi-Tenant Payment Architecture

Multi-Tenant Payment Architecture: How to Isolate Every Tenant on One Payment Platform

Table of Contents

A multi-tenant payment architecture lets one software platform process payments for many businesses, its tenants, through a single integration, while each tenant's merchants, customers, bank accounts, fees and data stay isolated from every other tenant. On TIB Finance, multi-tenancy is not a feature added on top: it is the data model. Your organization is the client, each tenant is a service created with one API call, each bank account is a merchant, and the server itself enforces the walls between tenants.

TIB Finance is a sovereign Canadian payment processor, headquartered in Montreal and founded in 2018, built for B2B and multi-tenant payment processing. Businesses build their own platform on top of TIB, with their own clients and sub-merchants, and a real, human, bilingual team supports every client and every partner. TIB serves more than 1,000 businesses, processes over $600 million a year and handles 200,000+ transactions every month.

Here, the platform is you. A tenant is one of your clients, such as a property manager, a lender or a franchise. A merchant is a tenant's bank account and the name its payers see. Customers pay your tenants.

In short: one TIB client (you) holds many services (your tenants). Each service has its own merchants, customers, payment methods, fee grid and limits. A merchant session only sees its own merchant, the server refuses administration calls from it, idempotency keys are scoped per login, and every transaction webhook carries the MerchantId and MerchantName. TIB keeps the tenants apart.

Building a multi-tenant platform? Talk to our team, or try the free sandbox.

What is a multi-tenant payment architecture?

Any platform that collects or pays out money for its clients faces the same three questions. Where does each tenant's money land? Who can see which data? How is every payment, fee and event traced back to the right tenant? A multi-tenant payment architecture answers all three in the payment layer itself, so your application does not have to rebuild the walls in its own code.

A platform can bolt sub-accounts onto a system designed for one merchant and rely on its own code to keep them apart, or build on a processor whose data model is multi-tenant from the first record. TIB Finance is the second kind. Weighing becoming a payment facilitator instead? Read our guide to the PayFac alternative in Canada, or see multi-tenant payment processing for B2B platforms for the business view.

How does TIB Finance model each tenant?

Every entity on TIB sits in one hierarchy: client, then service, then merchant, then customer, then payment method. Bills, payments and transfers are attached to a merchant, and each merchant has its own destination bank account.

Client: your platform
Service: Tenant AService: Tenant BService: Tenant C
Merchant: bank account 1Merchant: bank account 2
Customers and payment methods
  • Your organization is the TIB client. You connect once and keep the view across every tenant.
  • Each tenant is a service. One CreateSubClient call creates it with its own name, its own language and its own currency, CAD or USD, and returns the new ServiceId. That ServiceId then replaces yours in every call made for that tenant.
  • Each bank account or unit is a merchant. CreateMerchant adds it, with the MerchantName that payers see on bills and payment pages, plus an ExternalSystemId that ties it to its record in your own ERP or CRM and an ExternalSystemGroupId that groups related merchants.
  • Each payer is a customer under that tenant, never shared with another tenant.

Each sub-client gets its own isolated environment, with dedicated merchants, customers and payment methods. When a tenant needs onboarding, CreateSubClient also returns a BoardingRedirectUrl, and GetServiceBoardingStatus shows where every merchant of a service stands.

How does the server keep tenants apart?

Isolation that lives only in your code is one bug away from a leak. On TIB, the walls are enforced server-side, in the session itself.

Scoped sessions

CreateSession opens a client-level session. GetLoginAccessList lists a login's accesses at client, service or merchant level, and Login opens a session at the chosen level.

MerchantId forced by the server

In a merchant session, the server sets MerchantId to the session's merchant, whatever value is sent. A tenant cannot read or act on another tenant's data.

Administration refused

A merchant session cannot create merchants or sub-clients, add bank accounts, delete merchants, or read service settings and onboarding status. CreateSubClient is refused in a service session too.

Read-only access and 2FA

An access can be read-only, and its session inherits that. Repeated failed logins lock the account, and two-factor authentication is added at protected operations.

The practice is one session per tenant, never shared between tenants. The official SDKs support the same two-step login for merchant-level and service-level users. The developer documentation covers every call.

Can each tenant have its own fees, limits and payment methods?

Yes. Each service carries its own fee grid and its own rules, and your platform reads them back through GetService. That is where your business model lives.

  • Fees per tenant: credit card, debit and instant transfer, each with a mode, a percentage and a fixed amount; convenience and cancellation fees; Interac deposit and collection fees; NSF, card failure, stop payment and Interac return fees.
  • Limits per tenant: collection and deposit limits per operation and per day, limits per bank account, an NSF cushion and a merchant deposit delay.
  • Payment methods per tenant: the list of methods allowed for collection and for deposit, and the option to block free deposits and supplier payments.
  • Your own revenue: a platform can charge its own fee on payments, and the fees of a service can be billed to a specific merchant.

A high-volume lender and a five-unit landlord can share your platform with completely different economics.

How are funds and reporting separated by tenant?

Money follows the hierarchy. Each merchant has its own destination bank account, so a payment created under one tenant's merchant settles to that bank account and nowhere else. Reporting follows the same lines: ListExecutedOperations filters by ServiceId, by MerchantId (forced in a merchant session), by transfer group and by date type, and every operation carries its MerchantId.

Two more safeguards matter at platform scale:

  • Idempotency per login. Idempotency keys are scoped to the login that sends them and are honored on 12 operations, including CreatePayment, CreateTransferBatch, CreateCustomerV2 and RevertTransfer.
  • Batches with approval. CreateTransferBatch handles up to 5,000 operations per call, and transfers can require dual approval. GetPendingTransferApprovals returns nothing for a service that is not yours.

Reporting and reconciliation are built in: see our guide to automated payment reconciliation and managing high-volume payments.

How do webhooks tell you which tenant an event belongs to?

Every TransactionEvent webhook says where it belongs. Its payload includes the Target (Client or Merchant), the Direction (Collect or Deposit), the Step (Validation, Transmission, StatusCheck or Payback), the Status, a DescriptionCode, the Amount, and the MerchantId and MerchantName. Your platform routes each event to the right tenant straight from the payload.

You give your webhook URL to your TIB representative, and webhooks come from a published IP range that you can allow-list. The full field reference is in the official webhook documentation.

How do tenants take payments inside your product?

Your tenants' customers pay without leaving your product. The Drop-In secure payment form accepts cards and bank payments in your app without your platform handling sensitive data. It loads in an iframe with a single-use token, which keeps your platform out of PCI scope, and TIB Finance itself is PCI DSS Level 1 certified.

Payment pages can carry your colors and logo: your brand, our infrastructure. Payers choose Interac, EFT or credit cards, in English or French. Instant payments move in seconds, 24/7/365, through TIB's own instant payment system. See instant payouts for platforms in Canada and how long payments take in Canada.

How does TIB compare with Zum Rails and VoPay for multi-tenant platforms?

Zum Rails and VoPay both serve platforms, and both do it seriously. Zum Rails gives partners a portal to onboard clients, manage compliance and track payments, with DocuSign built in (Zum Rails partner portal). VoPay gives developers a broad API, with "over 250 endpoints" and "300+ partners" (VoPay home page), and a Partner API for ISOs, ISVs and PayFacs (VoPay Partner API). Sources verified November 22, 2026. The difference is depth. On TIB, the tenant is the data model, and the isolation, the economics and the routing all hang off it.

TopicTIB FinanceZum RailsVoPay
Tenant onboardingOne CreateSubClient call per tenant, with onboarding by APIThe partner adds customers in the partner portal, under Customers, then Add new (knowledge base)New accounts are onboarded via API or through the Partner Portal (documentation)
Tenant structureClient, service, merchant, customer, with a bank account per merchantPartners can manage the API keys of their sub-customers (documentation)Accounts can have Sub-Accounts, by operating name, business unit or geography (documentation)
Economics per tenantA full fee grid and limits per service, readable by APICustomer billing is specified on schedule A of the customer's contract (knowledge base)Partners manage permissions, limits and commercial arrangements with the accounts they create (documentation)
HeadquartersMontreal, founded in 2018U.S. headquarters in Miami, announced September 2024 along with its CEO's move there (announcement)Global headquarters in Doha, Qatar, announced January 2026 (Business Wire release)
FrenchBilingual platform, support and developer pagesFrench-language website (zumrails.com/fr)No French version: vopay.com/fr-ca/ returns a 404

Competitor facts come from the linked pages, verified November 22, 2026.

TIB's depth is what a table row cannot hold: a server-forced MerchantId, refused administration calls, per-login idempotency and the MerchantId on every webhook. For full comparisons, see TIB Finance vs Zum Rails and TIB Finance vs VoPay.

Why build a Canadian platform on a Canadian processor?

TIB Finance is a sovereign Canadian payment processor, headquartered at 360 Saint-Jacques Street in Montreal and founded in 2018. It is registered with the Bank of Canada as a payment service provider under the Retail Payment Activities Act (RPAA) (Bank of Canada registry). Zum Rails appears in the same registry, as its home page shows (verified November 22, 2026), so on registration the two are on par.

Where the companies are headed is another matter. Zum Rails opened its U.S. headquarters in Miami in September 2024, and announced that its CEO would permanently relocate there (Zum Rails announcement). Its CA$10.5 million Series A had a single investor, Minneapolis-based Arthur Ventures (BetaKit, Arthur Ventures). According to its CEO, the U.S. should account for more than 60% of its revenue in 2028 (Mergermarket). In January 2026, VoPay announced it had established its global headquarters in Doha, Qatar (Business Wire release). All verified November 22, 2026.

TIB Finance stays focused on Canadian businesses and the platforms that serve them. See registered PSPs in Canada and choosing a Canadian payment processor.

How do you start building your multi-tenant platform on TIB?

A typical processor hands you an API key and a documentation link. TIB Finance sends people. A dedicated integration team works inside your processes until payments run on their own, and integration is free for eligible businesses.

  1. Talk to our team. Describe your tenants, flows and business model, and we map them onto TIB with you.
  2. Test in the sandbox. Open a free sandbox account, get your API credentials by email, and run every payment flow end to end before you go live, with our guide to testing payment integrations.
  3. Connect once. Wire the API, the Drop-In and the webhooks with the payment API integration guide, the API use cases and the developer hub. An MCP server also lets AI agents and automated workflows query transactions and trigger payment operations.
  4. Grow tenant by tenant. Each new client is one more service, with the same structure and controls.

Plans from $25/month, with pricing adapted to your volume and business model: talk to our team. If you resell or refer TIB to your own network, the partner program offers a $250 gift card on your first mandate and up to 60% commissions, with co-marketing, co-selling and integration partnerships.

What do platform teams ask about multi-tenant payments?

What is a multi-tenant payment architecture?

A multi-tenant payment architecture lets one platform process payments for many businesses, its tenants, through a single integration, while each tenant's merchants, customers, bank accounts, fees and data stay isolated. On TIB Finance, your organization is the client, each tenant is a service and each bank account is a merchant, and the server enforces the isolation.

How do I create a tenant on TIB Finance?

One CreateSubClient call creates a tenant, called a service, with its own name, language and currency, CAD or USD. It returns the new ServiceId, which you use in every call for that tenant, and a BoardingRedirectUrl when the tenant needs onboarding.

Can one tenant see another tenant's data?

No. In a merchant session, the server sets MerchantId to the session's merchant, whatever value is sent, and refuses administration calls such as creating merchants or sub-clients. Accesses can also be read-only, and two-factor authentication protects sensitive operations.

How do webhooks identify the tenant?

Every TransactionEvent webhook carries the MerchantId and MerchantName, along with the target, direction, step, status and amount, so your platform routes each event to the right tenant straight from the payload.

How does TIB Finance compare with Zum Rails and VoPay for platforms?

All three serve platforms. Zum Rails offers a partner portal with sub-customers, and VoPay offers a Partner API with sub-accounts (verified November 22, 2026). TIB Finance makes the tenant its data model, with server-enforced isolation, fees and limits per tenant and the MerchantId on every webhook, backed by a bilingual team in Montreal.

Is TIB Finance a Canadian company?

Yes. TIB Finance is a sovereign Canadian payment processor, founded in 2018 and headquartered in Montreal, and it is registered with the Bank of Canada as a payment service provider under the RPAA. It serves more than 1,000 businesses and processes over $600 million a year.

How much does TIB Finance cost for a platform?

Plans from $25/month, with pricing adapted to your volume and business model. Talk to our team for a proposal that fits your platform.

How do we get started?

Talk to our team about your tenants and payment flows. Integration is supported and free for eligible businesses, and developers can test everything in a free sandbox.

Build Your Multi-Tenant Platform on TIB

Tell us about your tenants and payment flows. A real, bilingual team in Montreal maps your platform onto TIB with you.

Talk to Our Team Try the Sandbox

Building a platform or reselling payments? Become a TIB partner.