Providing a Charging Receipt Without Requiring a Driver Account
Choose a supported receipt route, publish simple retrieval steps and test one guest journey before opening card-payment charging. A one-time visitor should be able to obtain the relevant payment record without creating an operator account. The chosen terminal and payment integration must support that route.
Describe the guest journey without assuming an app
Start with a hypothetical visitor who pays at the charger, completes a session and leaves without registering with the operator. Ask how that person obtains the receipt and what happens if they request it later.
Decide which delivery method the project will actually support. Depending on the chosen integration, possibilities to investigate include an electronic route, a printed record or assistance from support. Do not advertise all of them merely because they exist in other payment systems.
Keep the requirement separate from an app account. The business must agree what information is necessary for the chosen receipt route, rather than adding a registration step by default.
Obtain evidence for the selected terminal
For alternating current (AC) charging, EVB's AC product range lists a floor-mounted family with point-of-sale payment facilities. Ask the charger, terminal and payment providers to demonstrate the guest-receipt route for the proposed configuration.
Payment-provider documentation illustrates why delivery needs its own arrangement. Stripe, for example, describes email and custom receipts with their own integration requirements. Ask the EVB supplier to demonstrate the chosen guest route without assuming those provider features are already part of the installation.
For the purchasing record, show three steps: where the guest requests the receipt, how they receive it and how support retrieves it later. Record the method actually demonstrated and any fallback the provider supports.
Choose the minimum information needed to find the session
Agree the references support will accept when a driver asks for a record. Useful candidates include the site and outlet, approximate time and a customer-visible payment or session reference.
The chosen provider should specify what is sufficient and safe to request. Staff should not ask customers to send full card details, security codes or photographs exposing sensitive payment information.
Also decide how support verifies that a requested record belongs to the person asking. A convenient lookup process should not disclose another driver's receipt. The supplier must explain the supported access controls rather than leaving reception to invent them.
Test delivery and the fallback route
Use an approved test arrangement to follow the guest process from the customer's perspective. Check how the request is made, what the resulting document contains and whether the record identifies the relevant charging transaction.
Then test the agreed alternative when the preferred route is unavailable. If a driver cannot receive an email, for example, support needs a supported response rather than an instruction to create an app account that may not resolve the problem.
Record the system version, steps observed and any limitation. Ask whether the test environment behaves differently from the live receipt service, so a test-only result is not mistaken for proof of operational delivery.
Explain what document the driver receives
Use accurate names in signs and support instructions. A payment receipt, a charging-session summary and a tax invoice may serve different purposes. Do not promise a legally valid invoice or a particular delivery deadline without the relevant commercial and local requirements being checked.
Name the team responsible for receipt requests and keep the retrieval instructions available to them. If the payment provider must handle an enquiry, define how the operator passes it on without exposing unnecessary customer information.
Give occasional visitors clear retrieval instructions and keep the demonstrated route with the support team. Advertise only the delivery methods supported by the selected terminal and payment service.