Stripe Add Seller

Audience: Low-code Engineers

Skill Prerequisites: Actions, Tokens

Connects a seller's Stripe account to your Stripe platform, using Stripe Connect. The action sends the user to Stripe, where they sign in (or sign up) and approve the connection. Stripe then sends them back to the page they started from.

Once connected, the seller appears in your platform's list of connected accounts. You can then send payments to them, for example with the Transfer Destination of Stripe Checkout.

note

This action is part of the Stripe add-on (DnnSharp.Stripe). The add-on is installed separately and needs the STRIPE feature in your license. If it isn't licensed, the action fails with a "not licensed" error. If you don't see the Stripe actions, the add-on isn't installed.

Typical Use Cases

• Add a Connect with Stripe button to a seller sign-up form in a marketplace
• Let service providers link their own Stripe account so they can receive payments through your platform

Don't use it to

• Take a payment. Use Stripe Checkout instead.
• Save your own Stripe keys. Use Add Stripe Connector instead.
• Run in a workflow or a background process. The action needs a browser to redirect.

Related Actions

Action Name	Description
Get Stripe User Account	Finds a connected account's ID by its email.
Stripe Checkout	Takes a payment and can transfer it to a connected account.
Redirect to URL	Sends the user to another page.

Input Parameter Reference

Parameter	Description	Supports Tokens	Default	Required
API Secret Key	Your platform's Stripe secret key. It's used when the user comes back from Stripe, to complete the connection.	Yes	empty string	Yes
Client Id	Your platform's Connect client ID, from the Connect settings in the Stripe Dashboard. It starts with ca_.	Yes	empty string	Yes

The action has no output parameters.

How the connection works

1. The action saves the secret key and the current page URL in two encrypted browser cookies (StripeAPISecretKey and StripeReturnUrl). They expire after one day.
2. It redirects the user to Stripe's Connect page (https://connect.stripe.com/oauth/authorize), with your client ID and read_write access.
3. The user approves the connection on Stripe.
4. Stripe sends the user to the PAA handler at /DesktopModules/DnnSharp/Common/WebHandlers/DnnSharpStripe.ashx/.
5. The handler reads the cookies and completes the connection with Stripe.
6. The user is redirected back to the page where the action ran.

PAA doesn't store the connected account ID. Stripe keeps the connection. To find a seller's account ID later, use Get Stripe User Account with their email.

Considerations

• Register the redirect URI. In the Stripe Dashboard, add https://yoursite.com/DesktopModules/DnnSharp/Common/WebHandlers/DnnSharpStripe.ashx/ to your Connect redirect URIs. Use your own domain, and keep the trailing slash. If the site runs in a virtual folder, include it. The protocol (http or https) matches the current request.
• Put it last. The action ends the action list with a redirect. Actions after it don't run.
• Nothing runs after the connection. There are no success or error action lists. The user always returns to the start page, even if the connection failed, and no tokens tell you whether it worked. Check the result with Get Stripe User Account.
• Cookies are needed. If the browser blocks cookies, or the user takes more than a day, the handler fails.
• Keep keys out of the action. Don't type the secret key into the action if other people can edit the application. Use a token that reads it from a safe place.

Examples

tip

To understand how to use the below examples, please see Running Examples.

1. Connect a seller's Stripe account

This action runs on the Connect button of a seller form. The StripeSecretKey and StripeClientId tokens hold your platform's keys.

{
    "Title": "Stripe Add Seller",
    "ActionType": "StripeAddSeller",
    "Description": "Connect the seller's Stripe account to the platform",
    "Parameters": {
        "APISecretKey": "[StripeSecretKey]",
        "ClientId": "[StripeClientId]"
    }
}

Revised 09/27/2026