Archived snapshot · this is the current version
This is V1.26.09, effective September 10, 2026. It matches the live document.
Current version → All versions
Skip to main content
UNBOOT.ME
View my citation
—— Legal · Before you pay

Payment
Agreement

Effective date
September 10, 2026
Last updated
September 10, 2026
Version
V1.26.09
Version history →
Sections
53
The key point

Authorizing a payment and agreeing with the notice are two different things. You can pay to get your vehicle released and still dispute whether the notice should have been issued.

Read the record and the amount on screen before you pay. Keep the receipt. Nothing here waives a right that cannot lawfully be waived — including your billing-error and card-dispute rights.

This Payment Agreement (“Payment Agreement” or “Agreement”) governs payments submitted through the Unboot.me platform in connection with parking compliance, parking enforcement, vehicle warning, citation, immobilization, release, towing-related, or associated transactions. Please read this Agreement carefully before submitting payment.

By selecting or activating an acceptance control associated with this Agreement and submitting payment through Unboot.me, you acknowledge that you have reviewed the applicable enforcement record and payment information presented to you, represent that you are authorized to use the selected payment method, authorize the disclosed transaction, and agree to this Payment Agreement.

This Agreement supplements the Unboot.me Terms & Conditions and Privacy Policy. If there is a conflict between this Agreement and the Terms & Conditions concerning a payment-specific issue, this Payment Agreement controls as to that payment-specific issue, except where applicable law requires otherwise.

Nothing in this Agreement eliminates, limits, or waives any right that cannot lawfully be waived.

Full index
Part About Unboot.me and definitions
01

About Unboot.me

Unboot.me is a technology platform providing software and related services for parking compliance and parking enforcement operations.

The platform may be used by authorized property owners, property managers, parking operators, security organizations, enforcement agencies, field operators, towing providers, educational institutions, residential communities, commercial properties, and other authorized entities (“Authorized Agencies”).

Among other functions, Unboot.me may facilitate:

documentation of parking-related events;
warnings;
citations;
vehicle immobilization records;
vehicle release workflows;
towing requests;
photographs and enforcement documentation;
payment processing;
payment-status records;
location-confirmation records;
electronic receipts;
dispute administration;
notifications;
audit records; and
related operational and compliance functions.

UNLESS EXPRESSLY STATED OTHERWISE FOR A PARTICULAR TRANSACTION, UNBOOT.ME IS A TECHNOLOGY PROVIDER AND PAYMENT-PROCESSING INTERFACE AND IS NOT THE PROPERTY OWNER, VEHICLE OWNER, GOVERNMENTAL AUTHORITY, TOWING OPERATOR, OR FIELD ENFORCEMENT OPERATOR RESPONSIBLE FOR THE UNDERLYING PARKING ENFORCEMENT DECISION.

An Authorized Agency or its authorized personnel generally determines whether an enforcement event should be created and is responsible for the underlying authority for enforcement, applicable parking rules, signage, property authorization, violation classification, and enforcement fee, except for any separate Unboot.me platform or processing fee expressly disclosed before payment.

02

Definitions

For purposes of this Agreement:

“Authorized Agency”
means the property owner, property manager, parking operator, enforcement organization, security organization, institution, business, association, or other entity authorized to create or administer a parking compliance or enforcement record through Unboot.me.
“Cardholder”
means the individual legally authorized to use the payment card or other payment instrument submitted for a transaction.
“Enforcement Record”
means a warning, citation, immobilization, parking-compliance, tow-related, or other parking-enforcement record created or maintained through Unboot.me.
“Motorist”
means the driver, registered owner, lessee, person in possession of the vehicle, or other individual interacting with an Enforcement Record.
“Payer”
means the individual submitting payment. The Payer may or may not be the registered owner or driver of the vehicle.
“Payment Processor”
means a third-party processor, acquiring bank, payment gateway, card network, financial institution, or related provider participating in the processing of a transaction.
“UB.me ID”
means the human-readable identifier assigned to an Enforcement Record by Unboot.me.
“Vehicle”
means the vehicle associated with the Enforcement Record being reviewed or paid.
03

