A defined compliance obligation can still leave difficult questions about evidence and confidence.
Coverage pressure, merchant continuity, and defensible review often pull in different directions.
Who you’d be doing this for
“We can’t just pause our sellers while we wait for perfect labels.”
Yue Sun · Compliance Systems Engineer
Maintains payment-flow data for a marketplace that must continue processing while meeting new cross-border reporting requirements.
What is at stake
27% of in-scope flows still lack a structured classification, and the new treatment takes effect on a fixed date. You have to commit to a model and an evidence standard that hold up once reporting begins.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- deadline coverage vs. evidentiary certainty
- merchant continuity vs. reporting exposure
- model scale vs. human verification
- abstention safety vs. review capacity
Why Stripe
At Stripe, payment infrastructure decisions can often need to preserve both merchant continuity and auditable treatment.
Written with these in mind
Not your kind of problem? 17 more at Stripe, or browse every organization.
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.