Tokenization
Reports
Refund
post

/merchants/{merchant_id}/token

You can create a token with arbitrary user parameters. You send these parameters when obtaining the token and receive them back after a successful payment. A token can only contain parameters either described in this document or predefined by you.

If any parameter is sent in the wrong format or has the wrong type, no token will be issued. You will receive a 422 HTTP code with the error description in the JSON body. In extended_message you will receive an information what exact parameters have been sent incorrectly.

Note

This API method can't be used under high load. When the number of requests is high, rate limits may apply. Contact your Account Manager to find out the rate limits for this API method.

Authorization

basic

Request Parameters

1 Path Parameter

Request Body

1 Example
Schema
object
$schema: http://json-schema.org/draft-04/schema#
user
object

User details.

settings
object

Custom project settings.

purchase
object

Object containing purchase details.

custom_parameters
object

You can pass additional parameters in the token in the custom_parameters object to configure anti-fraud filters. The recommended parameters are shown in the drop-down list. See Pay Station documentation.

Responses

Created.

1 Example
Schema
object
$schema: http://json-schema.org/draft-04/schema#
token
string

Send a Test Request

Send requests directly from the browser (CORS must be enabled)
Path Params
1 path param not set
merchant_id
$$.env
username
password