Application of this Agreement

This Agreement applies whenever a person submits a payment through Unboot.me relating to an Enforcement Record.

The Agreement applies whether the payment concerns an immobilization, citation, release-related amount, or another charge displayed through the platform.

Warnings for which no payment is required are not payment transactions and therefore generally are not governed by the payment-authorization provisions of this Agreement.

Additional contractual terms may apply to towing, storage, impoundment, vehicle release, property access, or services provided directly by third parties.

Part Before you pay
04

Review of the Enforcement Record before payment

Before payment is submitted, the Payer is responsible for reviewing the information presented through Unboot.me. Depending on the transaction, this information may include:

Vehicle license plate Registration state Vehicle description Record type Alleged violation Photographs Enforcement location Date and time Authorized Agency Amount due Payment status UB.me ID Location-confirmation information

The Payer should not submit payment if the Payer believes that the displayed Vehicle, Enforcement Record, amount, or other material transaction information is not the transaction the Payer intends to pay.

If information appears incorrect, the Payer should use the available Unboot.me support or dispute process.

05

Payment authorization

By submitting a payment through Unboot.me, the Payer expressly represents, warrants, acknowledges, and agrees that:

1. the Payer has intentionally initiated the transaction;
2. the Payer has reviewed the amount displayed before payment;
3. the Payer has reviewed sufficient information identifying the applicable Enforcement Record;
4. the Payer is the Cardholder or otherwise has actual authority from the Cardholder to use the payment method;
5. the payment information supplied is accurate;
6. the Payer authorizes the Payment Processor and other financial institutions participating in the transaction to process the displayed amount;
7. the Payer authorizes Unboot.me to transmit information reasonably necessary to complete, authenticate, document, reconcile, refund, investigate, or defend the transaction;
8. the payment is being made in connection with the specifically identified Enforcement Record; and
9. the Payer understands the consequences of submitting the payment as described in this Agreement and on the applicable payment screen.

This authorization is effective when the Payer submits the payment.

06

Third-party payers

A person other than the Vehicle owner or driver may pay an Enforcement Record. For example, a spouse, employer, family member, fleet operator, rental company, friend, or other authorized person may submit payment.

A third-party Payer is bound by this Agreement to the same extent as any other Payer.

Payment by another person does not automatically make that person the Vehicle owner, driver, violator, or party responsible for the underlying Enforcement Record.

The third-party Payer nevertheless represents that the payment method was used with lawful authorization.

07

Amount authorized

The amount presented immediately before payment is the amount the Payer authorizes Unboot.me and the Payment Processor to process.

The displayed total may consist of one or more authorized amounts, including an enforcement fee, immobilization-related amount, citation amount, or other separately identified charge.

Any processing, convenience, platform, administrative, tax, or similar charge collected through the transaction should be disclosed before the Payer submits payment where required by applicable law.

Unboot.me will not rely on this Agreement as authorization to impose an undisclosed material charge.

Part What payment accomplishes
08

What payment accomplishes

The operational effect of payment depends upon the Enforcement Record.

For an immobilized Vehicle, payment may satisfy the payment condition required for the applicable release workflow and may notify authorized personnel that the Vehicle is eligible for immobilization-device removal.

For a citation, payment may satisfy the amount associated with that citation and cause the transaction to be recorded as paid.

For other Enforcement Records, payment produces the effect identified through the payment interface.

Payment does not itself guarantee that a physical action, including boot removal or vehicle release, will occur instantaneously.

When field personnel, towing providers, property personnel, or other third parties must perform an action after payment, actual completion may depend upon location, availability, traffic, weather, safety, access, operational conditions, or other circumstances outside Unboot.me’s direct control.

09

Payment is not necessarily an admission of liability

Submitting payment constitutes authorization of the financial transaction.

However, unless applicable law provides otherwise, payment does not necessarily constitute an admission by the Payer that every factual or legal allegation underlying the Enforcement Record is correct.

A Motorist may retain any non-waivable right to challenge an Enforcement Record through an available Unboot.me dispute process, Authorized Agency process, court, administrative process, or other procedure recognized by applicable law.

