Opposition · USPTO

Opposition 91233730

OtherUSPTO

Opposition 91233730 at USPTO between Chex Systems, Inc., Fidelity National Information Services, Inc. and Seamless Checks, LLC, over the mark SEAMLESSCHEX, filed Mar 30, 2017. Status in the office record: other.

View SEAMLESSCHEXGet this data via the API
Status
Other
Result
Other
Filed
Mar 30, 2017
Marks involved
5
Parties

Who is involved

The parties as named in the office record.

Opponent

Chex Systems, Inc., Fidelity National Information Services, Inc.

Respondent

Seamless Checks, LLC

Timeline

How the case has moved

Dates from the USPTO record and the SEAMLESSCHEX filing.

  1. SEAMLESSCHEX filed

    Application 86810499 filed at the USPTO.

  2. Opposition filed

    Chex Systems, Inc., Fidelity National Information Services, Inc. started opposition 91233730 at USPTO against SEAMLESSCHEX.
Marks

Marks involved

1 contested mark, 4 marks the challenger relies on.

MarkRoleApplicationOffice
SEAMLESSCHEXContested86810499USPTO
CHEXSYSTEMSRelied on78766627USPTO
CHEXADVISORRelied on85874632USPTO
BIZCHEXRelied on86089310USPTO
PROSPECTCHEXRelied on86325264USPTO
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_1d7e44a7-7580-453c-95e6-4042316269ec
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_1d7e44a7-7580-453c-95e6-4042316269ec",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91233730",
  "status": "other",
  "office_code": "US",
  "filed_date": "2017-03-30",
  "parties": [
    {
      "name": "Chex Systems, Inc., Fidelity National Information Services, Inc.",
      "role": "opponent"
    },
    {
      "name": "Seamless Checks, LLC",
      "role": "respondent"
    }
  ]
}