Skip to content

Handle errors for Stripe Connect OAuth flow better #706

Description

@joshsmith

Problem

We still need to handle errors better when part of the process fails.

There are a few different errors:

  • 400 when the code has already been used
  • The organization already has a StripeConnectAccount
  • Others I'm not thinking of?

The oauth-stripe.hbs has the loading logic, but depending on what went wrong, we should just update that with some helpful information rather than redirect.

In the case of the code being used already, we should probably check if there is an account created and if not, render them a button to connect again?

If it already has a Stripe account, probably just redirect.

Other errors, maybe retry? Not sure.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions