Fintech Cuts Hit 7,347, and 92% Sit at Three Employers

Every layoff tracker this quarter leads with the "tech" total. Challenger, Gray & Christmas puts Fintech in its own bucket, and that bucket ran up a 305% year-over-year jump to 7,347 announced cuts through August 2026. If you source engineers and you have been filtering on "tech layoffs," you have missed the entire pool.

What Challenger's separate Fintech bucket actually contains

Fintech is its own line in Challenger's 30-industry taxonomy, assigned per announcement by analysts, and in 2026 it ran up 7,347 cuts through August, a 305% increase year over year. The Second Talent tally of Challenger's numbers is the only public read on this cohort as its own line item.

The scale of the miss for most sourcers looks like this:

Fintech's jump outpaces the tech sector's own surge by roughly six times, and it moves in the opposite direction of the all-industry number. The mechanism matters: because analysts assign the bucket per announcement (not by NAICS code), the boundary between Financial, Technology, and Fintech is fuzzy, and a Boolean that only pulls "tech layoffs" quietly drops the whole 7,347.

305%

Three employers own 92% of the cohort

Block (about 4,000), Visa (about 2,600), and Chime (about 150) together account for roughly 6,750 of the 7,347 Fintech YTD figure, or about 92%. That concentration is unusual and it is the sourcer's edge: you can build most of your target list from three alumni searches, not thirty.

The named events:

• Block, February 26, 2026: approximately 4,000 employees, roughly 40% of the workforce, cutting from over 10,000 to just under 6,000. That single event is more than 54% of the entire Fintech YTD total.
• Visa, July 2026: about 2,600 cuts, concentrated in the technology and product teams that build and maintain VisaNet.
• Chime, July 2026: about 150 jobs, roughly 10% of the neobank's workforce, announced five days before Q2 earnings on AI-efficiency grounds.

CFO Amrita Ahuja framed Block's cut in forward-looking language: "We are choosing to shift how we operate at a time when our business is accelerating and we see an opportunity to move faster with smaller, highly talented teams using AI to automate more work." Read the mechanism there. These are not underperformers. They are people cut for org shape, which means the reference calls come back clean and the outbound pitch can say so.

Then there is the pipeline behind the 7,347:

• PayPal, announced May 5, 2026 by CEO Enrique Lores: about 4,760 jobs, roughly 20% of the workforce, phased over two to three years. Most of this has not yet rolled into the YTD figure.
• Mastercard: about 4% of the global workforce earlier in 2026.
• Robinhood: 10% headcount reduction announced June 2026.
• Coinbase: open postings dropped from roughly 300 to around 133 in under 90 days in early 2026, a leading indicator of the next contraction.

Between the announced cuts already in the bucket and the PayPal pipeline still landing through 2027, this is a two-year sourcing window, not a one-quarter opportunity.

Why title-based sourcing fails on payments engineers

"Payments Engineer" as a title search misses more than 95% of the actual pool. In Refolk's index, only 11 people in the US publicly title themselves "Payments Engineer," and the top employers among them include Apple, Umpqua Bank, Woodforest, Visa, Western Union, and ServiceTitan. Half of the pool does not sit at a fintech.

11

The reason is structural. Payments work is a skill set carried by people titled "Senior Software Engineer," "Staff Backend Engineer," "SRE," "Fraud Engineer," or "Treasury Engineer" inside Block, Visa, Stripe, Adyen, and Braintree. The title reflects the ladder at the employer; the skill reflects what the person actually builds. Sourcing by title collapses that distinction and hands you 11 names.

Skills-based and employer-based sourcing surfaces an order of magnitude more real payments engineers. The signals to actually use:

• Payment rails experience: ACH, SEPA, FedNow, RTP, card-present, card-not-present.
• Protocol depth: ISO 8583, ISO 20022, EMV, 3DS.
• Compliance: PCI-DSS, PSD2, SOC 2.
• Gateway and processor APIs: Stripe, Adyen, Braintree, Checkout.com, Worldpay.
• Employer filters: ex-Block, ex-Visa, ex-PayPal, ex-Braintree, ex-Chime, ex-Robinhood.

This is the exact gap Refolk closes for payments recruiting. Instead of a 40-line Boolean that still misses the pool, you describe the person in plain English ("backend engineers who worked on card authorization at Block or Visa in the last three years, now open to work") and get a ranked shortlist back that pulls from GitHub, LinkedIn, and the open web at once.

Sourcing by title hands you 11 names. Sourcing by skill and ex-employer hands you the actual cohort.

The second-order Stripe cohort is the highest-signal segment

The candidates worth calling first are engineers who did a Stripe tour in 2022 or 2025, landed at Block, PayPal, Coinbase, or Klarna, and just got cut again in 2026. Two fintech tours, the second one ended in restructuring, currently on the market. That is the top of your list.

