Customer application
Laadpas (charging card)
Request a charging card in a few steps, with no data left lying around afterwards.
- Role
- Mendix developer and front-end developer
- Period
- January 2024 – October 2024
- Client
- ANWB
- Type
- customer application (public)
- Key technology
- Mendix 10, REST/OAuth, SCSS
About the project
If you want a charging card, you first pick the kind: free or on a subscription, for private or business use. Then you choose how many cards and key fobs you need. That part happens in this app. The customer then finishes off with the charging card partner, in a step where they pay and set up a direct-debit mandate.
What I built
I worked on the request flow, the validation and the integrations. The styling was entirely mine, from the forms and choice buttons to the modals and the thank-you page.
Key features
Address lookup
a postcode and house number are enough, and the rest comes from the BAG (the Dutch national register of addresses and buildings).
Instant validation
in the browser: you see a mistake straight away, not after you hit submit.
Payment and direct-debit mandate
with the partner, through a secured REST integration using OAuth.
Privacy by design:
every half hour the app deletes all customer data. Once the request has gone to the partner, nothing stays behind, and honestly I think that's the neatest part of the app.
Tools used
- Mendix
- Mendix 10.24nanoflowsscheduled events
- Integrations
- REST/OAuthBAG APIGoogle Tag Manager
- Front-end
- SCSSAtlas
What I learned
- 01
Building a customer flow: that's quick and hard to get wrong, and whose use you can measure.
- 02
Connecting securely to an external partner: with OAuth.
- 03
Data minimisation in practice:: keep data for as long as you actually need it, then get rid of it.