Partnership Evaluation | Renatus

PLANNING PARTNERSHIP EVALUATION

Prepared for Demo Account · 09 Sep 2026

Meridian Pay × CIMB Partnership Evaluation

Meridian Pay is solving a real and urgent problem — private credit lines at capacity, a 18-month window before the major bank SME channels close, and a partner who genuinely needs what Meridian Pay has built. The strategic logic of the partnership is sound: CIMB gets a functioning digital invoice-finance product inside its own app in months rather than years; Meridian Pay gets bank-cost capital and access to a distribution base it cannot replicate independently. The pilot demonstrated that CIMB's SME customers will use a self-serve financing product and that Meridian Pay's scoring and servicing held up under bank-grade due diligence scrutiny. That is meaningful validation, even if the cohort was best-case. The partnership as currently drafted, however, concentrates three major concessions in CIMB's favour simultaneously: a 60/40 revenue split, full credit-policy control, and three-year Malaysia-wide exclusivity.

Each is individually negotiable and arguably justifiable. Together they create a structure where CIMB controls the volume outcome through credit policy, captures the majority of the income, and forecloses Meridian Pay's ability to pursue alternative bank partnerships if the volume targets are not met. The governance mechanism — a quarterly joint steering committee with no credit-policy authority — cannot resolve the central dispute that will arise. The integration complexity is real, with a 12-month technical build (not the 7–9 months CIMB's digital team estimates), four culturally misaligned CIMB functions, and an unresolved question about what happens to Meridian Pay's existing 1,400 customers. The deal is worth doing — but not in its current form.

The partnership

Deal value

MYR 90m

Total value in play

Value split

40 / 60

Our share / their share

Term

3 years

Strategic window 18 months Until market closes

Meridian Pay is an invoice-financing platform serving approximately 1,400 active Malaysian SME customers, having financed roughly MYR 180m over the past twelve months through two private credit lines that now constrain its growth. The proposed partnership with CIMB would embed Meridian Pay's origination technology and risk-scoring engine inside CIMB's OCTO Biz SME banking app, with CIMB supplying the lending capital and granting access to its SME customer base. In structural terms, Meridian Pay transitions from a standalone lender carrying expensive private credit risk to an embedded product running on bank-cost capital — and CIMB acquires a fully operational invoice-finance capability without the cost or time of building one internally. A three-month pilot conducted earlier in 2026 involved 40 CIMB SME customers and financed approximately MYR 4m across 62 invoices, with average tenor of 47 days and average facility of MYR 65,000. Repayment performance was clean — 59 of 62 invoices settled within terms, the remaining three within two weeks of due date, and no losses recorded.

However, CIMB selected participants from customers with at least three years of clean banking history, making this a best-case cohort. The 13% opt-in rate from the invitation list (40 from 300) confirmed demand for self-serve digital financing. CIMB's credit and compliance teams used the pilot as simultaneous due diligence — reviewing Meridian Pay's scoring model, KYC process, and collections — and this review directly triggered the full partnership conversation. What the pilot has not tested is scale: performance across a broader, unselected SME population with risk profiles closer to Meridian Pay's own book (1.8% non-performing) remains unproven. The proposed full-term agreement spans three years. CIMB has requested exclusivity across Malaysia for the full term; Meridian Pay has not yet agreed. The strategic window is estimated at 18 months: Maybank and RHB are both known to be in active discussions with embedded-finance providers, and once those banks commit to partners, the primary SME distribution channel through Malaysia's major banks will be closed.

Strategic fit

Strategic fit score

Aligned

Capital and distribution exchange

Meridian Pay gets bank-cost capital and CIMB's SME base; CIMB gets a working digital invoice-finance product without a two-year build. The exchange is clean and immediate.

Digital SME strategy alignment

CIMB has publicly committed to growing digital SME revenue share. This partnership directly advances that stated priority — it is not a side project.

Speed-to-market advantage

Both parties benefit from the same urgency: the 18-month strategic window before Maybank and RHB close the major-bank channel. Neither party is served by delay.

Divergent

Exclusivity vs optionality

CIMB wants three-year Malaysia-wide exclusivity to protect its defensive investment. Meridian Pay's growth logic requires the ability to pursue other bank partnerships or expand product scope — both of which the exclusivity forecloses.

Brand visibility vs white-label

Meridian Pay's long-term value is partly in brand and market position. CIMB's preference is almost certainly for a white-label product that keeps lending within the CIMB relationship. These are in direct tension.

