Polygon’s Coinme Acquisition: Owning the Entry Point to Payments

SG Group View: moving a firm boundary changes the division of work

A company providing payment infrastructure acquires a function at the point where money enters its system. The question is broader than whether another intermediary disappears. How much of the work previously negotiated between businesses can now be directed within one group? If other payment firms continue to build products using those functions, a new division of work remains between the owner and its customers.

On 14 October 2026, Polygon Labs announced that it had completed its acquisition of Coinme, incorporating regulated U.S. money movement into Open Money Stack. Tazapay is among the initial adopters named. Available functions and coverage are subject to jurisdiction and configuration.^[1]

SG Group views this as a change in where payments work sits. Owning more functions can create room to alter their combination. It does not erase the value of businesses that understand customers and handle local work. The question is where the benefits of integration accrue: to the infrastructure provider’s earnings, the resources available to its business customers, or the terms offered to end users.

Connecting a function and deciding how to change it

Well-designed connections allow separate companies to present a single product. The number of screens a user sees need not equal the number of businesses coordinating behind them. To understand an acquisition’s economics, look beyond the convenience of a single interface to who can allocate people to changes in the underlying functions.

Consider developing a feature that groups payments. An external provider needs its own reason to prioritise the work. Within one group, management may consider the combined benefit to related businesses when allocating resources. A change that is difficult to justify from the supplier’s earnings alone may become worthwhile across the group. This is one difference between owning a function and connecting to it.

Internal decisions still consume resources. More demands on a shared budget can require meetings and management to set priorities. Fewer negotiations with an external supplier do not establish that the underlying work has vanished. Start by separating a change in who coordinates from a reduction in how much coordination is needed. The basics of share ownership and shareholder rights also help distinguish an interest in a company from particular operational powers.

Ownership matters where a contract cannot specify every future change

Businesses can build a dependable relationship without an acquisition by specifying functions, prices and response times in a contract. Ownership is more likely to matter when they repeatedly choose changes that were not concrete when the contract was signed. Where future uses cannot all be listed, treatment of additional work shapes the relationship.

Suppose a business customer wants to handle sales receipts and employee payments within the same system. Account presentation, payment approvals and transaction categories might all require changes. Each function can work on its own without every provider being ready to adapt to the new combination at the same time. In this example, the issue is continuing joint modification, rather than the first connection.

Bringing more joint changes inside the business may reduce repeated renegotiation. Approvals by banks and business customers do not thereby become decisions for the same company. Assessing the benefit requires specifying which parts of the changed work move inside the firm and which remain outside it.

Who funds an investment tailored to one relationship?

Software or procedures built for a particular combination of payment functions may become less valuable outside that combination. The more investment tailored to a partner is required, the more future pricing and specifications matter. Each party’s future changes can affect the other’s investment, creating questions that are difficult to settle in advance.

Separate companies can support recovery of that investment through minimum-use commitments, shared development costs or prices fixed for a period. Ownership is another possible arrangement. Considering benefits across a group can make spending worthwhile even where one function alone cannot recover it, because use of another function also grows.

An investment sensible for the group can nevertheless have unclear economics for an acquired division. If divisional performance is assessed in the same way as before, expected joint investment may fail to materialise. Ownership creates an opportunity to coordinate budgets and incentives. Whether the business uses that opportunity is a separate outcome.

Reusable combinations can spread the cost of joint development

When many business customers combine the same two functions, the connection and subsequent changes can be shared. Unlike a one-off request, that work can be reused. Having the infrastructure provider undertake it may reduce duplicated spending compared with each customer commissioning the same coordination separately.

Customer counts alone do not determine the effect. Many customers demanding entirely different changes leave less work to share. Functions with the same name can still require individual treatment when statements, approval stages or transaction scope differ. Growth in customers and growth in uses that can repay shared development are different things.

Businesses have reason to distinguish work that creates their own advantage from work they can share. Buying common functions may let them concentrate development on customer needs. The payment to the infrastructure provider then needs to be compared with work they no longer have to own and maintain themselves.

Customers’ different priorities remain inside a shared development plan

An integrated platform receives requests from multiple business customers. Deciding which to implement first becomes difficult when their interests differ. Building for a few large users and providing a function shared by many smaller users require different resources and ways of recovering costs.

An allocation that previously appeared as a negotiation with an outside provider may become part of the platform’s internal development plan. A single contact point does not ensure that a customer’s priorities will be adopted. There is a concrete choice between the benefit of common provision and room to accommodate individual circumstances.

