Opposition · USPTO

Opposition 91250434

OtherUSPTO

Opposition 91250434 at USPTO between PaySimple, Inc. and PayGround, Inc., over the mark WE EXIST TO MAKE RECURRING PAYMENTS SIMPLE, filed Aug 26, 2019. Status in the office record: other.

View WE EXIST TO MAKE RECURRING PAYMENTS SIMPLEGet this data via the API
Status
Other
Result
Other
Filed
Aug 26, 2019
Marks involved
6
Parties

Who is involved

The parties as named in the office record.

Opponent

PaySimple, Inc.

Respondent

PayGround, Inc.

Timeline

How the case has moved

Dates from the USPTO record and the WE EXIST TO MAKE RECURRING PAYMENTS SIMPLE filing.

  1. WE EXIST TO MAKE RECURRING PAYMENTS SIMPLE filed

    Application 88170367 filed at the USPTO.

  2. Opposition filed

    PaySimple, Inc. started opposition 91250434 at USPTO against WE EXIST TO MAKE RECURRING PAYMENTS SIMPLE.
Marks

Marks involved

1 contested mark, 5 marks the challenger relies on.

MarkRoleApplicationOffice
WE EXIST TO MAKE RECURRING PAYMENTS SIMPLEContested88170367USPTO
PAYSIMPLERelied on77124998USPTO
INVOICESIMPLYRelied on85314594USPTO
PAYSIMPLERelied on85592849USPTO
BILLSIMPLERelied on85653494USPTO
BOOKSIMPLERelied on86540124USPTO
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_2f12441f-9b50-45e6-916c-ae0784036e23
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_2f12441f-9b50-45e6-916c-ae0784036e23",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91250434",
  "status": "other",
  "office_code": "US",
  "filed_date": "2019-08-26",
  "parties": [
    {
      "name": "PaySimple, Inc.",
      "role": "opponent"
    },
    {
      "name": "PayGround, Inc.",
      "role": "respondent"
    }
  ]
}