How can I retrieve a Stripe Connect embedded Checkout Session without hardcoding the connected account ID?

Below is an explanation of what’s happening and how to work around it:

Why the Issue Occurs

When you create the checkout session using a request option with a given connected account (via StripeAccount in RequestOptions), the session is created in the context of that connected account. Later, when you try to retrieve the session without specifying the connected account ID, Stripe can’t find the session in your platform’s (master) account. In other words, the checkout session “lives” on the connected account, so you must include its ID (via RequestOptions) when retrieving it.

Recommended Approaches

1. Persist the Connected Account ID:
Because you need to know which connected account the session belongs to, the recommended approach is to store (or otherwise pass along) the connected account ID when you create the session. For example, you can include it in your own session state or even add it to session metadata. That way, when your return URL endpoint is called, you can use the stored connected account ID along with the session ID to retrieve the session:

CSHARPCopied
// When creating the session, store both the session and account IDs
var requestOptions = new RequestOptions
{
    StripeAccount = "acct_12345..."
};
Session session = service.Create(options, requestOptions);

// Save both in your temp storage, database, or state
TempData["StripeSessionId"] = session.Id;
TempData["ConnectedAccountId"] = "acct_12345...";

Then later in your ReturnUrl endpoint:

CSHARPCopied
[HttpGet]
[AllowAnonymous]
public async Task<ActionResult> StripeCheckoutReturn()
{
    string sessionId = TempData["StripeSessionId"].ToString();
    string connectedAccountId = TempData["ConnectedAccountId"].ToString();

    var service = new SessionService();
    var requestOptions = new RequestOptions
    {
        StripeAccount = connectedAccountId
    };

    Session session = service.Get(sessionId, requestOptions: requestOptions);
    
    if (session.PaymentStatus == "paid")
    {
        // Process the successful payment, e.g. using session.ClientReferenceId
    }
    
    return View();
}

2. Use Metadata:
If you prefer not to store the connected account details separately in your own infrastructure, you can also add the account ID (or other relevant info) as metadata on the session. For instance:

CSHARPCopied
var options = new Stripe.Checkout.SessionCreateOptions
{
    // ... other properties ...
    Metadata = new Dictionary<string, string>
    {
        { "connected_account", "acct_12345..." }
    },
    // when using StripeAccount in your requestOptions while creating, the session
    // is still created on the connected account
};

Then, when you retrieve the session using the connected account ID (which you’ll need to pull from your stored state or the metadata if available), you can reconcile it with your internal data. However, note that metadata is accessible only if you first supply the appropriate account context.

Summary

Because checkout sessions in embedded Stripe Connect integrations are created on behalf of a connected account, you must supply the connected account’s ID when retrieving the session later. This is expected behavior. The solution is to persist or pass along the connected account ID (or include it in metadata) when creating the session so that you can select the right account context when you later retrieve the session.

This approach lets you obtain the session (and its ClientReferenceId) and correctly reconcile it with your internal systems without causing a chicken-and-egg problem.