When reading adoption cases, look beyond how many companies chose a function to where they divide shared infrastructure from their own development. A common function usable by diverse firms offers room for broadly useful investment. A service dominated by bespoke adjustments has different integration economics.

A bundle changes the unit of comparison

Buying several functions together can reduce the work of managing connections and contracts with different providers. The comparison then extends beyond each function’s listed price. Customers need to compare what they pay for a bundle with the work retained internally when buying the same scope separately.

A company that already owns half the necessary functions will assess the same bundle differently from one starting from scratch. Broad coverage may be valuable to the latter while including functions the former does not need. Whether a bundle is inexpensive depends on who is buying and what it replaces.

Modular purchasing can allow a company to retain existing work while replacing one part. Rather than declaring bundles or individual purchases universally superior, compare the customer’s current configuration with the work it expects to add.

There is no single correct allocation of shared costs

Where one development team or management function supports several products, allocation of common costs changes their apparent profitability. A product that looks weak on its own may help recover total costs when used with another. Reading integration through standalone product margins can miss this relationship.

Conversely, overall profit does not establish which additional function deserves investment. The work required to attract extra use needs to be separated from expenses already being incurred. Treating an arbitrary allocation of common costs as the cost of another transaction can either understate or overstate the value of expansion.

Customers do not need access to every internal calculation. They need to compare the purchased combination with another way of accomplishing the same work. Whether the provider’s shared costs produce a benefit for customers depends on how much of that comparison is possible and how strong the alternatives are.

Equal transaction volumes can involve different amounts of work

Transaction volume is an accessible description of scale in payments infrastructure. Equal-value transactions can nevertheless use different combinations of functions. Calling one function from an existing system and delegating work from customer registration through statement delivery place different demands on the provider.

If more transactions use common functions, extra activity may be supported with relatively little additional work. Growth in requests requiring individual inquiries and exceptions can require more staff alongside volume. Differences in prices are therefore not the only reason equal increases in activity may produce different increases in profit.

The same relationship matters to customers purchasing wholesale infrastructure. Delegating more work may reduce their own spending while widening the effect of the provider’s terms on their business. Read growth in transaction volume alongside the functions supplied and the customers using them.

Supplying infrastructure and delivering a customer product

A payment business does not lose its product simply because it uses someone else’s infrastructure. It can still design an interface, explain charges, answer inquiries and connect payments with other work. Between a common function and a customer’s business sits design undertaken by the company using the platform.

Better infrastructure may let that company offer products it could not easily build alone. Yet as more firms can buy the same function, owning access to it becomes less distinctive. Customers of the infrastructure provider may need to create value elsewhere, beyond what everyone can purchase.

A business serving end users may understand industry practices and the sequence of their work. The infrastructure provider can expand function supply without absorbing all of that understanding itself. Extending ownership of functions and extending direct sales to end customers are different strategic choices.

Specialist work remains above common functions

Consider a hypothetical payroll service. Buying payment functions does not settle what employees receive and when, which deductions apply or what statements employers require. Sharing one part of payment work does not turn every payroll service into the same product.

Customers may value a completed workflow more than a list of functions. The service business then selects infrastructure and embeds it in specialist work. Even if common functions become less expensive, scarce expertise can keep the final product’s price from falling by the same amount.

Conversely, the service business may play a smaller role where customers can combine functions directly and specialist work is standardised. Counting intermediary companies does not establish who retains earnings. The durability of the division depends on what work customers pay for and how easily they can replace it.

Common functions can move the location of specialisation

If access to a payment entry point once distinguished a service, widespread availability of the same function can shift competition elsewhere. Firms may have reason to redirect staff towards another customer problem rather than recreate functions that have become easy to buy.

This need not disadvantage specialist companies. A common platform can fill gaps and let them focus on strengths. Access to broad payment functions can also help entrants develop a deep product for a narrow industry. Integration of infrastructure and greater variety in customer-facing products can coexist.

If every customer must wait for the same change, however, the shared development plan can affect the pace of product improvement. Maintaining specialist value also requires room to alter customer-specific work. Each business needs a strategy for where shared functions end and independent changes begin.

Customer relationships depend on more than the amount of information held

When a customer-facing business and an infrastructure provider participate in the same transaction, the issue is who understands requests and can translate them into a product. Handling transaction information and understanding the customer’s business are different capabilities. Processing more transactions need not give the supplier the best understanding of why customers choose the product.

To reduce failed payments, for example, a service business might change presentation or input procedures while its infrastructure provider changes processing with a connected institution. The useful response depends on where the problem occurs. The division can create value when the customer-facing business explains circumstances and the platform turns that information into a common function.

