Credit denial wins games when it creates a scoring or access window. Making an opponent poor is not enough by itself. The useful question is whether the attack stops the Corp from defending a server, prevents the Runner from completing a run, consumes clicks needed for board development, or makes another threat suddenly credible.
That distinction keeps economic pressure grounded in tempo. If you spend three clicks and several cards to remove credits that your opponent replaces with one efficient economy action, you probably traded down. If one run forces the Corp to rez expensive ice and leaves a central server exposed, the same apparent exchange may produce the access that decides the game.
Treat credit denial as a means of changing available decisions. Then ask what you can accomplish before the opponent rebuilds.
Credit denial is several different kinds of pressure
“Credit denial” is strategy vocabulary, not a defined rules term. It can describe direct credit loss, forced spending, taxation, trace pressure, or the exploitation of a known credit threshold. Those mechanisms may produce a similar board state, but they interact with the rules differently.
| Pressure type | What happens | What you are trying to gain |
|---|---|---|
| Direct loss | Credits leave a player’s credit pool | A temporary inability to pay important costs |
| Forced expenditure | The opponent pays for runs, rezzing, traces, trashing, or tag removal | Tempo plus a narrower range of available plays |
| Click pressure | The opponent uses basic credit actions or economy cards to recover | Time for scoring, setup, or additional accesses |
| Threshold pressure | A visible total falls below the amount needed for a specific line | A scoring, running, or bluffing window |
| Economy removal | A card producing future credits is trashed or disabled | Reduced recovery or weaker long-term efficiency |
Credits in each player’s pool are open information. Pool credits can pay costs and contribute to traces, but hosted credits follow the permissions on their cards and are not removed by effects that make a player lose credits. Recurring credits also replenish at the beginning of their controller’s turn rather than accumulating indefinitely. Direct pool loss is therefore much stronger against an opponent holding conventional credits than against one whose economy is distributed across hosted or recurring sources. The Netrunner Comprehensive Rules provides the exact distinctions.
Both sides can also spend a click to gain one credit. That action establishes an important baseline: economic pressure can force recovery, but it cannot permanently prevent a player from acting. Its value comes from making those recovery clicks replace installs, draws, advances, runs, or other productive actions. This is why economy density in deckbuilding affects both sides of the denial equation. A deck with efficient, redundant economy is harder to keep below a meaningful threshold.
Runner denial should attack the Corp’s next decision
The Runner often pressures the Corp indirectly by making it pay to defend. The Corp normally rezzes ice as it is approached during a run, so an unrezzed server represents a future expense rather than a completed defense. A low Corp credit total can therefore create a rez-pressure window, although it does not tell the Runner what the facedown card is or how much it costs.
Before making a denial run, compare two outcomes. First, what must the Corp spend if it defends? Second, what becomes vulnerable after that spending? Forcing an expensive rez is useful when it opens another server, delays an agenda score, weakens a trace threat, or makes repeated runs affordable. It is less useful when the rezzed ice permanently secures the only server you can profitably attack.
This is where understanding ice and icebreaker costs matters. A run can be economically favorable for the Corp even when it spends more credits in the moment. The Corp may be buying a durable barrier while the Runner pays temporary breaker costs on every later encounter. Count future costs, not just the dramatic pile of credits returned to the bank.
A useful Runner heuristic is to identify a threshold before acting: “If the Corp falls below this total, I can challenge the remote and still threaten a central.” Without that follow-up, the Runner may merely help the Corp turn liquid credits into a stable board.
Corp denial works by making the Runner’s plan incomplete
The Corp usually attacks Runner economy through taxing servers, additional run costs, traces, tags, resource pressure, or direct credit-loss effects. The goal is not necessarily to reduce the Runner to zero. It is to leave the Runner unable to assemble all parts of a successful turn: reaching the server, breaking the ice, surviving consequences, and converting access into points.
Tags illustrate how separate costs can compound. Removing a tag costs the Runner one click and two credits. While the Runner remains tagged, the Corp can spend one click and two credits to trash a Runner resource. The important strategic question is not simply whether a tag landed. It is whether clearing it disrupts the Runner’s next turn, or whether floating it exposes economy or another essential resource.
Traces create another visible contest. The Corp openly spends credits to increase trace strength before the Runner decides how much to spend establishing link strength. A trace can therefore extract credits even when its effect does not resolve, but only if the threat is serious enough that the Runner chooses to contest it. An irrelevant trace is not denial; it is an invitation for the Runner to keep their money.
Direct loss can produce a larger immediate swing but remains conditional. Bigger Picture, for example, requires a tagged Runner and can remove tags, make the Runner lose five credits for each tag removed, and give the Corp credits equal to the amount lost. Its ceiling looks impressive, but the Runner must have tags and pool credits available to lose. Hosted credits are not swept away by that loss effect.
Denial matters only if you convert it
Economic pressure has a short shelf life. After creating a shortage, the active player needs a conversion plan. For the Runner, that usually means accessing cards, trashing a key piece of economy, forcing another rez, or threatening more than one server. For the Corp, it may mean advancing an agenda, establishing a taxing remote, landing a consequential trace, or forcing the Runner to rebuild instead of running.
Measure the line in clicks as well as credits. Suppose a Runner spends a click and a card to make the Corp poorer, but the Corp recovers with one efficient operation and continues scoring. Little changed. If the same action forces the Corp to spend two clicks recovering while a central remains vulnerable, the Runner may have purchased both time and access.
The same reasoning applies in reverse. A Corp that spends its whole turn and several cards attacking the Runner’s wallet may surrender central-server pressure. The Runner can sometimes accept being poor if the Corp has also become too slow or too exposed to exploit it. The larger contest between Corp time and Runner access is covered in what each side is trying to accomplish.
Watch for economy that your attack does not touch
A visible credit total is important, but it is not the entire economy. Hosted credits may be protected from direct credit-loss effects, while recurring credits return at the beginning of their controller’s turn. Some economy also exists as installed cards, draw capacity, or efficient events and operations waiting in hand. Denial plans become unreliable when they count only the pool and ignore how quickly the opponent can reconstruct it.
Bad publicity now requires similar care. Under the March 2, 2026 rules update, bad-publicity credits enter a separate fund at the beginning of each run. They are not part of the Runner’s credit pool and return to the bank when the run ends. A Corp assessing whether the Runner can afford a run must therefore include that temporary fund without treating it as ordinary pool money. The detailed timing is covered in the guide to the 2026 bad-publicity rules.
Common denial mistakes
- Attacking credits without naming the payoff. If you cannot identify the score, access, trash, or tempo window you gain, the line may be busywork.
- Counting gross loss instead of net investment. Spending a card, influence, clicks, and credits to remove a slightly larger number can still be unfavorable.
- Ignoring recovery structure. Recurring, hosted, and highly efficient burst economy can make a low pool total misleading.
- Forcing the wrong rez. The Corp may be happy to convert credits into ice that taxes every future run.
- Overcommitting while behind on points. A denial engine that takes several turns to matter may not answer an immediate scoring or access threat.
- Assuming archetype labels settle the question. A “denial deck” still needs draw, economy, pressure, and a way to score or steal agendas.
Build denial as a supporting plan, not a collection of annoyances
During deckbuilding, start with the normal plan. What server does the Runner expect to attack, or what scoring window does the Corp expect to create? Add denial pieces that make that plan cheaper or more reliable. Redundant pressure is valuable when its components remain useful outside the perfect combination; narrow cards become dangerous when they need tags, exact credit totals, and a second payoff card before doing anything.
Legality also matters because the available denial tools change with formats and balance updates. Null Signal identifies Standard as its flagship organized-play format and maintains current card pools, rotation information, and balance changes on its supported-formats page. Check individual examples against the format you intend to play rather than carrying an old decklist forward unchanged.
Balance decisions can also reveal how denial is evaluated in the wider game. Null Signal’s Standard Balance Update 26.08 described credit denial as one of the Runner’s fundamental ways to pressure the Corp, alongside trashing key cards and multi-access. That framing is useful: denial is one pressure axis, not a complete win condition on its own. The same balance update also records the ban of Méliès U in Standard effective August 1, 2026, reinforcing why current legality checks belong in the deckbuilding process.
Use the window test
Before committing to credit denial, ask four questions: What exact resource am I attacking? How much does the line cost me? Which opposing action becomes unavailable? What will I do before that action becomes available again?
If the final answer is “nothing yet,” save the denial piece or take a more productive action. If the answer is “score this agenda,” “make two meaningful accesses,” or “force the last affordable rez and attack elsewhere,” the economic pressure has a job.
That is the core of effective Netrunner credit denial strategy: do not chase poverty as a scoreboard. Attack the credits that connect your opponent’s current position to their next important play, then use the interruption immediately.
Frequently Asked Questions
Does credit denial require reducing the opponent to zero credits?
No. The relevant target is the threshold below which the opponent cannot complete an important run, rez, trace, recovery action, or scoring line.
What is the difference between direct credit loss and taxation?
Direct loss removes credits from the credit pool. Taxation instead makes the opponent spend credits on costs such as runs, rezzing, traces, trashing, or tag removal.
Can credit-loss effects remove hosted credits?
No. Hosted credits are not part of the credit pool and follow the spending permissions on their cards.
Why are recurring credits resilient to denial?
Recurring credits replenish to their printed amount at the beginning of their controller’s turn rather than accumulating. A low pool total can therefore understate the opponent’s available economy.
When is forcing the Corp to rez ice actually useful?
It is useful when the expense opens another server, delays a score, weakens another threat, or makes follow-up runs affordable. It can be a poor trade when the Corp simply buys a durable defense.
How do tags create economic pressure on the Runner?
Removing a tag costs the Runner one click and two credits. Remaining tagged also lets the Corp spend one click and two credits to trash a Runner resource.
Can a trace count as credit denial if its effect fails?
Yes, if the threatened effect is important enough that the Runner spends credits to contest it. An irrelevant trace creates no pressure because the Runner can decline to spend.
How do bad-publicity credits affect denial calculations?
Under the March 2, 2026 rules update, they enter a separate fund at the beginning of each run, can be spent during that run, and return to the bank afterward. They are not ordinary pool credits.
How should credit denial fit into deckbuilding?
Use it to support a coherent scoring or access plan, not as a collection of narrow annoyances. Check current format and balance information before relying on particular cards.