Buyer Support
Seller Support
FastSpring has already partnered with Nexus to make it simple for publishers to launch creator-optimized web stores using FastSpring, and so today we’re excited to release a detailed approach for integrating Nexus-powered creator programs directly into the FastSpring checkout on any website or store. Content creators are a great way to drive players directly to your web store completely outside the fee structure and steering rules of app stores, but with Nexus and FastSpring, you can now capture that intent, reward it, and nurture to help you automatically increase profitability for your games.
Combining FastSpring’s checkouts with Nexus’ Support-a-Creator program means more opportunities to convert high-intent users and less operational overhead to do it.
Learn more about FastSpring’s and Nexus’ partnership for web stores, or hear more by listening to our podcast episode with Nexus CEO Justin Sacks.
Why Creator Codes?
Creators are a trusted link to your brand. Communities are built around streamers and influencers, and the nudge to support them is an organic way to drive engagement. It’s warmer and more personal than an in-app push to purchase. Personalized creator codes capture that relationship and give you a way to attribute and reward engagement directly to the source helping you have a long and profitable relationship with creators.
Unique creator codes send the message that the creator is getting direct credit across app stores, consoles, and web stores. Users redeem them because it supports someone they care about, and a discount is a bonus on top of that. That connection builds retention and profits for you and community for the creator.
Why a Web Store?
Mobile app stores routinely charge up to 30% per transaction, and that fee doesn’t come with more control. It comes with less. Your pricing, your promotions, your customer data, and your creator program all live within another company’s rules.
On your own web store, you set the price and own the transaction. Creator codes can work purely as attribution, understanding which creators are driving engagement without touching your pricing, or paired with a FastSpring coupon to add a user incentive on top. The two modes are fully independent.
FastSpring’s Merchant of Record model handles the concerns that make going direct feel complicated: tax calculation, global compliance, and payment processing across dozens of methods and currencies. You get the benefits of owning the channel without having to build your own checkout experience.
How FastSpring Checkouts + Nexus Works
The user enters a creator code. The creator shares theira code with their audience on Twitch, YouTube, Discord, wherever their community lives. When the user enters it at checkout, or clicks a link with a pre-populated creatorNexus code, your browser sends that code to your server.
Nexus validates the code. Using your Nexus public key, your page calls the Nexus API to confirm the code belongs to a registered creator. Nexus responds with the creator’s identity if valid, or an error if it isn’t. This happens before the purchase as a lightweight lookup.
FastSpring applies the discount, if you want one. If the code is valid and you’ve set up a matching FastSpring coupon, the user sees the discount in the embedded checkout before they complete the purchase. Running attribution-only? The checkout proceeds at full price and the attribution is still captured.
Purchase completes, attribution is recorded. FastSpring processes the payment and fires a webhook to your server. Your server pulls the coupon code and order details from the webhook payload and calls Nexus with your private key to record the attribution. Nexus uses the transaction data to calculate and record the creator’s earnings. The creator gets credited. No spreadsheets, manual data pulls, or hands-on processes required.
As a matter of security, your Nexus private key never touches the browser. Validation at code entry uses the public key; attribution after purchase uses the private key. Both happen on your server. Full implementation details are in the Nexus integration documentation.
Why FastSpring + Nexus
The integration works because FastSpring and Nexus communicate at exactly the right moments. When a user enters a code, your FastSpring page reaches out to Nexus to validate it before the checkout completes. When the purchase is done, FastSpring fires a webhook and Nexus records the attribution. Nexus handles the creator side: attribution, relationships, and payment distribution. FastSpring handles the transaction side: tax, compliance, fraud, and global payment coverage. Each does something the other doesn’t, and neither requires your team to do it manually.
If you’re already using FastSpring’s Steer Safe™ approach to move players from in-app to your web store, this fits the same server-side pattern naturally. It’s the same architecture, one layer deeper.
Ready to connect your creator relationships to real revenue? Walk through the full implementation in the Nexus integration docs, or schedule time with a Solutions Specialist to learn how FastSpring and Nexus can support you and your creators.
