When DOGE Reached the Treasury's Payment Systems in February 2025

The most powerful computer system most Americans have never heard of lives inside an office called the Bureau of the Fiscal Service. It is not glamorous. It runs on code, some of it decades old, written in languages few young programmers learn anymore. But when a Social Security check lands in a retiree's bank account, when a tax refund arrives, when a veteran's disability benefit is paid or a contractor gets paid for paving a federal highway, the money almost always moves through these systems. For generations, the people who ran them were career civil servants whose names appeared in no headlines, and whose professional creed could be summed up in one idea: if Congress said to pay it, it gets paid. At the end of January 2025, the senior career official in charge of those systems, David Lebryk, a Treasury employee for decades, left the department after a dispute over whether a new team from Elon Musk's Department of Government Efficiency should be given access. Within days, the team was in.

In short: In early February 2025, staff from the Department of Government Efficiency gained access to the Treasury payment systems that disburse most federal money, prompting lawsuits from unions, retirees and states over privacy and over who decides which payments go out. Courts limited the access for a time, and the episode exposed how much of the government's integrity rests on rules and norms rather than locks. The deeper question was never about the code; it was about whether anyone in the executive branch may quietly stop a payment Congress has ordered.

The plumbing nobody thinks about

To understand why this mattered, start with what the Fiscal Service does. Federal agencies decide who is owed money: the Social Security Administration determines a retiree's benefit, the Department of Veterans Affairs approves a disability claim, the Defense Department signs a contract. Those agencies then send payment files to Treasury, and the Fiscal Service actually pushes the money out the door, trillions of dollars every year, to tens of millions of people and businesses.

That arrangement builds in a deliberate separation. The agencies decide eligibility; Treasury executes. Treasury's payment staff are not supposed to second-guess whether a grant is wise or a contractor deserving. Their job is to verify that the payment is properly certified and to send it. That narrowness is a feature. It means no single official sitting at the switchboard can decide, on his own, that some lawful payment will not be made.

The systems also hold enormous amounts of sensitive information: Social Security numbers, bank account and routing numbers, home addresses, the names of people who receive particular benefits. The Privacy Act of 1974, passed after Watergate revealed how government files could be abused, restricts who inside the government may see such records and for what purpose. Access is meant to be limited to people who need it for their jobs, with training, background checks and logs.

The Fiscal Service in its current form is young, created in 2012 when Treasury merged two older bureaus, one that handled payments and one that handled the public debt. Its work, though, is as old as the republic: the first Treasury secretary, Alexander Hamilton, built the department around the idea that the government's credit depended on paying what it owed, on time, every time. Bond markets, foreign governments and ordinary families all rely on that reliability. A missed or blocked payment is not just a bookkeeping glitch. It is a small breach in the most basic promise the government makes.

How DOGE got in

The Department of Government Efficiency was created by an executive order on January 20, 2025, which renamed and repurposed an existing office, the United States Digital Service. Its stated mission was to modernize federal technology and cut waste. In practice, its small teams, many of them young engineers recruited from Musk's companies and the tech industry, fanned out across agencies seeking access to personnel, contracting and payment data.

At Treasury, according to news reports and later court filings, the request for access to the payment systems met resistance from Lebryk, who had served under presidents of both parties. He was placed on leave and then announced his retirement. Treasury Secretary Scott Bessent approved access for a DOGE team that included Tom Krause, a software executive, and Marko Elez, a young engineer. The department told members of Congress that the access was limited to reviewing the systems and that DOGE staff would not alter payments.

Musk, meanwhile, was posting about the work in far broader terms. On his social media platform he described the team as shutting down payments he considered improper, including payments to some nonprofit contractors. Whether or not any payment was in fact stopped by the team, the statements themselves alarmed people who understood how the system was supposed to work, because they described exactly the power the separation was designed to prevent.

Then came a run of uncomfortable disclosures. In early February, Elez resigned after a newspaper linked him to racist posts on a social media account; he was rehired days later after Musk and Vice President JD Vance publicly backed bringing him back. Later court filings acknowledged that his access had at one point been configured incorrectly, with the ability to change data rather than only read it, before the error was fixed. Treasury maintained that no improper changes were made. For critics, the admission confirmed the core worry: that the safeguards depended on configurations and promises rather than law.

The lawsuits and what they argued

Several groups went to court within days. Labor unions representing federal workers and an organization of retirees sued in federal court in Washington, arguing that giving DOGE staff access to their members' personal and financial data violated the Privacy Act and the Internal Revenue Code's confidentiality rules. A coalition of Democratic state attorneys general, led by New York, sued in Manhattan on behalf of states that receive federal funds through the same systems.

In the New York case, a federal judge issued a temporary restraining order on February 8, 2025, blocking DOGE-affiliated staff from accessing the payment systems while the case proceeded. That order drew furious criticism from administration allies, who said a judge was micromanaging the executive branch's own computers. A second judge later replaced it with a preliminary injunction that kept restrictions in place, and the court eased them in the following months as the government documented the training, vetting and security procedures its staff had completed. In the Washington case, the judge declined to issue a broad preliminary injunction, finding that the plaintiffs had not shown the kind of irreparable harm needed, while leaving the underlying claims alive.

That mixed record is itself instructive. Courts were generally reluctant to tell an agency head that his own appointees could never look at his own department's data. They were more receptive when plaintiffs could point to specific statutory protections and to evidence that normal vetting had been skipped. In June 2025 the Supreme Court allowed DOGE staff to access Social Security Administration data while a separate privacy suit continued, a signal that the justices were inclined to give the executive branch room on internal access questions.

The administration's case, stated fairly

The administration's argument deserves a full hearing, because it is not frivolous. Improper payments are real. The Government Accountability Office has reported for years that the federal government makes very large sums in improper payments annually, through fraud, error and payments to people who have died or are no longer eligible. A new administration elected on a promise to root out waste has a legitimate interest in examining how payments flow and where controls fail. And it is the president, not a career official, who is ultimately responsible for running the executive branch. If a career employee could veto a cabinet secretary's decision about who reviews a system, the voters' choice of president would mean less.

There is also a fair point about modernization. Many federal systems are old, poorly documented and expensive to maintain. Bringing in engineers who can read the code and propose improvements is something reformers in both parties have called for.

The answer is that every one of those goals can be pursued through the procedures that already existed. Agencies have inspectors general whose job is to hunt fraud. Treasury itself runs a program to stop payments to dead people and ineligible recipients. Modernization projects can be staffed with vetted employees who complete security training before they touch production systems. What alarmed critics was not that someone was looking for waste. It was the combination of speed, unclear legal authority, skipped vetting and public statements about cutting off payments, all on systems that hold the private records of most Americans.

The real question: who may stop a payment?

Strip away the drama, and the February episode raised a constitutional question that runs through this whole era. Congress holds the power of the purse. When it appropriates money for a purpose and an agency has lawfully obligated it, the executive branch is supposed to spend it. The Impoundment Control Act of 1974 sets out the narrow procedures by which a president may propose not spending appropriated funds, and they require Congress's approval.

A payment system is where that principle becomes physical. If a person with access to the switchboard can block payments to a disfavored grantee, an entire layer of congressional power can be undone in a keystroke, with no public notice and no vote. The career officials who ran the systems understood this. Their insistence that they would execute properly certified payments, and nothing more, was a way of keeping policy decisions where they belonged: in Congress and in the accountable agencies that make eligibility decisions.

This is why the fight over Treasury access was never just about privacy, important as that is. It was about whether the most basic machinery of government would stay neutral. The same theme runs through the battles over withheld grants, the pocket rescission of foreign aid later in 2025, and the effort to shut down whole agencies. Each tested whether the rules that keep spending decisions with Congress still had force.

What changed, and what did not

Musk left his government role at the end of May 2025, and DOGE's public profile faded. Its claimed savings were disputed by outside analysts, and several of its most visible claims were corrected or withdrawn. Inside agencies, though, many of the access permissions, data-sharing arrangements and staff changes it set in motion stayed in place. Some of the people DOGE placed were reported to have stayed on in the departments they had been sent to review.

The lasting lesson is about fragility. Before 2025, it was simply assumed that no political team would be given broad access to the government's central payment systems without the usual vetting. That assumption rested on habit and professional culture as much as on law. When the habit was broken, the law turned out to be slow to respond and uncertain in its reach. Lawsuits took weeks to produce temporary orders, and those orders were narrowed as the government filed affidavits about its procedures. Meanwhile the people whose data sat in the systems, retirees, veterans, taxpayers, had no way of knowing who had looked at their records or why, and most never learned that the question had been fought over at all.

I think the right response is to write the norms down. Congress can specify in statute who may access the payment systems, what vetting they must complete, what logs must be kept and reported, and that no official may block a lawfully certified payment except through the procedures of the Impoundment Control Act. Such a law would bind every future administration, of either party, and it would protect the people whose records sit in those systems more reliably than a career official's courage did in January 2025.

What you can do

Payment systems are invisible until something goes wrong. Making them a political subject is the first step toward protecting them.

• Ask your members of Congress to put the safeguards in law. Find your representative and senators, with phone numbers, contact forms and their latest votes, and ask whether they will support legislation setting rules for access to Treasury's payment systems and the data in them.
• Watch the privacy fights as they reach the courts. The Court watch page follows the Supreme Court's opinions and its emergency docket, where several of the 2025 cases about agency data ended up.
• Comment when agencies change how they handle your data. Changes to records systems often go through public notice; the open-comment page lists federal rules accepting comments now, with guidance on writing one.
• Keep track of the wider story. Our topic pages on the hollowing out of federal agencies and on big tech and AI gather reporting on how technology teams reshaped the government in 2025 and 2026.
• Back the groups that brought these cases. Unions, retiree groups and privacy advocates carried the early litigation; the organizations directory lists nonprofits by cause in every state.

Somewhere in the Fiscal Service, a career employee is still checking that each payment file is properly certified before the money goes out. That person is the last link between a law Congress passed and the family waiting for a deposit. The least the rest of us can do is make sure the rules protecting that link are as solid as the people who hold it.