Get Mobile Tokenization Config
Unlike websites, if a native mobile application is running on a mobile device owned by the end consumer, then the
installed application that has native controls for ingesting card data is not in scope for the developer/company's
PCI assessment. In these cases, the sensitive data goes from the consumer owned device directly to Coinflow for
tokenization, providing the application with PAN token that can be stored for future use and/or immediate
transaction processing.
This endpoint will return the config which you will need to pass along with the card data to the mobile tokenization endpoint.
See recipe: https://docs.coinflow.cash/recipes/card-tokenization-for-mobile-apps-checkout-only
Authentication
Authorizationstring
The API key of the merchant - see https://docs.coinflow.cash/api-reference/api-reference/authentication/get-session-key
Query parameters
token
The token for the previously-tokenized data with which you wish to associate a CVV.
- (optional) The Token which you would like to associate the CVV with.
Response
Ok
Timestamp
The timestamp (UTC) when the AuthenticationKey is generated, in yyyyMMDDHHmmss format.
TokenExID
The merchant’s Tokenization ID. (This is generated by Coinflow for you).
TokenScheme
The Token Scheme to be used to tokenize the provided data.
AuthenticationKey
The Authentication Key generated on Coinflow's server.
The Authentication Key is only valid with a timestamp less than 20 minutes old.
Token
The token for the previously-tokenized data with which you wish to associate a CVV.
