#bongowilliams

1 messages · Page 1 of 1 (latest)

leaden flareBOT
restive abyss
#

Does both your failed Invoice and your succeeded Invoice has au_becs_debit in request?

#

If possible please give 2 examples request id (req_xxx) on each of them

split horizon
#

Hi! sure, give me a couple of mins and i'll grab some info for you 🙂

split horizon
#

Basically we use stripe connect via the php api to create Invoices for booking payments for our https://muzeek.com platform users as standard connected accounts. We're supposed to be using automatic payment methods, so that stripe choses which payment methods to display, so I'm not sure why the becs errors would even show. We did recently make changes to our payment methods, but yesterday to go one step further with testing, we've switched off becs completely from our settings and blocked them in the connected account payment methods settings, and the error still occurs.

It's interesting to note, that this error wont occur every time, for example testing with the same code, connected account id, customer id and tax rate id etc and the only difference being the $ amount, the invoice will sometimes be created fine, and other times throw this same error.

Some of the cases seem to include:

  • if the connected account is Restricted and the amount is under $1500 - then the becs error occurs
  • if the connected account is Restricted and the amount is over $1500 there is no error and the invoice is created successfully
  • if the amount is under or over $1500 and the connected account is Complete (not Restricted), there is no error and the invoice is created successfully
#

here's some ids for to help:

#
  • Successful invoice ($1500 + gst): in_1Ln8N22Yk2uzn0uIHJo7RlnG
  • Unsuccessful invoice ($1000+gst): req_xyw1zy2FIqXC5e - error info below
  • Muzeek platform account id: acct_15UTmcFSC7BAXCaW
  • invoice connected account id: acct_1LHMNG2Yk2uzn0uI
  • invoice customer id: cus_MG5H6MN8FWZbDW
  • **Error code in detail: **(Status 400) (Request req_xyw1zy2FIqXC5e) The payment method type "au_becs_debit" is invalid. Please ensure the provided type is activated in your dashboard (https://dashboard.stripe.com/account/payments/settings) and your account is enabled for any preview features that you are trying to use.
#

please let me know if there's anything else you need to help debug, or if you have any questions

#

I'd just also like to reiterate that: with my testing, for the account acct_15UTmcFSC7BAXCaW I am able to create invoices for the connected account in some instances without error still (it appears to be when the fee is below around $1500 the error occurs, but over is fine...)
and our connected account invoices api functionality has been working fine for months, and only has recently caused an error when we started playing around with platform default payment methods for connect (which we were to believe were automatically applied if the connected account had activated and turned on, but shouldn't cause errors)

restive abyss
#

Gimme sometimes to look at this, but by a quick glance I see the error only occurs on Restricted Connected Account? It's expected that Restricted account lacks capabilities to accept payment methods, not only limited to au_becs_debit

#
  • if the connected account is Restricted and the amount is under $1500 - then the becs error occurs
  • if the connected account is Restricted and the amount is over $1500 there is no error and the invoice is created successfully
  • if the amount is under or over $1500 and the connected account is Complete (not Restricted), there is no error and the invoice is created successfully
    There might be some further restriction on amount as you observed here
split horizon
#

yeah i think that's the case - but we are swithcing off becs, and have it set to automatic payment methods (i beliieve) so it's weird this would only just become an issue now. the amount wasnt a restriction until recently

#

it is werid that I could create 2 invoices for the same connected account - over $1500 and it works fine, but under $1500 throws the error (which it didnt used to)

#

and yeah its important to note that this is a new issue, and happened only recently since we were swithcing on and off** default payment methods** in our platform account / connected account settings

#

thanks for looking at this for me

#

also another note: we havent set becs as a payment method anywhere, it should only be an option if its chosen by the connected account right? so why, on top of everything else, would that cause the invoice to throw an errror, if it's not a forced payment method...

restive abyss
#

Yes you are right. This looks weird to me. Gimme some more times...

split horizon
#

okay thanks so much. happy to help with any other questions that may assist

restive abyss
#

Hi, looks like it's best to reach out to Support (or continue with them if you already in touch with them) to clarify. My general advice is, don't test with Restricted Accounts. Just verify it and once it is in green status, you should face no error

split horizon
#

oh really? okay

#

im in touch with them

#

thanks for your help

restive abyss
#

Good luck!

split horizon
#

do you think there's someone else in the discord that might be able to offer another opinion? we're not really getting anywhere with stripe support and it seems very odd that no-one can really identify the cause of this, let alone provide us with an option or solution of how to move forward

#

I'd like to perhaps speak with someone that can help me debug this even, Im happy to try whatever it takes to investigate and get a solution to this

#

if you arent able to continue to help me debug or fix this - can you please link someone into that chat that can help? that would be very much appreciated

restive abyss
#

I am afraid we are developers here and is not equipped to investigate this better than support team. Support team could already looking deeper and confirming with other internal teams so they are your better bet

#

But the point stands, that you should verify the account, avoid Restricted status and you should be free from this issue

split horizon
#

okay thanks - i appreciate the advice

#

when you say "verify" the account, is that different to an account on "Restricted" status?

#

its so strange that it used to work, and that it still does work when teh amount is hifgher than $1500 for an account with the issue

#

and also strange that we've removed becs from our dashboard an admin as payment options completely but this error would still occur... it makes no sense really

#

would you suggest any api code to force "Automated payment options" so that stripe knows not to apply becs if the connected account does not have the required settings for this

restive abyss
#

Yes I agree that it's strange when it used to work and now doesn't. Support team probably already investigating it. The thing is when it only occurs with Restricted account, it doesn't matter that much. Eventually you need a green account and the issue will be gone

split horizon
#

for sure, we just have a use case where our users can send invoices out for restricted accounts - which is what our whole worfklow is based off the ability to do (as they were before). so its not a simple solution for us to enforce this now. espeicallly seeing as it has worked previously, and also stsill works depending on what $ amount the invoice is set to

#

ill follow up with support, appreciate your help

#

do you have any advice in terms of settings for our platform and connected account payment methods to remove becs? or do you know why the api would not be obeying the automated payment methods here, and just bypassing becs if it is not set up to work correctly due to the account status?

restive abyss
#

I am not 100% sure but The automated payment methods setting page, could not have influence over Invoices. Invoices has a different section here.

#

The "Manage" button

split horizon
#

okay - that's for the platform account, but i will try to turn it off there too, thanks

restive abyss
#

we just have a use case where our users can send invoices out for restricted accounts - which is what our whole worfklow is based off the ability to do
It might be a good time to revisit this. It sounds like a discourage pattern and will only led you to edge cases like this time

#

For the setting, if you create Invoice for Standard Accounts by a stripe-account header, you might want to turn off in connected account too

split horizon
#

okay sure, but that is our users connected account, so we cant do that for them

restive abyss
#

Ah yes, probably ask them to try

split horizon
#

we cant we have so many users, but i apprecaite the advice