Opposition · USPTO

Opposition 91277137

OtherUSPTO

Opposition 91277137 at USPTO between Lyft, Inc. and Lyte Ventures Pte. Ltd., over the mark LYTEPAY, filed Jul 1, 2022. Status in the office record: other.

View LYTEPAYGet this data via the API
Status
Other
Result
Other
Filed
Jul 1, 2022
Marks involved
24
Parties

Who is involved

The parties as named in the office record.

Opponent

Lyft, Inc.

Respondent

Lyte Ventures Pte. Ltd.

Company trademarks
Timeline

How the case has moved

Dates from the USPTO record and the LYTEPAY filing.

  1. LYTEPAY filed

    Application 79298451 filed at the USPTO.

  2. Opposition filed

    Lyft, Inc. started opposition 91277137 at USPTO against LYTEPAY.
Marks

Marks involved

1 contested mark, 23 marks the challenger relies on.

MarkRoleApplicationOffice
LYTEPAYContested79298451USPTO
LYFTRelied on85743120USPTO
LYFTRelied on86183222USPTO
LYFTRelied on86183253USPTO
LYFTRelied on86183891USPTO
LYFTRelied on86183906USPTO
LYFT LINERelied on86872085USPTO
LYFTRelied on86982665USPTO
UNDERCOVER LYFTRelied on87182313USPTO
LYFTRelied on87254350USPTO
LYFT SCOOTERSRelied on88041722USPTO
LYFTRelied on88041743USPTO

+12 more marks in this case

API

Get this data via the API

Every fact on this page comes from the Signa API. Track oppositions and cancellations on any mark with one request.

  • GET/v1/proceedings/{id}

    Parties, dates, outcome and every mark in the case

  • GET/v1/proceedings?trademark_id={trademark_id}

    Every proceeding on a mark

Get API keyView docs
GET /v1/proceedings/{id}
ID=prc_09fb1117-babe-4836-8d75-f9c8d29b4d5b
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_09fb1117-babe-4836-8d75-f9c8d29b4d5b",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91277137",
  "status": "other",
  "office_code": "US",
  "filed_date": "2022-07-01",
  "parties": [
    {
      "name": "Lyft, Inc.",
      "role": "opponent"
    },
    {
      "name": "Lyte Ventures Pte. Ltd.",
      "role": "respondent"
    }
  ]
}