Skip to content

Cards

Cards

Last updated: (timestamp)

Cards

cards
Methods
Create card
post/v1/cards

Create a new virtual or physical card. Parameters shipping_address and product_id only apply to physical cards.

Get card
get/v1/cards/{card_token}

Get card configuration such as spend limit and state.

Update card
patch/v1/cards/{card_token}

Update the specified properties of the card. Unsupplied properties will remain unchanged.

Note: setting a card to a CLOSED state is a final action that cannot be undone.

List cards
get/v1/cards

List cards.

Convert virtual to physical card
post/v1/cards/{card_token}/convert_physical

Convert a virtual card into a physical card and manufacture it. Customer must supply relevant fields for physical card creation including product_id, carrier, shipping_method, and shipping_address. The card token will be unchanged. The card's type will be altered to PHYSICAL. The card will be set to state PENDING_FULFILLMENT and fulfilled at next fulfillment cycle. Virtual cards created on card programs which do not support physical cards cannot be converted. The card program cannot be changed as part of the conversion. Cards must be in an OPEN state to be converted. Only applies to cards of type VIRTUAL (or existing cards with deprecated types of DIGITAL_WALLET and UNLOCKED).

Embedded card UI
get/v1/embed/card

Handling full card PANs and CVV codes requires that you comply with the Payment Card Industry Data Security Standards (PCI DSS). Some clients choose to reduce their compliance obligations by leveraging our embedded card UI solution documented below.

In this setup, PANs and CVV codes are presented to the end-user via a card UI that we provide, optionally styled in the customer's branding using a specified css stylesheet. A user's browser makes the request directly to api.lithic.com, so card PANs and CVVs never touch the API customer's servers while full card data is displayed to their end-users. The response contains an HTML document (see Embedded Card UI or Changelog for upcoming changes in January). This means that the url for the request can be inserted straight into the src attribute of an iframe.

<iframe id="card-iframe"
        src="https://sandbox.lithic.com/v1/embed/card?embed_request=eyJjc3MiO...;hmac=r8tx1..."
        allow="clipboard-write" class="content"></iframe>

You should compute the request payload on the server side. You can render it (or the whole iframe) on the server or make an ajax call from your front end code, but do not ever embed your API key into front end code, as doing so introduces a serious security vulnerability.

Provision card (Digital Wallet)
post/v1/cards/{card_token}/provision

Allow your cardholders to directly add payment cards to the device's digital wallet (e.g. Apple Pay) with one touch from your app.

This requires some additional setup and configuration. Please Contact Us or your Customer Success representative for more information.

Reissue physical card
post/v1/cards/{card_token}/reissue

Initiate print and shipment of a duplicate physical card (e.g. card is physically damaged). The PAN, expiry, and CVC2 will remain the same and the original card can continue to be used until the new card is activated. Only applies to cards of type PHYSICAL. A card can be reissued or renewed a total of 8 times.

Renew a card
post/v1/cards/{card_token}/renew

Applies to card types PHYSICAL and VIRTUAL. For PHYSICAL, creates a new card with the same card token and PAN, but updated expiry and CVC2 code. The original card will keep working for card-present transactions until the new card is activated. For card-not-present transactions, the original card details (expiry, CVC2) will also keep working until the new card is activated. A PHYSICAL card can be reissued or renewed a total of 8 times. For VIRTUAL, the card will retain the same card token and PAN and receive an updated expiry and CVC2 code. product_id, shipping_method, shipping_address, carrier are only relevant for renewing PHYSICAL cards.

Get card's available spend limit
get/v1/cards/{card_token}/spend_limits

Get a Card's available spend limit, which is based on the spend limit configured on the Card and the amount already spent over the spend limit's duration. For example, if the Card has a monthly spend limit of $1000 configured, and has spent $600 in the last month, the available spend limit returned would be $400.

Search for card by PAN
post/v1/cards/search_by_pan

Get card configuration such as spend limit and state. Customers must be PCI compliant to use this endpoint. Please contact support@lithic.com for questions. Note: this is a POST endpoint because it is more secure to send sensitive data in a request body than in a URL.

Web Push Provision card (Digital Wallet)
post/v1/cards/{card_token}/web_provision

Allow your cardholders to directly add payment cards to the device's digital wallet from a browser on the web. Currently only suported for Apple Pay.

This requires some additional setup and configuration. Please Contact Us or your Customer Success representative for more information.

Domain Types
Card
Cardintersection

Card details with potentially PCI sensitive information for Enterprise customers

ShowShow
cvvstring
optional

Three digit cvv printed on the back of the card.

