#joao-eduardo_api

1 messages · Page 1 of 1 (latest)

manic jacinthBOT
#

đź‘‹ 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/1396858542639812672

đź“ť Have more to share? Add more details, code, screenshots, videos, etc. below.

gritty ginkgo
#

Hi there

#

Taking a look

rocky hatch
#

@gritty ginkgo thank you!

gritty ginkgo
#

Can you link the doc you're referring to here?

rocky hatch
#

sure, give me one minute

gritty ginkgo
#

Ok I see

#

I guess I don't follow your question

#

You only need each connect account to accept the terms when using direct charges or on behalf of

#

If you use destination charges, you don't need each connect account to accept the terms

#

If using destination charges, you'd just need to accept terms once for your platform

rocky hatch
#

So if I'm using destination charges but not using on_behalf_of, only my platform account should need to accept the terms?

gritty ginkgo
#

correct

rocky hatch
#

I see... do you happen to know when and where I, as a platform account, can accept these terms?

gritty ginkgo
#

Users are presented with Apple’s Tap to Pay on iPhone Terms and Conditions the first time they connect to the reader on iPhones.

#

From the same section you linked

rocky hatch
#

But who would that appear to? Because I'm building an app that the connected accounts will use—my clients will use it to collect money. From what I understand, I should be the one accepting those terms, since I’m the platform account.

gritty ginkgo
#

Also from that section This flow isn’t presented on subsequent connections using the same Stripe account, including on other mobile devices.

#

You just need to do it once

#

For the first connection

#

You should connect to a device with your platform account and accept the terms

#

The terms shouldn't be presented again assuming you're just doing destination charges

rocky hatch
#

But look... in the documentation, it’s important to note that Stripe makes acceptance of the terms a conditional requirement.

From what I understood, if I don’t set on_behalf_of when connecting, nothing will show up—neither for me, when connecting the first time, nor for my clients at any point, right?

Take a look at this excerpt from the documentation:

"Each connected account must accept the Terms and Conditions when:

A Connect user creates direct charges

A Connect user creates a destination charge and specifies an on_behalf_of account"

#

Sorry @gritty ginkgo , it's still hard for me to understand... bear with me 🙂

gritty ginkgo
#

From what I understood, if I don’t set on_behalf_of when connecting, nothing will show up—neither for me, when connecting the first time, nor for my clients at any point, right?
No. You're misunderstanding

#

Every stripe account that is the merchant of record must accept terms

#

In a destination charge flow without on_behalf_of, your platform is the merchant of record

#

So you just need to accept terms once

#

Additionally:
`Each connected account must accept the Terms and Conditions when:

A Connect user creates direct charges
A Connect user creates a destination charge and specifies an on_behalf_of account`

#

Because in those 2 scenarios the connect account are the merchants of record

rocky hatch
#

So I think I found a bug. Because by integrating without passing on_behalf_of—which means my platform account is the merchant—the terms acceptance screen didn’t appear for me.

Could I be doing something wrong?

gritty ginkgo
#

So you have a working integration and are connected to the reader without ever having submitted your apple id?

rocky hatch
#

yes

gritty ginkgo
#

In live mode?

#

Like you've already accepted a payment?

#

Or is this just test mode

rocky hatch
#

If I don’t include on_behalf_of when creating the Payment Intent—and later when connecting to a reader—the Apple terms screen doesn’t appear.

But when I do include it, it works exactly as you described: the terms screen appears the first time, and after I accept it, everything works fine and it no longer shows up. I can only get it to appear again if I go to Apple’s site and manually revoke the agreement.

#

In test mode, we didn't lauch the app yet

gritty ginkgo
#

Is it possible someone else on your team already accepted an agreement on your platform?

#

Or are you the only one working on this

rocky hatch
#

Hmm, now you’ve got me thinking. I’m not the only one working on this integration.
Do you happen to know where I can check if someone on our team has already accepted the terms as the platform acct?

gritty ginkgo
#

I'm not sure if there's a way to check this

#

Let me ask a colleague

rocky hatch
#

thank you!

gritty ginkgo
#

They said there's an open feature request to be able to do this via the sdk, but it's not currently possible

rocky hatch
#

Got it... So just to summarize:
I could continue my integration using destination charges without on_behalf_of and still be compliant with Apple’s requirements.
In that case, my platform account would be considered the merchant, and the Apple terms screen should appear the first time for the platform — and that’s it, correct?

gritty ginkgo
#

Yes correct

rocky hatch
#

Thank you for your time. I appreciated it!!