---
title: Limited PCI Scope
slug: limited-pci-scope
docTags: 
createdAt: 2026-06-01T13:20:13.522Z
---

# How It Works

With this approach, you can tokenize and store payment card data, minimizing PCI compliance scope while maintaining control over payment processing.

1. **Provision Token** – Obtain a secure token for a transaction.
2. **Use Token** – Utilize token for payments, either in single-use or multi-use forms.

:::hint{type="warning"}
You must be **PCI Level 1 compliant** to implement this approach.
:::

## Provisioning Tokens

::::WorkflowBlock
:::WorkflowBlockItem
### Tokenize card data

This step allows you to process payments while minimizing PCI exposure. Send card data to the PSP for authorization, then provision a **Forter token** for secure storage.

The Forter token is then linked to a **network token**, ensuring enhanced security and enabling future transactions.

```mermaid
sequenceDiagram
    autonumber
    participant B as Buyer
    participant M as Merchant
    participant F as Forter Tokenization Server
    participant PSP as PSP
    
    B->>M: Pay {cardData}
    M->>PSP: Authorization {cardData, {3DSValues}}
    PSP-->>M: Response {authorizationOutcome}
    M-->>B: Payment Succeeded/Failed
    M->>F: Provision Forter Token {cardData}
    F->>F: Provision Forter Token {cardData}
    F-->>M: Response {forterToken}
    F->>F: Provision Network Token {cardData}
    F->>F: Bind Tokens {forterToken, networkToken}
```
:::

:::WorkflowBlockItem
### Pay with Forter token

At this stage, use the single-use token to complete a payment.

```mermaid
sequenceDiagram
    autonumber
    participant B as Buyer
    participant M as Merchant
    participant F as Forter Tokenization Server
    participant PSP as PSP
    
    B->>M: Pay {selectedCardIndex}
    M->>M: Retrieve Forter Token {selectedCardIndex}
    M->>F: Detokenize {forterToken}
    F->>F: Retrieve Network Token {forterToken}
    F->>F: Provision NT Cryptogram {networkToken}
    F-->>M: Response {networkToken, ntCryptogram}
    M->>PSP: Authrization {networkToken, ntCryptogram, {3DSValues}}
    PSP-->>M: Response {authorizationOutcome}
    M-->>B: Payment Succeeded/Failed
```

Once authorized, the transaction is completed.
:::

:::WorkflowBlockItem
**Upgrade token (Optional)**

After payment, you may [upgrade the token to multi-use](https://docs.forter.com/reference/upgrade-to-multi-use), allowing future payments without requiring card re-entry. Forter provides two solutions for generating a multi-use token.

**1. Network Token**: Preferred by issuers, adds security, and increases approval rates.

```mermaid
sequenceDiagram
    autonumber
    participant M as Merchant
    participant F as Forter Tokenization Server
%%    participant FV as Forter Vault
    participant CN as Card Network
    
    M->>F: Upgrade to Multi-Use Token <br/> {forterSingleUseToken, networkToken.provision=true}
%%    F->>FV: Retrieve Card Data {forterSingleUseToken}
%%    FV-->>F: Response {cardData}
    F->>CN: Provision Network Token {cardData}
    CN-->>F: Response {networkToken}
    F->>F: Create Multi-Use token {cardData, networkToken}
    F->>M: Response {multiUseToken} 
    M->>M: Save Forter Token {multiUseToken}
```

**2. Multi-Use Token without Network Token:** If a network token isn’t available, Forter provides its own secure token.

```mermaid
sequenceDiagram
    autonumber
    participant M as Merchant
    participant F as Forter Tokenization Server
%%    participant FV as Forter Vault
    participant CN as Card Network
    
    M->>F: Upgrade to Multi-Use Token <br/> {forterSingleUseToken}
%%    F->>FV: Create Multi-Use token {forterSingleUseToken}
%%    FV-->>F: Response {multiUseToken}
    F->>M: Response {multiUseToken} 
    M->>M: Save Forter Token {multiUseToken}
```
:::
::::

***

## Use Tokens

Once a token has been provisioned, you can use it for future payments. The method depends on whether a Network Token was issued.

Based on the way the token was created there are two different options for using the card

**1. Using a Forter Token linked to a&#x20;**\&#xNAN;***Network Token***

```mermaid
sequenceDiagram
    autonumber
    participant U as Buyer
    participant CP as Checkout Page
    participant M as Merchant
    participant F as Forter Proxy
%%    participant FV as Forter Vault
    participant PSP as PSP
    participant CN as Card Network
    
    U->>CP: Pay with selected card
    CP->>M: Pay {selectedCardIndex}
    M->>M: Retrieve Forter Multi-Use token {selectedCardIndex}
    M->>F: Authorization <br/> {multiUseToken, networkToken.provision=true}
%%    F->>FV: Retrieve Network Token {multiUseToken}
%%    FV-->>F: Response {networkToken}
    F->>CN: Provision Cryptogram {networkToken}
    CN-->>F: Response {cryptogram}
    F->>PSP: Authorization {cryptogram}
    PSP-->>F: Response {authorizationResult}
    F-->>M: Response {authorizationResult}
    M-->>CP: Payment succeeded/failed
    CP-->>M: Payment succeeded/failed
```

:::hint{type="info"}
A cryptogram is a secure, time-sensitive authentication value that improves approval rates and security for network token transactions.
:::

**2. Use a Forter Multi-Use Token (No Network Token).**

```mermaid
sequenceDiagram
    autonumber
    participant U as Buyer
    participant CP as Checkout Page
    participant M as Merchant
    participant F as Forter Proxy
%%    participant FV as Forter Vault
    participant PSP as PSP
    
    U->>CP: Pay with selected card
    CP->>M: Pay {selectedCardIndex}
    M->>M: Retrieve Forter Multi-Use token {selectedCardIndex}
    M->>F: Authorization <br/> {multiUseToken}
%%    F->>FV: Retrieve card data {multiUseToken}
%%    FV-->>F: Response {cardData}
    F->>PSP: Authorization {cardData}
    PSP-->>F: Response {authorizationResult}
    F-->>M: Response {authorizationResult}
    M-->>CP: Payment succeeded/failed
    CP-->>M: Payment succeeded/failed
```

***