maxLength3
minLength3
panstring
optional

Primary Account Number (PAN) (i.e. the card number). Customers must be PCI compliant to have PAN returned as a field in production. Please contact support@lithic.com for questions.

maxLength16
minLength16
Card Spend Limits
CardSpendLimitsobject
ShowShow
available_spend_limitobject
Hide ParametersShow Parameters
annuallynumber
optional

The available spend limit (in cents) relative to the annual limit configured on the Card (e.g. 100000 would be a $1,000 limit).

forevernumber
optional

The available spend limit (in cents) relative to the forever limit configured on the Card.

monthlynumber
optional

The available spend limit (in cents) relative to the monthly limit configured on the Card.

spend_limitobject
optional
Hide ParametersShow Parameters
annuallynumber
optional

The configured annual spend limit (in cents) on the Card.

forevernumber
optional

The configured forever spend limit (in cents) on the Card.

monthlynumber
optional

The configured monthly spend limit (in cents) on the Card.

spend_velocityobject
optional
Hide ParametersShow Parameters
annuallynumber
optional

Current annual spend velocity (in cents) on the Card. Present if annual spend limit is set.

forevernumber
optional

Current forever spend velocity (in cents) on the Card. Present if forever spend limit is set.

monthlynumber
optional

Current monthly spend velocity (in cents) on the Card. Present if monthly spend limit is set.

Non PCI Card
NonPCICardobject

Card details without PCI information

ShowShow
tokenstring

Globally unique identifier.

account_tokenstring

Globally unique identifier for the account to which the card belongs.

card_program_tokenstring

Globally unique identifier for the card program on which the card exists.

createdstring

An RFC 3339 timestamp for when the card was created. UTC time zone.

formatdate-time
fundingobject

Deprecated: Funding account for the card.

Hide ParametersShow Parameters
tokenstring

A globally unique identifier for this FundingAccount.

formatuuid
createdstring

An RFC 3339 string representing when this funding source was added to the Lithic account. This may be null. UTC time zone.

formatdate-time
last_fourstring

The last 4 digits of the account (e.g. bank account, debit card) associated with this FundingAccount. This may be null.

maxLength4
minLength4
stateenum
Accepts one of the following: "DELETED", "ENABLED", "PENDING"

State of funding source. Funding source states: * ENABLED - The funding account is available to use for card creation and transactions. * PENDING - The funding account is still being verified e.g. bank micro-deposits verification. * DELETED - The founding account has been deleted.

Hide ParametersShow Parameters
"DELETED"
"ENABLED"
"PENDING"
typeenum
Accepts one of the following: "DEPOSITORY_CHECKING", "DEPOSITORY_SAVINGS"

Types of funding source: * DEPOSITORY_CHECKING - Bank checking account. * DEPOSITORY_SAVINGS - Bank savings account.

Hide ParametersShow Parameters
"DEPOSITORY_CHECKING"
"DEPOSITORY_SAVINGS"
account_namestring
optional

Account name identifying the funding source. This may be null.

nicknamestring
optional

The nickname given to the FundingAccount or null if it has no nickname.

maxLength255
minLength1
last_fourstring

Last four digits of the card number.

maxLength4
minLength4
pin_statusenum
Accepts one of the following: "OK", "BLOCKED", "NOT_SET"

Indicates if a card is blocked due a PIN status issue (e.g. excessive incorrect attempts).

Hide ParametersShow Parameters
"OK"
"BLOCKED"
"NOT_SET"
spend_limitnumber

Amount (in cents) to limit approved authorizations (e.g. 100000 would be a $1,000 limit). Transaction requests above the spend limit will be declined.

spend_limit_durationSpendLimitDuration

Spend limit duration values:

  • ANNUALLY - Card will authorize transactions up to spend limit for the trailing year.
  • FOREVER - Card will authorize only up to spend limit for the entire lifetime of the card.
  • MONTHLY - Card will authorize transactions up to spend limit for the trailing month. To support recurring monthly payments, which can occur on different day every month, the time window we consider for monthly velocity starts 6 days after the current calendar date one month prior.
  • TRANSACTION - Card will authorize multiple transactions if each individual transaction is under the spend limit.
stateenum
Accepts one of the following: "CLOSED", "OPEN", "PAUSED", 2 more

