Connect a Payter terminal to a Team

Before you can connect a Payter terminal make sure that you have activated it with Payter. If you are in the US or Canada, please follow this guide.

1. Add the Payter Terminal in your Team

1. Open a Team and click on Payment
2. Navigate to Payment Terminals
3. Click Add Terminal and choose Payter payment terminal type
4. Enter the serial number and click Add
   • If the serial number is not found, it means the terminal has not been onboarded with Monta’s Merchant ID. Confirm you have followed the steps here to make this request.
   • See here for North America.

2. Configure the Terminal

Now that the Terminal has been created and added, you can configure it. Payter offers two types of terminals:

• Apollo model with a touch screen
• P6X model without a touch screen

Available settings vary depending on whether a screen is present for configuration.

You have the option to configure a Payter terminal with a screen to “ignore” the screen and act like a terminal without a screen and no touch screen interface.

Apollo Terminal (with touchscreen)

1. Choose the default display language
2. [Optional] Review maximum reservation amount (Leaving blank is recommended)
   • Leaving blank will use Monta’s auto calculation based on your price group and be the same as the app experience. This is Monta’s recommendation.
   • Lowering this will result in the charge session being stopped when the driver reaches the amount.
3. Toggle on touchscreen interface
   • Toggling off will result in this terminal acting like a terminal without a touchscreen
4. Select which choice you want a driver to see when they approach the screen
   • Language (best for terminals in multi-lingual market)
   • Charge selector (best for terminals in single language markets)
5. [Optional] Enable Tap to Stop Charging
   • When enabled, a driver will be able to tap the terminal with same card that was used to start a session to end the session. Other ways drivers can stop a charge session include from their car or (depending on the hardware) on the charge point.
6. [Optional] RFID card support
   • When enabled the payment terminal can read RFID (Charge Keys)
   • This needs to be configured both in Monta and in MyPayter. Look for a setting in your MyPayter account called RFID Mifare.
   • After the terminal reads the ID, Monta still authorizes the charge. An RFID can be added to a team or personal Monta wallet, or operate on a recognized roaming network for Monta to authorize the charge.
   • Not all RFID cards can be read by Payter terminals, but most cards used for secure purposes can. For more about Payter and RFID, see here.
7. Important: After making any changes to the terminal always save and then, use the Remote Action “Refresh” to push the changes to the payment terminal.

P6X (no touchscreen)

1. Choose a display language for the Payment terminal screen
2. [Optional] Review maximum reservation amount (Leaving blank is recommended)
   • Leaving blank will use Monta’s auto calculation based on your price group and be the same as the app experience. This is our recommendation.
   • Lowering this will result in the charge session being stopped when the driver hits this amount
3. [Optional] Enable Tap to Stop Charging
   • When enabled, a driver will be able to tap the terminal with same card that was used to start a session to end the session. Other ways drivers can stop a charge session include from their car or (depending on the hardware) on the charge point.
4. [Optional] RFID card support
   • When enabled the payment terminal can read RFID (Charge Keys)
   • This needs to be configured both in Monta and in MyPayter. Look for a setting in your MyPayter account called RFID Mifare.
   • After the terminal reads the ID, Monta still authorizes the charge. An RFID can be added to a team or personal Monta wallet, or operate on a recognized roaming network for Monta to authorize the charge.
   • Not all RFID cards can be read by Payter terminals, but most cards used for secure purposes can. For more about Payter and RFID, see here.
5. Important!: After making any changes to the terminal settings always save and then, use the Remote Action “Refresh” to push the changes to the payment terminal.

3. Perform a test

Perform a test transaction, so the Monta system can verify the Terminal details. This test should be conducted on site.

1. Click on “Remote actions” and choose the “Test Payment Transaction” tool.
2. Select “Start Test”
3. Monta will make authorize 1 EUR/GBP/DKK/SEK/NOK and cancel it to verify that currency is setup correct. You should see a 1.00 fee appear on your Payter screen appear. Tap a card.
4. If the payment is authorized, the test will complete.

4. Apply the terminal to charge points

1. Click on the three dots in the top right
2. Choose the action Apply to chargers
3. Select the tick box next to the charge point you wish the payment terminal to authorize payment for. You can select more than one. You can also select an entire site.
   • Note: A terminal connected to multiple ports is sometimes called Kiosk mode. When a P6X (no touch screen) terminal is set up in kiosk mode, there is no way to select which port you want to charge at from the terminal. Instead it’s based on which port was just plugged in. See section below for the expected driver experience.

5. View Sessions and Network Logs

Sessions

Sessions show you every session recorded by the terminal, including sessions that ended in a failed payment. You may notice a lot of scanning timeout jobs on P6X terminals because a session is started everytime a driver plugs in a connector, but the driver may decide to pay another way (ex. with the app).

1. Click on the specific payment terminal and open the Sessions tab.
2. Sessions are listed in reverse chronological order (newest first)
3. The committed amount is the final price the driver paid.
4. The failed reason column shows why the session failed to start.

