# Integration Guides

Forter provides **secure, PCI-compliant solutions** for handling payment card data. This guide outlines **integration options, best practices**, and **key considerations** for implementing Forter’s card vaulting services.

# [Hosted Fields + Proxy](https://docs.forter.com/integration-guides#hosted-fields-proxy) Hosted Fields + Proxy

1. ### [Collect card data securely](https://docs.forter.com/integration-guides#collect-card-data-securely) Collect card data securely  
   Forter’s [Hosted Fields](https://docs.forter.com/hosted-fields-sdk) enables secure collection of card data on the checkout page to remove PCI scope.

2. ### [Process payments using a token](https://docs.forter.com/integration-guides#process-payments-using-a-token) Process payments using a token  
   Once the customer enters their payment credentials, Forter provides an agnostic **single-use token** (or "nonce") that can be used to **process tokenized payments with any PSP**. Refer to the [Detokenization Proxy](https://docs.forter.com/detokenization-proxy) guide to learn how.

3. ### [Upgrade to multi-use token (Optional)](https://docs.forter.com/integration-guides#upgrade-to-multi-use-token-optional) Upgrade to multi-use token (Optional)  
   To store a token for future transactions (e.g., saved cards or recurring payments), upgrade a single-use token to a multi-use token by setting networkToken.provision to true when calling the /upgrade endpoint.

# [Direct API Integration](https://docs.forter.com/integration-guides#direct-api-integration) Direct API Integration

This solution is compatible for PCI level 1 merchants only  
Forter’s **Limited PCI Compliance** approach allows merchants to handle tokenized card data while limiting their PCI scope.

1. ### [Tokenize card data](https://docs.forter.com/integration-guides#tokenize-card-data) Tokenize card data  
   After collecting card details, generate a token using one of the following API calls:  
   - **Multi-use token**: Call the /tokenize endpoint .  
   - **Single-use token**: Call the /create-single-use-token endpoint.  
   To generate a **network token**, set networkToken.provision to true when calling the /tokenize endpoint.

2. ### [Detokenize for payment processing](https://docs.forter.com/integration-guides#detokenize-for-payment-processing) Detokenize for payment processing  
   When ready to process a payment, retrieve the original card details by calling the /detokenize endpoint, then proceed with payment processing.

3. ### [Upgrade to multi-use token (Optional)](https://docs.forter.com/integration-guides#upgrade-to-multi-use-token-optional-1) Upgrade to multi-use token (Optional)  
   To store a token for future transactions (e.g., saved cards or recurring payments), upgrade a single-use token to a multi-use token by setting networkToken.provision to true when calling the /upgrade endpoint.