> ## Documentation Index
> Fetch the complete documentation index at: https://docs.slm.m1amdocs.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Payment Method Tokenization

Subscribe vaults customers credit cards for you allowing you to be PCI compliant while storing the payment method details in Vindicia's servers in an encrypted form. Payment Method Tokenization (PMT) uses the REST interface (api.vindicia.com) to send the credit card information back to Vindicia (It is very similar to HOA (Hosted Order Automation) that uses the SOAP Interface). This means you can accept credit cards on your website securely without ever handling the sensitive information within your network.

PMT essentially tokenizes the card in the Subscribe system and serves as your vaulting for the credit card without your server ever having to save or store the PCI components of the card number (Primary Account Number \[PAN]), expiration date, or card verification number \[CVN]).

PMT uses the REST interface (api.vindicia.com) to send the credit card information back to Vindicia. PMT can only create a payment method. It does not create other objects that HOA can. REST will return the VID of the newly created payment method object. You will have to make an additional REST call to associate this object with an account. For more information on Subscribe REST calls, see [Subscribe OpenAPI and REST Reference Guide](https://docs.vindicia.com/bundle/SubscribeAPIs/page/index.html)

**Note:** This system conforms with PCI SAQ A compliance

* **[Setting up Payment Method Tokenization](../topics/Setting_up_Payment_Metho)**


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.