The Parking Experience Team is responsible for the technical environment and systems that handle look-up queries. This includes:
Invoice printing, business rules, and distribution are handled by other Riverty teams.
Look-ups are triggered immediately after receiving a parking session via the /v1/clients/{clientId}/receivables
endpoint. Based on the country, the system queries a national provider.
For example:
No, Riverty does not cache any data. Every lookup request from a Merchant is forwarded to a data provider in real time.
The system is continuously monitored. If anomalies or high failure rates are detected in lookup processes, alerts are triggered to ensure rapid investigation and response.
No, we do not whitelist license plates.
However, we can whitelist the following:
Yes, the Parking API detects duplicate receivables and avoids forwarding them for invoicing.
We recommend collaborating directly with the Parking Service Provider to clarify edge cases or integration questions.
Deviation reports are sent once a week. Additionally, webhook notifications are available to track receivable statuses in real time.
Use ISO 3166-1 alpha-2 country codes.
Examples: "NO"
(Norway), "FI"
(Finland), "SE"
(Sweden)
The Riverty tech team builds and maintains the Free Flow Parking backend — a centralized invoicing platform.
Claims are transferred to IFA Finance DAC, a finance institution based in Dublin, Ireland.
Yes, we support crediting. You can view API documentation here:
https://api-pt.riverty.io/parking/swagger/index.html
The Receivables API allows users to:
Use the endpoint:
POST /v1/clients/{clientId}/receivables
Use:
POST /v1/clients/{clientId}/receivables/{receivableId}/invoicerecipient
Make sure your client is configured for Contract Parking before sending the request.
No, the Parking API is designed to handle one plate number, one parking event, in one facility per request.
element
object represent in the API?The element
defines the parking space location:
Yes, we have Parking Tunnel Service (aka PTS). We can pull data from your system and integrate it with the Parking API. Once we receive your data, we handle the look-up process internally based on that input.
Contract Parking allows API users to bypass the car owner lookup by license plate and instead directly provide the contract payer’s details. These details are then used to automatically issue and send an invoice to the specified address.
You can refer to the documentation for full process details:
https://api-pt.riverty.io/parking/swagger/index.html
Endpoint: /v1/clients/{clientId}/receivables/{receivableId}/invoicerecipient
You can find full details for all supported Parking API features in the Swagger documentation:
https://api-pt.riverty.io/parking/swagger/index.html
Tax calculations for crediting follow rules based on the taxIncluded
flag.
taxIncluded = true
Example:
{
"currencyValue": "100",
"taxAmount": "20",
"taxRate": "0.25"
}
KBA (Kraftfahrt-Bundesamt) has specific requirements for acceptable license plate formats when submitting lookup requests for German vehicles.
You can find more details on the official KBA website: https://www.kba.de
Do you find this page helpful?