Simulate a card's tokenization

post

https://sandbox.lithic.com/v1/simulate/tokenizations

This endpoint is used to simulate a card's tokenization in the Digital Wallet and merchant tokenization ecosystem.

Body Params

account_score

integer

Defaults to 5

The account score (1-5) that represents how the Digital Wallet's view on how reputable an end user's account is.

cvv

string

required

length between 3 and 3

The three digit cvv for the card.

device_score

integer

Defaults to 5

The device score (1-5) that represents how the Digital Wallet's view on how reputable an end user's device is.

entity

string

Optional field to specify the token requestor name for a merchant token simulation. Ignored when tokenization_source is not MERCHANT.

expiration_date

string

required

length between 5 and 5

The expiration date of the card in 'MM/YY' format.

pan

string

required

length between 16 and 16

The sixteen digit card number.

tokenization_source

string

enum

required

The source of the tokenization request.

Allowed:

wallet_recommended_decision

string

enum

Defaults to APPROVED

The decision that the Digital Wallet's recommend

Allowed:

Responses


User has not been authenticated	Invalid or missing API key
API key is not active	The API key used is no longer active
Could not find API key	The API key provided is not associated with any user
Please provide API key in Authorization header	The Authorization header is not in the request
Please provide API key in the form Authorization: [api-key]	The Authorization header is not formatted properly
Insufficient privileges. Issuing API key required	Write access requires an Issuing API key. Reach out at lithic.com/contact
Insufficient privileges to create virtual cards.	Creating virtual cards requires an additional privilege


Rate limited, too many requests per second	User has exceeded their per second rate limit
Rate limited, reached daily limit	User has exceeded their daily rate limit
Rate limited, too many keys tried	One IP has queried too many different API keys

201OK

400A parameter in the query given in the request does not match the valid queries for the endpoint.

404The specified resource was not found.

422Unprocessable entity.