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.
Merchant identity matching must stop duplicates without merging real store relationships.
Fast onboarding protects activation, while careful matching protects the merchant data used for risk analysis and fraud detection.
Who you’d be doing this for
“I’ve got two setup links for the same store, and finance is asking which one is real.”
Sylvie Wolf · Merchant Payments Manager · a character in this brief
Owns the merchant’s checkout payment methods and coordinates activation with its commerce-platform team.
What is at stake
Duplicate merchant identities are splitting setup status for new platform merchants. You have to protect quick activation without collapsing legitimate multi-store relationships.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- activation speed vs. identity accuracy
- automatic matching vs. multi-store integrity
- partner compatibility vs. shared-data consistency
- fast release vs. rollback confidence
Why Affirm
Merchant Data Platform records connect onboarding touchpoints to the APIs merchants use to accept financing at checkout.
Written with these in mind
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.
- Software Engineer II, Frontend (Marketing and Privacy) · no longer posted
- You will work in a modern web stack across React, TypeScript, shared component systems, testing, performance, and observability, with opportunities to develop deeper expertise in technologies such as Google Tag Manager, analytics and experimentation platforms, conversion tracking, and marketing APIs.
- Software Engineer II, Backend (Partner Merchant Interface) (opens in a new tab)
- Senior Software Engineer, Backend (Partner Merchant Interface) · no longer posted
- Staff Software Engineer · 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.
Where similar work appears
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.
Only 68% of invited employees make a first card purchase within 48 hours.
You have to weigh faster activation against keeping entity assignment and spend controls accurate.
Duplicate status callbacks are sending platform operators into repeat payout investigations.
You must weigh fast self-service guidance against evidence that holds across real integrations.
Approved agent purchases with changed prices are failing during authentication.
You have to weigh faster completion against a control path that bad actors could exploit.
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.
A proposed home promotion shares 38% of its sampled audience with an electronics campaign.
You decide whether the prototype drops shoppers already in the electronics campaign itself or leaves each shared shopper for a strategist to keep or exclude.
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.
Platform merchants want a quick path to financing, while their risk evidence varies widely.
You have to weigh activation speed against the controls needed to monitor exposure after approval.
Other problems with a similar purpose
In each of these, as in this one, the aim is to make complex payment systems feel dependable in the exact real-world moment someone needs to complete one.
Approved reimbursements can remain pending after an employee changes bank details.
You must weigh faster routing against sending money using stale account information.
Mobile job completion is creating duplicate charges after some technicians reconnect.
You must protect payment integrity without making field completion brittle.
A fixed enforcement date is coming, and 38% of eligible volume sits on custom confirmation flows that will break.
You have to pick who migrates, and lean on verified safety evidence rather than rollout counts.