#johan-connect-onboarding

1 messages · Page 1 of 1 (latest)

copper tangleBOT
solid current
#

What sort of connected accounts are you working with?

#

Can you share examples of when it behaved differently than what you're seeing today?

A request ID should work

frosty marsh
#

custom

#

I can't think of a way of how to do this since it's not displaying the BACS DD fields required now it just assumes that they're completed

#

let me show you how it looks now

solid current
#

I looked and I don't think we've changed anything... double checking..

Would be helpful if you have any examples of this working differently in the past

frosty marsh
#

say for example here:

#

this test account: acct_1OEZnnB37MUZWWEh

#

in the request body we do:

"capabilities": { "bacs_debit_payments": { "requested": "true" } }

but the response is:

"capabilities": { "bacs_debit_payments": "active", "card_payments": "active", "transfers": "active" },

why is enabling them if we aren't requesting this?

#

let me know if you need more details. thanks!

solid current
#

hmm, let me ask a colleague to take a look too

frosty marsh
#

thanks

#

take your time I can wait here!

primal pelican
#
requested_capabilities: {
    0: "card_payments",
    1: "transfers",
  },
#

You may want to review your account creation code for changes, if this is not what you expect to be happening

#

It's true that the update request only added the bacs_debit_payments capability, but the response is the entire account object with the status of all requested capabilities, new and previously added.

frosty marsh
#

yes but we are only requesting them, this doesn't mean they need to be active

#

and the second request from the connected account is enabling them

#

I just don't understand why this is happening because we are not doing anything in the code to manipulate this

primal pelican
#

They automatically become active when the required information is supplied, which is satisfied by the information you sent when request the bacs capability

#

You don't explicitly make capabilities active, that happens by fulfilling requirements

frosty marsh
#

it wasn't automatically active a few weeks back

#

we had to manually fulfil the missing requirements in a stripe checkout form we trigger

primal pelican
#

Connect Onboarding, i imagine you mean

frosty marsh
#

yes exactly! that's the right terminology

primal pelican
#

It's possible that you provided different test information, or the requirements changed to allow those to become active based on what you provided.

#

Can you explain why this is a problem?

frosty marsh
#

are you sure this behaviour didn't change in your end to enable these capabilities by default to test accounts?

#

we have end to end tests in our application that are currently failing due this change. where we only enable card payments at the beginning and then at some point we enable bacs DD for uk accounts

#

this stopped working out of nowhere and we're trying to figure out how to go about this. we don't want to enable all these capabilities at once, we want to enable one by one as we go with the e2e's

primal pelican
#

Verification requirements for accounts/capabilities can and do change over time

#

If you have a concrete example of the previous behaviour you're describing, I can see if anything jumps out at me between them

frosty marsh
#

I'm not sure If I can do this since we haven't change anything in our end and we cannot bring the previous flow as it's coming from stripe

primal pelican
#

I mean a reference to an example test account from before this change you describe

#

ie if it worked last week, and account create/update you did last week

frosty marsh
#

ah okay! let me try to find out

copper tangleBOT
frosty marsh
#

found one

#

all of them before the 15th of November actually

#

the problem started on the 16th

#

acct_1OCpJPBDsD4wLhfH

#

you can see there:

"bacs_debit_payments": "inactive",

primal pelican
#

thanks, tkaing a look

frosty marsh
#

thank you! no worries take your time I will be here

primal pelican
#

ok, yes, this changed because we no longer require you to collect a display name, a default is set to make onboarding easier. So settings.bacs_debit_payments.display_name was dropped from the requirements, and the information you provided is sufficient to make the capability active.

frosty marsh
#

okay I understand so just to confirm: in my case all these three capabilities will be active straightaway and I don't need to complete the connect account onboarding again for enabling bacs DD as before

#

I can simply remove this step on my e2e and it should work right?

primal pelican
#

Yes, that sounds right based on current behaviour

frosty marsh
#

thanks a lot!

#

thanks for debugging with me hope I didn't take much of your time

#

have a great day man, cheers