#sandy.nozaki

1 messages · Page 1 of 1 (latest)

normal mountainBOT
crisp jacinth
#

You can use both these methods simultaneously

bitter gorge
#

so that means the connected account would have two accounts for destination and sct charge types?

crisp jacinth
#

As far as I know, you could do SCT and Destination charges to the same account.

bitter gorge
#

ok but how about for non-regional? like canada?

#

were currently using destination with full service agreement but once migrating to sct we would have to create new connected account for that canadian vendor with recipient service agreement.

crisp jacinth
bitter gorge
#

but can we have both of the connected accounts open?

#

at least for the transition period?

#

we plan to go live iwth sct on 8/1 but all charges before 8/1 will be on destination and well the transfer of those funds will be a few days after since charges become available T+2

crisp jacinth
#

I don't see why not. Specific individuals can own multiple Connect accounts on your platform. What type of accounts are they?

bitter gorge
#

custom

crisp jacinth
#

Actually, I don't think the account type matters either. You can just have 2 identical accounts under your platform in this case

bitter gorge
#

so connected account can have 2 accounts under platform of which 1 can be using destination and 1 can be using sct under the same platform?

crisp jacinth
#

Yup, but you would need to re-onboard them onto their 2nd account, so you could do something like: get all info you could possibly get from the current account and create a new account with it. Once the 2nd account was created, provide your users with a link to update all their more sensitive information (i.e. any PII you can't get from the API) on the 2nd account.

bitter gorge
#

yeah i understand we would need to reboard them on the 2nd acct w the correct service agreement

#

once we have the 2nd connected boarded and ready....what happens to those charges that were made on the 1st connected account with destination charges?

crisp jacinth
#

They continue to exist on the first account

normal mountainBOT
bitter gorge
#

ok then what happens to those connected accounts that we do not need to switch over to recipient service agreement?

crisp jacinth
#

You would just keep their existing account and not make a 2nd one I would think, right?

bitter gorge
#

yeah but what would happen to those charges that were made destination

#

would it just follow destination regardless of when we switch over to sct?

crisp jacinth
#

SCT and Destination aren't set at the account level. They both have a series of different configurations at the payment level, so those accounts can receive both simultaneously

bitter gorge
#

do we like need to switch from one to another?

left skiff
#

👋 stepping in for my teammate!

#

if you want to continue using destination charges for some connected accounts and SCT for others, you'll need to work in this logic on your end

bitter gorge
#

how do we switch from one to another

#

i think for non-regional we'll have 2 connected accounts for destination and sct, at anytime can we stop charges from occurring in one account? we plan to just use destination until 7/31 then start charges on SCT on 8/1. but understand we will have to keep the destination connected account open until all the transfers are completed. but do not want the charges to occur anymore after 7/31

left skiff
#

You'll have to build that conditional in on your end

#

So, starting on 8/1, you'll stop making requests to create destination charges

bitter gorge
#

ok but how will the transfers for the charges that were made on 7/31 occur?

left skiff
#

not sure I follow. the funds for the transfers associated with those destination charges will still be sent to the account used when creating the destination charge

bitter gorge
#

so lets say 7/31 cnnected is under destination and that will be transferred T+2 regardless of changing it to SCT which we will code on our end to start charging using SCT whenever we want

#

can you just confirm this, "Stripe that we can use both destination and SCT simultaneously under our Platform. Charges that occurred before 8/1 will follow the Destination charge process/procedure we just have to make sure to build a condition in our end so that starting 8/1 we'll stop making requests to create destination charges. "

left skiff
#

yes, the above is correct

bitter gorge
#

and then i guess once we are ready we can deactivate the 1st connected account for those that we created the 2nd connected under diff service agreements?