> For the complete documentation index, see [llms.txt](https://docs.hyperswitch.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hyperswitch.io/integration-guide/workflows/vault/integration/server-to-server-vault-tokenization.md).

# Server to Server

### Secure, Direct Card Tokenization from Your Server

Tokenize payment cards directly from your servers to Juspay Hyperswitch's Vault Service, bypassing client-side tokenization. This server-to-server approach provides enhanced security and flexibility, ideal for PCI-compliant businesses managing payment methods programmatically.

#### Key Features

* **Full Token Management** – Create, retrieve, update, and delete payment tokens directly from your server.
* **Network Tokenization** – Generate network tokens through a single API.
* **Secure Storage** – Store tokens safely in Hyperswitch's Vault.
* **Reduced Frontend Complexity** – Shift tokenization processes to the backend, minimizing frontend dependencies.

### Prerequisites

To implement server-to-server tokenization, you need:

* **PCI DSS compliance to handle card data securely:** Make sure you have necessary PCI compliance to handle raw card data directly
* **Secure API authentication to protect transactions:** Generate your Hyperswitch API key from Developers --> API Keys section on your Hyperswitch dashboard
* **Robust error handling for tokenization failures:** Implement necessary handling for failure cases

### How It Works

1. **Collect Card Details** – Your server collects card details (requires PCI compliance).
2. **Send a Tokenization Request** – Make a POST request to /payment\_methods with the card details.
3. **Token Creation & Validation** – Hyperswitch validates the request and generates a secure token in the vault.
4. **Network Tokenization (Optional)** – If configured through your Hyperswitch dashboard, we also generate network tokens when you pass relevant parameters as mentioned below
5. **Receive Payment Method ID** – You get a pm\_id, which can be used for future payments.

### API Requests for Server to Server Tokenization

{% hint style="info" %}
All Vault API requests require a **Vault API Key** and your **Profile ID**. See [Vault Configuration](/integration-guide/workflows/vault/configuration.md) for step-by-step instructions on generating these credentials from the Hyperswitch Control Centre.
{% endhint %}

#### 1. Create a Customer

* Endpoint: `POST /customers`
* Purpose: Create a customer to enable storing their payment methods

```bash
curl --location 'https://app.hyperswitch.io/api/v1/customers' \
--header 'Content-Type: application/json' \
--header 'x-profile-id: <profile-id>' \
--header 'Authorization: api-key=<api-key>' \
--data-raw '{   
    "merchant_reference_id": "customer_1770299",
    "name": "John Doe",
    "email": "guest@example.com"
}'
```

For detailed request parameters and examples, refer to the [Create Customer API Reference](https://api-reference.hyperswitch.io/v2/customers/customers--create-v1).

#### 2. Create a Payment Method Id

* Endpoint: `POST /payment_methods`
* Purpose: Generate a Id for a card

```bash
curl --location 'https://app.hyperswitch.io/api/v1/payment-methods' \
--header 'Content-Type: application/json' \
--header 'Accept: application/json' \
--header 'X-Profile-Id: <profile-id>' \
--header 'Authorization: api-key=<api-key>' \
--data '{
    "customer_id":"12345_cus_019e2102e4fb7a32b456d8f896e8f51e",
    "payment_method_type": "card",
    "payment_method_subtype": "credit",
    "payment_method_data": {
        "card": {
            "card_number": "4111111111111111",
            "card_exp_month": "03",
            "card_exp_year": "2030",
            "card_holder_name": "joseph Doe",
            "card_cvc": "737"
        }
    },
    "storage_type": "persistent"
}'
```

For detailed request parameters and examples, including how to create payment method tokens with network tokens, refer to the [Create Payment Method API Reference](https://api-reference.hyperswitch.io/v2/payment-methods/payment-method--create-v1).

#### 3. Retrieve a Payment Method Id

* Endpoint: `POST /payment_methods/:pm_id`
* Purpose: Retrieve a Payment Method for a Id

```bash
curl --location 'https://app.hyperswitch.io/api/v1/payment-methods/:payment_method_id' \
--header 'Content-Type: application/json' \
--header 'Accept: application/json' \
--header 'Authorization: api-key=<api-key>' \
--header 'x-profile-id: <profile-id>'
```

For detailed request parameters and examples, including how to retrieve payment method id with network tokens, refer to the [Retrieve Payment Method API Reference](https://api-reference.hyperswitch.io/v2/payment-methods/payment-method--retrieve-v1).

#### 4. Update a Payment Method Id

* Endpoint: `PATCH /payment_methods/:pm_id/update_saved_payment_method`
* Purpose: Modify Payment Method details.

```bash
curl --location --request PUT 'https://app.hyperswitch.io/api/v1/payment-methods/:payment_method_id/update-saved-payment-method' \
--header 'Content-Type: application/json' \
--header 'Accept: application/json' \
--header 'X-Profile-Id: <profile-id>' \
--header 'Authorization: api-key=<api-key>' \
--data '{
    "payment_method_data": {
        "card": {
            "card_holder_name": "joseph",
            "nick_name": "some_name11",
            "card_cvc": "737"
        }
    }
}'
```

For detailed request parameters and examples, refer to the [Update Payment Method API Reference](https://api-reference.hyperswitch.io/v2/payment-methods/payment-method--update-v1).

#### 5. Delete a Payment Method Id

* Endpoint: `DELETE /payment_methods/:pm_id`
* Purpose: Remove a Id from the vault.

```bash
curl --request DELETE \
  --url https://sandbox.hyperswitch.io/v1/payment-methods/:payement_method_id \
  --header 'Authorization: <api-key>' \
  --header 'X-Profile-Id: <profile-id>'
```

For detailed request parameters and examples, refer to the [Delete Payment Method API Reference](https://api-reference.hyperswitch.io/v2/payment-methods/payment-method--delete-v1).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.hyperswitch.io/integration-guide/workflows/vault/integration/server-to-server-vault-tokenization.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.