Connect Waylet accounts, fuel payments and EV-charging sessions to your stack — under user authorisation
Waylet is Repsol's mobile wallet for paying at more than 3,000 service stations, recharging electric vehicles at over 4,000 public charging points and managing parking, gift cards and energy tariffs. The platform crossed 10 million registered users in February 2026, almost a year ahead of Repsol's 2024–2027 strategic-plan target. Behind that traffic sits a rich, structured dataset: fuel and EV-charging transactions, loyalty balance accruals, coupons, route plans, and PSD2-aligned authentication events.
We deliver protocol analysis and API source code that exposes this data in OpenBanking-style endpoints, so finance, fleet and analytics teams can sync Waylet activity into their own systems without rebuilding the mobile flow from scratch.
What we deliver
Each Waylet engagement ships as a self-contained bundle so your team can run it on day one — no scaffolding, no missing credentials documentation, no untested edge cases.
Deliverables checklist
- OpenAPI 3.1 specification for every endpoint
- Protocol & auth flow report (SCA challenge, token refresh, device binding)
- Runnable source for login, statement, EV-session and loyalty endpoints (Python & Node.js)
- Webhook receiver template for charging-session and payment events
- Postman collection plus pytest / vitest test suites
- Compliance brief covering PSD2, GDPR and Spanish LOPDGDD obligations
Engagement options
- Source code delivery from $300 — runnable code plus docs; pay only after acceptance.
- Pay-per-call hosted API — call our managed Waylet endpoints with usage-based billing, no upfront fee.
- Custom retainer — for fleet operators, energy retailers and ERP vendors needing ongoing protocol updates as the app evolves.
Data available for integration
The table below maps the structured datasets exposed by Waylet to the screen or feature they originate from, the granularity you can expect, and the typical downstream use case. We surface only data the authenticated user can already see in the app.
| Data type | Source feature | Granularity | Typical use |
|---|---|---|---|
| Fuel refuel transactions | Pay at the pump (Repsol / Campsa / Petronor) | Per-transaction: station ID, litres, fuel grade, gross/net amount, timestamp | Expense reconciliation, fleet fuel cards, scope-1 emissions reporting |
| EV charging sessions | Charging point reservation & pay | Per-session: connector, kWh, tariff, start/stop, Waylet credit accrued | Driver reimbursement, MID-billed B2B charging, sustainability dashboards |
| Waylet balance & savings | Wallet, balance accumulation rules | Real-time balance, lifetime savings, redemption history | Loyalty analytics, customer-LTV models, marketing automation |
| Parking sessions (green/blue zone) | SER parking module | Per-session: zone, duration, vehicle plate, amount | Fleet parking expense, mobility-as-a-service back-office |
| Coupons & gift cards | Online store partners (MediaMarkt, El Corte Inglés, IKEA, Decathlon, AliExpress, Miravia, eDreams) | Card code, value, status, partner brand, expiry | Cashback platforms, employee benefit portals, perks aggregation |
| Klin car-wash & service receipts | Repsol Klin tunnel / pressure / vacuum | Service type, station, amount, date | Vehicle-care subscriptions, lease-end reconditioning audits |
| EV route plans & reservations | Chargetrip-powered route planner | Origin/destination, stops, ETA, vehicle SoC, reserved point | Fleet route optimisation, range-anxiety analytics, telematics enrichment |
| Authentication events (PSD2) | SCA login & payment challenges | Challenge type, factor, result, IP/device fingerprint | Fraud monitoring, audit trails, regulator reporting |
Typical integration scenarios
The scenarios below come from real questions we receive about Waylet. Each one names the business context, the dataset involved, and how it lands in an OpenData / OpenFinance pattern.
1 — Fleet fuel-card reconciliation
A logistics operator gives drivers Waylet accounts instead of physical fuel cards. Each night, our connector pulls fuel refuel transactions and EV charging sessions per driver, normalises them into a camt.053-style statement, and pushes them into the operator's TMS. Result: same-day visibility instead of weekly card statements.
2 — Energy retailer cross-sell
An energy retailer running the Waylet Luz tariff wants to attribute home-electricity savings to fuel-station behaviour. We expose a unified balance and savings stream so the retailer's CRM can score customers by combined energy + mobility wallet value, and trigger targeted offers.
3 — Accounting & ERP sync (SAP / Odoo)
Finance teams need every Repsol receipt as a posted invoice. Our adapter maps the Waylet electronic receipt — VAT, fuel grade, station tax ID — to SAP S/4HANA F-43 entries or to Odoo vendor bills, eliminating manual ticket entry for accounting clerks.
4 — EV mobility analytics & carbon reporting
A mobility analytics startup builds CO₂-saved dashboards for corporate clients. Waylet's EV-charging session events feed kWh delivered, time-of-use tariff and renewable share, which the platform converts into scope-1 displacement and scope-2 grid-weighted footprints.
5 — Fraud monitoring & PSD2 audit
A payments compliance vendor consumes our Waylet authentication-event stream — SCA challenge type, device fingerprint, geo signal — to detect anomalous login attempts in near real time and to assemble the audit trail that PSD2 supervisors increasingly request from regulated providers.
Technical implementation
The snippets below illustrate three different integration surfaces: the SCA-aware login, a paginated statement query, and a webhook payload for an EV-charging session. Field names match the production payloads we ship.
1. PSD2 SCA login (stepped)
// Step 1: initiate
POST /api/v1/waylet/auth/init
Content-Type: application/json
{
"username": "user@example.es",
"password": "<hashed>",
"device_id": "uuid-...",
"platform": "android"
}
=> 200 { "challenge_id": "ch_...", "factor": "otp_sms" }
// Step 2: respond to SCA challenge
POST /api/v1/waylet/auth/challenge
{ "challenge_id": "ch_...", "code": "482931" }
=> 200 {
"access_token": "...",
"refresh_token": "...",
"expires_in": 1800,
"scope": "wallet statements ev_sessions"
}
2. Statement / transaction query
POST /api/v1/waylet/statement
Authorization: Bearer <ACCESS_TOKEN>
{
"from_date": "2026-04-01",
"to_date": "2026-04-30",
"types": ["FUEL", "EV_CHARGE", "PARKING"],
"page": 1,
"page_size": 100
}
=> 200 {
"items": [{
"tx_id": "wl_3xN...",
"type": "EV_CHARGE",
"station_id": "ES-MAD-0142",
"kwh": 38.4,
"amount_eur": 16.27,
"balance_credit_eur": 16.27,
"occurred_at": "2026-04-12T18:24:11+02:00"
}],
"page": 1, "total": 73
}
3. EV charging-session webhook
POST https://your-app.example/webhook/waylet
X-Waylet-Signature: t=...,v1=...
{
"event": "ev_session.completed",
"session_id": "evs_91a...",
"user_ref": "u_77f...",
"connector": "CCS2",
"started_at": "2026-04-12T18:02:09Z",
"ended_at": "2026-04-12T18:24:11Z",
"kwh": 38.4,
"tariff": "REPSOL_PUBLIC_FAST",
"amount_eur": 16.27,
"credit_eur": 16.27
}
// On 5xx we retry with exponential backoff up to 24h.
Compliance & privacy
Regulations we follow
Waylet operates under the EU revised Payment Services Directive — see PSD2 on Wikipedia — which mandates Strong Customer Authentication on login and on most payment events. Our integrations preserve the full SCA flow rather than bypassing it.
Personal data handling is aligned with the EU GDPR and Spain's LOPDGDD (Ley Orgánica 3/2018). Card data never traverses our systems in plaintext: the Repsol stack acquires through PAYCOMET, a PCI-DSS Level 1 processor, and we propagate only token references.
How we keep integrations safe
- User-authorised access only — explicit consent capture and revocation API.
- Data minimisation: scoped tokens (e.g.
statementsonly, nopayments). - Encryption in transit (TLS 1.2+) and at rest (AES-256) for any cached payloads.
- Full audit log of every API call, exportable for PSD2 supervisor reviews.
- Optional EU-only data residency and configurable retention windows.
Data flow / architecture
A typical Waylet integration follows a clear four-stage pipeline. Each stage is replaceable so customers can choose self-hosted or fully managed deployment.
- Client / SDK — Mobile or backend client triggers SCA login and obtains a scoped access token.
- Ingestion gateway — Our connector polls statement endpoints and subscribes to webhook events (charging, payment, refund).
- Normalisation & storage — Events are normalised to a canonical schema (camt.053-style for finance, OCPI-aligned for EV) and persisted in Postgres or BigQuery.
- Egress / analytics — Downstream systems pull through REST APIs, scheduled CSV/XLSX exports, or push streams (Kafka, Webhook, ERP adapter).
Market positioning & user profile
Waylet is a Spain-only consumer app with strong B2B2C reach: roughly 30% of its 10 million users now rely on it for non-fuel services such as EV charging, parking, car wash and partner gift cards. The audience skews toward private drivers, urban commuters and small fleets across mainland Spain and the Balearic and Canary Islands; Apple CarPlay and Android Auto support broaden the in-vehicle footprint. Demand for API-level access typically comes from fleet operators, energy retailers, expense-management SaaS, mobility-analytics startups and accounting/ERP integrators that need structured Waylet data alongside other Spanish payment rails such as Bizum and SEPA Instant.
Screenshots
Tap any screenshot to enlarge. Each one corresponds to a screen we have mapped during protocol analysis and can expose through the API surface above.
Similar apps & integration landscape
Waylet sits in a Spanish ecosystem of fuel-station, mobility and mobile-payment apps. Teams that need Waylet data often require unified exports across some of the apps below, so we list them here as part of the broader integration landscape.
- Repsol Vivit — Repsol's home electricity and gas app; combined Waylet + Vivit balances give a full energy + mobility view of a single customer.
- Bip&Drive — Multi-brand Spanish fuel and tolls payment app covering Repsol, Cepsa, Galp, BP and Shell; integrators frequently need a single statement that merges Bip&Drive and Waylet refuel events.
- Mundo Galp — Galp's Iberian fuel-loyalty and payment app with seasonal cents-per-litre programmes; relevant for fleets that fill at both Galp and Repsol stations.
- Mi BP — BP's loyalty + payment app in Spain offering up to 10 cents per litre off; common counterpart to Waylet for cross-brand fuel-card analytics.
- Moeve (formerly Cepsa) — Cepsa's rebrand with its own mobile payment and EV-charging stack; enterprise reporting often combines Moeve and Waylet data.
- Twyp — ING's Spanish wallet app supporting cashback at fuel stations; a frequent partner data source for personal-finance dashboards alongside Waylet.
- Bizum — Spain's dominant person-to-person instant payment scheme; integrations often pair Bizum reconciliation with Waylet wallet movements for SMB accounting.
- Shell App / Shell Recharge — Shell's EV-charging and station app; useful comparison source for EV session pricing and OCPI-style normalisation.
- PAYCOMET / PaynoPain — The acquiring stack behind Waylet's e-commerce checkout; exposes complementary merchant-side reporting APIs.
- Apple Pay & Google Pay — Tokenised card wallets present alongside Waylet on most user devices; relevant when modelling end-to-end consumer payment behaviour in Spain.
About us
OpenFinance Lab is an independent technical studio focused on app protocol analysis and OpenData / OpenFinance integration. Our engineers come from acquiring, banking-as-a-service, mobility platforms and reverse-engineering backgrounds, and we have shipped integrations across Spanish, EU, UK, LATAM and Asian payment apps.
- Payments, digital banking, fuel-retail and EV-charging back-ends
- Enterprise API gateways, security reviews and PSD2 audit support
- Custom Python, Node.js and Go SDKs with full test harnesses
- End-to-end pipeline: protocol analysis → build → validation → compliance brief
- Source code delivery from $300 — runnable code and full docs; pay only after acceptance
- Pay-per-call hosted API — usage-based billing, no upfront cost
Contact
To request a quote, share NDA paperwork or submit your Waylet integration scope, open our contact page:
Engagement workflow
- Scope confirmation: integration scenarios and API needs (login, statements, EV sessions, loyalty).
- Protocol analysis and API design (2–5 business days, depending on SCA factor count).
- Build and internal validation (3–8 business days), including webhook signing and replay tests.
- Documentation, sample requests and end-to-end test cases (1–2 business days).
- First delivery typically within 5–15 business days; third-party reviews may extend timelines.
FAQ
What Waylet data can you actually extract through an API integration?
How do you handle PSD2 Strong Customer Authentication?
What is the typical delivery timeline?
Can you support fleet, ERP and accounting use cases?
Original app overview (appendix)
Waylet. Pagos con el móvil is Repsol's mobile payment and loyalty app for Spain, available on Android and iOS. Released by REPSOL S.A. and active since 2012, it has expanded from a fuel-payment tool into a multi-service platform spanning mobility, retail and energy. The app crossed 10 million registered users in February 2026, almost a year ahead of Repsol's 2024–2027 strategic-plan target, with around 30% of users now relying on it for non-fuel services.
Headline capabilities advertised on the Google Play listing include:
- Pay at the pump at more than 3,000 Repsol Group service stations (Repsol, Campsa, Petronor) using a QR code and PIN/biometric.
- Locate, reserve (15 minutes) and pay at more than 4,000 public EV charging points across Spain, with operator coverage from Ionity, Powerdot, Atlante, EDP, Porsche, Volkswagen, BSM and Crece.
- Plan EV routes through a Chargetrip-powered planner with state-of-charge inputs and Maps/Waze export.
- Manage parking-meter payments in green and blue SER zones from the phone.
- Pay at Repsol Klin car-wash tunnels, pressure washing and vacuuming services.
- Buy gift cards and shop online with partner brands such as MediaMarkt, El Corte Inglés, Decathlon, IKEA, AliExpress, Miravia, eDreams, PcComponentes — earning between 3% and 10% balance back.
- Earn balance up to 20 cents per litre on fuel and up to 100% of public EV recharge amounts, redeemable on future purchases.
- Subscribe to the Waylet Luz energy tariff for additional savings on home electricity.
- Operate inside the vehicle through Apple CarPlay and Android Auto.
Security is built around PSD2 Strong Customer Authentication (SCA), reinforced login factors and PCI-DSS-certified processing through PAYCOMET. The app is restricted to use within Spain and is provided in Spanish. This page is a third-party technical positioning summary; Waylet is a product of Repsol S.A.