Create a fuel card
Follow this guide to add a masked card alias and allocate it to a driver/vehicle. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.
Where to goAdmin Area → Courier & Logistics → Settings → BP Fuel → Fuel Cards → Add
What you’ll accomplish
Add a masked card alias and allocate it to a driver/vehicle. The instructions below follow the supplied module’s controller, form and model rules, including server-side validation and downstream effects.
Follow these steps
- Enter a clear card alias.
- Enter the card number through the protected field.
- Select driver and/or vehicle allocation.
- Save.
- Check only the masked last four digits are displayed.
Fields and options to review
AliasRequired.
Stored display**** plus the final four digits.
AllocationDriver and/or vehicle references.
ActiveControls matching/use in sync.
Rules the system enforces
- The full card number is not retained as a visible value.
How to confirm it worked
- The source record, status/history and any downstream notification, provider, POD or finance record should agree after the action.
Security, audit and operational checks
- Use the exact record and least-privilege role before changing any state.
- Verify the saved record after every action; a browser message alone is not evidence that every downstream step completed.
- Use protected document and image routes rather than exposing server filesystem paths.
- Keep customer, driver, provider, financial and credential data within the authorised workflow.
- For provider, finance, employment, transport and compliance decisions, follow the organisation’s authorised professional process.
Do not bypass the code flowDo not force database values, invent a status, mark a job completed without signed POD evidence, or expose encrypted credentials to make a screen appear successful.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.