A Motorist may dispute the underlying enforcement decision while still having intentionally authorized the payment transaction.

Accordingly, a disagreement concerning whether an Enforcement Record should have been issued does not, by itself, mean that the associated payment was unauthorized or fraudulent.

10

Unboot.me’s role in the underlying enforcement decision

Except where Unboot.me expressly states otherwise, Unboot.me does not independently determine whether the Vehicle originally violated a parking rule.

The Authorized Agency or its properly authorized personnel is responsible for establishing its authority to enforce the applicable parking rules and for complying with laws applicable to the underlying enforcement activity.

This may include requirements concerning property authorization, parking policies, signage, notices, immobilization authority, fee limitations, towing requirements, grace periods, vehicle release requirements, or other jurisdiction-specific requirements.

Unboot.me’s processing or documentation of an Enforcement Record does not independently establish that the underlying enforcement action was lawful.

Likewise, Unboot.me’s role as technology provider does not make Unboot.me the owner, possessor, lessor, towing company, or enforcement agency merely because a transaction is processed using the platform.

Part Evidence and location
11

Location confirmation

Unboot.me may request that the Payer confirm the Payer’s location in connection with a payment.

Where enabled, the platform may compare a Payer-provided or device-derived location against the documented location associated with the Vehicle.

Location confirmation may use device geolocation and may allow a user to adjust or confirm the location being submitted.

A payment may be categorized as verified, mismatched, overridden, or unverified depending upon the information available to the system.

A Payer may in certain circumstances proceed when location permission has been denied or is unavailable. In that event, the transaction may be recorded as having unverified location information.

Location verification is one item of transaction evidence. It is not represented as absolute proof of identity, vehicle ownership, legal responsibility, or the legality of the underlying Enforcement Record.

12

Payment and enforcement evidence

The Payer acknowledges that Unboot.me is designed to create a documented electronic record surrounding an enforcement event and payment.

Subject to system availability, applicable law, the Privacy Policy, and the information associated with the particular Enforcement Record, the evidentiary record may include information such as:

UB.me ID License plate Registration state Vehicle information Enforcement location Authorized Agency Record type Violation description Amount charged Timestamps Photographs Payment date Payment authorization information Processor transaction identifiers Payer name Payer telephone Payer email Payment-method information permitted to be retained Location-verification status Location-confirmation evidence Payment receipts Correspondence Dispute submissions Operational status updates Release-related events Towing-related events System audit information

The purpose of maintaining these records includes transaction administration, customer support, fraud prevention, auditing, compliance, dispute resolution, chargeback response, litigation support, and protection of the Motorist, Authorized Agency, field personnel, Unboot.me, and other authorized participants.

13

Photographic and location evidence

An Enforcement Record may contain photographs of the Vehicle, license plate, parking position, immobilization activity, signage, location, or other relevant conditions.

Payment documentation may also include maps or location-confirmation information.

The existence of such information does not create an irrebuttable presumption that the Enforcement Record is valid.

It may, however, be used as evidence concerning the identity of the Vehicle, location, timing, enforcement event, payment transaction, release process, or a later dispute.

Part Processing and card security
14

Payment Processors and financial institutions

Payments submitted through Unboot.me may be processed using one or more independent Payment Processors.

Payment processing therefore may also be subject to terms, network rules, security procedures, fraud screening, authorization rules, and operational requirements established by those Payment Processors, card networks, acquiring banks, or issuing banks.

Unboot.me does not control whether an issuer approves or declines a particular card transaction.

A transaction may be rejected because of insufficient funds, issuer restrictions, fraud screening, incorrect payment information, network failure, authorization failure, card restrictions, security requirements, or other circumstances.

Unboot.me may request that the Payer use another available payment method when a transaction cannot be authorized.

15

Payment card security

Unboot.me may use third-party payment infrastructure designed to limit the exposure of payment-card information to the Unboot.me environment.

Payment card information will be handled in accordance with applicable contractual, technical, security, and legal requirements.

The Payer understands that no electronic payment system can be represented as entirely immune from security incidents.

