Stigg allows you to easily add checkout experiences to your application using an embeddable checkout widget.

In this flow, the Stigg frontend SDKs can initiate a checkout session directly against the Stigg backend; thus, saving you the need to create a dedicated "checkout" endpoint in your backend. 

Consequently, this means that the Stigg frontend SDKs can perform write operations in the Stigg platform.

When stricter access is required, it's possible to limit the frontend SDKs to read-only access. 

Doing is possible by leveraging Stigg's client-side hardening implementation and adding a ro: prefix to the generated customer token.

More details can be found here.