Explain It in 30 Seconds
A company can need information from a customer's bank without being that bank.
It might verify the account receiving a payout, help the customer understand transactions or provide a way to pay from the account.
Tink supplies supported connections and tools for those jobs.
The bank continues to maintain the account. The customer completes the required authorization. The business uses the resulting capability within its own product.
Tink's commercial role is reusable infrastructure between those participants, rather than a new bank account that every end user must open.
Founded in Stockholm in 2012, it developed that business before becoming part of Visa. [S60]
Why Account Connectivity Is Different
A bank relationship is not an open database
A financial application cannot treat every customer's account as freely available information.
Access depends on the relevant permission and authentication process.
That changes the product problem.
The platform must help the customer complete a permitted journey and return useful information to the application.
Verification and payment are separate jobs
An account-ownership check can help establish who holds a supported account.
It does not itself instruct a payment.
Payment initiation lets an authorized user start a supported transfer, but a valid instruction is not the same thing as every recipient having received usable money.
Tink presents Account Check and Pay by Bank as distinct capabilities. [S104][S105]
A business can use one without needing the other for every transaction.
Coverage must fit the actual task
A connection is commercially useful when it supports the customer's institution, market and required function.
An aggregate bank count cannot show that every proposed application works.
The real purchase decision concerns the specific user journey and the work the client would otherwise maintain.
The Deal
Visa announced the Tink agreement on June 24, 2021.
The announcement described €1.8 billion of total financial consideration, including cash and retention incentives. [S99]
The acquisition completed on March 10, 2022. [S11]
Visa's acquisition note describes 100% ownership and approximately $1.9 billion in cash; its allocation table totals $1.863 billion. [S16]
The announced euro convention and the later dollar accounting disclosure are not amounts to add together.
The transaction bought Tink, not the financial institutions connected through its platform.
What Visa Bought
Technology and maintained connections
Tink supplied a platform for accessing permitted financial data and initiating supported payments.
The value included the ability to keep those connections useful as banks and authentication requirements changed.
A list of endpoints without reliable maintenance would be a much weaker asset.
A client-facing operating business
The acquisition also brought customer relationships and an experienced organization.
Clients were buying a capability for their own financial products.
They were not necessarily seeking more card transactions, so Tink needed a proposition that made sense independently of Visa's card brand.
A different position in the payment journey
Account information can be useful before a payment happens.
A bank-payment initiation can also be useful without becoming a card purchase.
Those roles extended the kinds of problems Visa could help institutions solve.
They did not make every account balance or transfer principal revenue for the group.
Connecting Authentication, Data and Payment
The account-check journey
Tink's displayed Account Check flow separates consent, bank selection, authentication and account selection.
The result can include supported account identifiers and holder information. [S104]
For an illustrative payout-onboarding journey, a marketplace wants to identify the account to which a seller will later be paid.
The seller completes the bank connection. The marketplace uses the supported result in its onboarding decision.
That can replace some manual entry and checking.
It does not establish that every item sold was legitimate, or perform all the marketplace's broader controls.
The payment journey
For a supported Pay by Bank flow, the customer chooses the bank and completes the required authentication and payment authorization. [S105]
The commercial application can present that route inside its own checkout or account-funding experience.
The visible product therefore belongs to the client, while Tink supplies part of the enabling infrastructure.
A documented partner example
Tink's October 2022 Adyen announcement describes UK pay-by-bank support building on an existing Account Check relationship for payout setup.
That is a concrete connection between two different jobs: verify details for money going out, and enable an authorized bank payment coming in. [S68]
The announcement's plans for further markets were plans at that date, not proof of every later rollout.
Why Buy Rather Than Rebuild Each Connection?
The starting asset was not only an API design.
It was an operating platform, bank connectivity, authentication work, client relationships and accumulated implementation knowledge.
Recreating those elements would require continuing work across different institutions.
Buying Tink gave Visa an existing organization addressing that problem.
Visa's broader relationships and resources could support distribution and development.
The business still had to earn client adoption. Ownership did not make unsupported banks available or remove customer-permission requirements.
Account Connectivity as Infrastructure
The application sits above the connection
A client's product can use the same kind of connection for different purposes.
Account verification helps onboarding. Transaction information can support a financial view. A supported payment route helps move money.
The business value comes from completing the relevant task rather than collecting the largest possible amount of data.
The platform sits between dependencies
Tink depends on bank interfaces, authentication and client implementation.
The client depends on Tink returning a useful and understandable result.
This creates continuing service work after the initial integration.
A confusing bank-authorization step can lose a customer even when the underlying connection is technically available.
The payer buys a service, not the account balance
The business customer contracts for the selected capabilities.
Money in a linked bank account remains different from platform revenue.
The economic comparison includes integration effort, ongoing operation and the quality of the customer journey, not just an advertised connection total.
What Changed After Acquisition
The completion release described Tink operating as a standalone subsidiary in the near term. [S11]
That preserved a separately identifiable organization at the transaction's starting point.
Its later platform continues to present authentication, account checks, payments and developer tools under the Tink identity. [S67]
The change in ownership therefore did not erase its original customer problem.
It gave Visa an acquired business participating in account-based financial experiences alongside the group's card and other payment capabilities.
The integration question is whether the combination makes those services easier to adopt and more useful.
It is not whether every Tink interaction can be relabeled as a Visa card transaction.
What Most People Misunderstand
“Tink owns the banks it connects.”
It supplies capabilities around supported accounts. The acquisition did not transfer the connected banks to Visa.
“Account Check sends the payout.”
Verification and the eventual money movement are different operations.
“Customer consent makes all financial data available forever.”
The service operates within the applicable permissions, supported flow and continuing requirements.
“Tink is Plaid under a different name.”
They are separate businesses. Visa's proposed Plaid acquisition did not complete.
“The acquisition value proves the platform's revenue.”
Purchase consideration is what Visa committed to obtain the business, not its annual sales or realized integration return.