Internal CIMB alignment risk

The digital partnerships team, SME banking team, and credit function have materially different levels of enthusiasm for this deal. The credit team's preference to build internally is not resolved by signing the partnership — it resurfaces the first time a credit decision is disputed or a scoring model needs updating.

Our strategy:

Meridian Pay's strategic objective is to break through a capital constraint that is now the binding limit on growth. With MYR 180m financed across 1,400 customers and two private credit lines at capacity, the platform cannot grow volume without either raising more expensive private capital or accessing a cheaper, larger funding base. The partnership is an attempt to solve both the capital problem and the distribution problem simultaneously — embedding the product inside CIMB's SME app converts Meridian Pay from a standalone lender competing for origination into an infrastructure layer running on bank-cost capital at bank scale.

Their strategy:

CIMB's motivation is defensive wallet-share protection, not product gap-filling. The bank already operates a conventional invoice-finance product, but it is relationship-manager-dependent, manual, and designed for the upper tier of the SME base — fewer than 5% of CIMB's SME customers have ever used it. Smaller SMEs (MYR 50,000 ticket size) are sourcing working-capital financing from Funding Societies, Meridian Pay, and other fintechs. CIMB retains the operating account and transactional data but loses the lending margin and relationship depth to external players. Under its current group strategy, CIMB has publicly committed to growing the share of SME revenue from digital channels. This partnership delivers a digitally native invoice-finance capability in months rather than the approximately two years an internal build would require.

Where they align:

The overlap is real and valuable where it exists. Meridian Pay needs distribution and capital; CIMB needs a product that works at MYR 50,000 ticket sizes without relationship-manager cost. For the first 12–18 months of a full rollout, both parties benefit from the same outcome: more SMEs taking invoice financing inside the CIMB app, with Meridian Pay's engine doing the underwriting and CIMB's balance sheet funding it. The defensive and offensive motivations produce identical short-term behaviour — grow the embedded product, make it work, prove the model.

Where they diverge:

The divergence opens as the partnership matures. Meridian Pay's growth logic requires building brand, product breadth, and eventually either other bank partnerships or direct lending again — all of which conflict with three-year Malaysia-wide exclusivity. CIMB's defensive logic may eventually require owning the capability rather than licensing it: if the product succeeds, their credit team's preference to have built it internally becomes a strategic posture, not just internal politics. There is also a branding asymmetry — Meridian Pay's growth is served by visibility; CIMB's by white-labelling. And the internal alignment at CIMB is uneven: the digital partnerships team is enthusiastic, the SME banking team is cautious, and the credit function is sceptical. A partnership that depends on cross-functional commitment at a large bank is exposed to the slowest or most resistant function.

Honest assessment:

The fit is real but time-bounded. The interests converge strongly in the first phase — proving the embedded model works at scale — and diverge as Meridian Pay's growth ambitions exceed what CIMB's defensive posture can accommodate. The three-year exclusivity request is the structural expression of this divergence: CIMB wants to lock in the capability while it figures out what to own; Meridian Pay needs optionality the exclusivity removes. The fit scores high on immediate alignment and lower on durability. It is strategic fit in the sense that both parties need something the other has — but the underlying motivations are asymmetric enough that governance of the divergence point matters more than the initial alignment.

Economic fit

Value split

Our share

Their share

Value captured

Value captured (us)

MYR 40m

0.7x

Value captured (them)

MYR 54m

Our capture relative to theirs

Value to us

Meridian Pay captures a 40% share of gross financing income across MYR 1.2bn of projected volume over three years, plus a fixed platform fee of MYR 1.2m per year regardless of volume. Total expected receipts are approximately MYR 40m over the term — MYR 36m in revenue share plus MYR 3.6m in platform fees. Against a MYR 6m build cost in year one, the partnership generates a net positive of roughly MYR 34m if volume projections hold. Beyond the cash return, the partnership solves the binding constraint on growth: private credit lines are replaced by CIMB's balance sheet, removing the capital ceiling that has prevented Meridian Pay from scaling beyond its current 1,400-customer base.

Value to them

CIMB captures 60% of gross financing income — approximately MYR 54m over three years — while retaining the SME operating account relationship and the transactional data that comes with it. The strategic value extends well beyond the MYR 54m: every MYR of working-capital financing kept inside the CIMB app is a MYR not flowing to Funding Societies or Meridian Pay's direct channel. At year-three run rate, CIMB would have approximately MYR 80m in outstanding invoice-finance facilities, generating lending margin on a book it did not have to build. The fixed platform fee of MYR 1.2m per year is a cost to CIMB, offset against the value of not running an 18-to-24-month internal build programme.