Card state values: * CLOSED - Card will no longer approve authorizations. Closing a card cannot be undone. * OPEN - Card will approve authorizations (if they match card and account parameters). * PAUSED - Card will decline authorizations, but can be resumed at a later time. * PENDING_FULFILLMENT - The initial state for cards of type PHYSICAL. The card is provisioned pending manufacturing and fulfillment. Cards in this state can accept authorizations for e-commerce purchases, but not for "Card Present" purchases where the physical card itself is present. * PENDING_ACTIVATION - At regular intervals, cards of type PHYSICAL in state PENDING_FULFILLMENT are sent to the card production warehouse and updated to state PENDING_ACTIVATION. Similar to PENDING_FULFILLMENT, cards in this state can be used for e-commerce transactions or can be added to mobile wallets. API clients should update the card's state to OPEN only after the cardholder confirms receipt of the card. In sandbox, the same daily batch fulfillment occurs, but no cards are actually manufactured.

Hide ParametersShow Parameters
"CLOSED"
"OPEN"
"PAUSED"
"PENDING_ACTIVATION"
"PENDING_FULFILLMENT"
typeenum
Accepts one of the following: "MERCHANT_LOCKED", "PHYSICAL", "SINGLE_USE", 3 more

Card types: * VIRTUAL - Card will authorize at any merchant and can be added to a digital wallet like Apple Pay or Google Pay (if the card program is digital wallet-enabled). * PHYSICAL - Manufactured and sent to the cardholder. We offer white label branding, credit, ATM, PIN debit, chip/EMV, NFC and magstripe functionality. * SINGLE_USE - Card is closed upon first successful authorization. * MERCHANT_LOCKED - [Deprecated] Card is locked to the first merchant that successfully authorizes the card. * UNLOCKED - [Deprecated] Similar behavior to VIRTUAL cards, please use VIRTUAL instead. * DIGITAL_WALLET - [Deprecated] Similar behavior to VIRTUAL cards, please use VIRTUAL instead.

Hide ParametersShow Parameters
"MERCHANT_LOCKED"
"PHYSICAL"
"SINGLE_USE"
"VIRTUAL"
"UNLOCKED"
"DIGITAL_WALLET"
auth_rule_tokensarray of string
optional
deprecated

List of identifiers for the Auth Rule(s) that are applied on the card. This field is deprecated and will no longer be populated in the Card object. The key will be removed from the schema in a future release. Use the /auth_rules endpoints to fetch Auth Rule information instead.

cardholder_currencystring
optional

3-character alphabetic ISO 4217 code for the currency of the cardholder.

digital_card_art_tokenstring
optional

Specifies the digital card art to be displayed in the user's digital wallet after tokenization. This artwork must be approved by Mastercard and configured by Lithic to use.

exp_monthstring
optional

Two digit (MM) expiry month.

maxLength2
minLength2
exp_yearstring
optional

Four digit (yyyy) expiry year.

maxLength4
minLength4
hostnamestring
optional

Hostname of card's locked merchant (will be empty if not applicable).

memostring
optional

Friendly name to identify the card.

pending_commandsarray of string
optional

Indicates if there are offline PIN changes pending card interaction with an offline PIN terminal. Possible commands are: CHANGE_PIN, UNBLOCK_PIN. Applicable only to cards issued in markets supporting offline PINs.

product_idstring
optional

Only applicable to cards of type PHYSICAL. This must be configured with Lithic before use. Specifies the configuration (i.e., physical card art) that the card should be manufactured with.

replacement_forstring
optional

If the card is a replacement for another card, the globally unique identifier for the card that was replaced.

Spend Limit Duration
SpendLimitDurationenum

Spend limit duration values:

  • ANNUALLY - Card will authorize transactions up to spend limit for the trailing year.
  • FOREVER - Card will authorize only up to spend limit for the entire lifetime of the card.
  • MONTHLY - Card will authorize transactions up to spend limit for the trailing month. To support recurring monthly payments, which can occur on different day every month, the time window we consider for monthly velocity starts 6 days after the current calendar date one month prior.
  • TRANSACTION - Card will authorize multiple transactions if each individual transaction is under the spend limit.
ShowShow
"ANNUALLY"
"FOREVER"
"MONTHLY"
"TRANSACTION"

CardsAggregate Balances

cards.aggregate_balances
Methods
List card aggregate balances
get/v1/cards/aggregate_balances

Get the aggregated card balance across all end-user accounts.

CardsBalances

cards.balances
Methods
Get card balances
get/v1/cards/{card_token}/balances

Get the balances for a given card.

CardsFinancial Transactions

cards.financial_transactions
Methods
Get card financial transaction
get/v1/cards/{card_token}/financial_transactions/{financial_transaction_token}

Get the card financial transaction for the provided token.

List card financial transactions
get/v1/cards/{card_token}/financial_transactions

List the financial transactions for a given card.