In this guide
Fintwist is now presented as Corpay Prepaid on the provider’s current consumer website. On the source-check date, the former Fintwist homepage also redirected to that site. This establishes a public branding and navigation change. It does not, by itself, establish a new card number, a different issuing bank, a changed fee schedule or a need to re-enroll with an employer. Provider: current homepage
That boundary is the important part of the change. A reader seeing a new name may reasonably wonder whether the service has moved. The next question, however, is not “Which search result looks most familiar?” It is “What instruction applies to the account I already have?” This article separates what the public evidence shows from the account changes it cannot prove.
Three kinds of change that should not be confused
A brand change affects the name used to describe a service. A navigation change affects where the provider directs a visitor. An account change affects a particular agreement, payment destination or customer record. Those changes can occur together, but one should not be inferred solely from another.
Consider a hypothetical employee who receives an email saying the program has a new name. The employee also has a payroll portal that still lists the old name. Without further information, this is not enough to conclude that payroll must be redirected. The correct next question is whether the employer or provider issued an account-specific instruction, not whether the two labels currently match.
Equally, a familiar name is not sufficient proof that an unfamiliar website is legitimate. A change in branding creates an opportunity for confusing search results and messages. Evaluate the source of an instruction before acting on it, particularly when the instruction asks for credentials or changes where wages are sent.
Why more than one name may still appear
The provider’s EmployBridge resource page still contains employer-specific material using Fintwist and Comdata terminology, alongside the newer branding notice. That is evidence that different labels coexist in public documentation, not evidence that every Comdata product is the same consumer card or that all instructions on that page apply to every employer. Provider: EmployBridge resources
Our reading of that coexistence is practical: a name can help locate a document, but it cannot determine the document’s applicability. Look for the employer program, issuing bank and actual activity covered. A page explaining one employer’s activation process should not become a universal set of activation steps merely because the familiar brand appears in its heading.
The distinction also helps when reading old articles. A historical article can accurately describe the name used at the time and still be unsuitable as a current operating manual. Before acting on an old screenshot, ask whether the provider still points to the same service and whether the screen is describing your role as a cardholder rather than an employer administrator.
What the public change does not establish
| Observation | Supported conclusion | Conclusion that needs more evidence |
|---|---|---|
| A current homepage uses a new brand | The provider publicly uses that name | Every customer has a new agreement |
| An old homepage redirects | The old entry point currently leads elsewhere | Every old deep link is safe or current |
| A resource page retains an older label | Older terminology remains in that material | The entire page is current for every program |
| A message asks for new payment details | Someone is requesting a change | The request is authorized and necessary |
The right-hand column is not a prediction that something is wrong. It identifies the information you still need. A naming update can be legitimate while a particular instruction remains unverified. Treating these as separate questions avoids both unnecessary alarm and misplaced confidence.
A verification note you can actually use
When you encounter an instruction associated with the change, record the source, the date you received it, the action it requests and the deadline it states. Then ask the employer or provider, through an established route, to confirm whether it applies to your program. Do not send the publication a card photograph or an identity document to ask whether a message is genuine.
For example, “The notice says to update a saved bookmark” is different from “The notice says to submit a new routing number to payroll.” The second changes the destination of future money and deserves its own confirmation. A legitimate-looking announcement is not a reason to copy payment details from a search result or a stranger’s screenshot.
The Federal Trade Commission advises contacting a company through a website or telephone number you already know is genuine rather than relying on a link or number supplied in a suspicious message. Use that principle to verify the instruction, not merely the logo. FTC: recognizing and avoiding phishing
Do not troubleshoot the wrong layer
A changed website name and a failed sign-in can happen at the same time without proving that one caused the other. Record whether the problem occurs before the account opens, during a verification step, or only when requesting a feature. The account-access guide uses those distinctions to make a support report more useful.
Likewise, a missing transfer is not explained simply by finding an older brand on a transaction description. Match the actual payment records first. Our paycheck guide separates the employer’s payment record from the card account’s credits and available balance. The transaction data matters more than a visual mismatch between brand labels.
There is no public evidence in the sources used here for a universal instruction to discard a card, replace an issuing bank, or change payroll details solely because the consumer website uses Corpay Prepaid. Your own account may receive additional instructions; verify those on their merits. The naming change is a starting fact, not a substitute for those instructions.
What to retain after you verify the change
Keep the confirmed service entry point and the applicable account notice in a place you can find again. Remove an obsolete bookmark only after you have established its replacement through the provider. Preserve any instruction that materially changes your payment arrangements so you can later explain when and why a change was made.
For the broader product structure, return to the Fintwist reading guide. This page owns a narrower question: how to interpret a public name change without inventing account consequences. Its source check documents the public pages consulted; it is not an inspection of private customer accounts or a guarantee that a provider will keep every URL unchanged.