#elkhayyat_code

1 messages · Page 1 of 1 (latest)

fathom knollBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1412317241239797800

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

random coyote
#

hi there 👋 give me a moment to take a look

#

Could you share with me the API request ID that returned that error message?

#

it should looks like this req_xxxxxxx

distant fog
#

I will need to reach out one of the customers to be able to reprodue it

random coyote
#

I see, othwerwise you should also provide me your Stripe account ID so that I can take a better look at your integration. You can find your account id by logging in to https://dashboard.stripe.com/settings/account . It'll have the prefix acct_

distant fog
#

acct_1R6XkvGCSp0OEgPL

random coyote
#

thanks, give me awhile to check

distant fog
#

take your time

random coyote
#

could you share with me the connected account ID as well?

distant fog
#

sorry, the payment method should be added to the main account not connected account,
connected accounts are meant for payouts only,

#

Current Flow:

  1. Customer Creation: A Stripe Customer is created under ezPayments' main account
  2. SetupIntent: Created for the customer with us_bank_account payment method type
  3. Financial Connections: User authenticically connects their bank account
  4. Payment Method: Bank account becomes a payment method attached to the customer
  5. Account Storage: Stored in the Account model as US_BANK_ACCOUNT type

Key Evidence from Code:

  # In stripe_service.py - creates under main account
  setup_intent = stripe.SetupIntent.create(
      customer=customer_id,  # Customer under ezPayments account
      payment_method_types=["us_bank_account"],
      # ...
      api_key=settings.STRIPE_SECRET_KEY,  # Main account API key
  )
  # In ach_service.py - stored as payment method
  account = Account.objects.create(
      tenant=tenant,
      account_type=Account.AccountTypeChoices.US_BANK_ACCOUNT,
      stripe_payment_method_id=payment_method_id,  # Payment method, not connected account
      # ...
  )
#

i have the url that the customer redirected to after linking the bank account

random coyote
distant fog
#
https://connections-auth.stripe.com/wells-fargo/complete?state=bcsess_xxxxxxxxxxx&code=xxxxxxxx
https://connections-auth.stripe.com/chase/complete?code=xxxxxxx&state=xxxxxx
#

last trial was 26th Aug, around 16:00 UTC

random coyote
#

Are you using webview?

distant fog
#

"No, we are not using webviews. Our implementation uses:

  • Web browser-based integration with Stripe Elements/JavaScript SDK
  • Standard redirect flow after Financial Connections completion
  • Server-side processing of setup intents via webhook and redirect handlers
  • Desktop and mobile web browsers (not native app webviews)"
random coyote
#

Okay, are you able to trigger this error and share a video recording of when in the bank connection flow that error message return? I believe "The auth session is in an invalid state for this action" is an error message shown on the page, right?

distant fog
#

yes on the page with this url:

https://connections-auth.stripe.com/chase/complete?code=xxxxxxx&state=xxxxxx
random coyote
distant fog
#

is it safe to share the code and state?

random coyote
#

so I will need to be able to see when the error message actually returns

#

what do you mean by state?

distant fog
#

those are url query paramters in the url

#

this is a screenshot of the error the customer sent while opening a ticket

#

she tested both wells frago and chase banks, both returned the same error

random coyote
#

thank you, let me check

distant fog
#

on sandbox [test mode]
it returns success, your account was connected
but on production customers faces the issue above

random coyote
#

would it be possible for you to share a video on a live bank connection because it looks like there are two auth windows in live mode

#

and the second auth window is the one throwing the error

distant fog
#

ok, i asked the customer to record a video, i can expect it in 12 to 16 hours due to different time zones.
will share it once i got it.

random coyote
#

I understand there may be sensitive details in the video. If you don't mind, we can work async over email

#

it will give you time to redact sensitive information in the video too as this is a public channel

distant fog
#

ok, please