Unboot.me’s collection and use of personal information is further governed by its Privacy Policy.

16

Transaction descriptor

The transaction may appear on the Cardholder’s financial statement using a merchant or billing descriptor associated with Unboot.me, an Authorized Agency, a Payment Processor arrangement, or another descriptor disclosed in connection with the payment.

The Payer is responsible for reviewing the transaction receipt and retaining it so that the charge can later be recognized.

If the Payer or Cardholder does not recognize a statement descriptor, the Payer should compare the amount and date against the applicable Unboot.me receipt before claiming that the transaction was unauthorized.

17

Electronic acceptance

The Payer’s affirmative electronic action accepting this Agreement and submitting payment constitutes the Payer’s electronic acceptance of this Payment Agreement to the extent permitted by applicable law.

Unboot.me may maintain evidence of that acceptance, including the version of the Agreement presented or otherwise applicable at the time of payment and the date and time of acceptance.

Electronic acceptance has the same intended contractual effect as a handwritten signature to the extent recognized by applicable law.

Nothing in this provision eliminates any special disclosure, consent, delivery, or record-retention requirement imposed by applicable law.

Part Receipts and payment status
18

Transaction receipt

After successful payment, Unboot.me may generate an electronic receipt associated with the Enforcement Record. The receipt may contain information such as:

Amount paid Payment status Record type UB.me ID Vehicle information Date and time Payment method information Payer information Authorized Agency Location Transaction evidence Photographs Maps Location-confirmation status Timeline information

The Payer should download or otherwise retain the receipt for the Payer’s records.

A receipt documents the payment and associated information available at the time of generation.

19

Server-authoritative payment status

Unboot.me may maintain a server-side record establishing whether and when an Enforcement Record was paid.

The Payer understands that refreshing a browser, using another device, clearing browser storage, reinstalling software, losing connectivity, or otherwise changing the Payer’s local device environment does not erase a completed server-side transaction.

A completed payment therefore should not be resubmitted merely because a local interface temporarily fails to display the payment.

The Payer should verify the transaction status or contact Unboot.me before attempting a second payment where there is uncertainty.

Part Refunds and duplicate payments
20

Duplicate payments and processing errors

If the Payer believes that Unboot.me or the Payment Processor processed the same obligation more than once, processed an incorrect amount, or processed a transaction after the system indicated failure, the Payer should promptly contact Unboot.me.

Unboot.me may investigate using the applicable UB.me ID, processor information, timestamps, receipt information, and payment audit records.

Confirmed duplicate charges, demonstrable processing errors, or other erroneous transactions will be handled as required by applicable law and applicable payment-network or Payment Processor requirements.

Nothing in this Agreement permits Unboot.me to retain money that applicable law requires to be returned.

21

Refunds

Unless otherwise required by law or expressly stated at the time of payment, payments associated with completed parking enforcement transactions are generally final after processing because the payment may immediately change the operational status of an Enforcement Record and may initiate release or other performance.

A refund nevertheless may be issued where appropriate, including circumstances involving:

a verified duplicate transaction;
an amount processed in error;
cancellation authorized by the responsible Authorized Agency;
a determination through an applicable dispute process that a refund is warranted;
a Payment Processor correction; or
circumstances in which applicable law requires repayment.

Unboot.me may require sufficient information to verify the transaction before a refund is processed.

A refund may be returned only through a method permitted by the Payment Processor and applicable financial institution.

The time required for a refund to appear on an account may depend upon the Payment Processor or financial institution and is outside Unboot.me’s direct control.

Part Disputes and chargebacks
22

Disputing an Enforcement Record

A disagreement with the underlying warning, citation, immobilization, tow-related action, or other Enforcement Record should ordinarily be raised through the designated dispute or support process.

The Payer may be asked to provide contact information, an explanation, photographs, documents, or other evidence supporting the dispute.

Submission of an enforcement dispute does not automatically establish that the original payment was unauthorized. Similarly, submitting payment does not eliminate a non-waivable right to challenge the underlying enforcement action.

Unboot.me may administer, facilitate, document, route, or otherwise support the dispute process for an Authorized Agency.

