Use Case

Spawned Stripe Customize Guide 3: Advanced Integration & Configuration

This guide provides developers with advanced techniques for customizing the Spawned and Stripe integration. You'll learn how to configure webhooks, handle custom logic for payments, and manage the 0.30% creator fee structure within your own applications. We cover practical examples for extending the base functionality.

Try It Now

Key Benefits

Configure Stripe webhooks to listen for payment events from your Spawned token page.

Implement custom logic to handle the 0.30% creator fee and optional holder rewards.

Use the Spawned API to sync token launch data with your external systems.

Build custom checkout flows while maintaining integration with the Spawned launchpad.

Troubleshoot common integration issues like webhook verification and fee calculation.

The Problem

Traditional solutions are complex, time-consuming, and often require technical expertise.

The Solution

Spawned provides an AI-powered platform that makes building fast, simple, and accessible to everyone.

Verdict: Customizing Spawned Stripe for Advanced Use Cases

When does it make sense to customize?

For developers launching tokens on Solana, customizing the Spawned Stripe integration is a practical way to embed payments into larger applications. The built-in connection handles the 0.30% creator fee automatically, but you can extend it for specific needs like custom user dashboards, special purchase rules, or complex revenue splitting. If your project requires basic token sales with the included AI website, the default setup is sufficient. However, for projects building a full ecosystem—like a gaming hub where tokens grant access—this customization is essential. The process involves API calls and webhook management, but avoids the complexity of building a payment system from scratch.

Do customize if: You need payments to trigger actions in your own app, require custom data attached to purchases, or must split revenue beyond the standard 0.30% fee.
Use the default if: Your goal is a simple token launch page and you don't need to programmatically manage purchases or user data.
Key consideration: Customization maintains the 0.30% creator fee and optional 0.30% holder rewards, but lets you control the experience around it.

Step-by-Step: Configuring Stripe Webhooks for Spawned

Connect your backend to live payment events.

Webhooks allow your server to receive real-time updates on payments made through your Spawned token page. This is the foundation for custom automation.

