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

Create a spending card

Request a virtual card be created.

To use this endpoint from the browser, you’ll need to specify the /accounts/{accountID}/issued-cards.write scope when generating a token.
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

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"
    }
  }'\
200 404 429
Card created.
{
  "authorizedUser": {
    "firstName": "Jane",
    "lastName": "Doe"
  },
  "brand": "Discover",
  "createdOn": "2019-08-24T14:15:22Z",
  "expiration": {
    "month": "01",
    "year": "21"
  },
  "formFactor": "virtual",
  "fundingWalletID": "string",
  "issuedCardID": "ec7e1848-dc80-4ab0-8827-dd7fc0737b43",
  "lastFourCardNumber": "1234",
  "memo": "string",
  "state": "active"
}
No account with the specified accountID was found.
Request was refused due to rate limiting.

Response headers

X-Retry-In

string <duration>
How long (in milliseconds) to wait until able to retry the request.

Path parameters

accountID

string <uuid> required
ID of the account.

Body

application/json

authorizedUser

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

firstName

string required

lastName

string required

birthDate

object
An individual’s birthdate.
right_key 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 required

expiration

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

month

string 2 characters

year

string 2 characters

memo

string
Optional descriptive name.

Response

application/json

authorizedUser

Fields for identifying an authorized individual.
right_key Show child attributes

firstName

string

lastName

string

brand

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

createdOn

string<date-time> <=24 characters

expiration

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

month

string 2 characters

year

string 2 characters

formFactor

string<enum>
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
Unique identifier for the wallet funding the card.

issuedCardID

string<uuid> <=36 characters Pattern
UUID v4

lastFourCardNumber

string

memo

string
Optional descriptor for the card.

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