Skip to content

Mobility & on-demand

Collect fares. Pay drivers. One connected flow.

Accept supported rider payment methods and pay eligible drivers through local bank and wallet routes.

  • Payouts that confirm in seconds
  • Around the clock, weekends included
  • Banks and wallets
Product story. Figures on screen are illustrative.

Delivering results for global businesses

  • Airwallex
  • LianLian Global
  • PayPal
  • XTransfer
  • TransferMate
  • PingPong
  • Global66
  • Skyee
  • TransFi
  • GCC Remit
  • Nium
  • Routefusion
  • Trolley
  • Cadana
  • neomoney
  • Rapyd
  • TerraPay
  • CurrencyBird
  • Ontop
  • Thunes
  • Triple-A
  • Xtract
  • Payoneer
  • Noah
  • Ksher
  • Manteca

Market figures

Why real-time rails matter for on-demand platforms

Public figures from official and industry sources. Each one links to its source.

Why Localpayment

Built for the rhythm of on-demand work

Talk to our sales team

Tell us your markets and volumes, and we’ll design the integration with you.

Recommended method mix

How riders pay and how drivers get paid, country by country

Tokenized cards and instant transfers on the rider side; bank and wallet rails on the driver side, paying in real time where the local rail supports it, weekends included. Only methods documented in our API are listed. Limits, speeds and cut-off times per method are on each country page.

Money flow

From a rider’s fare to a driver’s account

One integration collects from riders, holds local balances, pays drivers and couriers around the clock and converts what is left to USD.

  1. 1

    RiderYour platform:

    Books a ride or an order

    The rider pays with a tokenized card (Argentina, Colombia, Mexico, Peru) or a local method such as Pix, SPEI or PSE chosen in your app.

  2. 2

    Your platformLocalpayment:

    Charge the rider

    POST /api/payin/ with your external ID. On cards, pre-authorize at pickup and capture the final fare at drop-off.

  3. 3

    LocalpaymentYour platform:

    Signed webhook

    Every status change arrives signed with HMAC-SHA256. The fare is credited to your local balance and matched to your trip ID.

  4. 4

    Your platformLocalpayment:

    Release earnings

    POST /api/payout/ per driver with a UUID external ID so a retry never pays twice, or upload a batch in the Business Portal in real time, 24/7.

  5. 5

    LocalpaymentDriver or courier:

    Paid in seconds, 24/7

    Pix, SPEI, COELSA, TEF, CCE, Bre-B and SINPE Móvil confirm in seconds. Direct wallet payouts are also available in Bolivia (same day), Costa Rica and Peru.

  6. 6

    LocalpaymentYour treasury:

    Local balance → USD

    Convert your commission within local market hours; lock the rate with a quote token when the amount is known.

  7. 7

    Your treasuryLocalpayment:

    Top up before peaks

    Fund payout balances by wire or with USDC / USDT (credited about 2–10 minutes after confirmation). Low-balance alerts warn you before a weekend run.

Cards are available in Argentina, Colombia, Mexico and Peru. Conversion happens within local market hours; the rate is locked with a quote token. Localpayment does not collect cash.

For developers

Pay a driver with one API call

Authenticate with a Bearer token, send the payout and listen for the signed webhook. The same request shape works on every rail — only the country, currency, payment method code and beneficiary change.

  • Your own externalId on every payout for traceability
  • HMAC-SHA256 signed webhooks for each status change
  • Optional approval step with double signature
# Example request — see docs.localpayment.com for the exact contract
curl -X POST https://api.stage.localpayment.com/api/payout/ \
  -H "Authorization: Bearer $ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "externalId": "8c4e2f10-0000-4000-8000-000000000481",
    "country": "MEX",
    "currency": "MXN",
    "amount": 1250.00,
    "paymentMethod": { "type": "BankTransfer", "code": "0130", "flow": "DIRECT" },
    "accountNumber": "<your-account-number>",
    "conceptCode": "0001",
    "beneficiary": {
      "type": "INDIVIDUAL",
      "name": "Luis",
      "lastname": "Ramírez",
      "document": { "type": "RFC", "id": "RARL900101XXX" },
      "bank": { "account": { "type": "C", "number": "012180000000000000" } }
    }
  }'

Industry FAQ

Where is this solution available?

Coverage varies by product, payment method and market. Check Coverage & Network for the current details.

How fast do drivers receive their money?

On real-time rails — Pix in Brazil, SPEI in Mexico, COELSA in Argentina, TEF in Chile, CCE in Peru, Bre-B in Colombia and SINPE Móvil in Costa Rica — payouts confirm in seconds, 24/7. Other rails usually settle same day or next business day, depending on the country and cut-off times.

Can drivers be paid to a wallet?

Yes. Direct wallet payouts are available to Yape in Bolivia, SINPE Móvil in Costa Rica and CCE wallets in Peru. Wallets can also be credited by bank transfer in Argentina, Brazil, Chile, Colombia, El Salvador and Mexico.

How do you handle riders who pay in cash?

We do not collect cash. Instead, each driver can get a personal virtual account or pay by QR, so the commission they owe is settled by electronic transfer and matched automatically.

What happens if a payout fails?

Verify payout aliases and validate bank accounts before sending to avoid rejections. If a payout is returned, you receive the status by webhook, and returns and recalls are handled through the API.

Can we approve large payout batches before they go out?

Yes. Payouts can require authorization, and batches in the Business Portal support double-signature approval, so one person prepares and another approves.

How do we fund payouts?

Fund your account by wire transfer, or with USDC or USDT on Ethereum and Tron — stablecoin deposits are credited automatically, usually 2–10 minutes after confirmation. Low-balance alerts warn you before a balance runs out.

How do refunds and canceled trips work?

Card payments in Argentina, Colombia, Mexico and Peru can be pre-authorized and captured for the final fare, so a canceled trip is simply not captured. Refunds on payins go back by the local rail, in local currency, and each one carries your external ID for reconciliation.

Pay your fleet faster

Payouts in real time where the local rail supports it — through one API and one contract.

How can we help?

Download your copy

Leave your details and get the full edition instantly.