Access Your Stripe Dashboard: Log into the Stripe account connected to your Spawned project.
Navigate to Developers > Webhooks: Click 'Add endpoint'.
Enter Your Endpoint URL: Provide the URL of your server (e.g., https://yourapp.com/api/stripe-webhook).
Select Events to Listen For: At minimum, subscribe to checkout.session.completed and payment_intent.succeeded. For full reliability, add payment_intent.payment_failed.
Retrieve the Signing Secret: Stripe will provide a webhook signing secret (whsec_...). Store this securely in your server's environment variables.
Implement Verification: In your webhook handler, verify the Stripe-Signature header using the secret to ensure requests are genuine.
Test with CLI or Dashboard: Use stripe listen and stripe trigger locally, or send test events from the Stripe dashboard.

Once configured, your server will receive a payload for each successful payment. This payload includes the client_reference_id field, which Spawned sets to your token's mint address. You can use this to link payments to specific tokens and holders.

Managing Fees and Revenue in Custom Flows

A core aspect of customization is understanding and potentially interacting with the fee structure. Spawned charges a 0.30% creator fee on every token trade facilitated through its platform. When you use the Stripe integration for direct purchases (e.g., selling token bundles for USD), this fee is automatically calculated and allocated.

If you build a custom checkout, you must ensure this fee is respected. The simplest method is to use the Spawned payment link generation API, which handles fee inclusion. For more complex scenarios, you can calculate the fee client-side: for a $100 purchase, the creator fee is $0.30, leaving $99.70. Your custom logic would then send $99.70 to your designated wallet and ensure the $0.30 is accounted for in the platform's revenue tracking.

Remember, post-graduation from the launchpad, a 1% perpetual fee applies via the Token-2022 program. Custom integrations should be aware of this transition, as it may affect net proceeds on secondary market sales linked to your initial Stripe purchases.

Common Custom Integration Patterns

Here are specific examples of what developers build using the Spawned Stripe integration as a foundation:

Gaming Token Access: Sell a token bundle via Stripe that automatically whitelists a user's wallet for a game demo. The webhook triggers a script to add the purchasing wallet address to an access control list.
Membership Tiers: Offer different USD payment tiers (e.g., $50, $100, $250) that award different amounts of your token. Use the client_reference_id and custom metadata in Stripe to determine the tier and execute the corresponding token transfer.
Revenue Sharing Dashboard: For projects with multiple creators, build an internal dashboard that pulls successful payment data from your webhooks. Calculate individual shares after the 0.30% platform fee and display real-time revenue.
Physical-Digital Bundles: Sell a physical item (hoodie, NFT plaque) paired with a token amount. Use Stripe for the full order and the checkout.session.completed event to trigger both shipping fulfillment and on-chain token distribution.

Custom Integration vs. Building Your Own Payment System

Why customize instead of building from scratch?

Aspect	Customizing Spawned Stripe	Building Your Own Stripe Integration
Development Time	Days to a week. Leverages existing token launch and fee logic.	Weeks to months. Requires building checkout, compliance, fee handling, and token linkage from zero.
Fee Management	Inherits the 0.30% creator fee model automatically. Your code works around this constant.	You must design, implement, and test your own fee logic and distribution.
Token Launch Context	Directly connected to your Spawned token page and AI website. Seamless user experience.	Isolated system; you must manually bridge the gap between payment and token launch data.
Maintenance	Spawned maintains core payment and chain integration. You maintain custom webhooks and logic.	You are responsible for all parts of the payment stack, including security updates.
Best For	Projects that have launched a token on Spawned and need to add specific payment automations.	Projects that require a completely unique payment flow unrelated to a token launchpad's structure.

The clear advantage of customization is speed and focus. You avoid rebuilding the complex connection between fiat payments, Solana tokenomics, and platform fees, letting you concentrate on your unique business logic.

Troubleshooting Custom Integration Issues

Quick fixes for frequent developer hurdles.

Problem: Webhook events are not reaching my server.

Solution: Check your endpoint is publicly accessible (no localhost). Verify firewall rules. Use the Stripe CLI stripe listen --forward-to your_url for local testing.

Problem: 'Invalid signature' error in webhook verification.

Solution: Ensure you are using the correct signing secret for your endpoint (the live secret for live events, test secret for test events). Double-check your timestamp tolerance in the verification code.

Problem: Payment succeeds but my custom token distribution script doesn't run.

Solution: Confirm your webhook is listening for checkout.session.completed and not just payment_intent.succeeded. The session object contains the client_reference_id (mint address) and custom metadata you need. Add detailed logging to your handler.

Problem: Fee calculations are off by a small percentage.

Solution: Remember that Stripe also charges a processing fee (e.g., 2.9% + $0.30). Your revenue is amount_charged - Stripe_fee - Spawned_creator_fee(0.30%). Calculate based on the final captured amount, not the initial price.

Ready to Build Your Custom Payment Flow?

Customizing the Spawned Stripe integration lets you create unique monetization paths for your Solana token while benefiting from a tested launchpad foundation. Start by launching your token on Spawned to establish the core asset, then use this guide to connect your custom application logic.

Next Steps:

Launch Your Token: If you haven't already, create your token on Spawned to get your mint address and live Stripe connection.
Review API Docs: Access the Spawned developer documentation for the latest on payment link generation and data endpoints.
Implement a Test Webhook: Set up a test endpoint using the Stripe CLI to see the data flow before going live.
Join the Community: Connect with other builders in the Spawned Discord for specific integration questions.

By combining Spawned's 0.30% creator fee model and AI website with your custom code, you can build a sustainable revenue engine around your token.

Start Building Free Explore Projects

Frequently Asked Questions

No, the 0.30% creator fee is a fixed part of the Spawned platform's revenue model for trades and direct purchases facilitated through its system. Your custom integration works with this fee as a baseline. You can add additional fees or revenue splits on top of your proceeds after this fee is applied, but you cannot modify or remove the Spawned platform fee itself.

No, the AI-generated website for your token remains fully functional and separate. Customizing the Stripe integration typically happens on your own external server or application. The 'Buy with Stripe' button on your Spawned website will still work as designed. Your custom code intercepts and acts on the payment events after they occur.

The most common method is to capture the user's wallet address during your custom checkout process before redirecting to Stripe. You can pass this as a custom metadata field (e.g., `wallet_address`) in the Stripe Checkout Session parameters. When the webhook fires, your server reads this metadata from the session object and uses it to direct the token transfer or grant access.

This specific guide and integration are built for Solana tokens launched via Spawned. The principles of customizing Stripe webhooks are universal, but the token distribution logic would be different. For multi-chain projects, you would need separate logic for each chain. Explore our guides for [Ethereum](/use-cases/token/how-to-create-gaming-token-on-ethereum) and [Base](/use-cases/token/how-to-create-gaming-token-on-base) for chain-specific launch context.

Your custom integration, which is based on Stripe webhooks and your own code, will continue to function. The key change is that secondary market trades of your token will be subject to the 1% perpetual fee via Token-2022, rather than the launchpad's fee structure. Your direct USD purchases via Stripe would still follow the logic you've built, independent of graduation.

Standard API usage for syncing token data or generating payment links is included. However, high-volume applications should implement sensible caching and polling intervals. The major cost consideration is the Stripe processing fee (e.g., 2.9% + $0.30) on each transaction, which is separate from the Spawned creator fee.

Yes, but it requires additional setup. You would use Stripe's Subscription product to create recurring charges. Your webhook would then listen for `invoice.paid` events. For each successful subscription payment, your custom logic would distribute a predetermined amount of tokens to the customer's linked wallet address, effectively creating a token drip or recurring access purchase.

Ready to get started?

Join thousands of users who are already building with Spawned. Start your project today - no credit card required.

Start Building Free See Examples