23

Chargebacks, payment disputes, and bank inquiries

A “Chargeback” or “Payment Dispute” generally occurs when a Cardholder asks a financial institution or payment network to investigate or reverse a payment.

Nothing in this Agreement prevents a Cardholder from exercising a legitimate right provided by applicable law or payment-network rules.

However, initiating a Payment Dispute does not automatically establish that the payment was fraudulent, unauthorized, incorrectly processed, or otherwise invalid.

When Unboot.me receives notice of a Payment Dispute, retrieval request, fraud inquiry, pre-dispute inquiry, Chargeback, or similar proceeding, Unboot.me may investigate and respond.

Unboot.me expressly reserves the right to challenge a Payment Dispute when available evidence indicates that the transaction was authorized, correctly processed, and associated with the identified Enforcement Record.

24

Authorization to provide evidence to payment institutions

By submitting payment, the Payer authorizes Unboot.me, to the extent reasonably necessary and permitted by law, to provide relevant transaction and enforcement evidence to entities involved in investigating or resolving a Payment Dispute. Those entities may include:

the Payment Processor;
acquiring bank;
issuing bank;
payment-card network;
fraud-prevention provider;
payment gateway;
Authorized Agency;
dispute-resolution service provider;
legal counsel;
insurer;
regulator;
governmental authority;
court; or
other entity legally entitled to receive the information.

Information submitted may include, where relevant and available:

Transaction amount and date Authorization results Payment status Processor transaction identifiers Permitted payment-method details Cardholder or payer information UB.me ID Vehicle and plate information Authorized Agency information Location Timestamps Photographs Payment-screen records Acceptance of this Agreement Agreement version Receipts Electronic communications Location-confirmation evidence Maps Dispute submissions Release records Towing-related records Audit information

Sensitive payment-card information will not be disclosed merely because a Payment Dispute exists where such disclosure is not permitted.

25

Evidence of an authorized transaction

Depending upon the facts and information available, Unboot.me may use a combination of evidence to demonstrate that a transaction was intentionally authorized. Relevant evidence may include:

the Payer’s affirmative payment action;
payer name, telephone number and email address;
the Vehicle and plate searched before payment;
the specific Enforcement Record displayed;
amount displayed;
UB.me ID;
electronic acceptance of this Agreement;
payment authorization result;
relevant processor authentication information;
transaction timestamp;
location-confirmation evidence;
relationship between the payer location and Vehicle location;
photographs;
prior or subsequent communications;
receipt access;
dispute activity;
release activity; and
other information reasonably demonstrating participation in or benefit from the transaction.

No single item is necessarily conclusive. Unboot.me may present the evidence collectively to establish the complete factual chronology.

26

False or misleading chargeback claims

A Payer must not knowingly make a materially false statement to a financial institution concerning a transaction.

For example, a Payer who personally and intentionally submitted a payment should not knowingly represent that the transaction was completely unauthorized merely because the Payer later disagrees with the underlying parking enforcement decision.

Likewise, a Payer should not knowingly claim that no service or benefit was provided where payment actually caused or enabled the documented operational outcome associated with the transaction.

Nothing in this section penalizes, discourages, or restricts a good-faith exercise of consumer billing-error, fraud, Chargeback, or other dispute rights. This section addresses deliberate material misrepresentations, not legitimate disagreements.

Where permitted by applicable law, Unboot.me and the applicable Authorized Agency reserve all rights and remedies concerning intentional payment fraud, use of stolen payment credentials, materially false representations, or other unlawful conduct.

27

A chargeback is not an adjudication of the parking violation

A financial institution’s Chargeback process primarily concerns the payment transaction.

Unless applicable law provides otherwise, a Chargeback determination does not necessarily adjudicate:

whether the Vehicle violated a parking rule;
whether the Authorized Agency possessed enforcement authority;
whether an immobilization was permissible under local law;
whether a citation was substantively correct; or
whether some independent legal obligation remains between the Motorist and the Authorized Agency.

Likewise, Unboot.me will not represent a card-network decision as a judicial determination concerning matters that the card network did not actually adjudicate.

