Skip to content

Commit 576ba04

Browse files
Merge pull request #183 from inplayer-org/docs-2125-web-payments-updated
DOCS-2125 Add enable-web-payments-with-stripe to navigation
2 parents a9ef894 + a5e27d2 commit 576ba04

File tree

2 files changed

+23
-2
lines changed

2 files changed

+23
-2
lines changed

docs/guides/web-payments.md docs/guides/enable-web-payments-with-stripe.md

+22-2
Original file line numberDiff line numberDiff line change
@@ -14,6 +14,8 @@ Since this implementation uses both JWP and <a href="https://jwplayer.com/press-
1414
- jwplayer.com
1515
:::
1616

17+
<br />
18+
1719
## Prerequisites
1820

1921
<table>
@@ -25,7 +27,7 @@ Since this implementation uses both JWP and <a href="https://jwplayer.com/press-
2527
</thead>
2628
<tbody>
2729
<tr>
28-
<td><strong>New or existing app</strong></td>
30+
<td><strong>New&nbsp;or&nbsp;existing app</strong></td>
2931
<td>Web-based app that displays content to users</td>
3032
</tr>
3133
<tr>
@@ -62,6 +64,8 @@ Since this implementation uses both JWP and <a href="https://jwplayer.com/press-
6264
</tbody>
6365
</table>
6466

67+
<br />
68+
6569
## Configure WebSocket notifications
6670

6771
WebSocket notifications enable communication between your app and JWP. Whether you implement web payments with the JavaScript SDK or REST API, you must set up JavaScript to set up and configure WebSockets notifications.
@@ -130,7 +134,7 @@ Follow these steps to listen for a subscription notification and display a messa
130134
3. Configure the appearance of the popup in the `.popup` CSS settings.
131135
4. Define how long the popup displays by adjusting the `setTimeout` values.
132136

133-
You can now set up web payments through the JavaScript API or REST API.
137+
You can now set up web payments through the [JavaScript API](#javascript-sdk) or [REST API](#rest-api).
134138

135139
## Set up web payments
136140

@@ -143,6 +147,8 @@ JWP enables you to set up web payments using either a JavaScript SDK or REST API
143147
This web payment solution only supports single packages.
144148
:::
145149

150+
<br />
151+
146152
### JavaScript SDK
147153

148154
#### New User
@@ -213,6 +219,8 @@ Follow these steps to enable web payments with Stripe for a new user:
213219
.catch(error => error.response.json().then(data => console.log("Error", data)));
214220
```
215221
222+
<br />
223+
216224
After you have validated the user's access, you can fetch the content by media ID and begin playback.
217225

218226
If you use an app config to manage your content, you can obtain the media ID from the `contentId` parameter of the app config URL.
@@ -221,6 +229,8 @@ If you use an app config to manage your content, you can obtain the media ID fro
221229
You can add <a href="https://docs.jwplayer.com/platform/docs/enable-protection-apps#url-signing-for-apps" target="_blank">URL signing</a> or <a href="https://docs.jwplayer.com/platform/docs/enable-protection-apps#drm" target="_blank">digital rights management (DRM)</a> for extra layers of content protection.
222230
:::
223231

232+
<br /><br />
233+
224234
#### Existing User
225235

226236
Follow these steps to enable web payments with Stripe for an existing user:
@@ -283,6 +293,8 @@ Follow these steps to enable web payments with Stripe for an existing user:
283293
.then(data => console.log(data))
284294
.catch(error => error.response.json().then(data => console.log("Error", data)));
285295
```
296+
297+
<br/>
286298
287299
After you have validated the user's access, you can fetch the content by media ID and begin playback.
288300

@@ -292,6 +304,8 @@ If you use an app config to manage your content, you can obtain the media ID fro
292304
You can add <a href="https://docs.jwplayer.com/platform/docs/enable-protection-apps#url-signing-for-apps" target="_blank">URL signing</a> or <a href="https://docs.jwplayer.com/platform/docs/enable-protection-apps#drm" target="_blank">digital rights management (DRM)</a> for extra layers of content protection.
293305
:::
294306

307+
<br />
308+
295309
### REST API
296310

297311
#### New User
@@ -353,6 +367,8 @@ Follow these steps to enable web payments with Stripe for a new user:
353367
-H "Authorization:Bearer <token>"
354368
```
355369
370+
<br />
371+
356372
After you have validated the user's access, you can fetch the content by media ID and begin playback.
357373

358374
If you use an app config to manage your content, you can obtain the media ID from the `contentId` parameter of the app config URL.
@@ -361,6 +377,8 @@ If you use an app config to manage your content, you can obtain the media ID fro
361377
You can add <a href="https://docs.jwplayer.com/platform/docs/enable-protection-apps#url-signing-for-apps" target="_blank">URL signing</a> or <a href="https://docs.jwplayer.com/platform/docs/enable-protection-apps#drm" target="_blank">digital rights management (DRM)</a> for extra layers of content protection.
362378
:::
363379

380+
<br /><br />
381+
364382
#### Existing User
365383

366384
Follow these steps to enable web payments with Stripe for an existing user:
@@ -415,6 +433,8 @@ Follow these steps to enable web payments with Stripe for an existing user:
415433
-H "Authorization:Bearer <token>"
416434
```
417435
436+
<br />
437+
418438
After you have validated the user's access, you can fetch the content by media ID and begin playback.
419439

420440
If you use an app config to manage your content, you can obtain the media ID from the `contentId` parameter of the app config URL.

sidebars.js

+1
Original file line numberDiff line numberDiff line change
@@ -42,6 +42,7 @@ module.exports = {
4242
'guides/syndication',
4343
'guides/sca',
4444
'guides/page-protection',
45+
'guides/enable-web-payments-with-stripe',
4546
{
4647
type: 'category',
4748
label: 'Standalone Services',

0 commit comments

Comments
 (0)