---
title: "Create Payment Token"
method: POST
path: "/v1/pg/sandbox/payment_token"
---

# Create Payment Token

`POST /v1/pg/sandbox/payment_token`

Create Token API will give the token in the response which will be used in .js function.

## Request body

- object
  - `amount` number, float, required — The amount of transaction
  - `udf` object — Merchant can pass extra parameters in the request which they require in the response. Key-value pair that can be used to store additional information about the entity.<ul><li>Each pair cannot exceed 256 characters.</li><li>Maximum 5 key-value pairs.</li></ul>Example: `"key_1": "DD”`
    - `key_1` string
    - `key_2` string
  - `contact_number` string, required — Mobile number of the customer. Please make sure you are passing actual customer mobile number. If you pass a hardcoded value, if the customer doesn't change the mobile number from layer the transaction will appear with hardcoded mobile number and name associated with it.
  - `email_id` string, required — Email Id of the customer
  - `currency` string, required — INR
  - `mtx` string, required — Reference id for the transaction. This should be unique for each transaction.
  - `sub_accounts_id` string — Mandatory Only in case of Split settlement use-case

## Response `200`

200

- object
  - `amount` string
  - `currency` string
  - `mtx` string
  - `attempts` integer
  - `sub_accounts_id` string
  - `users_id` integer
  - `created_at` string
  - `id` string
  - `entity` string
  - `status` string
  - `customer` object
    - `contact_number` string
    - `email_id` string
    - `id` string
    - `entity` string

## Other responses

- `403` — 403
- `422` — 422

---

[API](https://skmtc.net/zwitch/apis/2.md) · [All operations](https://skmtc.net/zwitch/apis/2/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/zwitch/2/revisions/4586157daf87/schema)