Paying against another saved vehicle needs a reviewed correction that connects the intended visit, payment reference and authorised adjustment.
A payment against the wrong vehicle profile needs authorised reconciliation with the intended visit. Verify the vehicle and session before changing anything, and preserve the original payment reference, correction reason and any refund or reallocation history.
Several vehicles may belong to the same account while having different visits and access permissions. Choosing another saved registration does not transfer the physical movement recorded by the camera, settle another session or authorise that other vehicle to leave.
Family passes and fleet accounts already required a distinction between the account holder and the vehicle making a visit. Digital payments keep that need.
An account organises vehicles and payments, but each observed visit still concerns a particular vehicle, time and site; a saved profile is not evidence that its vehicle made the journey.
A confirmation screen, assisted payment or one-time session reference may help a customer select the right visit. Additional recognition is not always necessary.
Correction becomes important when the wrong vehicle was chosen or an operator finds a payment linked elsewhere; sharing an account need not mean sharing every vehicle's access entitlement.
Compare the entered registration, arrival period, site and payment reference. If both vehicles have active visits, establish which charge the customer intended to settle rather than choosing whichever record looks convenient. Any refund or reallocation belongs with the authorised payment service, while the original observation should remain available for someone reviewing the correction later.
For example, paying against a household's second car does not settle the first car's observed visit until the intended session is reconciled by the authorised operator. Test how repeated corrections are prevented and how both records appear afterwards. The customer also needs a clear explanation when the association remains unresolved and further review is required.
Aero Ranger CORE Paid Parking connects payment-session context to vehicle review. It is relevant to comparing records before deciding whether an association needs changing.
The actual connector, correction actions and responsible payment operator still need verification in the deployment. CORE's published description does not establish native payment processing or automatic transfer of a charge between profiles; the payment service's authorised process remains necessary.
Aero Ranger: Paid parking; Aero Ranger: Audit logs
Sources were reviewed on the publication date. Check the linked material for current details.
