Skip to Main Content
Riverty Docs
riverty logo Docs

Introduction

Riverty Free Flow Parking empowers parking providers using Automatic Number Plate Recognition technology to easily invoice customers. This is particularly helpful for Parking Providers who serve large numbers of parkers who do not sign up for the Providers' app or providers who do not have an app.

Advantages for Merchants:

  1. Automated connection to local vehicle registration authorities
  2. Full upfront payment for new invoices
  3. All invoice and customer service provided by Riverty
  4. Webhook connectivity for Merchant dashboards

Advantages for Consumers:

  1. Full Free Flow Parking experience (no Kiosk)
  2. 48 hours to pay open invoices online free of charge
  3. Full access to Riverty Customer Service

Consumer Experience

0ec6953a-2b3d-4954-8d85-ea36640efd54.png

Parking API – Handle and Process Parking Transactions

  1. Customer enters parking → The ANPR system registers the vehicle plate number.
  2. Car Owner exits the parking facility without paying → ANPR system sends request to Parking API → Create Receivable request.
  3. Validation & Processing → The API validates the request and processes the parking session.
  4. Response with Receivable ID → The API returns a receivableId, which is later used for contract parking or invoicing.
  5. Session End & Invoicing → The invoice is generated based on the receivable data.

Status Flow:

  • Normal: PENDING → LOOKUP_REQUESTED → INVOICE_REQUESTED → INVOICE_CREATED
  • Errors: CARHOLDER_RESOLUTION_FAILED, WHITELISTED

Key Features:

  • ✔ Supports real-time and post-parking invoicing.
  • ✔ Provides transaction tracking via receivableId.
  • ✔ Ensures compliance with invoicing regulations.

Contract Parking API – Automate Subscription-Based Parking

  1. Create a receivable using the Parking API (POST /v1/clients/{clientId}/receivables).

  2. If the client is configured for Contract Parking, the receivable is created with status: WAITING_CONTRACT_DATA.

  3. Submit contract payer details using:
    POST /v1/clients/{clientId}/receivables/{receivableId}/invoicerecipient

Upon successful submission, the receivable status updates to PENDING, and automatic processing continues.

Status Flow:

  • Normal: PENDING → INVOICE_REQUESTED → INVOICE_CREATED

Do you find this page helpful?