Card Tokenization for Mobile Apps (Checkout Only)
Introduction
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.
The PCI SSC has a article that covers this: https://www.pcisecuritystandards.org/faq/articles/Frequently_Asked_Question/how-do-pci-standards-apply-to-organizations-that-develop-software-that-runs-on-a-consumer-s-device-for-example-a-smartphone-tablet-or-laptop-and-is-used-to-accept-payment-card-data/
Get Mobile Tokenize Config
This endpoint will return the config which you will need to pass along with the card data to the mobile tokenization endpoint
Tokenize Card with CVV
Using the response you received in step 2, Timestamp, TokenExID, TokenScheme, AuthenticationKey, pass this into the TokenizeWithCVV endpoint along data and cvv. This will authorize you to tokenize the card number and the CVV.
Initiate Card Checkout
Copy the token from the response in Step 3. Then, pass it into the card checkout endpoint.
At this point, you’ve completed a new card checkout!
Link CVV to token
CVVs associations are only valid for a single use.
To use a saved card for a new purchase, the CVV must be re-linked to the token.
NOTE: When getting the mobile tokenization config (in step 2), pass the token which was previously generated into the token query parameter
Initiate Saved Card Checkout
Copy the token from the response in Step 5. Then, pass it into the saved card checkout endpoint.
At this point, you’ve re-tokenized the card number with the CVV, and completed a saved card checkout!