28

Effect of a payment reversal

If a payment is reversed, refunded, voided, returned, or otherwise removed from settlement, Unboot.me may record the reversal in the transaction history.

Whether an underlying amount remains legally payable after a reversal depends upon applicable law, the nature of the Enforcement Record, the Authorized Agency’s rights, and the circumstances of the reversal.

A Payment Dispute does not authorize Unboot.me to disregard applicable consumer-protection law. Conversely, a Payment Dispute does not automatically extinguish an otherwise valid underlying obligation merely because a financial institution provisionally or administratively reverses the payment.

29

No penalty for good-faith exercise of cardholder rights

Unboot.me will not impose a charge solely because a consumer makes a good-faith exercise of a legally protected billing-error or card-dispute right where imposing such a charge is prohibited.

Nothing prevents Unboot.me or an Authorized Agency from pursuing remedies otherwise available under applicable law for intentional fraud or a knowingly false material representation.

Part Towing, storage and release
30

Towing, storage, and impound fees

Certain Enforcement Records may later involve a towing provider.

A towing provider may charge towing, storage, impoundment, administrative, release, or other amounts pursuant to applicable law and that provider’s own terms.

Unless expressly included in the total shown before payment, payment of an Unboot.me Enforcement Record does not necessarily constitute payment of independent towing, storage, or impound charges.

Similarly, payment of a towing provider’s charges does not necessarily satisfy an independent parking citation or other Enforcement Record.

The Motorist is responsible for reviewing the specific amounts identified before each transaction.

31

Vehicle release by a tow provider

Where a Vehicle has been towed, release may be governed by applicable law and the policies of the towing provider or impound facility.

Unboot.me may provide technology used to document a Vehicle release, recipient information, payment status, outstanding citations, photographs, and related records.

Unboot.me does not become the legal custodian of an impounded Vehicle merely because its software is used during that process.

Part Fraud screening and credentials
32

Fraud screening and transaction verification

Transactions may be evaluated for fraud, misuse, duplication, suspicious activity, or other payment risk.

Where permitted by law, Unboot.me or the Payment Processor may decline, suspend, void, or require additional verification of a transaction that appears unauthorized, fraudulent, duplicated, technically invalid, or inconsistent with payment-security requirements.

Unboot.me may also preserve information concerning suspected misuse where reasonably necessary for security, payment processing, compliance, or dispute purposes.

33

No storage of payment credentials beyond what is authorized

Unboot.me will not intentionally use this Agreement as permission to collect or retain complete payment-card credentials beyond what is reasonably necessary and legally permitted for payment processing.

Payment-card information may instead be tokenized, processed, or retained by an authorized Payment Processor.

Any payment information maintained by Unboot.me will be handled subject to applicable security obligations and the Privacy Policy.

Part Privacy and records
34

Privacy and use of transaction information

Payment through Unboot.me requires the processing of information necessary to identify and document the transaction.

This information may include the Payer’s name, telephone number, email address, transaction details, Enforcement Record details, Vehicle information, photographs, location-verification information, and related technical or operational records.

Unboot.me may use this information for purposes including:

processing payment;
generating receipts;
confirming transaction status;
communicating with the Payer;
coordinating release activity;
administering disputes;
responding to Chargebacks;
preventing fraud;
maintaining records;
auditing system activity;
complying with legal obligations; and
protecting the rights and safety of users, Authorized Agencies, field personnel, towing providers, payment institutions, and Unboot.me.

Additional information concerning privacy practices is provided in the Unboot.me Privacy Policy.

35

Location information and privacy

Where payment-location confirmation is used, precise or approximate location information may be collected and processed for transaction verification and documentation.

Raw coordinates, private storage locations, internal identifiers, or other restricted information need not be displayed publicly merely because location verification occurred.

Unboot.me may nevertheless retain and disclose relevant location evidence where authorized by the Privacy Policy, this Agreement, applicable law, court process, payment-dispute procedure, or another lawful basis.

36

Record retention

Unboot.me may retain transaction, payment, dispute, enforcement, receipt, location, audit, and related records for periods reasonably necessary to:

