This release is about payments. Express payments can now be routed to more than one settlement account depending on which site the charger belongs to, and drivers who pay with a card at a Payter terminal can get a receipt for their session as a web page, a PDF or by email.
Express payment splits
Split the money from an Express session across several settlement accounts, based on the site the charger belongs to.
Cost centers are now called accounting units, and they have their own section on the site page alongside Dashboard, Invoicing, Tariffs and Integrations. An accounting unit carries the settlement details for Express payments: the balance accounts the money should go to and the share each one receives.
You can add one or more Adyen balance accounts to an accounting unit, each with a percentage. The percentages have to add up to 100 and a balance account can appear only once. When an Express session is captured, the captured amount is divided between those accounts according to the shares you set. The eMabler transaction commission is deducted before the split.
An accounting unit assigned to a site also applies to every sub-site below it. If a sub-site needs a different balance account or a different split, give it its own accounting unit and that takes precedence over the one it would otherwise inherit. A session settles against the accounting unit that applies to its charger's site.
-
If an accounting unit has no splits configured, Express captures for its sites are routed exactly as before, through your Adyen store configuration.
Receipts for direct payment sessions
Drivers paying with a card at a Payter terminal can now get a receipt for their session, on the web, as a PDF or by email.
eMabler now hosts a receipt page for each direct payment session. The QR code on the terminal points at that session's own link, and scanning it opens the receipt.
If the driver scans the code while charging is still running, the page tells them the receipt is not ready yet and offers to email it. The receipt is then sent on its own once the session has finished and been priced, so the driver does not have to come back to the page. The link also stays valid after the session ends, so a driver who scans the code later still reaches their receipt.
A finished receipt shows the receipt number, session ID, payment method, location, charger and connector, session start and end in the charger's local time, the tariff, energy, duration, cost excluding VAT, VAT and total, along with the card type and the last four digits of the card. The driver can download it as a PDF or have it emailed to an address they enter. Receipts are available in English, Finnish, Norwegian and Swedish.
Terminal settings. Every payment terminal in Connect now has a Receipt source setting. Pick eMabler receipts and the receipt URL is filled in for you, or pick Custom receipt URL if you host receipts yourself. You can also set the receipt language per terminal.
What is printed on the receipt. The company details come from your organization settings: legal name, company address, VAT number and logo. Extra receipt fields let you add your own lines, one per line, printed below the company address.
-
Receipts are produced for direct payment sessions only. Sessions started with an RFID card, a roaming token or through the API do not generate one.
-
The receipt number is unique to each receipt across the platform. It is a reference the driver can quote to your support team.
Vehicle ID in Push Integrations
Push Integrations has a new message type: vehicle identification.
When a charger identifies the vehicle that has plugged in, for example through autocharge, the identification is now pushed to your endpoint as its own message. It tells you which vehicle was seen and which charging transaction it belongs to, so you can tie the session to a vehicle in your own systems, whether for fleet reporting, driver assignment or billing.
Each message carries the vehicle ID and the transaction ID, along with the charger, the site and the time the identification was received. When the charger provides them, the vehicle's MAC address and the vendor ID are included as well.
Add the new message type to your push integration in Connect, just like any other message type.