Opposition · USPTO

Opposition 91210093

OtherUSPTO

Opposition 91210093 at USPTO between Visa International Service Association and Wisa, LLC, over the mark WISA, filed Mar 22, 2013. Status in the office record: other.

Status
Other
Result
Other
Filed
Mar 22, 2013
Marks involved
16
Parties

Who is involved

The parties as named in the office record.

Opponent

Visa International Service Association

Company trademarks
Respondent

Wisa, LLC

Timeline

How the case has moved

Dates from the USPTO record and the WISA filing.

  1. WISA filed

    Application 85405360 filed at the USPTO.
  2. Opposition filed

    Visa International Service Association started opposition 91210093 at USPTO against WISA.
Marks

Marks involved

1 contested mark, 15 marks the challenger relies on.

MarkRoleApplicationOffice
WISAContested85405360USPTO
VISARelied on73099033USPTO
VISARelied on73387893USPTO
VISARelied on74427894USPTO
VISARelied on74561726USPTO
VISARelied on74651221USPTO
VISARelied on75220735USPTO
VISARelied on75220736USPTO
VISA ONLINERelied on75610825USPTO
VISARelied on75879911USPTO
VISA INTELLILINKRelied on77134915USPTO
VISA SAVINGSEDGERelied on77458711USPTO

+4 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 /v1/proceedings/{id}
ID=prc_ac005635-ff47-4e1e-b47d-c1a2c8d70958
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_ac005635-ff47-4e1e-b47d-c1a2c8d70958",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91210093",
  "status": "other",
  "office_code": "US",
  "filed_date": "2013-03-22",
  "parties": [
    {
      "name": "Visa International Service Association",
      "role": "opponent"
    },
    {
      "name": "WISA, LLC",
      "role": "respondent"
    }
  ]
}