Skip to main content

Testing Pay SDK payments in RuStore Console

Restriction

Testing Pay SDK payments and subscriptions works only in the RuStore environment. Testing payments outside RuStore — without authorization or if the RuStore app is not installed — is not supported.

To test payments:

  1. Make sure test mode is enabled for you.

    To apply changes after switching test mode, you need either to wait a few minutes or restart your app if it was open.

  2. If you are not yet authorized in RuStore on the device you are using for testing, sign in via VK ID that you are registered with in RuStore Console as the app tester.

    tip

  3. Open the app on the device or install it if this has not been done yet.

  4. Make a purchase in the app. For example, buy an in-game item or a subscription.

    During payment, a payment window will appear with the Test purchase label.

    img
    caution

    If the Test purchase label does not appear, you are making a purchase not in the test environment but in the production version of the app. Make sure test mode is enabled, and that you are signed in to the RuStore mobile app with the correct VK ID.

  5. Click Pay and select a testing scenario.

    img

  6. If a successful scenario is selected, make sure the payment is successful and the app has processed the purchase.

    img
    tip

    Test payments automatically appear in RuStore Console under Monetization — Test payments after payment.

    caution

    If the payment is successful but access to the purchase does not appear, check the implementation in your app. For other issues with testing scenarios, contact support at support@rustore.ru.

  7. If an unsuccessful scenario is selected, make sure a message is displayed indicating that the payment cannot be completed.

    img

Viewing test payments in RuStore Console​

To view the test payment history:

  1. Open RuStore Console.
  2. Select Applications in the top menu and open the app in which the test purchase was made.
  3. Go to the Monetization — Test payments tab.

On the Payment history tab, you can see all payments that were made in test mode. In terms of functionality, this section mirrors Managing payments, which shows user purchases made in the production version of the app.

img

On the Payment history tab, you can:

  • Switch between SDKs — use the toggle at the top of the tab to select payments for the corresponding SDK (Pay or BillingClient).

  • View detailed information for each payment by clicking it.

  • Filter payments by:

    • amount — specify the minimum and maximum amount or only one of the parameters;
    • status;
    • order number;
    • date — click the filter again and select a date to specify the required period. By default, the filter shows all payments since the start of the calendar month.

Test subscriptions​

Test subscriptions let you verify the full recurring billing cycle: from purchase to auto-renewals and handling unsuccessful payments.

Open Monetization → Testing → Test subscriptions.

Empty list of test subscriptions

Subscription list. Each row shows the current subscription state and the upcoming billing event:

  • Purchase ID.

  • Activation date and Active until.

  • Auto-renewal: enabled/disabled.

  • Upcoming payment: the expected result of the next charge — Successful / Unsuccessful.

  • Period:

    • free — trial free period.
    • starter — subscription period with a promo price.
    • main — main period with regular charges.
    • grace — a grace period after a failed charge attempt, during which the subscription is considered active but payment has not been received yet. The user retains access, and charge attempts continue.
    • hold — a period during which the subscription is considered inactive due to inability to charge payment. Access to the subscription is lost, but charge attempts continue.

  • Status:

    • active - the subscription is active.
    • paused - the subscription is paused due to payment issues.
    • stopped - charge attempts for the subscription have ended (all were unsuccessful). The subscription is closed automatically due to payment issues.
    • cancelled - the subscription was cancelled by the user or the developer. The paid period has ended, and the subscription is closed.
Test subscriptions list — table

Filters and search. Use the filters above the table — by status, activation date, product code (if needed — by period, title, and description). Search works by by purchase identifier (purchase id).

Active filters Search by Purchase ID

Subscription details. Clicking a row opens a card with a case snapshot:

  • Technical information: subscription code, Purchase ID.
  • Upcoming payment: date/amount and expected result.
  • Subscription: active until, period, auto-renewal.
  • Payments: a list of payments (paid, rejected, refunded) with dates.
info

Rejected payments do not appear in the overall list — you can see them only in subscriptions.

Test subscription details page

Actions. In the “⋯” menu (and in the card), you can Disable auto-renewal — to test how the app reacts to renewal cancellation.

Subscription actions menu

Limitations and test mode settings for subscriptions​

  • Access and purchase. Sandbox subscriptions are available only to authorized users with test mode enabled. The subscription management section is available only to users with the roles: company owner, administrator, financial manager. You can test unpublished subscriptions.
  • Payment scenarios. In the SDK at the payment step, two outcomes are available: successful (subscription is created) and unsuccessful (subscription is not created).
  • Auto-renewals and periods. By default — up to 10 charges, 10-minute interval. If there are additional periods, they apply sequentially: 1 charge in the free period, 1 in the starter period, then N in the main period.
  • **Free/starter periods are available for each purchase — for easier testing. For real subscriptions, free/starter periods are provided once per user.
  • Server notifications and validation. Server notifications are sent for test payments (including unsuccessful ones). Server-side validation for a test subscription is not available yet and will be added soon.
  • Data scope and access. The section shows only subscriptions for the current app. Available for apps with Pay SDK.