Cards

Virtual cards work the moment they are created; physical cards are produced and shipped to the holder.

Lifecycle

Pause, unpause and close cards.

Physical cards

Order, track and replace them.

Controls and groups

Limit where and how much cards spend.

Issuing a card

Every card has a holder, a user from GET /v2/users. It is issued on a card account and spends from one of its virtual accounts, the primary one unless you pick another. Name the account with accountId when the legal entity has more than one.

curl -X POST "https://api.slash.com/v2/cards" \
  -H "X-API-Key: $SLASH_API_KEY" \
  -H "x-legal-entity: $SLASH_LEGAL_ENTITY_ID" \
  -H "X-Idempotency-Key: $(uuidgen)" \
  -H "Content-Type: application/json" \
  -d '{
    "type": "virtual",
    "name": "Ads – Meta",
    "cardholderUserId": "u_2rj4l7hmrrrcv",
    "controls": {
      "limit": { "amount": { "amount": 500000, "currency": "USD" }, "period": "monthly" }
    }
  }'

Cards issue from the account’s default card product; pick another from GET /v2/card-products with cardProductId. Move a card to another virtual account of the same account with PATCH /v2/cards/{cardId}. The move finishes in the background, and the card shows its new virtualAccountId once it has.

Card numbers

The card object never carries the number or security code. Read them with GET /v2/cards/{cardId}/details, served only on https://vault.slash.com, which swaps Slash’s tokens for the real values on the way out. Add message-level encryption to keep them encrypted end to end.

Transactions

Card spend is listed with GET /v2/transactions/card, filtered by cardId or cardGroupId.

⌘I

Get started

Working with the API

Core objects

Money movement

Bill pay

Invoicing

Accounting

Cards

Lifecycle

Physical cards

Controls and groups

Issuing a card

Card numbers

Transactions

Lifecycle

Physical cards

Controls and groups

​Issuing a card

​Card numbers

​Transactions

Issuing a card

Card numbers

Transactions