Testing Pay SDK payments in RuStore Console
Testing Pay SDK payments and subscriptions only works within the RuStore environment. Testing payments outside RuStore — without authorization or without the RuStore app installed — is not supported.
To test payments via SBP, install the Test Bank app on your device. Without it, a test payment via SBP cannot be completed.
To test payments:
-
Make sure test mode is enabled for you.
For the changes to take effect after switching the testing mode, either wait a few minutes or restart your app if it was open.
-
If you are not yet signed in to RuStore on the device you are testing on, sign in with the VK ID registered in RuStore Console as a tester of the app.
-
Open the app on your device, or install it if you haven't done so yet.
-
Make a purchase in the app. For example, buy an in-game item or a subscription.
During payment, the payment window appears with the Test purchase label.
cautionIf the Test purchase label does not appear, you are making the purchase outside the test environment — in the production version of the app. Make sure that test mode is enabled and that you are signed in to the RuStore mobile app with the correct VK ID.
-
In the Payment method block, choose how you want to test the purchase: by bank card or via SBP.
The next steps depend on the payment method you selected.
- Payment by card
- Payment via SBP
-
Tap the payment button.
The testing scenario selection appears in the payment window.
-
Select a scenario and tap Check:
- Successful — the payment completes successfully;
- Unsuccessful — the payment completes with an error.
-
If you selected the Successful scenario, make sure the successful payment screen appears and that your app has processed the purchase.
-
If you selected the Unsuccessful scenario, make sure a message appears stating that the payment could not be completed.
Tap To payment methods to choose a different method and try again.
Payment via SBP is available starting from Pay SDK version 11.1.
SBP can only be used to test one-time in-app purchases. Subscriptions are tested by card payment.
In the Test Bank app, you select the scenario that the payment will complete with. In the production version of the app, the user selects their own bank from the list at this step.
-
Tap the payment button.
The bank selection screen opens.
-
Select Test Bank.
You will be redirected to the Test Bank app. It imitates the behavior of a real banking app during an SBP payment, but lets you choose the outcome of the payment.
-
Select a testing scenario and tap Pay:
- Successful payment — the payment completes successfully;
- Return an error — the payment completes with an error.
-
If you selected the Successful payment scenario, the successful payment screen appears in the Test Bank app. Tap Return to store.
Wait for the payment to complete in the RuStore window and make sure your app has processed the purchase.
-
If you selected the Return an error scenario, the failed payment screen appears in the Test Bank app.
After you return to the RuStore window, a message appears stating that the payment could not be completed. Tap To payment methods to choose a different method and try again.
Test payments appear automatically in RuStore Console under Monetization — Test payments once the payment is made.
If the payment succeeded but access to the purchase does not appear, check the implementation in your app. For any other issues with testing scenarios, contact technical support at support@rustore.ru.
Viewing test payments in RuStore Console
To view your test payment history:
- Open RuStore Console.
- Select Apps in the top menu and open the app the test purchase was made in.
- Go to the Monetization — Test payments tab.
The Payment history tab shows all payments made in test mode. In terms of functionality, this section mirrors Manage payments, which shows purchases made by users in the production version of the app.
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 tapping it.
-
Filter payments by:
- amount — set a minimum and maximum amount, or just one of them;
- status;
- order number;
- date — tap the filter again and select a date to set the period you need. By default, the filter shows all payments since the beginning of the calendar month.
Test subscriptions
Test subscriptions let you check the full recurring billing cycle: from sign-up to auto-renewals and handling of failed payments.
Open Monetization → Testing → Test subscriptions.
Subscription list. Each row shows the current state of the subscription and the next 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 — free trial period.
- introductory — subscription period at a promotional price.
- base — main period with regular charges.
- grace — grace period after a failed charge attempt, during which the subscription is considered active even though payment has not been received. The user keeps access, and charge attempts continue.
- hold — period during which the subscription is considered inactive because payment could not be charged. The user loses access, 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 run out (all were unsuccessful). The subscription was closed automatically due to payment issues.
- canceled — the subscription was canceled by the user or the developer. The paid period has expired and the subscription is closed.
Filters and search. Use the filters above the table — by status, activation date, and product code (and, if needed, by period, name, and description). Search works by purchase identifier (purchase id).
Subscription details. Tapping a row opens a card with a breakdown of the case:
- Technical information: subscription code, purchase ID.
- Upcoming payment: date/amount and expected result.
- Subscription: active until, period, auto-renewal.
- Payments: list of payments (paid, declined, refunded) with dates.
Declined payments do not appear in the general list — you can only see them within subscriptions.
Actions. In the "⋯" menu (and in the card), you can Disable auto-renewal to check how your app reacts when renewal is canceled.
Limitations and test mode settings for subscriptions
- Access and sign-up. Sandbox subscriptions are available only to authorized users with test mode enabled. The subscription management section is available only to users with the following roles: company owner, administrator, finance manager. You can test unpublished subscriptions.
- Payment method. Subscriptions are tested by card payment only. Payment via SBP is available for one-time in-app purchases.
- Payment scenarios. In the SDK, two outcomes are available at the payment step: successful (the subscription is created) and unsuccessful (the subscription is not created).
- Auto-renewals and periods. By default — up to 10 charges at a 10-minute interval. If additional periods are configured, they apply in sequence: 1 charge in the free period, 1 in the introductory period, then N in the base period.
- Free and introductory periods are available with every purchase, for testing convenience. For real subscriptions, free and introductory periods are granted once per user.
- Server notifications and validation. Server notifications are sent for test payments (including unsuccessful ones). Server-side validation of test subscriptions is not available yet and will be added soon.
- Data scope and access. The section shows only the subscriptions of the current app. Available for apps using Pay SDK.
- Grace and hold periods. If grace and hold periods are configured for a subscription, one charge is performed in each of these periods in test mode. After that, the subscription moves to the Stopped status (if the unsuccessful charges scenario is selected).