19 of 7,363 analysed fintechs name Twinfield as a connection destination for their embedded-finance stack — #21 among the destination systems this report tracks.
A destination, not a provider. Twinfieldreceives the transactions a fintech’s embedded-finance stack produces; it does not supply the accounts, cards or rails underneath. That is why it is counted here and not on the vendor leaderboards.
Unified-API providers disclosed by the same companies. These are the vendors doing the integration work — the Twinfield connection is what they sell.
Analysed companies whose own public disclosure names Twinfield as a destination.
The spellings companies used, all counted on this page.