How to set up local terminal integration

Local integration is a hardware-only integration, where the payment terminal and charge point communicate directly via a physical cable.

In this setup:

• The charge point itself manages all communication with the terminal, including:
  • Starting the payment
  • Pre-authorizing funds
  • Calculating the final cost*
  • Capturing the payment
• Payments are processed by your PSP, not Monta.
• Monta provides transaction visibility for reconciliation, reporting, and receipt generation.

By linking a payment terminal to a Team in Monta Hub, you unlock:

• Access to Monta’s receipt service
• Transactions recording to simulate revenue flows between teams

Note: If you're using California Pricing, Monta calculates the final cost and sends it to the charge point, which then forwards it to the payment terminal.

⚠️Local terminal integrations do not support kiosk mode. Each charge point must be paired with its own payment terminal.

Choosing the right setup

Depending on your use case, there are two supported setups:

Option 1: Transactions Between Two Teams (Paying Team → Receiving Team)

Recommended for Solution Providers or Resellers

• A Paying Team (e.g. a solution provider) pays for the charge session.
• A Receiving Team (e.g. the CPO) receives the revenue.
• Monta logs a transaction between the two teams.

This setup ensures that:

• Revenue flows to the correct team (the charge point owner)
• Costs are tracked on the provider’s side

Note: Create a dedicated team named ‘Payment terminals’ and ensure that Billing method is set to Operator Transactions.

Option 2: Transactions Within the Same Team

Recommended when only receipts are needed

• The same Team is both the payer and receiver.
• No revenue is transferred between wallets, as it stays within the same team.
• Useful when you simply want to provide a receipt for the payment done through your PSP.

Step-by-step setup

Now that you've chosen the right setup, follow these steps to configure a local payment terminal in Monta Hub by configuring a dynamic or static idTag from Monta team to OCPP configs of the charge point to map transactions for tracking and receipt generation.

Prerequisites

Before integrating a payment terminal with Local Integration, ensure that:

• The charge point supports a custom OCPP configuration key to define the idTag for transactions associated with the payment terminal. Alternatively, it should support a hardcoded idTag or prefix.
• Decide what setup that best suits your use case (See “Choosing the right setup”).
• You have the required permissions in Monta Hub to 1) Payment terminals and 2) CPI tool.
• Create a new team from called “Payment terminals” and set billing method to Operator transaction. This will be referred to as the “Paying team”.

1. Add a Payment Terminal to Hub

1. Select the relevant Team where the charge point is configured.
2. Click on Payments and then on the Payment terminals tab.
3. Select Add Payment Terminal.
4. Choose Local Terminal as the integration type.
5. Fill in the required fields:
   • Name: Assign a recognizable name to the terminal (e.g., charge point serial number + terminal serial number).
   • idTag: Define a unique idTag for transactions. This can be manually entered or automatically generated. Note, some hardware brands only supports a limited number of characters.
     • Partial idTag matching (optional): Enable this if your charge point generates dynamic idTags (e.g., cardTx123456). This allows transactions to be recognized based on a constant prefix (e.g., "cardTx").
   • Select “Paying team”: The transactions will be taken from the Paying Team and added to this Team. I.e. the paying team will be bearing the cost and the receiving team, this team, will be getting the revenue.
   • Reservation amount:
     • Defined in OCPP as:
       • CreditCardPreAuthAmount
       • PaymentTXMaxAmount

3. Link the idTag to Your Charge Point Configuration

To map transactions correctly, configure the charge point with the appropriate idTag settings:

1. Go to your charge point settings in Monta’s CPI tools.
2. Locate the Custom OCPP Configuration Keys.
3. Assign the same idTag used in the payment terminal setup.
   1. In OCPP, idTag may also be referred to as:CreditCardVirtualTagIdorPaymentCardIdTagPrefix
4. Locate the OCPP config CreditCardReceiptUrl and update the URL to https://receipt.monta.com

Once a charge is completed via the payment terminal, a receipt is automatically generated and available on https://receipt.monta.com/. Depending on your configuration, the transaction will either stay within the same team or flow from the Paying Team to the CPO’s team.

Supporting Drivers in Finding Their Receipts

Drivers who make payments via payment terminals can retrieve their receipts at: https://receipt.monta.com/

How Drivers Can Search

To assist drivers in finding their receipts, advise them to:

• Enter the date of the charging session.
• Search by the charging site name or location.

🔍 Note: Searching by the last four digits of the payment card is not always possible, as most locally integrated terminals do not transmit this data.

Exceptions: Siemens SichargeD & Cali Pricing

For integrations via Cali pricing or the chargepoint model Siemens SichargeD, Monta does capture the last four digits of the card. In these cases, drivers can search receipts using those digits.

⚠️ When drivers pay via Apple Pay or Google Pay, card details are often masked, making it difficult to search by card number. In such cases, site and date are the most reliable search parameters.