Cancellation · USPTO

Cancellation 92017838

OtherUSPTO

Cancellation 92017838 at USPTO between Wells Fargo & Company and First Financial Management Corporation, over the mark GEORGIA EXPRESS BANKING SYSTEM, filed Mar 23, 1989. Status in the office record: other.

View GEORGIA EXPRESS BANKING SYSTEMGet this data via the API
Status
Other
Result
Other
Filed
Mar 23, 1989
Marks involved
2
Parties

Who is involved

The parties as named in the office record.

Petitioner

Wells Fargo & Company

Company trademarks
Respondent

First Financial Management Corporation

Company trademarks
Timeline

How the case has moved

Dates from the USPTO record and the GEORGIA EXPRESS BANKING SYSTEM filing.

  1. GEORGIA EXPRESS BANKING SYSTEM filed

    Application 73267851 filed at the USPTO.

  2. GEORGIA EXPRESS BANKING SYSTEM registered

  3. Cancellation filed

    Wells Fargo & Company started cancellation 92017838 at USPTO against GEORGIA EXPRESS BANKING SYSTEM.
Marks

Marks involved

1 contested mark, 1 mark the challenger relies on.

MarkRoleApplicationOffice
GEORGIA EXPRESS BANKING SYSTEMContested73267851USPTO
EXPRESS BANKINGRelied on73598534USPTO
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_df3e74b8-6de6-4dae-b536-ffb1de966bff
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_df3e74b8-6de6-4dae-b536-ffb1de966bff",
  "object": "proceeding",
  "proceeding_type": "cancellation",
  "proceeding_number": "92017838",
  "status": "other",
  "office_code": "US",
  "filed_date": "1989-03-23",
  "parties": [
    {
      "name": "WELLS FARGO & COMPANY",
      "role": "petitioner"
    },
    {
      "name": "FIRST FINANCIAL MANAGEMENT CORPORATION",
      "role": "respondent"
    }
  ]
}