Value split

At the expected 60/40 settlement, CIMB captures approximately MYR 54m and Meridian Pay approximately MYR 36m in revenue share over three years, before the platform fee. The split is asymmetric in CIMB's favour, which is defensible given that CIMB holds all credit risk on an MYR 80m peak outstanding book. It is less defensible when combined with CIMB's demand for credit-policy control and three-year Malaysia-wide exclusivity — three concessions that each independently constrain Meridian Pay, and which collectively shift negotiating leverage to CIMB on every subsequent decision about product scope, scoring model changes, and partnership renewal.

Value at risk

Meridian Pay's direct financial exposure is MYR 6m in engineering and integration costs in year one, most of which is sunk before the partnership produces meaningful volume. The larger exposure is strategic: three-year exclusivity means that if CIMB's internal adoption is slow, its credit team is obstructive, or volume falls short of the MYR 150m year-one target, Meridian Pay has no fallback — the 18-month window to sign Maybank or RHB will have closed. CIMB's exposure is the loan book: a credit deterioration in the SME segment would put an MYR 80m peak book at risk, with losses sitting entirely on CIMB's balance sheet. The credit-policy control CIMB is seeking is a direct consequence of this exposure — and it is a reasonable ask in isolation.

Sustainability

The 60/40 split is sustainable as long as both parties' contributions to the partnership remain roughly stable — Meridian Pay provides the scoring and servicing, CIMB provides the capital and the customer base. It becomes unstable in two scenarios. First, if CIMB's credit team asserts increasing control over the scoring model, Meridian Pay's operational autonomy shrinks while its revenue share stays fixed — the split no longer reflects the actual division of work. Second, if the partnership succeeds and CIMB decides it wants to internalise the technology rather than renew, it will do so from a position of strength: three years of volume data, a proven customer base, and a Meridian Pay that has been locked out of alternative bank partnerships for the full term. The platform fee partially addresses the sustainability problem by guaranteeing cost recovery at low volume, but it does not address the structural power shift that exclusivity creates at renewal.

Governance & pre-mortem

Governance mechanism:

A joint steering committee of three representatives from each side, meeting quarterly, with escalation to CIMB's head of SME banking and Meridian Pay's CEO. Individually facility decisions outside the credit policy go to CIMB's credit committee for manual review. The steering committee has authority over product and marketing decisions only — credit policy sits with CIMB's credit committee, which Meridian Pay has no seat on.

Predictable dispute:

The foreseeable dispute is not about an individual credit decision but about the credit policy itself. Construction subcontractors represent approximately 25% of Meridian Pay's current book — a segment banks treat with well-documented caution. Six to nine months into a full rollout, any cluster of losses in that segment will prompt CIMB's credit committee to tighten policy: sector exclusions, lower limits, additional documentary requirements. Approval rates could fall from the current 70% toward 40%. Volume drops below plan, Meridian Pay's revenue share falls with it, and the joint steering committee — which has no authority over credit policy — cannot resolve the dispute. The mechanism that exists is designed for the disagreements that will not matter and is silent on the one that will.

Resolution path:

As drafted, there is no resolution path for a credit-policy dispute — the steering committee cannot override the credit committee, and the agreement contains no contractual parameters constraining how far CIMB can tighten. Meridian Pay's proposed remedy is to embed a Credit Policy Schedule in the agreement with defined approval-rate corridors (e.g. a breach threshold below 50% for two consecutive quarters), sector concentration limits, and loss triggers. Within those parameters, CIMB can tighten unilaterally. Outside them, any change requires steering committee approval on a defined timeline. If approval rates breach the floor for two consecutive quarters, exclusivity falls away — converting the dispute from a dead end into a structured negotiation with a consequence for both sides. CIMB has not yet agreed to this.

Honest assessment:

The governance as drafted is paper-thin on the dimension that matters most. The joint steering committee is a reasonable mechanism for operational disagreements about product features, marketing, and SLA disputes — and completely inadequate for a credit-policy dispute that directly controls volume and revenue. The term sheet has created a structure where CIMB holds credit-policy authority, lending capital, and exclusivity simultaneously, while Meridian Pay holds the technology and servicing obligation with no contractual lever if any of those three combine against it. The proposed Credit Policy Schedule with approval-rate corridors and an exclusivity release trigger is the right fix — it does not remove CIMB's credit control, it creates a defined boundary between unilateral action and joint decision. Getting this into the agreement before signing is the single most important negotiation remaining.

