#davehogan

1 messages · Page 1 of 1 (latest)

icy escarpBOT
keen steeple
ebon mulch
#

Thanks for the reply, those are IBANs not bank account numbers.

keen steeple
#

AFAIK, there's no sort code/acc test credentials. What kind of accounts are you onboarding?

ebon mulch
#

For context I'm integrating with Stripes BACS API further down chain which is not compatible with IBANS. UK based connected accounts with BACS functionality turned on.

keen steeple
#

For processing payments, or payouts?

ebon mulch
#

These details are used for both Stripe connect payouts and billing people.

keen steeple
#

Yeah, that won't work. You can't use a single API object to both collect payments and process payouts

ebon mulch
#

We have an existing integration which works this way in other countries.

keen steeple
#

What is it you're doing right now?

ebon mulch
#

I'm trying to signup for a UK Stripe connect account using account number & sort code. I then have another optional flow which enables charges via a custom integration with the PaymentIntents API.

keen steeple
#

What kind of Stripe accounts are you onboarding?

ebon mulch
#

Custom stripe connect accounts based in the UK

keen steeple
#

And you're onboarding them via the hosted UI?

#

Which can collect the banking credentials from your customers

ebon mulch
#

No a custom integration, I'm having to be vauge because this is a public channel

#

So we have a Stripe connect integration based around a custom signup flow(both FE/BE) which creates Stripe connect accounts. Once those accounts are created in some cases we then setup a mandate to charge the processing fees.

#

I've gotten it working now, the details are Account Number "00012345" Routing Number "108800"

keen steeple
#

But I wasn't sure if they worked as payout details (they're mostly for payments). Guess they do

ebon mulch
#

Thanks, it would be good at add that to the connect docs if it possible to help other folks

#

to add that*

keen steeple
#

Yep, I'll flag that!