administer the Enforcement Record;
comply with legal obligations;
meet payment-network or processor requirements;
respond to disputes or Chargebacks;
preserve accounting records;
prevent fraud;
enforce contractual rights;
support litigation;
maintain audit integrity; and
satisfy legitimate operational requirements.

Information will not be retained solely because this Agreement exists where applicable law requires earlier deletion.

Retention is further governed by the Privacy Policy and applicable law.

37

Audit records and data integrity

Unboot.me may use technical safeguards designed to preserve the integrity and chronology of enforcement and payment records.

Where records are maintained as immutable or tamper-evident records, the purpose is to provide reliable evidence concerning what information was recorded and when.

Such safeguards do not mean that Unboot.me guarantees that every fact originally entered by a human user was correct.

They are intended to help demonstrate whether stored records were subsequently altered and to preserve the integrity of the electronic history.

Part Communications and third parties
38

Communications regarding payment

The Payer authorizes Unboot.me to send transactional communications reasonably related to the payment and Enforcement Record using contact information supplied by the Payer. Such communications may include:

payment confirmation;
receipt availability;
release information;
ETA information;
dispute information;
support communications;
payment corrections;
refund information;
fraud inquiries; or
other operational notices.

Transactional communications are distinct from marketing communications.

39

Payment does not transfer ownership or control

Processing a payment does not give Unboot.me ownership of the Vehicle, control over the property, ownership of the underlying Enforcement Record, or physical custody of an immobilized or impounded Vehicle.

Unboot.me’s payment and technology role must be distinguished from the legal and operational responsibilities of the Authorized Agency and any towing provider.

40

Third-party actions

Unboot.me is not responsible for the independent conduct of an Authorized Agency, field operator, property owner, property manager, security provider, towing provider, Cardholder’s bank, card network, or Payment Processor except to the extent responsibility cannot lawfully be excluded or the conduct is legally attributable to Unboot.me.

Claims concerning physical damage to a Vehicle, towing conduct, storage conditions, physical immobilization-device installation or removal, property signage, or field enforcement activity may therefore involve the party that actually performed or authorized the activity.

Unboot.me may nevertheless preserve and provide platform records relevant to such a claim.

41

No guarantee of bank or card-network outcome

Unboot.me cannot guarantee the outcome of any Chargeback, fraud claim, issuer inquiry, card-network case, pre-arbitration proceeding, arbitration proceeding, processor review, or other financial-institution dispute.

Issuing banks, acquiring banks, Payment Processors, and card networks may apply their own rules and independently evaluate evidence.

Unboot.me’s submission of evidence does not guarantee that a financial institution will decide in Unboot.me’s or an Authorized Agency’s favor.

42

Payment Processor interruptions

To the extent permitted by law, Unboot.me is not responsible for delays or failures caused exclusively by an independent Payment Processor, card network, bank, internet provider, device failure, telecommunications failure, or other third-party service outside Unboot.me’s reasonable control.

If a payment interface malfunctions, the Payer should avoid repeatedly submitting the same transaction until payment status can be confirmed.

44

Intentional misuse

A user must not use the Unboot.me payment system to:

use a stolen payment instrument;
knowingly submit payment without authority;
manipulate transaction information;
intentionally submit materially false payer information;
interfere with payment processing;
exploit software errors to avoid payment;
submit fabricated evidence;
falsify a Payment Dispute; or
otherwise engage in fraudulent or unlawful conduct.

Unboot.me may investigate suspected intentional misuse and may preserve or disclose relevant evidence as permitted by law.

45

No waiver of non-waivable rights

Nothing contained in this Payment Agreement is intended to waive:

rights under applicable consumer-protection law;
legally protected billing-error rights;
rights applicable to unauthorized payment transactions;
rights that payment-card network rules prohibit a merchant from restricting;
rights created by applicable parking or towing law; or
any other right that cannot lawfully be waived by contract.

If a provision of this Agreement conflicts with a non-waivable legal requirement, the legal requirement controls to the minimum extent necessary. The remaining provisions continue in effect.

