← AirBnB
Complex day at AirBnB

Correct credits owed to eligible hosts without paying twice

You’re the software engineer. Your team is in the room. Printed Oct 19, 2026.

The correction must repay eligible hosts without creating a second financial obligation.

Property managers need credits before the next payout cycle, while Payments needs proof that each credit settles once.

Who you’d be doing this for

“My owner asked why three eligible stays never showed up, and I have nothing solid to send back.”

Juraj Popescu · Property Manager

Manages a portfolio of listings enrolled in a host-funded program and reconciles expected credits against payouts.

What is at stake

Eligible property managers are missing credits after qualifying stays settle, while similar accounts received them after a retry. You must weigh fast repayment against the risk of issuing a credit twice.

Why it isn’t already fixed

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

  • host repayment speed vs duplicate settlement risk
  • broad cohort coverage vs proven eligibility
  • payout-cycle urgency vs durable data provenance
  • account consistency vs minimal data access

Why AirBnB

Host-funded programs depend on Passport & Commerce and Payments settling account value correctly across the hosting marketplace.

Written with these in mind

backend reliability engineerpayments systems engineerdistributed systems debugger

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