Electric Vehicle Charging
The solution for processing electric vehicle (EV) charging transactions is Card Present Connect | Electric Vehicle Charging. This solution is built on global standards established by card schemes to ensure reliable, scalable, and secure processing for card-not-present transactions and EMV contact/contactless card-present transactions. Magnetic stripe processing should be used only as a fallback payment method.
Supported Card Types and Entry Modes
These card types are supported for EV charging transactions:
- Mastercard
- Visa
These entry modes are supported for EV charging transactions:
- EMV contact and contactless
- Magnetic stripe swipe
Card-Present Transaction Risk Control Requirements
Card-present transactions carry lower risk than card-not-present transactions because the customer and payment card are physically present, which can result in lower transaction fees. However, acquirers must still apply standard risk-control measures. Acquirers must monitor transaction activity and manage fraud and disputes in accordance with payment network rules, including the Global Acquirer Risk Standards. They also must comply with these Visa risk compliance programs:
- Visa Fraud Monitoring Program
- Visa Dispute Monitoring Program
To meet risk control requirements, acquirers can use one of these options:
- Enable transaction and fraud monitoring tools.
- Ensure that their payment technology providers (PTPs) implement transaction and fraud monitoring tools.
- Deploy their own transaction and fraud monitoring tools.
Each option provides necessary fraud and risk controls for direct merchant relationships and for PTPs that do not operate their own monitoring solutions.
For more information, see Fraud and Risk Management Solutions.
Electric Vehicle Charging Transaction Scenarios
This section describes the EV charging transaction scenarios supported by .
Pre-Pay Transaction Scenario
The Pre-Pay transaction scenario for EV charging enables a customer to pay in advance for the electricity they plan to use when charging their electric vehicle. The transaction amount is calculated based on the amount of time or number of kilowatts (kW) the customer chooses at the start of the charging session. When the final cost of the charging session is less than the estimated amount, an automatic, host-generated partial reversal request is sent at the time of capture.
This diagram shows the Pre-Pay transaction workflow.
The Pre-Pay transaction workflow for EV charging typically consists of this sequence of events:
- The customer chooses the amount of time or number of kW to charge their electric vehicle and presents a payment method to pre-pay for the EV charging session.
- The charging session transaction amount is calculated by the EV charging payment system using the amount of time spent charging or number of kW chosen.
- The authorization request is sent to the
issuing bank. - The issuing bank approves the transaction and sends an authorization response. A temporary hold for the authorized amount is placed on the customer's payment method.
- The EV charging session starts. To add more time or kW, the customer must start a new charging session.
- The EV charging session ends when the customer's chosen amount of time or number of kW is reached. If the charging session ends before the chosen amount of charging is achieved, an automatic, host-generated partial reversal request is sent for the unused transaction amount.
- A capture request for the final transaction amount is sent to the issuing bank. When the final cost of the charging session is less than the estimated amount, an automatic, host-generated partial reversal request is sent at the time of capture.
Post-Pay Transaction Scenario
The Post-Pay transaction scenario for EV charging enables a customer to pay for the electricity they use to charge their electric vehicle when the charging session ends. The final transaction amount is calculated based on the amount of time or number of kilowatts (kW) used during the EV charging session.
This diagram shows the Post-Pay transaction workflow.
The Post-Pay transaction workflow for EV charging typically consists of this sequence of events:
- The customer can choose a specific amount of time or the number of kilowatts (kW) to charge their electric vehicle or can start a charging session for an unspecified amount.
- The customer presents a payment method to pay for the EV charging session.
- The EV charging session starts.
- The EV charging session ends when the customer's chosen amount of time or number of kW is reached, the battery is fully charged, or the customer manually stops the charging session.
- The charging session transaction amount is calculated by the EV charging payment system using the amount of time spent charging or the number of kW consumed.
- A sale request is sent to the issuing bank.
Flexible Transaction Scenario
The Flexible transaction scenario for EV charging enables an efficient and customer- and merchant-friendly solution for EV charging transactions. The transaction amount is calculated based on the amount of time or number of kilowatts (kW) used during the EV charging session. This transaction scenario has implementation prerequisites. For more information, see Prerequisites for the Flexible Transaction Scenario.
The Flexible transaction scenario offers these features and benefits:
- Real-time adjustments to the EV charging session cost. For more information about this key feature, see the description of dynamic adjustment capability below.
- Accommodation of variations in charging time and energy consumption.
- Customers benefit from more accurate billing based on actual usage.
- Merchants benefit from receiving accurate payments for the energy provided and reduce the risk of unpaid balances or excessive refunds.
A key feature of the Flexible transaction scenario is the dynamic adjustment capability. When the EV charging session costs more than the initially estimated amount, an incremental authorization request is sent to obtain the additional transaction amount. A merchant can send multiple incremental authorization requests during the charging sessions to increase the charging transaction amount. When the final cost of the charging session, including incremental authorizations, is less than the estimated amount, an automatic, host-generated partial reversal request is sent at the time of capture.
This diagram shows the Flexible transaction workflow.
The Flexible transaction workflow for EV charging typically consists of this sequence of events:
- The customer presents a payment method to start a charging session at an EV charging station.
- The charging session transaction amount is calculated using the amount of time spent charging or number of kW chosen.
- The authorization request is sent to the issuing bank.
- The issuing bank approves the transaction and sends an authorization response. A temporary hold for the authorized amount is placed on the customer's payment method.
- The EV charging session starts.
- The final transaction amount is calculated by the EV charging payment system based on the charging time or kW consumed. When the transaction amount is more than the initially authorized amount, an incremental authorization is sent to the issuing bank for the difference between the two amounts.
- The issuing bank approves the incremental authorization request, when applicable.
- The EV charging session ends when the battery is fully charged or when the customer manually stops the charging session.
- A capture request for the final transaction amount is sent to the issuing bank. When the final cost of the charging session, including any incremental authorizations, is less than the estimated amount, an automatic, host-generated partial reversal request is sent at the time of capture.
Prerequisites for the Flexible Transaction Scenario
To implement the Flexible transaction scenario for EV charging, your payment system must have these prerequisite capabilities:
- Calculates initial estimated EV charging cost based on average charging duration and energy consumption.
- Monitors real-time EV charging progress.
- Performs incremental authorizations.
- Communicates with payment systems to perform adjustments.
Electric Vehicle Charging EMV and Card Data
You can request these payment services for EV charging with EMV and card data:
- Authorization
- Incremental authorization
- Capture
- Reversal
- Sale
- Void
This table shows which EMV tags are required (M), prohibited (P), optional (O), or conditional (C: send the tag when it is present in the card and terminal):
| Data Element | EMV Tag | Mastercard | Visa |
|---|---|---|---|
| Transaction Date | 9A | M | M |
| Transaction Type | 9C | M | M |
| Transaction Currency Code | 5F2A | M | M |
| Terminal Country Code | 9F1A | M | M |
| Amount Authorized | 9F02 | M | M |
| Amount Other | 9F03 | M | M |
| Application PAN Sequence Number | 5F34 | C | O |
Application Transaction Counter (ATC) | 9F36 | M | M |
| Application Interchange Profile (AIP) | 82 | M | M |
| Dedicated File (DF) Name | 84 | M | M |
| Terminal Verification Results (TVR) | 95 | M | M |
| Issuer Application Data | 9F10 | M | M |
| Application Cryptogram | 9F26 | M | M |
Cryptogram Information Data (CID) | 9F27 | M | O |
| Terminal Capabilities | 9F33 | M | M |
| Cardholder Verification Method (CVM) Results | 9F34 | M | O |
| Unpredictable Number (UN) | 9F37 | M | M |
| Form Factor Indicator | 9F6E | O (Authorization); P (Refund) | C |
| Mastercard Authenticated Application Data | 9F60 | O | Does not apply |
| Mastercard Kernel Identifier-Terminal | 96 | O | Does not apply |
Electric Vehicle Charging Transaction Descriptions
Use the EV charging transaction descriptions listed in the tables to help you identify types of request messages for production transactions in and in your transaction reports. Include the clientReferenceInformation.comments field with a transaction description value when you submit a request.
If you want to review your test environment result after you add the comments field, contact customer support.
Pre-Pay Transactions
This table lists the pre-pay transaction descriptions:
| Service | Card present (CP) or Card not present (CNP) | Comments Field Value | Description |
|---|---|---|---|
| Authorization | CP | Pre-Pay Auth | Authorizes specific amount or duration to start the EV charging session. |
| Capture | CP | Pre-Pay Capture | Captures final amount for the charging session. |
| Capture | CP | Pre-Pay Capture Less Than Auth | Captures final amount for the EV charging session when less than the authorization amount. Sends automatic, host-generated partial reversal request for the unused amount when the charging session expires. |
Post-Pay Transactions
This table lists the post-pay transaction descriptions:
| Service | Card present (CP) or Card not present (CNP) | Comments Field Value | Description |
|---|---|---|---|
| Sale | CP | Post-Pay Sale | Sale for the amount used during the EV charging session when the customer pays after the charging session. |
Flexible Transactions
This table lists the flexible transaction descriptions:
| Service | Card present (CP) or Card not present (CNP) | Comments Field Value | Description |
|---|---|---|---|
| Authorization | CP | Flexible Auth | Authorizes specific amount or duration to start the EV charging session. |
| Capture | CP | Flexible Capture | Captures final amount for the charging session. |
| Capture | CP | Flexible Capture Less Than Auth | Captures final amount for the EV charging session when less than the authorization amount. Sends automatic, host-generated partial reversal request for the unused amount when the charging session expires. |
| Incremental authorization | CP | Flexible Incremental Auth | Requests incremental authorization when final amount is higher than estimated amount. |
Error Transactions
This table lists the error transaction descriptions:
| Service | Card present (CP) or Card not present (CNP) | Comments Field Value | Description |
|---|---|---|---|
| Reversal | CP | Error REVERSAL Timeout | Reverses previous authorization request for which a response was not received. Reversal not used for sale. |
| Reversal | CP | Error REVERSAL | Reverses previous authorization request. Reversal not used for sale. |
| Void | CP | Error VOID Timeout | Voids previous sale or capture request for which a response was not received. |
| Void | CP | Error VOID Payment | Voids previous payment (sale) within the same day. |
| Void | CP | Error VOID Capture | Voids previous capture within the same day. |
Thanks for your feedback!
Last published: September 29, 2026