Rights to use information, contact customers and propose products depend on actual contracts. Owning infrastructure does not establish unrestricted access to a business customer’s customer information. Confusing those relationships can either overstate or understate the competitive position of the service business and its supplier.

Turning requests into products also creates wholesale demand

Expanding infrastructure supply requires businesses that want the functions. A service company that sells products and brings organised customer needs to its supplier is both a purchaser and a source of concrete demand. Specialist firms can extend uses without the infrastructure provider selling directly into every industry.

The provider’s development and the customer’s selling efforts influence each other. Useful functions make a product easier to sell; without prospective demand, development costs are harder to recover. Expanding either side alone need not produce growth. Functions suited to a use need to connect with the work of delivering that use to customers.

Helping customers sell can involve documentation, trial arrangements and communication of planned changes as well as new features. That work differs from processing an individual transaction. The economics of wholesale infrastructure extend beyond capacity to the resources supporting businesses as they build and sell products.

Internal sales and external income answer different questions

When another division uses an acquired function, internal pricing changes reported divisional revenue and profit. If one division’s extra revenue is simply another’s extra cost, it is not new income entering the business. Moving a corporate boundary can readily change how these amounts appear.

The combination relevant to integration includes revenue from external customers, payments to outsiders and work added or removed internally. Replacing a supplier payment with internal spending does not create an equal profit. Staff, systems and management still cost money, alongside the funds invested in the acquisition.

Internal prices have a role in divisional assessment but are separate from measures of total business value. The guide to connections between the financial statements helps organise revenue categories and cash movements. Checking whether the compared scope is consistent is more useful than reading a growth rate alone.

External work remains beyond the acquired function

What can move inside the business is the acquired operation’s functions and the scope of authority used to run them. Banks, local businesses and customer companies around it do not all enter the same organisation. Work remaining before and after the acquired function constrains the effect of ownership.

An internal change may be approved quickly but remain unusable until an external connection adapts. Being able to explain related work together has value, yet does not necessarily confer control over outside decision schedules.

Identifying the stages where discretion expands helps select uses in which integration can matter. Comparing internal changes with changes that must be commissioned externally gives customers a more concrete assessment than a broad promise of completing everything within one company.

A common development plan reaches several products

Customers may nevertheless need to adapt their interfaces and procedures to use a common change. One update for the provider can generate work at every receiving company. Counting only the provider’s development hours cannot establish the benefit of sharing; the work needed to make the update usable also belongs in the assessment.

Customers able to adopt the same change at their chosen time can accommodate their own circumstances more readily. A configuration requiring simultaneous responses imposes different coordination demands.

Delegating everything and retaining part of the work

How much to delegate is a continuing choice. A young business might buy broad functionality together and bring part in-house as it grows. Another might find maintaining an established internal function too expensive and move it onto shared infrastructure.

An inexpensive bundle and the ability to reconfigure functions have separate value. Lower initial spending can coexist with restricted choices later if changing the arrangement is difficult. Modular purchasing matters not just for comparing current prices but for relocating work as the business changes.

For providers, growth need not require keeping every customer in one configuration. Allowing use to change with a customer’s development can preserve the relationship even as that business builds more itself. Looking for arrangements that benefit both sides reveals more choices than total internal production or total delegation.

Local specialisation remains in international products

An infrastructure supplier serving internationally active businesses may provide common functions across regions. Its customers can adapt explanations, commercial practices and operational requirements to local circumstances. More common functionality need not make local expertise redundant.

The same transfer function may be used with different invoicing practices, counterparty information and inquiry languages. Delegating common work can help a service business focus on local work and reduce the cost of international expansion. The size of the benefit depends on the balance between common and individual requirements.

Acquiring capabilities in one region does not establish that every use can be offered worldwide. Product coverage and local responsibilities still matter. The international significance lies less in a single authorisation or bundle erasing borders than in how businesses combine common functions with work in each jurisdiction.

Business revenue and network activity must be read separately

A business selling payment functions and a network recording transactions can earn compensation for different work. Payments to the business may cover connections, administration and support for customer companies. More processing on a network does not provide a direct calculation of that company’s profit.

Conversely, revenue earned by a broad service need not reach a particular cryptoasset in the same proportion. The relationship between those receiving business earnings and those participating in network use needs examination. Turning increased function supply directly into an asset-price forecast leaves out the mechanism distributing value.

