Complex day at Affirm

Set credit limits for electronics orders while fraud signals conflict

Published Oct 23, 2026

You’re the policy / risk manager. Your team is in the room.

The setting

is a buy now, pay later company that offers installment loans at checkout to shoppers and payment tools to merchants. is the pay-over-time financing that merchants add to their checkout.

The same disputed orders can justify protecting checkout access or closing exposure immediately.

High-value approval continuity protects the merchant’s sales event, while tighter controls protect the loss boundary and capital confidence.

Who you’d be doing this for

“My operations lead has a list of held orders, and the sales team wants to know why financing is suddenly uncertain.”

Rotich Gebremariam · Merchant Payments Manager · a character in this brief

Runs checkout financing performance and escalation management for the affected electronics merchant.

What is at stake

Disputed high-value electronics orders are rising while the merchant and Fraud disagree on what is driving them. You have to weigh legitimate checkout access against a loss decision that will be hard to reverse.

Why it isn’t already fixed

Every obvious fix costs something else. That’s the part you’d have to decide.

  • high-value conversion vs. disputed-loss exposure
  • rapid containment vs. verified attribution
  • merchant continuity vs. capital confidence
  • targeted controls vs. simple restrictions

Why Affirm

Merchant checkout financing depends on defensible exposure decisions when a large merchant’s financed orders begin producing disputed losses.

Written with these in mind

merchant risk strategistcredit risk managerfraud and policy practitioner

Not your kind of problem? 128 more at Affirm, or browse every organization.

Where the organization context comes fromThe postings this brief was written from, and the reporting read before it.

The organization context comes from public information. The situation and characters are written for the brief.

Job postings it was written from

Public descriptions of the work at Affirm. They are listed as sources, not as openings. The lines under a posting are its own words, where it meets this brief.

  • Analyst II, Credit · no longer posted
    • Conduct ongoing monitoring of credit, fraud, and dispute/chargeback trends by merchants
    • Assess brand, compliance, fraud and financial risk and determine credit exposure risk on new and existing merchants
  • Analyst II, Full Stack (Credit Analytics) · no longer posted
    • The Credit team works cross-functionally with Machine Learning, Product, Engineering, Capital Markets, and Commercial teams to responsibly manage the risk profile of the business.
    • Engage and coordinate with external stakeholders — including merchants, vendors, and regulatory bodies — to align credit risk practices, ensure compliance, and strengthen strategic partnerships.
  • Analytics Manager, Full Stack (Credit Risk) · no longer posted
  • Analytics Manager, Full Stack · no longer posted
  • Analyst I, Merchant Risk · no longer posted

This is the setup. The work is inside.

Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.

Other live briefs connected to this one, and what connects them.

Similar problems at other organizations

Like this one, each of these is about money moving incorrectly, late, or twice.

The same setting, from another role

Each is set around Affirm’s Affirm for Merchants, written for a different role. They’re separate briefs, not the same scenario.

Other problems with a similar purpose

In each of these, as in this one, the aim is to build controls against real harm that remain fair to the honest people who get caught in the signal.