Subscription payment widget in the sandbox

The subscription payment widget works in the sandbox just as in production: the same embed.js, mount() / open(), payment methods, methods and webview parameters, events and own-buttons route. The full parameter reference lives in the guide. This page covers what to plug in for the sandbox and how to drive the initial step to an outcome without a real bank.

What you need

Step 1. Create the subscription

The subscription is created on the partner’s server — with the same CreateSubscription and CustomerType=Card as in Card & SBP subscription. The project secret and the signature never reach the browser.

<Request>
  <SubscriptionProjectID>2001</SubscriptionProjectID>
  <CustomerType>Card</CustomerType>
  <CustomerId>12345</CustomerId>
  <Now>20260625120000</Now>
  <Signature>d2f36558ca5455be...</Signature>
</Request>

The response carries AuthorizeUrl and SubscriptionStatus=Pending. The widget token sits inside AuthorizeUrl — 32 hexadecimal characters.

The set of methods depends on the subscription terms (§6.8 of the guide):

Step 2. Embed the widget

<div id="bind"></div>
<script src="https://subs-sandbox.digitalspb.com/Cards/Sbp/embed.js"></script>
<script>
  SbpWidget.mount('#bind', {
    token: '8c0c8870d6fb4ee8a995ae183a44b928',   // from the AuthorizeUrl of the CreateSubscription response
    methods: ['sbp', 'sberpay'],                 // optional: narrow the set of methods
    onSuccess: function () { location.href = '/subscribed'; },
    onFail:    function () {},
    onExpired: function () {},
    onError:   function (e) { console.log(e.message, e.code); }
  });
</script>

There is no invoice here, so invoiceId is not passed — the widget addresses the subscription session by its token. For the modal mode use SbpWidget.open() with the same parameters minus the selector. webview: true turns on WebView mode, as in production.

Step 3. Confirm the initial step

The sandbox has no real banks, so confirmation is replaced with a simulation:

What happens next:

1. The widget polls the state every 5 seconds and sends success — onSuccess fires.
2. The subscription becomes Active, and the partner receives an EventType=APPROVED callback — the sandbox sends the first callback with a 15-second delay.
3. The sandbox sends no separate notification about the first charge: after a successful initial step only APPROVED arrives. To see the billing cycle and its notifications, enable it with a <TestInfo> block — see Sandbox hooks: charges. Without it, only activation, rejection and cancellation notifications arrive.

Own buttons — redirect route

The route from §6.12 of the guide works in the sandbox too:

GET https://subs-sandbox.digitalspb.com/Cards/Sbp/pay?token={token}&method=sberpay

alfapay and sberpay lead to the bank app imitation, sbp to the widget screen without a method choice. An unknown method, or one not available for the subscription — tpay included — returns 400 as an HTML page.

To get the list of methods without creating a payment, call GET https://subs-sandbox.digitalspb.com/Cards/Sbp/methods with an Authorization: Bearer {token} header.

What to check besides a successful initial step

Differences from production