Stripe Connect

Overview

Stripe Connect sends each supporter's payment straight to the project creator's own Stripe account, and your site keeps a platform fee. Fees can be a flat amount or a percentage. Connect runs on top of Stripe Checkout, so set up Stripe Checkout first.

This guide covers IgnitionDeck Commerce 2.4.2 and later. Version 2.4.2 adds a Connect webhook with its own signing secret, so orders on creators' accounts are recorded even if a supporter closes the browser before returning to your site.

Before you start

  • Stripe Checkout is set up and working. See Stripe Checkout (SCA).
  • Your IgnitionDeck license includes Stripe Connect. If it doesn't, the Stripe Connect settings are greyed out.
  • Your Stripe Connect platform application is approved for live payments. You can set everything up in test mode while you wait (see the approval tips at the end).
  • Test before you go live. See Payment Gateway Testing.

How the connection works

Two Stripe accounts are involved: yours (the platform owner's) and the creator's. They're linked once, when the creator connects, and your site uses that link for every payment after that.

  1. The creator connects. On the Creator Account tab of their dashboard, the creator clicks Connect with Stripe, logs in to Stripe and approves your platform.
  2. Stripe sends them back. Stripe returns the creator to your site through the redirect URI you add in Step 2. Your site saves the creator's Stripe account ID. That saved ID is the connection, and creators never share their own keys.
  3. Payments use the link. When a supporter backs the creator's project, your site uses your own Stripe keys to take the payment on the creator's account, and adds your platform fee.
  4. Stripe confirms each payment. The Connected accounts webhook (Step 4) tells your site about payments on creators' accounts, so every order is recorded.

How the money moves

  • The supporter pays on Stripe's checkout page. The charge is made on the creator's Stripe account, and Stripe pays the creator out on their normal schedule.
  • Your platform fee is taken from each payment and sent to your Stripe account automatically.
  • Your account never holds the creator's money, and you don't have to send payouts yourself.

Step 1: Turn on Stripe Checkout for creators

  1. In WordPress, go to IgnitionDeck » Gateways.
  2. Tick Enable Stripe Checkout for Creators and click Save.
  3. Click the gear icon next to it to open the Stripe Checkout settings. The Stripe Connect Settings are on the same page, below your API keys.

Step 2: Create your Connect app in Stripe (test mode first)

  1. In the Stripe Dashboard, turn on Switch to a sandbox (or the legacy Test Mode).

  2. Click on the gear icon in the top right and scroll down to Connect. If this is your first time, click Get started and answer Stripe's setup questions (see the approval tips at the end). The direct URL is dashboard.stripe.com/test/settings/connect).
  3. Under Connect » Onboard connected accounts, choose Onboarding options, then open the OAuth tab.

  4. Make sure Enable OAuth is turned on. This is not enabled automatically.

  5. Copy the Test client ID (starts with ca_ ) and paste into the Test

    Test client ID within Stripe Connect settings
    Test client ID within the IgnitionDeck » Commerce settings
  6. Under Redirects, click + Add URI and enter your return address:

https://yourdomain.com/dashboard/?payment_settings=1&ipn_handler=sc_return

Replace yourdomain.com  with your site's address, and dashboard  with your dashboard page's slug if it's different. Use the address your site actually loads on (with or without www , and https ). This is where creators land after connecting their Stripe account.

On a local site without SSL, use http  instead—this is only acceptable for test/sandbox modes as the live gateway requires https /SSL enabled.

Step 3: Add the Connect settings in IgnitionDeck

Back on the Stripe Checkout settings page, under Stripe Connect Settings:

Setting What to enter
Enable Development Mode Tick it while you're testing. Untick it before going live.
Development Client ID Your Test client ID from Step 2.
Production Client ID Your Live client ID (you'll copy it in Step 6).
Fee Type Flat Fee (in cents) or Percentage.
Fee Amount Your platform fee. For a flat fee, enter cents: 100  = $1.00. For a percentage, enter the number: 5  = 5%.
Button Style The look of the Connect with Stripe button creators see.

Click Save.

Keep Enable Development Mode in step with Test Mode (under IgnitionDeck » Gateways » Gateway Platform Settings): both on while testing, both off when live. If they don't match, creators get an error when they try to connect.

Using Fee Mods? You can set a different fee for individual projects, and let supporters cover the fee or add a donation at checkout. A project's own fee replaces the Fee Amount above for that project.

Step 4: Add the Connect webhook and signing secret

This webhook lets Stripe tell your site about payments made on creators' accounts. You need it in addition to the account webhook from the Stripe Checkout guide.

  1. In the Stripe Dashboard, go to Developers (bottom left of sidebar) » Webhooks and click the Add destination button.

  2. Under Event destination scope, select Connected accounts.

  3. Select Payload Style: Snapshot

  4. Select the most current API version (usually set as Default)
  5. Under Events, select these three events, then click Continue:
    • checkout.session.completed
    • checkout.session.async_payment_succeeded
    • invoice.payment_succeeded
  6. Choose Webhook endpoint and click continue
  7. Enter the endpoint URL: https://yourdomain.com/?memberdeck_notify=stripe. You can optionally add a destination name (e.g. IgnitionDeck payment return, etc.) and a description.

    The endpoint URL is the same address as your account webhook
  8. Click Create destination.
  9. Then under Overview » Destination Details, click Reveal under Signing secret and copy it (starts with whsec_ ).

  10. In IgnitionDeck, scroll to Stripe payment confirmations on the Stripe Checkout settings page. Paste the secret into Connect signing secret under Staging / Test Credentials, and click Save.

Select only these three events, not "Select all events." IgnitionDeck uses these three for creators' one-time payments and subscription renewals, and ignores everything else.

If you followed the older version of this guide, you may have a webhook pointing to ?ipn_handler=connect . IgnitionDeck no longer uses that address, so you can delete that webhook in Stripe.

Step 5: Test with a creator account

  1. Log in as a user who can create projects (a test creator account works well).
  2. Go to the creator dashboard and open the Creator Account tab.
  3. Click Connect with Stripe. In test mode, Stripe lets you skip the form and use a test account.
  4. You'll return to the Creator Account tab. The creator is now connected.
  5. Back one of that creator's projects using test card 4242 4242 4242 4242 , any future expiry date and any CVC.
  6. Check that:
    • the order appears in IgnitionDeck,
    • the payment appears in the creator's test Stripe account,
    • your platform fee appears in your own Stripe account under Collected fees, and
    • Stripe payment confirmations on the settings page shows a recent Last verified Checkout notification.

Step 6: Go live

  1. In Stripe, turn Test mode off and repeat Step 2: copy the Live client ID and add the same redirect URI in live mode.
  2. Paste the Live client ID into Production Client ID.
  3. Repeat Step 4 in live mode, and paste that signing secret into Connect signing secret under Production / Live Credentials.
  4. Untick Enable Development Mode and turn off Test Mode. Click Save. Live payments need HTTPS.

    Both gateway and Stripe Connect are in LIVE mode with boxes unchecked
  5. Ask any creators who connected during testing to connect again (see Common problems).

Updating from an earlier version to 2.4.2

Your existing Connect setup keeps working after the update. Creators stay connected and payments go through as before. To get the new order recording, add the signing secrets:

  1. In Stripe, find your existing Connected accounts webhook for ?memberdeck_notify=stripe , or create one (Step 4). Make sure it has all three events selected.
  2. Copy its signing secret into Connect signing secret, in both test and live mode.
  3. At the same time, add the Account signing secret from your account webhook (see the Stripe Checkout guide).
  4. Delete any old webhook that points to ?ipn_handler=connect.

Save both secrets together, and double-check them. Once any secret is saved, IgnitionDeck checks every subscription renewal message. If the Account secret is saved but the Connect secret is missing or wrong, creators' subscription renewals won't be recorded in IgnitionDeck. Stripe still collects the money.

All-or-Nothing pledges are authorized on your site's own payment form, not on Stripe's checkout page. They're recorded when the pledge is submitted, so the webhook isn't involved.

Common problems

What you see Why Fix
No such customer… a similar object exists in test mode, but a live mode key was used The creator connected while the site was in test mode, so their saved connection is a test one. Go to the Stripe Sandbox for the site. Locate the connected user's account under Connected Accounts and click the corresponding line item to view the record. Click the ••• menu and select Action: Remove Account to revoke their connection. They can then reconnect in live mode.
A creator's checkouts suddenly fail The creator disconnected your platform from inside their own Stripe account. Your site isn't notified when this happens. Revoke the creator's credentials (as above) and ask them to connect again.
Creators can't connect, or get an error when returning from Stripe Enable Development Mode doesn't match Test Mode, the client ID is missing, or the redirect URI in Stripe doesn't match your site's address exactly. Check that both modes match, the right client ID is saved, and the redirect URI matches character for character.
No Creator Account tab on the dashboard Enable Stripe Checkout for Creators is off, or the user can't create projects. Turn the setting on and check the user's role.
Connect signing secret not configured. on the settings page A payment came in on a creator's account, but the Connect secret field is empty for the current mode. Repeat Step 4 for the mode you're in.
Creators' subscription renewals are missing from IgnitionDeck The Connect signing secret is missing or wrong while the Account secret is saved. Copy the secret again from the Connected accounts webhook in Stripe, in the same mode, and save.
Stripe shows webhook deliveries failing with 301 or 302 The webhook address redirects (for example, www  to non-www , or http  to https ). Edit the webhook in Stripe to use the address your site actually loads on.

Tips for getting your Connect application approved

Stripe reviews each platform. These answers fit most IgnitionDeck sites but don't guarantee approval:

  • How will funds flow on your platform? Sellers will collect payments directly.

  • Industry: E-commerce products (or whatever best fits your site). Ultimately the platform using the IgnitionDeck plugins is an ecommerce marketplace that is facilitating ecommerce transactions for their connected users; therefore, E-commerce products is the most appropriate option*

    * This answer may vary depending on other factors related to your specific business model.

  • Where will sellers create their accounts? Onboarding hosted by Stripe.
  • Where will sellers manage their account? Stripe Dashboard.

Still need help? Contact Us Contact Us