Ask Moov Beta
Generative AI is experimental and can make mistakes.
Guides Dashboard Use cases API Changelog
  1. API reference
  2. Money movement
  3. Card issuing

Update a spending card

Update a Moov issued card.

To access this endpoint using an access token you’ll need to specify the /accounts/{accountID}/issued-cards.write scope.

PATCH
/issuing/{accountID}/issued-cards/{issuedCardID}
cURL 
 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15

curl -X PATCH "https://api.moov.io/issuing/{accountID}/issued-cards/{issuedCardID}" \
  -H "Authorization: Bearer {token}" \
  --data-raw '{
    "authorizedUser": {
      "firstName": "Jane",
      "lastName": "Doe",
      "birthDate": {
        "day": 9,
        "month": 11,
        "year": 1989
      }
    },
    "memo": "string",
    "state": "closed"
  }'\
204 400 401 403 404 409 422 429 500 504
The request completed successfully, but there is no content to return.

Response headers

x-request-id

string <uuid> required
A unique identifier used to trace requests.
The server could not understand the request due to invalid syntax.
{
  "error": "string"
}

Response headers

x-request-id

string <uuid> required
A unique identifier used to trace requests.
The request contained missing or expired authentication.

Response headers

x-request-id

string <uuid> required
A unique identifier used to trace requests.
The user is not authorized to make the request.

Response headers

x-request-id

string <uuid> required
A unique identifier used to trace requests.
The requested resource was not found.

Response headers

x-request-id

string <uuid> required
A unique identifier used to trace requests.
The request conflicted with the current state of the target resource.
{
  "error": "string"
}

Response headers

x-request-id

string <uuid> required
A unique identifier used to trace requests.
The request was well-formed, but the contents failed validation. Check the request for missing or invalid fields.
{
  "authorizedUser": {
    "birthDate": {
      "day": "string",
      "month": "string",
      "year": "string"
    },
    "firstName": "string",
    "lastName": "string"
  },
  "memo": "string",
  "state": "string"
}

Response headers

x-request-id

string <uuid> required
A unique identifier used to trace requests.
Request was refused due to rate limiting.

Response headers

x-request-id

string <uuid> required
A unique identifier used to trace requests.
The request failed due to an unexpected error.

Response headers

x-request-id

string <uuid> required
A unique identifier used to trace requests.
The request failed because a downstream service failed to respond.

Response headers

x-request-id

string <uuid> required
A unique identifier used to trace requests.

Headers

x-moov-version

string
API version

Specify an API version.

API versioning follows the format vYYYY.QQ.BB, where

  • YYYY is the year
  • QQ is the two-digit month for the first month of the quarter (e.g., 01, 04, 07, 10)
  • BB is the build number, starting at .01, for subsequent builds in the same quarter.
    • For example, v2024.01.00 is the initial release of the first quarter of 2024.

The latest version represents the most recent development state. It may include breaking changes and should be treated as a beta release.

Default: v2024.01.00

Path parameters

accountID

string <uuid> required
The Moov business account for which the card was issued.

issuedCardID

string <uuid> required

Body

application/json

authorizedUser

object
Fields for identifying an authorized individual.
Show child attributes

birthDate

object
Show child attributes

day

integer

month

integer

year

integer

firstName

string

lastName

string

memo

string

state

string<enum>

The state represents the operational status of an issued card. A card can only approve incoming authorizations if it is in an active state.

  • active: The card is operational and approves authorizations. Generally becomes active shortly after card creation.
  • inactive: The card cannot approve authorizations. This is currently a temporary state assigned post-creation during the activation process.
  • closed: The card is permanently deactivated and cannot approve authorizations. A card can be closed by request or when it expires.
  • pending-verification: Awaiting additional authorized user verification before the card can be activated.
Possible values: active, inactive, pending-verification, closed