The historical destinations for laid-off Stripe and Block engineers are well documented: Plaid, Adyen, Checkout.com, Square (now Block), PayPal Braintree, Coinbase, Klarna, and the Treasury and Capital teams at the larger banks, plus a long tail of Series B and C fintechs. Those same destinations are now the source. The chain looks like this:

1. 2022 Stripe cut, landed at Block, PayPal, or Coinbase in 2023.
2. 2026 cut at Block (Feb), Coinbase contraction, PayPal (May), or Visa (July).
3. On the market now, with two brand names and shipping proof from both.

To reconstruct the chain in a sourcing tool, you need a query that combines current or previous employer, tenure windows, and a skill filter, then intersects with an "open to work" signal. Refolk handles this as a single plain-English ask: "engineers who did a Stripe tour before 2023 and were at Block, PayPal, or Coinbase when the 2026 cuts landed" returns the intersection without assembling five saved searches.

Where to place them, and who is actually hiring

The absorbing employers for the 2026 fintech cohort are Stripe, Plaid, Ramp, Mercury, Adyen, Wise, Revolut, Toast, Gusto, Rippling, SoFi, Chime, Nubank, Klarna, and Rho. Note the contradiction in that list: Chime shows up as both a cutter (150 jobs in July) and a hirer, which confirms that role-level targeting beats company-level targeting.

The practical implication is that a blanket "avoid Chime" or "target Chime" instruction to your team is wrong. What matters is which team inside the company is contracting and which is growing. Stripe alone has roughly 500 open roles. Nubank's US launch team, Ramp, Mercury, and Rho are all buying payments and treasury engineers this quarter.

A 5-step sourcing plan for the 7,347

Run these five moves in order this week and you will have a working shortlist by Friday. None of them requires a new tool license.

1. Build three alumni lists. Ex-Block (post Feb 26, 2026), ex-Visa (post July 2026), ex-Chime (post July 2026). This alone covers 92% of the announced cohort.
2. Layer the PayPal pipeline. PayPal's 4,760-job reduction runs through 2027 in waves. Save the alumni search and re-run it monthly. Candidates land in batches tied to internal re-org dates, not the May announcement.
3. Drop title filters. Add skill filters. ISO 8583, PCI-DSS, payment gateway APIs, card authorization, fraud, treasury, ledger. Refolk's index shows title-only searches miss 95%+ of the real pool.
4. Intersect with a Stripe alumni filter. The two-tour cohort is the highest signal and the fastest close, because they have already been through one restructuring and know how to evaluate the next offer.
5. Pitch the org-shape framing. Use Ahuja's own words at Block. These are not performance cuts. Say so in the first message and the reply rate moves.

The reason to move now, not in Q1: Coinbase's postings dropped from ~300 to ~133 in under 90 days, which is the leading indicator of the next fintech contraction. When it lands, the cohort doubles and the outbound gets crowded. The people who called ex-Block engineers in March 2026 placed them by May. The people who wait until Q1 2027 will be pitching against ten other recruiters per candidate.

FAQ

Why does Challenger separate Fintech from Financial and Technology?

Because Challenger uses a 30-industry taxonomy where analysts assign the bucket per announcement, not by NAICS code. Fintech gets its own line so that neobanks, payments companies, and crypto exchanges do not disappear inside Financial (dominated by traditional banks and insurance) or Technology (dominated by SaaS and hyperscalers). Practical consequence for sourcers: pull all three buckets to see the full picture, and Fintech is the one most people skip.

Is Block's 4,000-job cut really about AI efficiency?

The framing is deliberate and the mechanism is real. CFO Amrita Ahuja said Block is choosing to operate with "smaller, highly talented teams using AI to automate more work," and the cut took the company from over 10,000 to just under 6,000. Whether or not AI actually replaces the work, the framing tells you the cuts are strategic rather than performance-based, which changes how you pitch these candidates: they were not fired, they were re-orged out, and their references will confirm it.

How do I find payments engineers if they do not use the title?

Search on skills, employer history, and code, not job titles. The core signals are payment rails (ACH, SEPA, FedNow, ISO 8583), compliance (PCI-DSS, PSD2), gateway and processor APIs (Stripe, Adyen, Braintree), plus ex-employer filters on Block, Visa, PayPal, and Braintree. Refolk's index confirms only 11 US profiles publicly title themselves "Payments Engineer," so any workflow anchored on the title is fishing in the wrong pond.

Which absorbing employers should I pitch these candidates to first?

Stripe, Plaid, Ramp, Mercury, Adyen, Wise, Revolut, Toast, Gusto, Rippling, SoFi, Nubank, Klarna, and Rho are all confirmed hiring in 2026. Stripe alone lists roughly 500 open roles. For the two-tour Stripe alumni cohort specifically, Ramp, Mercury, and Nubank's US launch team tend to move fastest because their hiring bar is calibrated to that background and their loops are shorter than the incumbents'.