A lot of embedded finance programmes rest on a description. The platform is a technology provider. The bank is the regulated party. The customer relationship is somehow shared.
The description is convenient. It is also frequently at odds with how the programme actually runs day to day.
Behaviour beats labelling
If the platform decides who is onboarded, sets pricing, owns the customer relationship and instructs the movement of value, its role in substance is not the role of a vendor — whatever the contract says, and depending on the facts of the arrangement.
This is not a drafting technicality. It decides who carries the consequence when volumes grow, when a state takes an interest, or when the partner bank exits the programme.
Design the role deliberately
The alternative is to choose the role rather than inherit it: vendor, programme manager, or permission holder, each tested against the same commercial objective, each with its cost and dependency profile written down.
Platforms that made that choice consciously tend to come through partner-bank diligence and re-papering exercises far better than platforms discovering their own structure during the review.
For us this is why the product has to model the institution and the programme, not simply the rulebook. The rule is rarely the ambiguous part. The configuration is.