Parking

Card Present Connect | Parking supports multiple payment models for the parking industry. This solution accommodates various attended and unattended parking models, from street meters to gated facilities, with transaction types tailored to each model.

Use this guide to:

Understand supported parking payment services.
Map transaction types to your parking operations.
Implement the payment flows that apply to your business.

The parking payment services described in this guide are supported by information in the Card Present Connect | Retail Integration Guide. This guide contains detailed payload examples and field-level specifications that support the parking transaction flows discussed here.

Supported Card Types and Entry Modes

These card types are supported for parking transactions:

Mastercard
Visa

These card entry modes are supported for parking transactions:

EMV contact and contactless
Magnetic stripe swipe

Parking Payment Models

The Parking solution supports various parking payment models on attended and unattended devices. These typical parking payment models are discussed in this guide:

On-street parking meter
Kiosk
Booth
Tap and Go

The list does not include all types of parking payment models.

On-Street Parking Meter Payment Model

This section is an overview of a typical on-street parking meter payment model.

Terminal Types: unattended payment devices.
Typical Implementation Patterns:
- Pre-authorize for the maximum parking time, capture the actual amount charged, and reverse any unused funds.
- Request an incremental authorization when the driver extends the parking time.
Payment Services: for information about payment services supported for unattended devices, see Unattended Parking Payment Services.

Kiosk or Booth Parking Payment Model

This section is an overview of a typical parking kiosk or booth payment model. Payment terminals used in this model can be attended or unattended. Typically, booths are attended and kiosks are unattended.

Terminal Types: attended or unattended payment devices.
Typical Implementation Patterns:
- Process a sale transaction for the calculated parking fee.
- Issue a refund for payment errors or cancellations.
Payment Services: for information about payment services for attended devices, see Attended Parking Payment Services. For information about payment services for unattended devices, see Unattended Parking Payment Services.

Tap and Go Parking Payment Model

This section is an overview of a typical tap-and-go parking payment model.

Terminal Types: unattended payment devices.
Typical Implementation Patterns:
- Pre-authorize on entry and capture the actual parking fee on exit.
- Send an account verification request (AVR) before entry to validate the payment card.
- Request an incremental authorization when the driver extends the parking time.
Payment Services: for information about payment services supported for unattended devices, see Unattended Parking Payment Services.

Parking Payment Services

The Parking solution provides various REST API payment services for attended and unattended parking devices. Supported services are documented by device type first. Details about payment services that use the same request and response fields follow. Examples include Incremental Authorization and Capture.

Parking Transaction Descriptions

This table lists the valid values for the clientReferenceInformation.comments REST API field used in Parking payment services:

Service	Field Value	Description
Authorization	`Parking AVR`	Zero-dollar account verification request (AVR).
Authorization	`Parking Authorization`	Request to place a hold on the cardholder's account. Capture or reversal required.
Incremental authorization	`Parking Incremental Auth`	Request for an incremental authorization when the final amount is higher than the estimated amount.
Reversal	`REVERSAL`	Reverse an authorization request, including incremental authorization.
Reversal	`REVERSAL Timeout`	Reverse an authorization that did not receive a response. Use the `clientReferenceInformation.transactionId` value from the original transaction.
Capture	`Parking Capture`	Captures final amount.
Capture	`Parking Capture Less Than Auth`	Captures a final amount less than the initial authorization amount. The host automatically sends a partial reversal request for the unused amount.
Sale	`Parking Sale`	Combined authorization and capture when final amount is known.
Refund	`REFUND Capture`	Credit of a previous capture transaction. Used when a capture cannot be voided.
Refund	`REFUND Payment`	Credit of a previous sale transaction. Used when a sale cannot be voided.
Credit	`Parking Standalone Credit`	Credit with no reference to a previous transaction.
Void	`VOID Capture`	Void a capture. Prior to merchant configured TC33 file generation time. Typically same day.
Void	`VOID Payment`	Void a sale. Prior to merchant configured TC33 file generation time. Typically same day.
Void	`VOID Refund`	Void a refund. Prior to merchant configured TC33 file generation time. Typically same day.
Void	`VOID Credit`	Void credit. Prior to merchant configured TC33 file generation time. Typically same day.
Void Timeout	`VOID Timeout`	Void a capture, sale, refund, or credit that did not receive a response. Use the `clientReferenceInformation.transactionId` value from the original transaction.

Parking EMV and Card Data

You can request these parking payment services with EMV and card data:

Authorization: standard and incremental
Capture
Credit

Send a conditional tag when it is present in the card and the terminal. This table shows whether each EMV tag is required (M), prohibited (P), optional (O), or conditional (C) for Mastercard and Visa transactions:

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

Attended Parking Payment Services

This section provides information about payment services for attended devices, including fixed payment terminals and mobile point-of-sale (mPOS) devices.

Attended devices are payment terminals operated by staff or located where assistance is available.

These are some implementation considerations when configuring parking payment services for attended devices:

Pre-authorization requests for EMV contact transactions must include EMV tags in follow-on capture requests.
Payment requests for attended mPOS devices must include the pointOfSaleInformation.catLevel field.
When the capture amount is less than the authorization amount, the host sends an automatic partial reversal for the unused amount.
Stand-alone credits and linked refunds are supported for attended parking operations.

These payment services are the same for attended and unattended devices: Incremental Authorization and Capture.

Unattended Parking Payment Services

This section provides information about payment services for unattended devices.

Unattended devices are payment terminals that operate without staff assistance. Examples include parking meters, automated kiosks, and entry/exit gate systems.

These are some implementation considerations when configuring parking payment services for unattended devices:

Account verification requests (AVRs) validate payment cards without authorizing funds.
Pre-authorization requests for EMV contact transactions must include EMV tags in follow-on capture requests.
Incremental authorizations support extended parking sessions.
Unattended sale and pre-authorization requests must include the pointOfSaleInformation.catLevel field to identify the terminal as unattended.
When the capture amount is less than the authorization amount, the host sends an automatic partial reversal for the unused amount.

These payment services are the same for attended and unattended devices: Incremental Authorization and Capture.

Was this page helpful?

Last published: September 29, 2026