Integration risk

Integration risk scorecard

	Complexity	Readiness
Systems
Teams
Customers

Systems:

Meridian Pay's origination and scoring platform must embed inside CIMB's OCTO Biz SME app, operating behind CIMB's authentication layer and pulling transactional account data through CIMB's internal APIs rather than the open-banking connections Meridian Pay uses today. Disbursement and repayment must route through CIMB's core banking system, and every facility must be booked as a CIMB loan — requiring Meridian Pay to feed CIMB's loan management system and regulatory reporting stack. KYC sits at the intersection: CIMB's customers are already onboarded, but CIMB's compliance team requires re-verification of beneficial ownership to their own standard, which is more demanding than Meridian Pay's current onboarding process. Under Malaysian AML/CFT requirements, the bank must maintain its own evidence set for beneficial ownership verification — typically tracing through to natural persons at a 25% ownership or control threshold — meaning Meridian Pay's existing KYC files cannot simply be inherited without independent review.

Teams:

Meridian Pay's integration-facing team is approximately twelve people: the engineering team and the credit and collections analysts. On CIMB's side, four functions are involved — SME banking, digital partnerships, credit, and compliance — each with different priorities, different reporting lines, and different decision-making rhythms. Meridian Pay operates in two-week sprints; CIMB operates on quarterly change windows and quarterly steering committees. The cultural distance is already observable: a scoring model tweak that took Meridian Pay two days to implement required six weeks to get signed off during the pilot. That six-week cycle is not an outlier — it reflects the structural difference between a fintech's deployment cadence and a bank's controlled release process, and it will be the day-to-day grind of the partnership rather than an exception.

Customer handoff:

Meridian Pay's 1,400 existing customers know Meridian Pay — they call Meridian Pay's team, are serviced by Meridian Pay's analysts, and are collected by Meridian Pay's collections function. Under the partnership, new CIMB-channel customers will see a CIMB-branded product, with Meridian Pay operating servicing and collections under CIMB's brand. CIMB's contact centre will receive calls from customers experiencing repayment issues but will not be trained on the product — creating a conduct risk gap where the customer-facing institution cannot resolve the customer's problem. The 1,400 existing Meridian Pay customers are excluded from the partnership entirely: they remain on Meridian Pay's platform, funded by the expensive private credit lines the partnership is meant to replace. Meridian Pay would therefore operate two parallel products with two separate cost structures and two capital sources for the full three-year term unless a migration path is agreed — and whether CIMB would accept those customers onto its balance sheet has not been resolved.

Biggest risk:

The highest-risk integration point is the customer servicing handoff, not the technical build. Running two parallel products — a CIMB-branded embedded product and Meridian Pay's own platform — means two capital structures, two servicing teams, and two customer experiences operating simultaneously for three years. This is operationally expensive and strategically confused: it prevents Meridian Pay from consolidating onto cheaper capital and creates a conduct risk where customers of the CIMB product receive service through a contact centre that does not know the product. The mitigation requires a defined migration path for existing Meridian Pay customers — either onto CIMB's balance sheet under agreed credit criteria, or onto a structured wind-down of the private credit lines — agreed before the partnership launches, not treated as a post-launch problem.

Risks

Credit-policy tightening after early losses

High slow strangulation, not a loud failure

Mitigation: Embed a Credit Policy Schedule in the agreement with defined approval-rate corridors (floor: 50% for two consecutive quarters triggers exclusivity release), sector concentration limits, and loss triggers. Within those parameters CIMB can tighten unilaterally; outside them, changes require steering committee approval on a defined timeline. Without this schedule, this is the most probable failure mode — Meridian Pay would be exclusive, under-earning, and locked out of Maybank and RHB for the remainder of the term.

CIMB in-houses the technology in year two

High existential if IP is unprotected

