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

Create a spending card

Request a virtual card be issued.

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

POST
/issuing/{accountID}/issued-cards
cURL 
 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29

curl -X POST "https://api.moov.io/issuing/{accountID}/issued-cards" \
  -H "Authorization: Bearer {token}" \
  --data-raw '{
    "fundingWalletID": "string",
    "authorizedUser": {
      "firstName": "Jane",
      "lastName": "Doe",
      "birthDate": {
        "day": 9,
        "month": 11,
        "year": 1989
      }
    },
    "formFactor": "virtual",
    "memo": "string",
    "expiration": {
      "month": "01",
      "year": "25"
    },
    "controls": {
      "singleUse": false,
      "velocityLimits" : [
        {
          "amount": 1000,
          "interval": "per-transaction"
        }
      ]
    }
  }'\
200 400 401 403 404 422 429 500 504
The request completed successfully.
{
  "authorizedUser": {
    "firstName": "string",
    "lastName": "string"
  },
  "brand": "Visa",
  "controls": {
    "singleUse": true,
    "velocityLimits": [
      {
        "amount": 10000,
        "interval": "per-transaction"
      }
    ]
  },
  "createdOn": "2019-08-24T14:15:22Z",
  "expiration": {
    "month": "01",
    "year": "21"
  },
  "formFactor": "virtual",
  "fundingWalletID": "string",
  "issuedCardID": "4b5b7571-0451-4af2-8783-80c65019073a",
  "lastFourCardNumber": "string",
  "memo": "string",
  "state": "active"
}

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 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"
  },
  "controls": {
    "velocityLimits": {
      "0": {
        "amount": "must be no less than 1",
        "interval": "must be a valid value"
      }
    }
  },
  "expiration": {
    "month": "string",
    "year": "string"
  },
  "formFactor": "string",
  "fundingWalletID": "string",
  "memo": "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 is to be issued.

Body

application/json

authorizedUser

object required
Fields for identifying an authorized individual.
Show child attributes

firstName

string required

lastName

string required

birthDate

object
Show child attributes

day

integer required

month

integer required

year

integer required

formFactor

string<enum> required
Specifies the type of spend card to be issued. Presently supports virtual only, providing a digital number without a physical card.
Possible values: virtual

fundingWalletID

string<uuid> required

controls

object
Show child attributes

singleUse

boolean
Indicates if the card is single-use. If true, the card closes after the first authorization.

velocityLimits

array
Sets the spending limit per time interval. Only one limit per interval is supported.
Show child attributes

amount

integer<int64>
The maximum amount in cents that can be spent in a given interval.

interval

string<enum>
Specifies the time frame for the velocity limit. Currently supports only per-transaction limits.
Possible values: per-transaction

expiration

object
The expiration date of the card or token.
Show child attributes

month

string 2 characters required

year

string 2 characters required

memo

string
An optional descriptive name for the card.

Response

application/json

authorizedUser

object required
Fields for identifying an authorized individual.
Show child attributes

firstName

string required

lastName

string required

brand

string<enum> required
The card brand.
Possible values: American Express, Discover, Mastercard, Visa, Unknown

createdOn

string<date-time> required

expiration

object required
The expiration date of the card or token.
Show child attributes

month

string 2 characters required

year

string 2 characters required

formFactor

string<enum> required
Specifies the type of spend card to be issued. Presently supports virtual only, providing a digital number without a physical card.
Possible values: virtual

fundingWalletID

string required
Unique identifier for the wallet funding the card.

issuedCardID

string<uuid> required

lastFourCardNumber

string required

state

string<enum> required

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

controls

object
Show child attributes

singleUse

boolean
Indicates if the card is single-use. If true, the card closes after the first authorization.

velocityLimits

array
Sets the spending limit per time interval. Only one limit per interval is supported.
Show child attributes

amount

integer<int64>
The maximum amount in cents that can be spent in a given interval.

interval

string<enum>
Specifies the time frame for the velocity limit. Currently supports only per-transaction limits.
Possible values: per-transaction

memo

string
Optional descriptor for the card.