Configure the BP fuel connection

Follow this guide to create the secure connection used to fetch fuel transactions. 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.

What you’ll accomplish

Create the secure connection used to fetch fuel transactions. The instructions below follow the supplied module’s controller, form and model rules, including server-side validation and downstream effects.

Follow these steps

1. Select sandbox or production environment.
2. Select authentication method.
3. Enter public HTTPS base URL and transactions endpoint.
4. Enter required credentials/token endpoint.
5. Enter mapping JSON containing transaction_id and transaction_at.
6. Set interval from 15 to 1,440 minutes.
7. Save inactive.
8. Test.
9. Activate only after validation.

Fields and options to review

Rules the system enforces

• Active configuration requires base URL and transactions endpoint.
• Authentication-specific credentials must be present.
• Header values and secrets are sanitised; line breaks are rejected.

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.

Continue with related guidance