Network Logs

The network logs show you what the terminal is reporting back to Monta and can help you investigate errors.

1. Click on the specific payment terminal
2. Click on the three dots in the top right
3. Select Network Logs
4. When viewing the logs, hover over the text in the Response column to see more details
5. You can refresh the logs using the circle arrow icon in the top right

6. Expected driver experience

You can use this to display instructions on site.

Apollo (with touch screen interface toggled on)

1. Driver arrives at terminal, selects which connector they want to charge at
2. Terminal displays the pre-authorization amount
3. Driver taps card/mobile pay and payment is approved
4. Driver sees the message on screen to plug in vehicle
5. Charge session begins
6. Charge session ends via car (or if enabled by tapping the same card on the terminal)
7. Driver sees QR code on payment terminal screen to download their receipt

P6X (no touch screen) or Apollo with touch screen off

Note: Payment terminal screen is idle until a connector is plugged into vehicle. Plugging in vehicle “wakes up” the terminal and tells it which connector this session is for. We recommend having signage on the site to inform a driver to plug in their vehicle first if they wish to pay via Payment Terminal.

1. Driver plugs in the car
2. Terminal displays the pre-authorization amount.
   • It will be in a state to receive a card for 2 minutes. If no card/mobile payment is read in this time the session will time out. Driver should unplug and plug in again.
3. Driver taps card/mobile pay and payment is approved
4. Charge session begins
5. Charge session ends via car (or if enabled by tapping the same card on the terminal)

Receipts

In order for drivers to receive a receipt, they need to visit https://receipts.monta.com/. Some operators choose to display a QR code on the charger/near the payment terminal that navigates a driver to this url. Suggested wording: To find your receipt for payment terminal transactions, visit https://receipts.monta.com/.

Price and Additional Fees

The terminal will not give details about any additional fees that might apply beyond $/kwh. We recommend displaying the price and other fees somewhere else on the charger.

Users who start a charge session by payment terminal have no way to receive a notification when their charge session has ended and idle fees are beginning.

Pre-authorization and Reservation Limits

If max reservation amount is left blank, Monta will calculate a preauthorization/reservation amount (same as in the app). This is based on an estimated amount of kwh and includes some extra to cover additional fees like idle fees. If the driver hits this kwh limit, the charge session will stop.

If max reservation is set to a value (ex. $40), the charge session will end when a driver has reached this payment limit. If the driver stays plugged in and accumulates idle fees, these will not be collected from the driver.

7. Troubleshooting

Review the Sessions tab to identify failure reasons. Common failed reasons include:

Authorize result was not approved (DECLINED)

• Credit Card brand may not be supported (e.g. American express not supported on P6X or Maestro cards not supported on Payter )
• The driver’s credit card may not authorized for contactless payments, or the limit for contactless payment approval is below the pre-authorization amount. Consider lowering your Max reservation amount to resolve this.

Scanning timeout | job

• No card read within the 2 minute scanning period

Scanning timeout | start from another source

• Within the 2 minute window that the terminal was searching for a card, the plug that initiated the terminal to start scanning had a charge session started another way. Terminals without a touch screen do not come online until a cable is plugged into a car and a session is triggered. The terminal will “search” for a card for 2 minutes. If no card is found, the session times out and the terminal goes back to idle state.

Drivers experiencing multiple card pre-authorization charges

• A driver may see two charges on their credit card if they start two charging sessions in quick succession. This can happen, for example, when a driver’s card is approved but the first session times out before charging begins. If they immediately tap their card again, the second session is authorized while the first hold is still being released. Although Monta sends a command to release the initial pre-authorization as soon as the first session fails, this release may be processed after the second session has already begun.
• The driver will receive any remaining pre-authorized amount back:
  • For a completed charge: The unused portion of the pre-authorization is released as soon as the session ends.
  • For a failed charge: The full pre-authorization is released as soon as the session is marked as failed.

8. Best Practices

1. If you have a payment terminal without a screen, and you have it connected to multiple chargers, add signage to the site to inform drivers they should plug their car in first, before starting payment.
2. If you want to provide receipts to your drivers, add signage to your site that informs them to visit receipts.monta.com (or make a static QR code that directs to this link for them to scan). From this site they can search for their receipt
3. If you leave the reservation amount field blank, we will use Monta’s calculation. If you prefer to set a higher or lower reservation amount, enter it in the Payment terminal settings.
   • If you set the payment reservation amount to $50, we will allow a user to charge for up to $50 of kwh, then stop the charge. If you have additional fees in your price group, like idle fees, you will not collect this if the driver charges up to $50 in kwh.
4. Payter terminals without a screen do not show information about additional fees. The ones with a screen show that there are additional fees, but not what they are. Operators should consider listing the additional fees somewhere else on the charger to inform drivers.
5. P68s terminal connected to a charger does not come online until a cable is plugged into a car and a session is triggered. It will “search” for a card for 2 minutes. If no card is found, the session times out and it goes back to sleep.