← Mercury
Complex day at Mercury

Decide what to move onto the new authorizer

You’re the product manager. Your team is in the room. Printed Aug 6, 2026.

A payment decision can improve overall and still fail the customers who rely on its controls.

Higher approval rates and consistent enforcement do not always move together.

Who you’d be doing this for

“I need the cards to work, but not by quietly ignoring the limits we set.”

Marina Sokolov · Controller

Oversees card policies and recurring vendor payments for a 250-person software company.

What is at stake

Routing has to move off the old provider within 90 days, and the new one approves more but disagrees on some merchant and limit rules. You have to pick a scope you cannot cheaply undo.

Why it isn’t already fixed

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

  • approval lift vs. control integrity
  • deadline certainty vs. verified parity
  • aggregate performance vs. edge-case harm
  • provider extension vs. durable transition

Why Mercury

For Mercury, it can affect whether card spend remains both dependable for employees and controllable for finance teams.

Written with these in mind

Payments platform product managerRisk-aware product leaderReliability-focused product manager

Not your kind of problem? 9 more at Mercury, 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.