Mitigation: Agreement must include: explicit IP ownership clause (scoring model and methodology remain Meridian Pay's); prohibition on using model outputs to train a replacement system; minimum run-off period of 12 months from termination notice to give Meridian Pay time to stand the book up elsewhere — either through private credit lines or an alternative bank partnership. CIMB will have 18 months of live data, customer behaviour, and a proven model by the time this risk crystallises. Without contractual protection, Meridian Pay will have spent three years and MYR 6m building its own replacement.

Integration overrun burns runway before the product is live

High makes the deal not worth signing rather than kills it outright

Mitigation: Two contractual requirements before signing: first, a phased launch structure with a limited-cohort go-live at month six on a lighter API integration (no full core banking connection required at phase one), followed by the full integration; second, the MYR 1.2m annual platform fee must commence from signature, not from launch. At eight months of runway, a partnership that is signed but not live will not carry a fundraise. Revenue from day one and a live product by month six are the minimum conditions for the deal to serve its financing purpose.

What this Reveals

This deal

	Score
Strategic fit
Economic fit
Governance
Integration
Risk profile

Pursue with conditions

The Meridian Pay × CIMB partnership has genuine strategic logic and a closing time window that makes inaction costly. CIMB needs a digital invoice-finance product that works at MYR 50,000 ticket sizes without relationship-manager cost; Meridian Pay needs bank-cost capital to break through the private credit line ceiling that is now the binding constraint on growth. The pilot demonstrated that CIMB's SME customers will use a self-serve financing product and that Meridian Pay's scoring and servicing can pass bank-grade due diligence. The economics at 60/40 with a MYR 1.2m annual platform fee are workable. None of that is the reason not to sign. The reason not to sign — as currently drafted — is structural. The agreement simultaneously grants CIMB the revenue majority, full credit-policy control, and three-year Malaysia-wide exclusivity, while providing a governance mechanism that has no authority over the dispute that will actually arise. That combination allows CIMB to under-deliver on volume by tightening credit policy — without breaching any contractual obligation — while Meridian Pay remains locked out of Maybank and RHB for the full term. The four structural conditions are not negotiating positions; they are the minimum framework that makes the deal's economics real rather than theoretical. If CIMB accepts the Credit Policy Schedule and the exclusivity release trigger, the deal is worth signing even if the IP protection and phased launch terms are softened. If CIMB refuses the Credit Policy Schedule outright, the volume plan was never real on their side, and the Maybank conversation should begin immediately while the 18-month window remains open.

Credit Policy Schedule embedded in the agreement with defined approval-rate corridors (floor: below 50% for two consecutive quarters triggers exclusivity release), sector concentration limits, and loss triggers — CIMB can tighten unilaterally within these bounds but requires steering committee approval with a defined timeline to move outside them.

Exclusivity release trigger: if approval rates breach the floor for two consecutive quarters, or if the product is not live within twelve months of signature, Malaysia-wide exclusivity falls away automatically.

IP and data protection clause: the scoring model and methodology remain Meridian Pay's intellectual property; model outputs cannot be used to train a replacement system; termination requires a minimum 12-month run-off period to allow Meridian Pay to stand the book up elsewhere.

Phased launch structure with a limited-cohort go-live at month six on a lighter API integration, followed by full core banking connection — and the MYR 1.2m annual platform fee commences from signature, not from launch, to contribute to runway during the build period.

Killer assumption

That CIMB will allow the product to operate at the level of credit risk the volume plan requires. Every projection — MYR 150m in year one, MYR 400m in year two, MYR 650m in year three — depends on approval rates holding near the 70% seen in the pilot. If CIMB's true credit appetite is the appetite of their legacy trade-finance product, the volume plan is fiction and the partnership will strangle quietly rather than fail loudly.

About About this report

What this is. This Partnership Evaluation was built through a guided conversation between Demo Account and Ren.

How it was built. All analysis reflects your own thinking — structured using established frameworks, sharpened, and presented clearly.

This report was produced by Ren, an AI advisor built by Renatus. It is based on information you provided during the conversation and established frameworks. It is intended to support — not replace — your own judgement. All conclusions should be reviewed before acting on them.

Renatus applies the underlying principles of established methods and credits their origin where relevant. Named frameworks, methods, and instruments are the property of their respective owners. Reference to them does not imply endorsement or affiliation.

Frameworks Guided Strategy Used

3 frameworks were used to structure your thinking:

Strategic Fit Analysis Tests whether the two parties' strategies reinforce one another in practice, or whether the partnership masks a strategic divergence.

Economic Symmetry Looks at whether the value created and the value captured are distributed in a way both parties find sustainable. Asymmetry kills partnerships over time.

Governance Pre-Mortem Names the disagreement that will eventually arise, and tests whether the governance mechanism can resolve it. Adapted from Gary Klein's pre-mortem methodology.

Back

Download

Pricing

Login

Meridian Pay × CIMB Partnership Evaluation

The partnership

Strategic fit

Economic fit

Governance & pre-mortem

Integration risk

Risks

What this Reveals

Cookie Settings