To redirect users to another page after they completed the payment, you can configure two types of redirects:

• automatic — a redirect with a set delay.
• manual — a redirect after a user closes the payment UI or clicks the redirect button.

You can configure a redirect in the following ways:

• in Publisher Account — use this option if you are setting up a project for a single application and don’t plan to create builds for different platforms.

• in the SDK settings — use this option if you plan to:
  • use the project for multiple applications
  • create builds for different platforms
  • sell in-game items via the website

Configurar redireccionamientos en la Cuenta del editor

1. Open your project in Publisher Account.
2. Click Pay Station in the side menu.
3. Go to the Settings > Redirect policy section.

4. In the Return URL field, enter the URL or path where a user is redirected to after making a payment.

5. To set automatic redirect parameters:
   1. 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.
   2. In the Delay field, enter a redirect timeout in seconds.

6. To set manual redirect parameters:
   1. In the drop-down list, choose Manual redirect condition:
      • None — do not redirect.
      • Successful payment — the redirect button appears when a payment is successful.
      • Successful or canceled payment — the redirect button appears when a payment is successful or canceled.
      • Any payment — the redirect button appears for any payment status.
   2. In the Redirect button caption field, enter the copy for the button that redirects a user to the return URL.

7. Click Save.

Configurar redireccionamientos en los ajustes del SDK

1. Open your Unity project.
2. Click Window > Xsolla > Edit Settings in the main menu.
3. Open the Inspector panel and go to the Pay Station > Redirect Policy section.
4. Go to the section corresponding to your application’s build platform (Desktop, WebGL, Android, or iOS) and specify the redirect parameters:

1. 1. Uncheck the Use setting from Publisher Account box.
   2. In the Return URL field, enter the URL or path where a user is redirected to after making a payment.

1. 3. To set automatic redirect parameters:
      1. In the drop-down list, choose Redirect Conditions:
         • 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.
      2. In the Redirect Timeout field, enter a redirect timeout in seconds.

1. 4. To set manual redirect parameters:
      1. In the drop-down list, choose Status for Manual Redirection:
         • None — do not redirect.
         • Successful payment — the redirect button appears when a payment is successful.
         • Successful or canceled payment — the redirect button appears when a payment is successful or canceled.
         • Any payment — the redirect button appears for any payment status.
      2. In the Redirect Button Caption field, enter the copy for the button that will redirect a user to the return URL.

Xsolla can act as a payment gateway when players pay for in-game purchases via Steam. In this case, you don’t need to integrate the Steam SDK or take into account the nuances of paying via Steam when setting up an in-game store.

To set up payments via Steam:

1. Sign an additional agreement with Xsolla.

2. Set up the gateway for Steam in your Publisher Account.
3. Set up native authentication via Steam.
4. Open the Unity project.
5. Click Window > Xsolla > Demo Settings in the main menu.
6. In the Inspector panel, select Steam Gateway from the Payments Flow drop-down list.

After changing the Unity project settings, the x-steam-userid header is added to the payment token request using the PurchaseItem SDK method.