The guide to network fees explains compensation for the recording stage. Assessing business value beyond that requires returning to which service is bought, by whom and at whose expense. Keeping transaction value, payment for functions and corporate profit separate makes the outcome of integration easier to interpret.

How the benefits of integration reach customers

Joint development and less work maintained in-house can give businesses room to build products. Strong competition for end customers may transmit that room into price or usability. Where specialised services have few substitutes, more of the benefit might remain in the service company’s margin.

The provider’s compensation and its customers’ benefits are not always a fixed pie. Making a previously impractical product viable can create revenue opportunities for both. Moving costs of existing work instead places more emphasis on bargaining over shares. Expansion of use and allocation of earnings need separate attention.

The connection to the world economy follows this route. International service businesses may expand specialised provision using common functions. That requires the further stages of product development and customer adoption. An acquisition announcement alone does not establish the scale of the resulting economic effect.

Acquisition spending and the benefit of joint operation

Even where ownership reduces external coordination, obtaining that authority requires an investment. The acquisition decision compares benefits from joint operation with costs incurred to obtain them. A favourable product assessment of easier connections cannot by itself explain the return on the entire investment.

Timing matters as well. Spending precedes income if shared development takes time to find widespread use. Comparing acquisition with continued outside collaboration requires examining both integration work and the work of maintaining the existing relationship. The alternative to acquisition should not be treated as costless or valueless.

The difference between profit and cash movements helps interpret this comparison. Short-term profit alone can undervalue development and sales work undertaken first. Equally, broad promises of future synergies do not identify which activities will eventually recover the funds.

The case for a good contract rather than ownership

A strong objection to emphasising ownership is that long-term contracts and joint-development agreements may accomplish the same purpose. Stable specifications, few changes and strong mutual incentives to expand use can allow cooperation without moving the corporate boundary.

The argument is strongest when functions can improve independently and alternative suppliers remain available. Limited investment tailored to one partner can also reduce concern over future terms. Rather than treating possession of a function as an advantage in itself, ask which joint changes a contract would struggle to support.

Frequent changes to several functions and work difficult to justify from one function’s earnings may increase the value of internal direction. The relevant evidence concerns the content of joint modifications and allocation of resources to carry them out, rather than the number of corporate names involved.

The case for combining specialist functions rather than buying a bundle

A second objection is that selecting specialist providers can produce a better-fitting configuration. Businesses with strong technical teams able to maintain combinations may gain little from a broad bundle. Integrated infrastructure is unlikely to have identical value for every buyer.

They may still choose to buy one part from a common platform. The comparison is between assembling the best functions from different providers and maintaining that combination over time. Specialist functions can look preferable on initial implementation while later coordination changes the assessment.

If the work stays stable and maintaining the combination creates enough value, separate purchases may fit. An integrated provider’s ability to serve such customers with selected functions then matters. Selling everything together and being chosen within many different configurations are different forms of competitive strength.

Three developments produce different benefits

In the first path, joint development is reused widely. The provider improves related functions and business customers build more end-user products on them. Recovery of common spending across many uses can allow the division between infrastructure and specialist firms to expand.

The second path achieves a deep fit for particular uses. Some businesses or industries may gain substantial value while others require extensive changes. Real integration benefits need not extend equally across every payment. In the third path, ownership changes but external work and internal resource constraints leave products and purchasing terms little altered.

These are scenarios without assigned probabilities. Alongside adoption counts, examine common functions, individual adjustments and product expansion. Growth dominated by bespoke work would provide weak support for the first path.

Look for specific changes in subsequent information

Future business descriptions and product material can reveal which joint changes became possible after acquisition, which functions customers can choose and how end-user products expanded. Evidence of the same function being reused in different applications is useful alongside additional adoption cases.

Price comparisons need consistent purchasing scope. Comparing a broad product with a narrow one can miss work left to the buyer. Modular availability and configurations retaining existing capabilities help explain the kinds of customers with which a wholesale platform divides work.

If acquired functions permit few changes beyond those available through outside collaboration and little work becomes reusable, the argument for substantial ownership benefits weakens. If several businesses can build otherwise difficult products on common functions, it gains support. Connecting contrary evidence to specific work makes the interpretation open to revision.

Final assessment: more ownership need not absorb every specialist

Owning a payment entry point can create value through internal allocation of related work. That value reaches markets not only by enlarging the owner’s functionality but also by enabling other businesses to build products for their customers.

The central question is which work moves inside and which expertise remains outside. Where infrastructure ownership and customer-facing businesses complement each other, an acquisition can support a new division of work rather than simply remove an intermediary.