Part Agreement administration
46

Relationship to Unboot.me Terms & Conditions

This Payment Agreement governs payment-specific matters. The Unboot.me Terms & Conditions govern broader use of the platform.

Any enforceable provisions in the Terms & Conditions concerning arbitration, informal dispute resolution, governing law, jurisdiction, venue, class-action procedures, limitation of liability, disclaimers, indemnification, assignment, or similar matters are incorporated into this Agreement to the extent they apply to a payment-related dispute.

Where a payment-specific provision in this Agreement conflicts with a general provision of the Terms & Conditions, this Agreement controls with respect to the payment-specific issue.

47

Version of Agreement applicable to a payment

Unless applicable law requires otherwise, the version of this Payment Agreement presented or otherwise applicable when the Payer authorizes a transaction governs that transaction.

Unboot.me may update this Agreement prospectively.

A later amendment will not retroactively change the Payer’s original payment authorization merely because the Agreement was subsequently modified.

Unboot.me may retain archived versions for evidentiary, audit, or compliance purposes.

48

Translations

Unboot.me may make this Agreement or portions of the platform available in multiple languages. Translations are provided to improve accessibility and understanding.

Unless applicable law requires otherwise, if a material inconsistency exists between an English version and a translated version, the English version controls.

Nothing in this provision permits a translation to be intentionally misleading or materially inconsistent with the terms presented to the Payer.

49

Severability

If any provision of this Agreement is determined by a court or other authority of competent jurisdiction to be illegal, invalid, or unenforceable, that provision will be enforced to the maximum extent permitted by law or severed to the minimum extent required.

The remaining provisions will continue in effect unless doing so would defeat the fundamental purpose of the Agreement.

50

No waiver

Failure by Unboot.me to enforce a provision of this Agreement in a particular instance does not constitute a permanent waiver of that provision or of Unboot.me’s right to enforce it in another instance.

Any waiver must be authorized by Unboot.me and applies only to the matter for which it was given.

51

Assignment

The Payer may not assign the Payer’s rights or obligations under this Agreement in a manner that would invalidate or alter a completed payment transaction.

Unboot.me may assign or transfer its rights or obligations in connection with a merger, acquisition, restructuring, sale of assets, financing, corporate reorganization, or transfer of the Unboot.me platform, subject to applicable law and the Privacy Policy.

52

Entire Payment Agreement

Together with the provisions of the Unboot.me Terms & Conditions and Privacy Policy that are expressly incorporated or otherwise applicable, this Payment Agreement constitutes the agreement concerning the authorization and administration of payments submitted through Unboot.me.

Statements by a field operator, property representative, towing employee, or other person do not modify this Payment Agreement unless that person is expressly authorized to modify Unboot.me’s contractual terms.

53

Contacting Unboot.me about a payment

Questions concerning a payment, duplicate charge, receipt, transaction status, or Enforcement Record may be submitted through the support options available through Unboot.me.

When contacting Unboot.me regarding a payment, users should provide the applicable UB.me ID whenever available.

For security reasons, users should not send complete payment-card numbers, card security codes, passwords, or other sensitive authentication credentials through ordinary email.

Part Acknowledgment
✓

Payment acknowledgment

Immediately before a payment is submitted, the Payer acknowledges the following:

What you confirm at checkout
✓ I have reviewed the Enforcement Record and amount displayed to me.
✓ I confirm that I am authorized to use the payment method provided.
✓ I intentionally authorize payment of the displayed amount for the identified Enforcement Record.
✓ I agree to the Unboot.me Payment Agreement and acknowledge the Unboot.me Privacy Policy.
✓ I understand that payment authorization is separate from any right I may have to dispute the underlying enforcement action.
✓ I understand that, if this payment is later disputed with a financial institution, Unboot.me may provide relevant transaction, payment, enforcement, location-confirmation, receipt, and acceptance records to the entities responsible for reviewing that dispute, as permitted by law.

By proceeding with payment, the Payer affirmatively accepts this Payment Agreement.

End of Payment Agreement
Unboot.me · Version V1.26.09 · Effective September 10, 2026