How Airbnb Rolled Out 20+ Local Payment Methods in Just 14 Months

LPMs: Definition, Discovery, and Selection

Local payment methods (LPMs) include country‑specific digital wallets (e.g., M‑Pesa, MTN, MoMo), online bank transfers, instant bank payments (e.g., PIX, UPI), and local payment networks (e.g., EFTPOS, Cartes Bancaires). Airbnb identified more than 300 unique options, applied a structured evaluation framework, and selected 20+ LPMs for 75 core travel markets, limiting each market to 1‑2 top‑ranked methods.

Airbnb Payment Platform Background

The platform decouples payment logic from core booking, experience, and service domains, collaborating with regulated payment service providers (PSPs) and financial partners to handle guest payments and host payouts while providing robust risk and compliance capabilities.

Payments Modernization

As part of the long‑term architecture (Payments LTA) overhaul, the monolith was split into domain‑oriented services covering Pay‑in, Payout, Transaction Fulfillment, Processing, Wallet & Instruments, Ledger, Incentives & Stored Value, Issuing, and Settlement & Reconciliation. This shift reduced feature lead time, increased reuse, and gave teams greater autonomy.

Supporting LPMs via Platform Refactor

The refactor introduced a connector‑plugin model for PSP integration, allowing API‑based and file‑based vendor connections and enabling dynamic routing between providers. Multi‑Step Transactions (MST) were added as a PSP‑agnostic framework that describes intermediate actions (redirect, SCA verification, payment‑method‑specific steps) using an ActionPayload.

{
  "actionType": "redirect",
  "actionParameters": {
    "redirectUrl": "https://pspvendor1....",
    "method": "GET"
  }
}

LPM Integration Architecture

Integrating LPMs introduced challenges such as app switching, session handoff, and disparate APIs for capture, refund, and settlement. The platform standardized three end‑to‑end flow prototypes:

Redirect flow : Guest is redirected to a third‑party site/app (e.g., Naver Pay, GoPay, FPX) and returns with a token to complete the booking.

Async flow : Guest receives a QR code or push notification, pays externally (e.g., PIX, MB Way, Blik), and the platform receives a webhook confirmation.

Direct flow : Guest enters payment credentials directly in the Airbnb UI (e.g., Carte Bancaires, Apple Pay) for real‑time processing.

This standardization enabled high reuse and dramatically lowered engineering effort for new LPMs.

Async Payment Orchestration

For redirect and async flows, the platform sends a capture request to the PSP, receives a redirectUrl or qrCodeData, redirects the guest or displays the QR code, and then validates the returned token or webhook to finalize the payment.

Redirect flow: send request → receive redirectUrl → redirect guest → guest completes payment → PSP returns token → platform confirms payment.

Async flow: send request → receive qrCodeData → display QR → guest pays via wallet → PSP sends webhook → platform updates status to success.

Configuration‑Driven Integration

A centralized YAML‑based Payment Method Config stores flow definitions, eligibility rules, input fields, and refund policies. Both backend services and the front‑end UI consume this single source, eliminating duplicated logic and enabling automatic code generation for Java classes, DTOs, enums, and scaffolding. Updating or adding an LPM now requires only a config change, cutting rollout time from months to weeks.

Payment Widget

The checkout widget renders the list of available LPMs and handles user input. Form specifications and eligibility checks are defined in the backend config payload, allowing the front‑end to dynamically adjust UI and validation without code changes. For example, Brazil’s PIX requires CPF, name, and surname fields, which are collected based on the config.

Improved Testability

Testing LPMs is hard because developers often lack access to local wallets. Airbnb enhanced its internal PSP Emulator to simulate both redirect and async interactions, providing a UI for mock PSP pages, QR code generation, and webhook scheduling, enabling reliable end‑to‑end tests without external sandboxes.

Observability Framework

A unified monitoring system aggregates metrics from client, backend, PSP, and webhook layers. Standardized alerts (e.g., "30‑minute Naver Pay resume failures > 5 and failure rate > 20%") reduce noise and surface issues quickly. This framework gives end‑to‑end visibility for each LPM, allowing engineers to diagnose problems in minutes instead of hours.

Impact

Significant booking uplift : Markets with newly enabled LPMs saw noticeable increases in reservations and new user acquisition.

Faster integration : Reusable flows and config‑driven automation shortened integration cycles from months to weeks.

Stronger reliability : Enhanced observability, standardized testing, and streamlined on‑call processes improved global resilience.

Conclusion

Supporting local payment methods helps Airbnb stay competitive in the global travel market by increasing checkout conversion, expanding reach, and unlocking growth opportunities. Ongoing platform evolution will continue to prioritize scalability, reliability, and extensibility to serve guests with familiar, trusted payment options worldwide.