Our team is building a fairly complex extension which definitely requires a backend / EBS. We’re also going to be allowing the spending of bits in our extension. I completely understand that we cannot process bits on the backend, but what has my team concerned is this paragraph from the Twitch Bits in Extensions Guide and Reference PDF (sorry cannot find a link)
The operations described in this document take place exclusively in your extension’s front end. The initiation of
the purchase flow and the callback of a completed transaction form a complete flow of exchanging bits for
experiences. Currently, bits cannot be exchanged for actions or state changes that require backend support. If
you have an idea that requires interaction with your backend, please talk to your Integration Success Engineer.
This has been interpreted as “We cannot have an EBS (period) if we’re also processing Bits”.
Our plan is to give viewers the opportunity to cheer / donate their way into elevated positions within the extension. The front end of the extension will process the bits and then notify our EBS of which product SKU was purchased.
Can someone please help me confirm that we can both process Bits on the front end of the extension and also have an EBS?