iFood Benefícios Data API: PAT Balances, Cards & PIX Fields
iFood Benefícios is the employee-benefits wallet from iFood Delivery de Comida e Mercado, the Brazilian food-delivery company, for workers who spend employer-issued PAT meal and food vouchers plus mobility credits on an Elo-branded iFood Benefícios card. After a CPF sign-in with optional device biometrics, the home tab shows saldo for Refeição, Alimentação and Mobilidade purses, an extrato of merchant taps and iFood-app orders, a virtual Elo PAN that can be added to Google Pay or Apple Pay, card-manufacture and carrier tracking, and a map of nearby restaurants that accept the plastic. From the same session holders open an iFood Pago digital account, register PIX keys, pay boletos, combine purse balances, request an additional card, elect PAT distribution at their employer, unlock Clube iFood perks after a recarga, and complete document-plus-liveness identity checks. Published for Brazil (Play package br.com.ifood.benefits; iOS listing id 1550867930), it sits in the same PAT wallet market as Alelo, Pluxee Brasil, Ticket (Edenred Brasil), VR Benefícios, Caju and Flash Benefícios.
PAT purse records distinguish employer meal, food and mobility credits through walletId and benefitType, with REFEICAO, ALIMENTACAO and MOBILIDADE as the illustrated benefit categories. Balance snapshots pair availableBalance and blockedBalance with BRL currency, lastRechargeAmount and the recharge timestamp lastRechargeAt. Statement records add transactionId, merchantName, mcc, amount and occurredAt; APPROVED, REVERSED or CANCELED status and POS or IFOOD_APP channel distinguish transaction outcomes and restaurant taps from app orders.
Elo card records carry cardId, panLast4, formFactor, expiry and status, plus separate googlePayTokenized and applePayTokenized flags. Virtual-card examples also include linkedCardId, cvvSet and createdAt. Delivery records describe IN_PRODUCTION, IN_TRANSIT, DELIVERED, ASTRAY or RETURNED through trackingStatus, alongside carrier, estimatedDeliveryDate and remainingAttempts. Together, these fields support card-operations views that keep card form, digital-wallet enrollment and physical delivery state distinct.
PIX key records include pixKeyType, claimId and portabilityId, while payment examples carry endToEndId, dailyLimitRemaining, receiptId and rejectReason, including INSUFFICIENT_BALANCE. The iFood Pago account snapshot adds accountStatus values PENDING_KYC, ACTIVE, REJECTED and CLOSED, plus pendingDocuments and pendingPersonalData. Boleto records contain typedLine, payeeName, dueDate and a payment receipt identifier. These objects give treasury-tool designers separate fields for account readiness, payment outcomes and receipt reconciliation.
Merchant-acceptance records combine latitude, longitude and distanceMeters with acceptsRefeicao and acceptsAlimentacao. PAT election records specify mealPercent, foodPercent, effectiveMonth and distributionAvailable. Payroll teams can design recharge-versus-election checks, expense teams can analyze merchant-category and channel mix, and field teams can build acceptance maps from these fields. The endpoint descriptions and examples here are illustrative rather than an officially supported iFood developer API; openData Studio turns app data into callable open data for these integration workflows.
Screenshots
API surface
Request/response examples are illustrative, reconstructed from the app's interface — not a live capture.
List PAT wallets and balances
GET
/v1/pat/pursesopenbankingReturns every PAT purse on the signed-in worker — Refeição, Alimentação and Mobilidade — with available and blocked BRL balances and the last employer recarga, for the home saldo tiles.
Auth: Bearer accessToken after CPF sign-in
- walletId
- benefitType
- productName
- availableBalance
- blockedBalance
- currency
- lastRechargeAmount
- lastRechargeAt
- hiddenBalance
GET /v1/pat/purses HTTP/1.1 Authorization: Bearer <access_token> Accept: application/json{ "wallets": [ { "walletId": "wal_refeicao_4419", "benefitType": "REFEICAO", "productName": "iFood Benefícios Refeição", "availableBalance": 642.80, "blockedBalance": 0, "currency": "BRL", "lastRechargeAmount": 700.00, "lastRechargeAt": "2026-10-01T08:12:00Z", "hiddenBalance": false }, { "walletId": "wal_alimentacao_4419", "benefitType": "ALIMENTACAO", "productName": "iFood Benefícios Alimentação", "availableBalance": 318.45, "blockedBalance": 12.00, "currency": "BRL", "lastRechargeAmount": 400.00, "lastRechargeAt": "2026-10-01T08:12:00Z", "hiddenBalance": false }, { "walletId": "wal_mobilidade_4419", "benefitType": "MOBILIDADE", "productName": "iFood Benefícios Mobilidade", "availableBalance": 95.00, "blockedBalance": 0, "currency": "BRL", "lastRechargeAmount": 150.00, "lastRechargeAt": "2026-09-15T09:00:00Z", "hiddenBalance": false } ] }Wallet statement (extrato)
GET
/v1/pat/purses/{walletId}/transactionsopenbankingPages the extrato for one PAT purse — merchant, MCC, amount, APPROVED/REVERSED/CANCELED status and POS vs iFood-app channel — for the statement tab.
Auth: Bearer accessToken after CPF sign-in
- walletId
- page
- pageSize
- transactionId
- merchantName
- mcc
- amount
- currency
- benefitType
- status
- channel
- occurredAt
GET /v1/pat/purses/wal_refeicao_4419/transactions?from=2026-10-01&to=2026-10-23&page=1 HTTP/1.1 Authorization: Bearer <access_token> Accept: application/json{ "walletId": "wal_refeicao_4419", "page": 1, "pageSize": 20, "transactions": [ { "transactionId": "txn_9f21c4", "merchantName": "Padaria Central", "mcc": "5812", "amount": 32.90, "currency": "BRL", "benefitType": "REFEICAO", "status": "APPROVED", "channel": "POS", "occurredAt": "2026-10-22T12:14:03Z" }, { "transactionId": "txn_9f21aa", "merchantName": "iFood Pedido", "mcc": "5814", "amount": 48.50, "currency": "BRL", "benefitType": "REFEICAO", "status": "REVERSED", "channel": "IFOOD_APP", "occurredAt": "2026-10-21T19:02:11Z" } ] }List physical and virtual Elo cards
GET
/v1/elo-cardsopenfinanceLists every Elo plastic and virtual iFood Benefícios card on the worker — PAN tail, form factor, wallet-tokenization flags and status — for the card carousel and Google Pay / Apple Pay tiles.
Auth: Bearer accessToken after CPF sign-in
- cardId
- panLast4
- brand
- formFactor
- status
- googlePayTokenized
- applePayTokenized
- expiryMonth
- expiryYear
- holderName
GET /v1/elo-cards HTTP/1.1 Authorization: Bearer <access_token> Accept: application/json{ "cards": [ { "cardId": "crd_ifb_4419", "panLast4": "4419", "brand": "ELO", "formFactor": "PHYSICAL", "status": "ACTIVE", "googlePayTokenized": true, "applePayTokenized": false, "expiryMonth": 8, "expiryYear": 2028, "holderName": "ANA SOUZA" }, { "cardId": "crd_ifb_vc_8821", "panLast4": "8821", "brand": "ELO", "formFactor": "VIRTUAL", "status": "ACTIVE", "googlePayTokenized": false, "applePayTokenized": false, "expiryMonth": 8, "expiryYear": 2028, "holderName": "ANA SOUZA" } ] }Issue virtual Elo card
POST
/v1/elo-cards/virtualopenfinanceMints a virtual Elo PAN against the worker's physical card so online iFood orders and in-app checkout can run while the plastic is in manufacture or blocked.
Auth: Bearer accessToken after CPF sign-in
- linkedCardId
- label
- cardId
- panLast4
- expiryMonth
- expiryYear
- cvvSet
- status
- formFactor
- createdAt
POST /v1/elo-cards/virtual HTTP/1.1 Authorization: Bearer <access_token> Content-Type: application/json { "linkedCardId": "crd_ifb_4419", "label": "Pedido iFood" }{ "cardId": "crd_ifb_vc_8821", "linkedCardId": "crd_ifb_4419", "panLast4": "8821", "expiryMonth": 8, "expiryYear": 2028, "cvvSet": true, "status": "ACTIVE", "formFactor": "VIRTUAL", "createdAt": "2026-10-23T11:04:00Z" }Card delivery tracking
GET
/v1/elo-cards/{cardId}/deliveryopendataReturns manufacture-to-door status for a newly issued plastic — IN_PRODUCTION, IN_TRANSIT, DELIVERED, ASTRAY, RETURNED — plus carrier and remaining delivery attempts.
Auth: Bearer accessToken after CPF sign-in
- cardId
- trackingStatus
- carrier
- trackingCode
- estimatedDeliveryDate
- deliveryAttempt
- remainingAttempts
- lastEventAt
GET /v1/elo-cards/crd_ifb_4419/delivery HTTP/1.1 Authorization: Bearer <access_token> Accept: application/json{ "cardId": "crd_ifb_4419", "trackingStatus": "IN_TRANSIT", "carrier": "LOGGI", "trackingCode": "IFB4419BR", "estimatedDeliveryDate": "2026-10-28", "deliveryAttempt": 1, "remainingAttempts": 2, "lastEventAt": "2026-10-23T09:41:00Z" }Registered PIX keys
GET
/v1/pix/keysopenfinanceLists PIX keys bound to the iFood Pago / benefits session (CPF, email, phone, EVP) with claim and portability state for the key-management screens.
Auth: Bearer accessToken after CPF sign-in
- pixKey
- pixKeyType
- status
- claimId
- portabilityId
- createdAt
- maxKeys
GET /v1/pix/keys HTTP/1.1 Authorization: Bearer <access_token> Accept: application/json{ "keys": [ { "pixKey": "12345678901", "pixKeyType": "CPF", "status": "ACTIVE", "claimId": null, "portabilityId": null, "createdAt": "2026-08-12T14:00:00Z" }, { "pixKey": "[email protected]", "pixKeyType": "EMAIL", "status": "CLAIM_PENDING", "claimId": "clm_77ab", "portabilityId": null, "createdAt": "2026-10-20T10:22:00Z" } ], "maxKeys": 5 }PIX cash-out payment
POST
/v1/pix/paymentsopenfinanceSubmits a PIX money-out from a PAT or digital-account purse, returning endToEndId, limit remaining and reject reasons such as insufficient balance or limit exceeded.
Auth: Bearer accessToken after CPF sign-in
- debitWalletId
- pixKey
- pixKeyType
- amount
- currency
- description
- paymentId
- endToEndId
- status
- rejectReason
- dailyLimitRemaining
- receiptId
POST /v1/pix/payments HTTP/1.1 Authorization: Bearer <access_token> Content-Type: application/json { "debitWalletId": "wal_refeicao_4419", "pixKey": "98765432100", "pixKeyType": "CPF", "amount": 80.00, "currency": "BRL", "description": "Repasse almoço" }{ "paymentId": "pix_3c91", "endToEndId": "E12345678202610231104abc", "debitWalletId": "wal_refeicao_4419", "amount": 80.00, "currency": "BRL", "status": "REJECTED", "rejectReason": "INSUFFICIENT_BALANCE", "dailyLimitRemaining": 250.00, "receiptId": null }Nearby accepting restaurants
GET
/v1/merchants/nearbyopendataReturns geolocated merchants in the PAT acceptance network around the worker, flagged for Refeição vs Alimentação, for the restaurant-pin map.
Auth: Bearer accessToken after CPF sign-in
- merchantId
- name
- category
- latitude
- longitude
- distanceMeters
- acceptsRefeicao
- acceptsAlimentacao
- pinCount
GET /v1/merchants/nearby?lat=-23.5505&lng=-46.6333&radiusMeters=1500&benefitType=REFEICAO HTTP/1.1 Authorization: Bearer <access_token> Accept: application/json{ "merchants": [ { "merchantId": "mct_padaria_central", "name": "Padaria Central", "category": "RESTAURANT", "latitude": -23.5512, "longitude": -46.6341, "distanceMeters": 180, "acceptsRefeicao": true, "acceptsAlimentacao": false, "pinCount": 1 } ] }PAT benefit election
GET
/v1/pat/electionsopenfinanceReads the worker's PAT meal-vs-food split election at the current employer and whether a new distribution window is open.
Auth: Bearer accessToken after CPF sign-in
- electionId
- employerId
- employerName
- mealPercent
- foodPercent
- status
- effectiveMonth
- distributionAvailable
GET /v1/pat/elections HTTP/1.1 Authorization: Bearer <access_token> Accept: application/json{ "electionId": "pat_2026_10", "employerId": "emp_acme_br", "employerName": "ACME Alimentos Ltda", "mealPercent": 60, "foodPercent": 40, "status": "CONFIRMED", "effectiveMonth": "2026-11", "distributionAvailable": true }iFood Pago digital account
GET
/v1/digital-accountopenbankingReturns the iFood Pago digital-account snapshot — status (PENDING_KYC, ACTIVE, REJECTED, CLOSED), branch/account and whether documents or personal data are still outstanding.
Auth: Bearer accessToken after CPF sign-in
- accountId
- accountStatus
- branch
- accountNumber
- availableBalance
- currency
- pendingDocuments
- pendingPersonalData
GET /v1/digital-account HTTP/1.1 Authorization: Bearer <access_token> Accept: application/json{ "accountId": "acc_pago_0091", "accountStatus": "PENDING_KYC", "branch": "0001", "accountNumber": "123456-7", "availableBalance": 0, "currency": "BRL", "pendingDocuments": true, "pendingPersonalData": true }Pay boleto from a purse
POST
/v1/bills/payopenfinanceValidates a boleto typed line and pays it from a selected PAT or digital-account purse, returning due date, payee and receipt id for the invoices list.
Auth: Bearer accessToken after CPF sign-in
- typedLine
- debitWalletId
- billId
- amount
- dueDate
- payeeName
- status
- receiptId
POST /v1/bills/pay HTTP/1.1 Authorization: Bearer <access_token> Content-Type: application/json { "typedLine": "23793.38128 60000.000003 00000.000400 1 84440000008000", "debitWalletId": "wal_alimentacao_4419" }{ "billId": "bol_4411", "typedLine": "23793.38128 60000.000003 00000.000400 1 84440000008000", "amount": 80.00, "dueDate": "2026-10-30", "payeeName": "Companhia de Energia", "debitWalletId": "wal_alimentacao_4419", "status": "PAID", "receiptId": "rcpt_bol_4411" }
Data categories
- card balances
- transactions
- virtual cards
- card delivery
- PIX keys
- PIX payments
- merchant network
- PAT elections
- digital account
- boleto payments
Where teams use this data
Payroll PAT reconciliation
HR bots pull availableBalance and lastRechargeAmount per benefitType (REFEICAO, ALIMENTACAO, MOBILIDADE) after each employer recarga and compare mealPercent/foodPercent on the PAT election for the next effectiveMonth.
Meal-spend analytics
Expense tools ingest transactionId, merchantName, mcc, amount and APPROVED/REVERSED status from the extrato, split by channel POS vs IFOOD_APP, without scraping the statement tab.
PIX cash-out and boleto ops
Treasury desks watch pixKey claim/portability state, then post PIX payments or boletos with endToEndId, dailyLimitRemaining, typedLine and receiptId when a purse has headroom.
Acceptance-network and plastic ops
Field teams plot nearby merchants (acceptsRefeicao, distanceMeters) and card-ops desks track trackingStatus / remainingAttempts so a virtual PAN (formFactor VIRTUAL) can cover spend while the Elo plastic is IN_TRANSIT.
Frequently asked questions
Which benefit-wallet and recharge fields are documented?
The examples cover REFEICAO (meal), ALIMENTACAO (food) and MOBILIDADE (mobility), distinguished by benefitType and walletId. availableBalance, blockedBalance and lastRechargeAmount are BRL amounts; lastRechargeAt is the recharge timestamp. PAT election records separately provide mealPercent, foodPercent and effectiveMonth for reconciliation design.
Does the data include PIX, Elo cards and the iFood Pago account?
Yes. PIX examples include pixKeyType, claimId and portabilityId for key management, plus endToEndId, dailyLimitRemaining and rejectReason for payments. Elo card records include formFactor and Google Pay and Apple Pay tokenization flags. The digital-account snapshot supplies accountStatus, pendingDocuments and pendingPersonalData, while boleto records include typedLine and receiptId.
Which fields can support a restaurant acceptance map?
The nearby-merchant examples include merchantId, name, latitude, longitude and distanceMeters. acceptsRefeicao and acceptsAlimentacao distinguish meal-benefit and food-benefit acceptance, allowing map designers to separate location from the benefit type a merchant accepts.
Is this an officially supported iFood developer API?
No. This page provides illustrative endpoint descriptions and field examples based on the app's features for integration design, not an officially supported iFood developer API. The documented examples specify Bearer accessToken authentication after CPF sign-in.
Apps similar to iFood Benefícios
- Meu Alelo — Meu Alelo is Alelo's worker app for Brazilian PAT vale-alimentação and vale-refeição plus mobility benefits, used to check statements, change the card PIN and pay by QR at accepting merchants.
- Pluxee Brasil — Pluxee Brasil is the cardholder app for Pluxee's PAT vale-alimentação and vale-refeição, including grocery spend, restaurant and delivery-app Refeição, and a Multibenefícios card with up to seven wallets.
- Ticket — Ticket is Edenred's Brazilian employee-benefits brand; its official app is used to check balances and statements for Ticket Alimentação, Restaurante, Flex, Transporte and Mobilidade cards.
- SuperApp VR — SuperApp VR is VR Benefícios' worker app for PAT-aligned Refeição and Alimentação plus Multi, Home Office and Auto balances, with in-app proximity payment so holders can pay without the physical card.
- Flash | Benefícios e Despesas — Flash is a Brazilian multi-benefit card and worker app that centralizes corporate benefits, PAT meal-and-food wallets, vale-transporte and expense management on one Flash card.
- Caju — Caju is a Brazilian benefits-and-spend platform that puts PAT, CLT and flexible-benefit categories — including meal, food, mobility, vale-transporte and home office — on one Visa-accepted card with a worker app.
- Swile Brasil — Swile Brasil is a PAT- and CLT-aligned multi-benefit Mastercard that puts alimentação, refeição, health, mobility, home-office, education, fuel and award wallets on one card, with a worker app for live balances and Apple Pay / Google Pay.
Topics
- iFood Benefícios Data API
- iFood Benefícios endpoints and fields
- PAT meal voucher balance
- iFood Benefícios PIX payment fields
- Elo virtual card data
- iFood Pago digital account
- PAT benefit election fields
- iFood Benefícios merchant acceptance map
- vale refeição iFood
Need this app's data API integrated?
We deliver scoped integrations for any named app — from USD 500 with source-code handoff, or hosted access billed per call. Tell us the data you need.
- NDA + SOW on every engagement
- Delivery in 3–7 days
- Payment only after acceptance
- Work scoped to authorized use