Stash Pay process

There are two core pillars to integrating Stash Pay: account linking and purchase handling.

Account linking

Stash needs to authenticate players to associate them with their purchases, and so that you can grant players their items in-game. We support third party accounts (Apple IDs, Google Play accounts, etc.), as well as custom authentication solutions so players don't need to create accounts with us.To further reduce friction, Stash supports signing in through deep-links and QR codes.

Purchase handling

The Checkout Links API is used to create checkout sessions from your website. Stash recommends implementing an API for authorizing purchases, and you'll need logic for granting players their items in-game. Stash notifies you with webhooks when players complete purchases, which you can use to trigger logic for granting players their purchases.

For webhook setup and implementation, see our Webhooks Overview and Webhook List documentation.

Timelines

Integration timelines vary but are often shorter for Stash Pay. The general process has four phases:

1. Planning and requirements
   • Define scope and set QA environments
2. Integrating
   • Set authentication and account linking
   • Implement checkout and purchase authorizations APIs
   • Update webhook handling
   • Testing
3. Customization and migration
   • Final integration tweaks
   • Run final load tests
   • Launch prep
4. Going live
   • Deployment
   • Post-launch monitoring
   • Start ongoing Stash support