A partner who embeds our payment services into their product is not buying a feature. They are entering an arrangement that runs in both directions.

We carry the upstream work the partner never sees. License maintenance, monitoring, supervisor relationships, safeguarding of customer funds, regulatory reporting. That is what makes embedding possible at all: the partner does not become a payment institution by offering payment services in their product, because the institution sits behind the surface and carries the regulated weight.

The inverse is what asks something of us in return. The partner owns the customer relationship, the product experience, the support team, the trust. Reputational events around the embedded service hit the partner first, even when the underlying mechanic is ours.

This shapes what onboarding actually is. We do not treat partner onboarding as customer acquisition. We treat it as a multi-year shared accountability that we should not enter lightly, and that the partner should not enter lightly either.

Some platforms do not pass that bar. Some do. Both outcomes are correct. The wrong outcome is to treat the question as a sales decision.

The harder reading of embedding is that the partner and the licensee are agreeing to be visible to each other's stakeholders for as long as the service runs. Regulators look through to the licensee. Customers look through to the partner. Each side has work the other side cannot do, and the work compounds when both sides take it seriously.

That is the product we are building. Not a payment rail. A relationship structure with payment services inside it.

We chose the structure that asks more of both sides, because that is the only structure that holds.