Lithic · Schema
tokenization-decisioning-response
The response payload that a Tokenization Decisioning responder may respond with in response to a request.
FintechCard IssuingPaymentsIssuer ProcessorKYCBanking as a Service
Properties
| Name | Type | Description |
|---|---|---|
| tokenization_decision | string | The decision for tokenization |
| phone_number | string | Phone number of the end user attempting a tokenization. Lithic must pass this to the card networks to pass to the wallets to display for the user as they select an authentication option in their digit |
| string | Email address of the end user attempting a tokenization to be used for authentication. Lithic must pass this to the card networks to pass to the wallets to display for the user as they select an authe | |
| mobile_application_name | string | Name of the mobile application that the digital wallet will open for the end user to complete authentication. For example, "Wells Fargo". |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "#/components/schemas/tokenization-decisioning-response",
"title": "tokenization-decisioning-response",
"description": "The response payload that a Tokenization Decisioning responder may respond with in response to a request.",
"type": "object",
"properties": {
"tokenization_decision": {
"description": "The decision for tokenization",
"type": "string",
"enum": [
"APPROVE",
"AUTHENTICATE",
"DECLINE"
],
"example": "APPROVE"
},
"phone_number": {
"description": "Phone number of the end user attempting a tokenization. Lithic must pass this to the card networks to pass to the wallets to display for the user as they select an authentication option in their digital wallet. Lithic will always default to using this value for authentication over the account holder information on file. E.164 format without hyphens. For example, \"+15555555555\" for a US phone number.",
"type": "string",
"example": "15555555555"
},
"email": {
"description": "Email address of the end user attempting a tokenization to be used for authentication. Lithic must pass this to the card networks to pass to the wallets to display for the user as they select an authentication option in their digital wallet. Lithic will always default to using this value for authentication over the account holder information on file. Permitted values: Valid email address. For example, \"johnny@appleseed.com\".",
"type": "string",
"format": "email",
"example": "test@example.com"
},
"mobile_application_name": {
"description": "Name of the mobile application that the digital wallet will open for the end user to complete authentication. For example, \"Wells Fargo\".",
"type": "string",
"example": "Wells Fargo"
}
},
"required": [
"tokenization_decision",
"phone_number",
"email",
"mobile_application_name"
],
"examples": [
{
"tokenization_decision": "AUTHENTICATE",
"phone_number": "+15555555555",
"email": "test@example.com",
"mobile_application_name": "Wells Fargo"
}
]
}
Work with this as data
Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for schemas
4 MCP tools reach this
find_json_schemasBrowse and filter every JSON Schema in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/lithic-com-tokenization-decisioning-response"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.