Payment product strategy: choosing who you serve and how you win

A payment product strategy starts with a choice about who the product is for. A cross-border payment product for small exporters is a different product from a cross-border product for multinational treasuries, even though both move money across borders. The exporter needs a simple price, a fast settlement, and a clear status. The treasury needs bulk files, liquidity forecasting, and integration with its ERP. A strategy that tries to serve both with one product serves neither, because the requirements conflict at every decision. The second choice is the value proposition, which is the reason a customer picks this product instead of the alternative. In payments the value proposition is usually one of four things: price, speed, certainty, or reach. A product that promises the cheapest cross-border payment competes on price and must keep its cost base low. A product that promises settlement in seconds competes on speed and must hold liquidity in every corridor. A product that promises the payment will arrive on the date stated competes on certainty and must control the full chain. The value proposition must be one thing, not four, or the product has no identity. Positioning follows from the value proposition. A product positioned as the cheapest must be marketed on price, priced transparently, and built to run at scale. A product positioned as the most certain must be marketed on reliability, priced at a premium, and built with the controls that deliver certainty. The mistake most payment products make is to claim all four positions at once, which means the marketing promises what the operations cannot deliver, and the first exception destroys the customer's trust. The competitive landscape in payments is unusual because the competitors are also the infrastructure. A bank that offers a cross-border payment product competes with the fintech that uses the bank's own correspondent network. A card scheme competes with the account-to-account payment that bypasses it. A product strategist must therefore map not only the direct competitors but the infrastructure dependencies, and must ask what happens to the product if a correspondent withdraws, a scheme raises its fee, or a regulator mandates a new rail. Segmentation is the practical tool. A payment product team segments by customer type, by corridor, by payment size, and by urgency. Each segment gets its own price, its own service level, and its own onboarding. A 500 euro payment from a freelancer to a supplier in Poland is not the same segment as a 5 million euro payment from a manufacturer to a supplier in China, and the product must treat them differently, with different screening, different cut-offs, and different status information. The segmentation must be written down, because every later decision refers to it. The strategy document is the deliverable. It states the target customer, the value proposition, the positioning, the competitive map, the segmentation, and the three year ambition. It also states what the product will not do, which is as important as what it will do. A product that will not serve sanctioned corridors, will not offer credit, or will not support a particular rail has a clear boundary, and the boundary protects the team from scope creep. The strategy must be approved by the product owner, the risk owner, and the technology owner together. For a business analyst, the strategy is the source of every requirement. A requirement that cannot be traced to the strategy is a requirement that should be challenged. The acceptance criteria for a strategy document must include a test where a proposed feature is checked against the target customer and the value proposition, and rejected if it does not serve them. Last reviewed 7 November 2026. Further reading: Michael Porter, Competitive Strategy; Clayton Christensen, The Innovator's Dilemma; the Payment Systems Regulator market reviews; McKinsey Global Payments Report 2024.