SMEs in MENA don't have a payment problem. They have a fragmentation problem. One tool for corporate cards. Another for expense claims. A third for vendor payouts. A fourth for cross-border. None of them talk to each other, so the finance team — often one person who also does operations — spends their day reconciling instead of managing.
Nym4Business (N4B) is NymCard's answer: a unified Financial Operating System for SMEs, white-labeled to financial institutions. I joined NymCard in June 2025 as PM for N4B, leading the product from a maturing platform toward a deployable FI-grade product. The goal: build something that a regulated bank or licensed FI could put their name on and offer to their SME client base.
The SME Financial Operations Problem#
Ask a UAE SME founder how they manage their company's finances and you'll hear the same story every time. Corporate cards from one provider. Expense reports on spreadsheets. Wire transfers from internet banking. International supplier payments through a foreign exchange broker. Digital invoices out of accounting software that doesn't connect to anything else.
Fragmented tooling.
Each point solution solves one problem and creates three integration gaps. Data doesn't flow between them.
Manual reconciliation.
Someone has to match the card statement to the expense report to the AP ledger. That someone is usually the CEO or a part-time bookkeeper.
Compliance exposure.
KYB, KYC, AML screening — each new financial provider requires its own onboarding. The compliance burden multiplies with every tool added.
No financial visibility.
Real-time cash position is a manual calculation. Spend by department is a question that requires someone to stop what they're doing and export a report.
Poor controls.
Approval processes live in WhatsApp threads. Card limits are set once and forgotten. Vendor payment authorization is informal.
The problem isn't that any one of these tools is bad. The problem is the architecture: point solutions, stitched together, operated manually. The fix isn't another point solution. It's a platform.
What N4B Is#
N4B is a white-label Financial OS: NymCard builds and maintains the platform, financial institutions brand it and distribute it to their SME clients. The full platform covers the end-to-end SME financial operations surface.
KYB / IDV / KYC Onboarding
Self-serve SME signup with staged compliance flow. Identity verification, UBO collection, and regulatory screening built in.
Corporate Card Issuance
Virtual and physical cards with configurable spend controls, limits, and merchant category restrictions.
Expense Management
Employee expense submission, receipt capture via OCR, reimbursement workflows.
Accounts Payable
Vendor management, invoice capture, payment scheduling, and AP approval workflows.
Accounts Receivable
Digital invoice creation and delivery to B2B and B2C customers.
Cross-Border Payments
Beneficiary management and international payment rails for vendor payouts across currencies.
Embedded Lending
Credit origination, disbursement tracking, and repayment management for FI credit products.
RBAC + Entity Hierarchy
Multi-level corporate structures with role-based access control and permission inheritance.
Approval Rule Engine
Maker-checker workflows with configurable rules for payments, card issuance, and account changes.
MFA + OCR
Multi-factor authentication and optical character recognition for document processing.
The FI is the direct customer — they pay for the platform, brand it, and integrate it into their SME offering. The SME's employees and finance teams are the end users. This is B2B2C: two distinct customers with different needs, different success metrics, and different relationships with the product.
My Role#
I lead N4B product end-to-end. Three areas I've driven specifically:
SME Self-Signup Portal
Designed and shipped the self-serve onboarding experience with staged KYB/KYC compliance flow. SMEs can start the onboarding process and explore the platform without hitting the full compliance wall upfront.
Corporate Hierarchy + RBAC + Approval Flows
Defined the entity model (company → department → user), permission inheritance, and the approval rule engine. The challenge: making abstract financial governance feel concrete and manageable for non-finance-trained SME administrators.
Requests Listing Redesign
Overhauled the requests management experience: filtering, sorting, bulk actions, and SLA-driven "due soon" logic so finance teams can triage approval queues without missing time-sensitive requests.
Decision 1: Staged KYB Onboarding#
The Problem
Traditional financial platform onboarding front-loads compliance. Upload your trade license. Provide UBO details. Wait for manual review. The business hits a twelve-field compliance form before they've seen a single screen of the product.
The Insight
In regulated financial services, the compliance requirements can't be removed — they're legally mandated. But the sequence can be engineered. The question isn't "how do we reduce KYB requirements?" but "when do we ask for each piece of information?"
The Solution
We split onboarding into two phases. Phase 1 captures enough to let the user explore the platform: account creation and basic identity confirmation. Phase 2 collects the deeper KYB/IDV requirements before full account activation. The compliance burden is identical — the experience is entirely different.
SME founders are time-poor. If they encounter a compliance wall before they've seen any product value, their mental model is "bank onboarding" not "financial tool." The staged approach lets them experience the product before asking them to invest time. Early exploration creates buy-in. Buy-in creates completion.
This isn't about hiding compliance requirements — it's about sequencing them intelligently. The FI still gets full KYB coverage. The SME gets a product before a form.
Decision 2: The Approval Rule Engine#
The Problem
Maker-checker workflows are standard in enterprise finance. A payment request flows to an approver, the approver validates, payment executes. The assumption is a clear organizational hierarchy with formal delegation of authority.
The Insight
SMEs don't work like enterprises. The "finance team" might be one person. Reporting lines are flat enough that formal approval feels like bureaucracy. The CEO approves everything personally regardless of amount — until they're traveling and that breaks down. The governance structures that enterprise maker-checker assumes often don't exist.
The Solution
Rules instead of roles. Rather than forcing a fixed org chart onto the platform, administrators define conditions: "any payment over AED 10,000 requires approval from X." "Card issuance requests require Y." The rule engine handles the routing and escalation. Administrators define the policy. The system enforces it.
The UX Challenge
The harder problem was the UX, not the logic. "Rules" is an abstract concept. SME owners think in outcomes: "I want to know before anything over AED 5,000 goes out." They don't naturally think in if-then-else. The rule creation interface had to translate from "outcome the admin wants" to "condition-action pair the system needs" without exposing the underlying logic.
Abstract financial governance has to become concrete financial controls. If the configuration UI requires a finance background to navigate, SME administrators won't configure it correctly — which means the controls won't work in practice.
Decision 3: Building for Two Customers#
N4B's distribution model creates genuine product tension. Every feature decision has two stakeholders with different priorities.
What the FI Wants
Financial institutions want differentiation they can sell. A white-label platform they can brand, configure, and position as their own product. They want the ability to surface only the modules relevant to their SME segment. They want onboarding flows they can wrap in their own brand language. They want feature toggles.
What the SME Wants
SMEs want a clean tool that reduces operational overhead. A consistent interface that works the way finance is supposed to work. Guided setup that doesn't require a consultant. Speed.
The Tension
These conflict at the margin. Maximum FI configurability means minimum product opinionatedness. A blank canvas that lets FIs customize everything is a canvas that most FIs will configure inconsistently, producing a bad SME experience.
Our Resolution
Our resolution: be opinionated about UX defaults, flexible about configuration. N4B has a clear opinion about how onboarding works, how approval flows are structured, and what default card controls look like. FIs can configure and brand within that opinionated structure, but they can't break the core experience.
FIs aren't buying infrastructure. They're buying product opinions — the accumulated knowledge of what a good SME financial operations experience looks like. Our job is to have and defend those opinions, while giving FIs enough flexibility to make it theirs.
Lynq: N4B in Production#
Lynq launched in May 2026 — an all-in-one financial operating system for SMEs, brought to market by Mawarid Finance, a UAE-based Islamic finance and investment group regulated by the Central Bank of the UAE. Lynq runs on NymCard's card processing and program management infrastructure.
"Lynq is our answer to a gap we consistently saw, where businesses were managing fragmented systems instead of focusing on growth."
Lynq launched with the core financial OS feature set: virtual and physical Mastercard corporate cards, global supplier payments, real-time financial visibility across all company activity, a dedicated virtual IBAN per business, and self-serve digital onboarding. The first cohort of UAE registered businesses can sign up at no cost.
Lynq is N4B white-labeled. Mawarid Finance chose Mastercard as the card network, built on NymCard's processing infrastructure. The phased feature rollout is deliberate — starting with the highest-value modules (cards, cross-border, centralized visibility) before expanding to the full platform surface.
Lynq is the public proof point. Every product decision made during N4B development shows up in how Lynq works — the staged onboarding, the spend controls, the real-time visibility. Seeing a regulated FI take it to market forces prioritization clarity that internal planning discussions don't.