Opposition · USPTO

Opposition 91300544

SuspendedUSPTO

Opposition 91300544 at USPTO between Coinbase, Inc. and Spendbase Inc., over the mark SPENDBASE, filed Jul 23, 2025. Status in the office record: suspended.

Status
Suspended
Filed
Jul 23, 2025
Marks involved
12
Parties

Who is involved

The parties as named in the office record.

Opponent

Coinbase, Inc.

Company trademarks
Respondent

Spendbase Inc.

Timeline

How the case has moved

Dates from the USPTO record and the SPENDBASE filing.

  1. SPENDBASE filed

    Application 98609988 filed at the USPTO.
  2. Opposition filed

    Coinbase, Inc. started opposition 91300544 at USPTO against SPENDBASE.
  3. Next

    Suspended

    No decision is recorded at USPTO yet.
Marks

Marks involved

1 contested mark, 11 marks the challenger relies on.

MarkRoleApplicationOffice
SPENDBASEContested98609988USPTO
COINBASERelied on86137223USPTO
COINBASERelied on86137224USPTO
COINBASERelied on86137226USPTO
COINBASERelied on88090653USPTO
COINBASERelied on88090654USPTO
COINBASERelied on88090656USPTO
COINBASERelied on90330843USPTO
COINBASERelied on90330847USPTO
COINBASERelied on90330854USPTO
COINBASERelied on97070275USPTO
COINBASE PAYRelied on97492169USPTO
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_56e57643-2a2d-4932-8818-c35c9bdee370
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_56e57643-2a2d-4932-8818-c35c9bdee370",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91300544",
  "status": "suspended",
  "office_code": "US",
  "filed_date": "2025-07-23",
  "parties": [
    {
      "name": "Coinbase, Inc.",
      "role": "opponent"
    },
    {
      "name": "Spendbase Inc.",
      "role": "respondent"
    }
  ]
}