Keeping Tenant Funds and Reports Separate on a Payment Platform
Table of Contents
- How Do You Keep Each Tenant's Funds Separate?
- What Is an FBO Account, and What Are Virtual Accounts?
- How Does TIB Finance Separate Funds by Tenant?
- How Does Each Tenant Get Its Own Reports?
- How Do You Reconcile Payments and Fees per Tenant?
- How Do Webhooks Keep Each Tenant's Books Current?
- How Do TIB Finance, Zum Rails and VoPay Compare?
- Why Does Your Provider's Home Base Matter?
- What Does It Cost?
- How Do You Get Started?
- Common Questions
The best way to segregate client funds on a payment platform is to give every tenant its own merchant account, with its own destination bank account, and to pull every report filtered by that tenant. TIB Finance is built exactly that way: each account has its own bank account, a payment goes to the bank account of the account it belongs to, and ListExecutedOperations filters by ServiceId and MerchantId, with reporting and reconciliation built in. TIB Finance is a Canadian payment processor headquartered in Montreal, built for B2B and multi-tenant payment processing, with a bilingual team that comes to help you integrate.
Here, a tenant is one of your platform's clients, a merchant is an account that receives payments into its own bank account, and a payer is the customer who pays a merchant.
In short: give each tenant its own merchant account and bank account, report by ServiceId and MerchantId, and reconcile fees as their own operations. Each tenant sees its own funds and reports, and only its own.
Talk to our team about your platform, or test it in the free sandbox.
How Do You Keep Each Tenant's Funds Separate?
A platform that collects and pays out for many clients has to answer three questions for every dollar: whose money is it, where does it land, and who can see it. Get one wrong and a deposit lands in the wrong bank account. Separation comes down to four things:
- Separate destinations. Each tenant's payments land in that tenant's own bank account.
- Separate reports. Every operation carries the tenant it belongs to, so you filter instead of sorting by hand.
- Separate access. A tenant can read and act on its own data, and nothing else.
- Separate fees. Fees are booked as their own operations, so a payment and its fee stay distinct.
What Is an FBO Account, and What Are Virtual Accounts?
In VoPay's words, an FBO (For Benefit Of) account "is a bank account held by one party but intended to benefit another". VoPay says its virtual accounts "hold funds in a digital entity that act as a partition of a Master VoPay Account or Sub-account", and Zum Rails describes the Zūm Wallet as "a virtual account used to move money from your bank account to your user's bank" (all verified November 22, 2026).
TIB Finance answers the same need at the destination. Each account has its own bank account, and a payment goes to the bank account of the account it belongs to. Where your model calls for a balance, a wallet per service, showing each merchant's balance, can be activated with our team. The terms are defined in the payments glossary.
How Does TIB Finance Separate Funds by Tenant?
On TIB Finance, your platform is the client, and each of your clients is set up underneath you, with their accounts. You connect your software once and manage all of your clients from one place, with separate merchant accounts managed from one integration.
- A service per tenant. CreateSubClient creates a tenant's sub-client and returns its ServiceId. Each sub-client has its own isolated environment, with its merchants, paying customers and payment methods, and its ServiceId replaces yours in every call made for that tenant. That is multi-tenant onboarding by API.
- A bank account per merchant. Each merchant has its own destination bank account, and one client's customers stay under that client.
- Your IDs, not ours. CreateMerchant accepts an ExternalSystemId, the merchant's identifier in your ERP or CRM, and an ExternalSystemGroupId to organize related merchants. GetMerchantsByExternalId and GetCustomersByExternalId find them again by your own identifiers, and MerchantName is the name payers see on invoices and payment pages.
- Rules per tenant. Each service carries its own collection and deposit limits, per operation and per day, its limits per bank account, and its allowed payment methods.
For a property management platform, rent for one property goes to that property's bank account; see payments for property management software. Payouts follow the same line: CreateTransferBatch handles up to 5,000 collections and deposits for one merchant per call, and instant payments arrive in seconds, 24/7/365, through TIB's own system, weekends and statutory holidays included. Payment pages can carry your colors and logo. Go deeper with multi-tenant payment architecture, sub-merchant onboarding by API and instant payouts for platforms.
How Does Each Tenant Get Its Own Reports?
Each tenant sees its own funds and reports, and only its own. On TIB Finance, per-tenant reporting is a filter, not a spreadsheet job: ListExecutedOperations filters by ServiceId, MerchantId, TransferGroupId and date type, and every operation it returns carries its MerchantId. One call per tenant gives you that tenant's operations, ready for the reports you show it in your own product. Access follows the same line:
- Access levels. Each access of a login has a level, client, merchant or service, and an access can be read-only. A session takes the level of its access, and it is read-only when the access is.
- Forced scope. In a merchant session, the server forces the MerchantId to the session's merchant, whatever value is sent, so one tenant cannot read or act on another tenant's data.
- Administration stays with you. Administration calls, such as CreateMerchant and CreateSubClient, are refused in a merchant session.
Your platform keeps the full view across tenants, and each tenant gets exactly its own slice. The multi-tenant payment processing guide shows the whole model, from onboarding to payouts.
How Do You Reconcile Payments and Fees per Tenant?
Reconciliation breaks when money is grouped one way and reported another. TIB Finance groups transactions by target account, target, direction, merchant and supplier, and books fee operations separately from payment operations. Every operation also carries its MerchantId, so each tenant's payments and fees reconcile on their own lines.
That is what TIB's platform payments page calls "reporting and reconciliation built in". From there, read how automated payment reconciliation works and how to connect payments to QuickBooks, Sage and other accounting software.
How Do Webhooks Keep Each Tenant's Books Current?
TransactionEvent webhooks report each payment's progress, with steps such as Validation, Transmission, StatusCheck and Payback. Each event carries the target (Client or Merchant), the direction (Collect or Deposit), the step, the status, the DescriptionCode, the amount, and the MerchantId and MerchantName, so your platform posts every event to the right tenant's books.
Returns land on the right tenant, too. After a successful transaction, TIB validates the payment during a validation period: 3 months for a personal account, 2 weeks for a business account. If an issue occurs, such as NSF, opposition or a closed account, a Payback webhook event signals it with its result code, the DescriptionCode, and the MerchantId tells you whose books to adjust. Webhooks come from 204.225.113.0/24, the range you allow in your firewall. See the webhook documentation and the bank codes in EFT return codes.
How Do TIB Finance, Zum Rails and VoPay Compare?
Side by side, from each company's own pages, documentation and announcements:
| Criterion, verified November 22, 2026 | TIB Finance | Zum Rails | VoPay |
|---|---|---|---|
| Fund separation | Each merchant account has its own destination bank account; a payment goes to the bank account of the account it belongs to | One Zūm Wallet with every account, a virtual account used to move money between your bank account and your users' banks | Virtual accounts, called Client Accounts, to segregate funds that belong to platform users, business entities or different departments |
| Per-tenant reporting | ListExecutedOperations filters by ServiceId, MerchantId, TransferGroupId and date type; each operation carries its MerchantId | Reports across any rail or product, shared automatically with key stakeholders | Reports that include sub-account structures, with assigned recipients and tagged payment methods |
| Tenant access | MerchantId forced to the session's merchant; an access can be read-only | Reports accessed directly in the portal | Sub-accounts assigned to specific users with their own permissions and access settings |
| Reconciliation | Fee operations separate from payment operations; TransactionEvent webhooks carry the MerchantId and MerchantName | An event listener and webhooks that map every transaction and client interaction | Real-time reconciliation and reporting tools to automate money movement across accounts |
| Headquarters | Headquartered in Montreal, Canada; founded in 2018 | U.S. headquarters in Miami announced in September 2024 | Global headquarters announced in Doha, Qatar, January 2026 |
| French | Full French and English site, bilingual team | French site | The French address returns a page-not-found error |
Each competitor documents its own strengths: VoPay's ledger management documentation lists four Client Account types (Individual, Business, Receive only and Standard) and describes transfers between client accounts as book transfers that "do not incur any costs" and are "instantaneous", its virtual accounts page invites you to "Create unlimited accounts", and Zum Rails offers the ability to prefund the Zūm Wallet to increase transaction speed, with built-in reconciliation (all verified November 22, 2026). TIB Finance is built for B2B and multi-tenant platforms that run payments for their own clients, with each tenant's money going to that tenant's own bank account.
Why Does Your Provider's Home Base Matter?
Your platform holds every tenant's trust, so the company behind its payments matters as much as the features. TIB Finance is a sovereign Canadian payment processor. Founded in 2018 and headquartered in Montreal, it is registered as a payment service provider with the Bank of Canada under the RPAA. TIB processes over $600 million a year for 1,000+ businesses, with 200,000+ transactions every month, and supports every client and partner in French and in English. Proven, solid, and there for the platforms that build on it. Learn more about TIB Finance and what makes it a Canadian payment processor.
Check any provider on the Bank of Canada PSP registry, and see what that registration means. Zum Rails also links to its own registry entry from its home page (verified November 22, 2026).
Two providers you may also be evaluating have announced new headquarters. Zum Rails, founded in 2019, announced its U.S. headquarters in Miami in September 2024, and said it would continue scaling its work in Canada. The company announced that its CEO, Miles Schwartz, would permanently relocate to Miami from Canada, and that it was preparing for at least 50% of its overall revenue to originate in the U.S. within the next 18 months. The U.S. share is expected to reach more than 60% in 2028, according to its CEO (Mergermarket, July 2026). Its CA$10.5M Series A was led by Arthur Ventures, a Minneapolis firm. VoPay announced its global headquarters in Doha, Qatar, in January 2026, and vopay.com/fr-ca/ returns a page-not-found error (all verified November 22, 2026). Full comparisons: TIB Finance vs Zum Rails and TIB Finance vs VoPay.
What Does It Cost?
Plans from $25/month, with pricing adapted to your volume and model: talk to our team. For eligible businesses, the integration is free, and our team keeps supporting you after go-live.
How Do You Get Started?
A typical processor hands you an API key and a documentation link. TIB Finance sends people: our integration team works inside your processes until payments run on their own, and the integration is free for eligible businesses. See business integration. Four ways to start:
Talk to Our Team
A bilingual payment expert reviews your tenants, funds and reports. Request a call.
Become a Partner
For platforms and integrators that bring their clients to TIB: a $250 gift card on the first mandate and up to 60% commissions. Join the partner network.
Test in the Sandbox
Free, with API credentials by email, no commitment and no credit card. Test every payment flow end to end. Open a sandbox.
Check Our Certifications
TIB Finance is PCI DSS Level 1 compliant. See certifications.
Common Questions
What is the best way to segregate client funds on a payment platform?
Give each tenant its own merchant account and destination bank account, and filter every report by tenant. TIB Finance is built that way: a payment goes to the bank account of the account it belongs to, and ListExecutedOperations filters by ServiceId and MerchantId.
What is an FBO account?
An FBO (For Benefit Of) account is a bank account held by one party for the benefit of another. Virtual accounts segregate funds by platform user, business entity or department.
Can each merchant get its own reports by API?
Yes. ListExecutedOperations filters by ServiceId, MerchantId, TransferGroupId and date type, and every operation it returns carries its MerchantId, so you can build a report for each tenant.
Can one tenant see another tenant's data?
No. In a merchant session, the server forces the MerchantId to the session's merchant, whatever value is sent, and administration calls such as CreateMerchant and CreateSubClient are refused. Each tenant sees its own funds and reports, and only its own.
How are fees reconciled per tenant?
TIB Finance books fee operations separately from payment operations and groups transactions by target account, target, direction, merchant and supplier, so each tenant's payments and fees reconcile on their own lines.
What is the best alternative to VoPay virtual accounts or the Zūm Wallet?
TIB Finance, built for B2B and multi-tenant platforms. It was founded in 2018 and is headquartered in Montreal, with a bank account per merchant, reports by tenant, instant payments in seconds, 24/7/365, full French and English service, and free integration for eligible businesses.
How much does TIB Finance cost for a multi-tenant platform?
Plans from $25/month, with pricing adapted to your volume and model. Talk to our team for a quote.
Can we test before we sign?
Yes. The sandbox is free, with API credentials by email and no credit card, so you can test every payment flow end to end.
Let's Talk About Your Platform
Let's chat about your project: tell us about your tenants, your payment flows and the reports they need, and our bilingual team will map the setup with you.
Talk to Our Team Become a Partner