Summary

  • Stripe supports card-data transfers to another processor but excludes payment credentials saved through Link.
  • A shopper's ability to reuse a wallet across stores is different from a merchant's ability to carry the same payment experience to another provider.
  • Orchestration, currently in private preview, also excludes Link. Routing transactions and exporting credentials require separate checks.

A returning customer is a lovely thing to have until someone asks them to become a new customer again at the payment form.

That is one possible piece of work hidden inside a processor switch. Procurement has found a better rate. Engineering has arranged the data transfer. Then the shop needs some buyers to provide payment details again, and the savings project acquires a customer-service budget.

Stripe's export documentation gives this problem a precise boundary. It provides a route for moving card data to another processor, while excluding credentials saved through Link. A merchant needs to know which payment paths that leaves intact. Counting customer records is an excellent way to answer a different question.

Familiar somewhere else

Link's attraction is that familiarity can arrive before the customer relationship does. According to the Checkout guide, a logged-in Link user can have information filled in even when it was originally saved at another business's checkout.

For a young shop, that is a useful head start. It can give a first-time buyer some of the ease normally associated with a return visit. The shopper does less repetitive work. The seller benefits from a habit it did not have to build alone.

But the habit belongs to a relationship that spans shops. The merchant has made a sale using a shared service. It has not thereby acquired a transferable copy of every credential that helped the sale happen. The customer can be new to the shop and thoroughly familiar to the wallet.

Stripe's Link guide describes recognition, authentication with a one-time code, and the filling of payment and shipping details. The shopper also has an account to manage. This is a person choosing a useful wallet, rather than an item of shop equipment to be loaded into the removal van.

Two kinds of movement follow. The buyer moves between stores and keeps a familiar way to pay. The seller moves between processors and wants to keep a familiar way to collect. Success in the first direction does not settle the second.

The work that is missing from the quote

Consider a hypothetical shop with several kinds of returning buyer. Some have ordinary card data available for transfer. Some chiefly use Link. Some of those people already have another suitable payment method. The groups overlap; transactions are not a headcount of customers who need help.

This is where an exit budget becomes useful. If a suitable alternative is already available, the transition may be modest. If fresh input is required, the shop must decide when to ask, how to explain the request and what to do with a purchase that stops halfway through. A file-transfer job becomes a checkout-design and support job.

The public documents examined here contain no merchant cohort or results after customers re-enter details; those measurements would determine the cost. Treating every Link user as a lost sale invents an answer. Treating the complete customer list as proof of effortless continuity avoids finding one.

The work can be small or concentrated among customers the shop particularly wants to retain. Either way, it needs an owner. The receiving system may have all the expected records while the people responsible for the next purchase still have unfinished tasks.

This is the commercial bill for replacing convenience. A service saved effort during use. Replacing it can put some effort back on the buyer or the business. The new processing rate belongs in the calculation, alongside the labour required to enjoy it. Procurement should not get to declare victory while support is still learning the script.

More routes, different luggage

Stripe also offers Orchestration, which routes payments among supported processors and enables certain retries through an alternative. At the time of checking, it remains in private preview and its supported scope excludes Link.

That makes the distinction between routing and departure particularly useful. Sending a transaction to another processor is one capability. Exporting saved credentials for use outside the existing service is another. A business can gain useful processing options without having solved every part of a future move.

The feature-support table also lists network-token support for some processors. A blanket claim that tokens cannot move would obscure the actual Link restriction. The particular credential and payment route matter more than a loose technical label.

The same document describes optional error protection. A payment requesting an unsupported feature can be routed to Stripe instead of the processor originally selected. A failover whose original processor was Stripe has a separate exception to avoid a duplicate attempt there. The intended route and the eventual route therefore deserve separate attention.

A diagram containing several processors is easy to buy. Evidence that the shop's relevant payments can actually use the alternatives takes more work. The latter is what gives the merchant options when a contract comes up for renewal.

A useful service can still need an exit budget

A merchant may reasonably choose to keep Link. A small shop might value an easier purchase today more than extensive preparations for a future move. A business combining several operations might put a higher price on an alternative it has already tested. Different shops can make different purchases intelligently.

The accounting error is to book the wallet's convenience twice: first as a benefit supplied by the service, then as an independent capability the merchant already owns. The first can be valuable throughout the relationship. The second requires evidence about the data and payment paths available after a change.

Link helps a buyer feel at home in a shop they have never visited. The merchant changing processors has its own welcome to prepare. The next completed purchase is a better test of that preparation than the notification that a file has arrived.