# Message test — https://nikulipe.com/ After reading your page, only 0 of 15 personas could name a reason to pick you over a similar option. - **Page tested:** https://nikulipe.com/ - **Audience tested against:** A Senior Sales/Product decision maker at a 500-5,000-person enterprise Payment service provider company. They already use other online payment aggregators in Europe like PPRO, but not necessarily in Africa. - **Personas:** 15 simulated - **Report:** https://grader.wynter.com/r/nikulipe-taking-local-payments-to-the-next-lev-tab_Qa8 > These answers are generated by AI, scored on Wynter's B2B Message > Layers framework using behaviorally-diverse simulated personas. The > methodology is real and the critique is directional. What a simulated > persona cannot have is a live budget, a renewal coming up, or a boss > asking about this quarter. --- ## 01 · The scores Every persona answered all four questions. These are four independent proportions of the same panel, not stages of a funnel. | Layer | Question | Cleared the bar | Strength | Of those who passed | | --- | --- | --- | --- | --- | | 1. Clarity | Do they understand what you do? | 15/15 | 78% | all with reservations | | 2. Relevance | Can they tell what it solves, and who it's for? | 15/15 | 94% | 11 without hesitation, 4 with reservations | | 3. Value | Do they actually want it? | 9/15 | 56% | all with reservations | | 4. Differentiation | Is there a reason to pick you over the alternatives? | 0/15 | 22% | — | **Brand alignment** (a side metric, not one of the four layers) — 10/15, 59% strength (all with reservations). Does the page read like the company you actually are? **Fix first: Differentiation.** Earliest failing layer, walking the sequence in order — not simply the lowest score. --- ## 02 · What to change, layer by layer Ordered worst-first. Specific edits, not a restatement of the score. ### Differentiation **Put a number in the Xsolla reference.** The CPO quote asserts satisfaction with no auth-rate lift, market count or volume attached. Add the measured result and the market it happened in. *effort medium · impact high · tested against Proof next to the claim* **Name African PSP and bank customers alongside Xsolla.** A single gaming logo cannot support a claim aimed at PSPs and banks. Add customers from the segments the page addresses, or a licensed-market count if names are confidential. *effort medium · impact high · tested against Proof next to the claim* **Move direct acquirer status and owned rails into the hero.** The one line readers recognised as a real separation from resellers and aggregators sits buried below. Lead with it and say what it removes: an intermediary margin, a hop, a reconciliation step. *effort low · impact high · tested against Give a reason to choose you* ### Value **Attach auth and conversion benchmarks to the performance claims.** Operational benefits stay hypothetical without figures. Publish auth-rate uplift by market, or offer a named pilot in a priority market as the proof step. *effort medium · impact high · tested against Specifics beat superlatives* **Quantify the ops saving in the one-contract, one-API claim.** Readers accepted contract consolidation as real but could not size it. State how many country contracts, KYC processes and partner relationships collapse into one. *effort low · impact high · tested against Tie the feature to the outcome* ### Clarity **List the payment methods and schemes by name.** "Full value chain" and "coverage" claims carry no itemised content. Name the wallets, cards, bank rails and mobile money brands supported, and the countries they run in, on the page itself. *effort medium · impact high · tested against Concrete over abstract* **Add settlement timelines and FX handling near the coverage claims.** Coverage language stops short of the mechanics a payments buyer checks first: settlement currency, payout SLA and how FX is priced. State those numbers beside the claim they support. *effort medium · impact high · tested against Specifics beat superlatives* **Replace 'full value chain' with what you actually operate.** The phrase forces readers to guess which steps you own. Spell out acquiring, processing, FX and settlement in plain words, and say which parts are yours versus a partner's. *effort low · impact high · tested against Plain language* ### Brand alignment (side metric) **Disclose scale: live markets, volume or licences held.** No transaction volume, market count or regulatory status appears anywhere, which reads thin to a bank or PSP assessing counterparty risk. One line of hard numbers fixes it. *effort low · impact medium · tested against Answer the live objection* --- ## 03 · What is working ### The hero line and PSP/merchant split make the problem and audience clear within seconds Eight respondents said the headline, subhead and explicit PSP-versus-merchant segmentation identified the audience and problem immediately. Several called the segmentation well-reinforced across the page. > the hero line "Reach new markets through leading Local Payment Methods" plus the subhead naming "Payment Service Providers and Global Merchants" told me both the problem and the audience within seconds > > — Director of Product, Payments, 1001-5000 > the headline "Reach new markets through leading Local Payment Methods" plus the subhead "Designed for Payment Service Providers and Global Merchants" told me the problem and the audience in the first two lines, no hunting needed. > > — VP of Sales, Fintech, 501-1000 > It was obvious fast — the H1 "Reach new markets through leading Local Payment Methods" plus the subhead naming "Payment Service Providers and Global Merchants" told me the problem (fragmented access to local payment methods in emerging/growth markets) and the audience within seconds. > > — VP of Product, Financial Services, 1001-5000 > the hero line "Reach new markets through leading Local Payment Methods" plus the subhead "Designed for Payment Service Providers and Global Merchants" told me the problem and the audience within the first two lines > > — Senior Sales Manager, Payments, 501-1000 > the hero line "Reach new markets through leading Local Payment Methods" plus the subhead "Designed for Payment Service Providers and Global Merchants" tells you both the problem (access to local payment rails in new markets) and the audience (PSPs and global merchants) in the first two lines > > — VP of Sales, Fintech, 501-1000 > the H1 "Reach new markets through leading Local Payment Methods" plus the subhead "Designed for Payment Service Providers and Global Merchants" told me both the problem and the audience within seconds, no hunting required. > > — VP of Product, Financial Services, 1001-5000 ### One contract and one API is the value claim respondents accepted on its face Four respondents named consolidating multiple country contracts into a single API and contract as a real reduction in ops overhead, partner relationships and KYC work. Each attached a condition that it be proven. > we'd drop the need to negotiate separate acquiring/FX/settlement setups country-by-country in Africa and Europe and instead run one contract and one API — that's a real reduction in ops overhead and legal/KYC work > > — VP of Sales, Fintech, 501-1000 > If it worked exactly as promised, I'd get one contract and one API to cover LPMs across Africa and Europe instead of stitching together local acquirers and KYC processes market by market — that's a genuine operational saving if it's true. > > — VP of Product, Financial Services, 1001-5000 > fewer local partner relationships to manage, fewer separate KYC processes per jurisdiction, one settlement report instead of a dozen > > — Senior Sales Manager, Payments, 501-1000 ### Direct acquirer status and own banking rails is the only differentiator respondents… Three respondents identified direct acquiring and owned banking rails as the single concrete separation from resellers and layered aggregators. Two explicitly called it the only concrete differentiator on the page. > being the direct acquirer on their own banking rails means fewer hops, fewer parties that can fail, and cleaner reconciliation, which matters when I'm comparing settlement risk. > > — Head of Sales, Financial Services, 501-1000 > The one concrete differentiator I'd flag is "We are the direct acquirer of each payment scheme and handle money flow on own banking rails: from processing to local collection and currency conversion (FX) to centralized settlement" > > — VP of Product, Financial Services, 1001-5000 --- ## 04 · What the personas said ### Coverage and 'full value chain' claims collapse without named schemes, methods… Nine respondents flagged the same gap: repeated coverage and value-chain language with no itemized payment methods, scheme names, market counts, FX rates, settlement timelines or flow mechanics. One called the missing schemes list a fatal weakness. > What's still missing is proof: which specific payment methods, what the actual settlement timelines and FX rates look like, and a case study with numbers rather than a generic Xsolla quote. > > — Head of Sales, Financial Services, 501-1000 > I'd still want to know their actual settlement volumes and which specific PSPs beyond Xsolla are live on this before I'd trust the "we handle everything from FX to settlement" claim. > > — VP of Sales, Fintech, 501-1000 > What would rule it out, or at least push me to a competitor, is the total absence of a coverage list or scheme names on this page — "leading Local Payment Methods" is repeated three times but never itemized > > — Director of Product, Payments, 1001-5000 > "full value chain" and "leading" are doing a lot of work without naming a single scheme, country, or step in the flow, so I can't tell if it's marketing gloss or an actual capability. > > — Senior Sales Manager, Payments, 501-1000 > the vague bit was "we cover the full value chain" and "handle money flow on own banking rails" — those phrases sound impressive but don't tell me which schemes, which countries, or what settlement actually looks like > > — Director of Product, Payments, 1001-5000 > What would rule it out against competitors is the total absence of a schemes list or coverage map — "we cover the full value chain" and "access a large number of leading Local Payment Methods" never names a single payment method or country > > — Senior Sales Manager, Payments, 501-1000 > I'd still want a concrete example of the actual settlement flow before I trust the "we cover the full value chain" line > > — VP of Sales, Fintech, 501-1000 > "direct acquirer of each payment scheme" and the market-size stats (1.5bn population, 50% of e-commerce via LPMs) are asserted with no source, so I'd want proof points before taking the coverage claims at face value. > > — VP of Product, Financial Services, 1001-5000 ### The Xsolla quote is the only proof on the page and it is not enough Six respondents said the single named Xsolla CPO reference gives a minor credibility nudge but carries no numbers and stands alone. Without more logos and coverage or conversion data they could not rank the offer against competitors. > The Xsolla customer quote naming a real, recognizable company and Anton Zelenin by name is the one thing that would nudge me toward taking a call — a named reference in gaming payments is harder to fake than generic praise. But it's a single quote with no numbers attached > > — Director of Product, Payments, 1001-5000 > But it's a single logo, and the "Trusted by industry leaders" line right above it has no other names attached, so it doesn't clear the bar on its own. > > — VP of Sales, Fintech, 501-1000 > What would rule it out against competitors is the total absence of a schemes list or coverage map — "we cover the full value chain" and "access a large number of leading Local Payment Methods" never names a single payment method or country > > — Senior Sales Manager, Payments, 501-1000 > a competitor with a published scheme list or uptime/settlement numbers would beat this on the shortlist > > — Senior Product Manager, Fintech, 1001-5000 > The Xsolla quote is the one thing that would nudge me toward a first call rather than closing the tab — a named, credible reference customer in a specific vertical (gaming payouts) with a specific pain point > > — Senior Product Manager, Fintech, 1001-5000 ### The absence of scale evidence and any African PSP or bank reference undercuts credibility Three respondents noted no transaction volumes, live market count or funding is disclosed, no African PSP or bank customers are named, and the sole reference comes from gaming rather than financial services. ### Respondents cannot size the value without settlement, FX, auth and conversion numbers Five respondents said the operational benefits stay hypothetical until backed by specific LPMs, countries, FX benchmarks, scheme coverage and settlement SLAs. One would require a pilot in a priority market before believing auth and conversion claims. > the promise is worth a meeting, but only to pressure-test the mechanism: which payment methods are actually live in the markets we care about, what settlement timelines and FX margins look like > > — Head of Sales, Financial Services, 501-1000 > But "worked as promised" is the catch: I've been burned before by a vendor claiming single-integration simplicity that turned into more reconciliation headaches than it saved. > > — Director of Product, Payments, 1001-5000 > "worth a meeting" hinges on specifics they haven't given me: which LPMs and countries exactly, settlement timelines, and some FX/conversion benchmark versus incumbents > > — VP of Product, Financial Services, 1001-5000 > A pilot in one priority market — say Nigeria or Poland — showing auth/conversion rates on their rails beating or matching our current local processor, with real settlement timing > > — Director of Product, Payments, 1001-5000 > there's nothing on this page — no list of actual payment methods, no coverage %, no approval/success rates, no settlement timelines — that lets me size the "what changes" number > > — Senior Product Manager, Fintech, 1001-5000 ### The tone reads correctly B2B but the words stay generic marketing language One respondent described the tone as direct and appropriately B2B while judging the underlying messaging generic. > The tone is fine for that audience — direct, no fluff about "empowering journeys" — but it's still marketing-brochure generic ("we cover the full value chain," "simple onboarding") > > — Director of Product, Payments, 1001-5000 --- ## 05 · The hardest read An adversarial pass over the findings. Every claim below was checked against the panel's own answers; unsupported ones were dropped. - **The page's central coverage promise is unbuyable — nine of fifteen could not verify the one thing being sold.** *(high)* Nine respondents flagged repeated coverage and value-chain language with no schemes, market counts, FX rates or settlement timelines; one called the missing schemes list fatal. A payments page that omits payments specifics forfeits its core claim. - **Clarity is being mistaken for persuasion: the page communicates who it is for and then gives them nothing to act on.** *(high)* Eight respondents grasped the problem and the PSP/merchant split within seconds, yet nine hit a coverage evidence gap and five could not size the value. Fast comprehension only accelerates arrival at an empty proof section. - **The proof stack is one quote deep, and it comes from the wrong industry.** *(high)* Six respondents said the single Xsolla CPO reference carries no numbers and stands alone; three noted no African PSP or bank customers are named and the sole reference is gaming, not financial services. Nothing corroborates the offer. - **Every accepted value claim is conditional, so the page converts nobody without a pilot.** *(high)* Four respondents credited one contract and one API as real ops reduction but each attached a proof condition, and one demanded a pilot in a priority market before believing auth and conversion claims. Belief is deferred, not won. - **The page rests its entire competitive case on a single line about direct acquiring.** *(medium)* Three respondents identified direct acquirer status and owned banking rails as the separation from resellers, and two called it the only concrete differentiator present. One removable sentence carries the whole positioning. - **Competitors cannot be ranked against this page, which means the buying decision stalls rather than tilts.** *(medium)* Six respondents said that without more logos and coverage or conversion data they could not rank the offer against competitors, and three noted no transaction volumes, live market count or funding is disclosed. Nothing forces a comparison in Onafriq's favour. --- ## 06 · Who answered | # | Role | Industry | Company size | | --- | --- | --- | --- | | 1 | Head of Sales | Financial Services | 501-1000 | | 2 | Director of Product | Payments | 1001-5000 | | 3 | VP of Sales | Fintech | 501-1000 | | 4 | VP of Product | Financial Services | 1001-5000 | | 5 | Senior Sales Manager | Payments | 501-1000 | | 6 | Senior Product Manager | Fintech | 1001-5000 | | 7 | Head of Sales | Financial Services | 501-1000 | | 8 | Director of Product | Payments | 1001-5000 | | 9 | VP of Sales | Fintech | 501-1000 | | 10 | VP of Product | Financial Services | 1001-5000 | | 11 | Senior Sales Manager | Payments | 501-1000 | | 12 | Senior Product Manager | Fintech | 1001-5000 | | 13 | Head of Sales | Financial Services | 501-1000 | | 14 | Director of Product | Payments | 1001-5000 | | 15 | VP of Sales | Fintech | 501-1000 | --- ## 07 · Before you act on this The methodology is real, and the critique is directional. What a simulated persona cannot have is a live budget, a renewal coming up, or a boss asking about this quarter. **Validate anything you're betting on with real ICPs who are actually in-market.** Being wrong is more expensive than you think. Finding out is cheaper than you'd guess. Wynter runs message testing with verified B2B professionals — trusted by HubSpot, RingCentral, Shopify, Cognism, Paddle, Veeam, Rippling and Miro. This report is kept for 60 days from 2026-08-26, then deleted along with the personas and their answers.