Redirects configuration
To redirect users to another page after they completed the payment, you can configure two types of redirects:
- automatic — a redirect in a set delay time.
- manual — a redirect after a user closes the payment UI or clicks the redirect button.

Configure automatic redirects
You can configure automatic redirects:
Configure automatic redirects in Publisher Account
- Open your project in Publisher Account and go to Pay Station > Settings > Redirect policy.
- In the Return URL field, enter a URL address or a path a user will be redirected to after making a payment.
- In the drop-down list, choose Automatic redirect condition:
- None — do not redirect.
- Successful payment — redirect when a payment is successful.
- Successful or canceled payment — redirect when a payment is successful or canceled.
- Any payment — redirect for any payment status.
- In the Delay field, enter a redirect timeout in seconds.
- Click Save.

Configure automatic redirects via API
Redirect configurations are specified in the return_url
parameter and the redirect_policy
parameter group in the Create token endpoint.
- In the
return_url
parameter, pass a URL address or a path a user will be redirected to after making the payment. - Set the
autoredirect_from_status_page
parameter totrue
. - In the
delay
parameter, pass a redirect timeout in seconds. - In the
redirect_conditions
parameter, pass conditions when a redirect is activated:none
— do not redirect.successful
— redirect when a payment is successful.successful_or_canceled
— redirect when a payment is successful or canceled.any
— redirect for any payment status.
The following GET-parameters are automatically added to the link:
user_id
— user IDforeigninvoice
— transaction ID passed in the external_id parameterinvoice_id
— transaction IDstatus
— transaction status
Configure manual redirects
You can configure manual redirects:
Configure manual redirects in Publisher Account
- Open your project in Publisher Account and go to Pay Station > Settings > Redirect policy.
- In the Return URL field, enter a URL address or a path a user will be redirected to after making a payment.
- In the drop-down list, choose Automatic redirect condition:
- None — do not redirect.
- Successful payment — redirect when a payment is successful.
- Successful or canceled payment — redirect when a payment is successful or canceled.
- Any payment — redirect for any payment status.
- Leave the Delay field empty.
- In the Manual redirect condition drop-down list, choose a payment status when the redirect button appears.
- In the Redirect button caption field, enter the copy for the button that will redirect a user to the return URL.
- Click Save.

By default, the redirect button copy is Back to the Game. It is localized into all Pay Station languages.
If your project supports several languages, you can enter redirect button copy for each of them in the respective fields.
When a user closes the payment UI, they are also redirected to the specified return URL.
Configure manual redirects via API
Redirect configurations are specified in the return_url
parameter and the redirect_policy
parameter group in the Create token endpoint.
- In the
return_url
parameter, pass a URL address or a path a user will be redirected to after making a payment. - In the
redirect_conditions
parameter, pass conditions when a redirect is activated:none
— do not redirect.successful
— redirect when a payment is successful.successful_or_canceled
— redirect when a payment is successful or canceled.any
— redirect for any payment status.
- In the
manual_redirection_action
parameter, pass the payment UI behavior triggered by the user clicking the close button or the return button:redirect
(by default) — a user is redirected to the return URL.postmessage
— clicking the close icon initiates sending theclose-widget
event, and clicking the return button — thereturn
event. In this case, a user isn’t redirected to the return URL. You need to configure processing of events for closing the payment UI or redirection.
- In the
redirect_button_caption
parameter, pass copy for the button that will redirect a user to the return URL. - In the
status_for_manual_redirection
parameter, pass a payment status when the redirect button appears:none
— do not redirect.successful
— redirect when a payment is successful.successful_or_canceled
— redirect when a payment is successful or canceled.any
— redirect for any payment status.
The following GET-parameters are automatically added to the link:
user_id
— user IDforeigninvoice
— transaction ID passed in the external_id parameterinvoice_id
— transaction IDstatus
— transaction status
ui.desktop.header.close_button
parameter is set to true
, only the postmessage
event is sent when a user clicks the close icon. It allows you to process the event and close the payment UI, and a user can stay at the page from which the payment was initiated.Examples of redirect configuration
EXAMPLE 1
If you use the same project in Publisher Account to process payments on different platforms, you can configure default redirects for payments processed in a browser and customized redirects — for mobile devices.
To configure default redirects, in the return_url
parameter, pass a URL address or a path a user will be redirected to after making a payment. A customized automatic redirect with 3 seconds delay may look like this:
{
"redirect_policy": {
"redirect_conditions": "successful",
"autoredirect_from_status_page": true,
"delay": 3
}
}
EXAMPLE 2
If you sell your items on a website and also use a game launcher, you can configure redirects for a website in your Publisher Account and customize redirect configurations for the launcher in the token:
{
"redirect_policy": {
"redirect_conditions": "successful_or_canceled",
"status_for_manual_redirection": "successful_or_canceled",
"manual_redirection_action": "postmessage"
}
}
Was this article helpful?
Rate this page
Don’t want to answer
Thank you for your feedback!
Found a typo or other text error? Select the text and press Ctrl+Enter.