#zhi-afterpay-checkout

1 messages · Page 1 of 1 (latest)

twin rain
#

@glossy hedge do you have an example Checkout Session id cs_test_123 I could look at?

glossy hedge
#

this is our request id: req_2zOLHMvfxmSX3v

#

I don't have the checkout session id

twin rain
#

all good that's enough for me to dig

#

Okay so first of all you are creating a Session on the connected account. You basically should never be doing that in the first place. Direct Charges should never be used with Express accounts. I would strongly encourage you to change that as fast as possible and move to Destination charges: https://stripe.com/docs/connect/destination-charges

glossy hedge
#

this is the error message

unknown.png
twin rain
#

And then since you use Connect here, you can't use afterpay on that account until after you request the correct capability in the API for it which as far as IU can tell you never did

#

it's not enough to enabled this on your own account, the settings are per connected account

glossy hedge
#

actually, we were told to pass stripe-account-id in the session creation api to do the direct charge

#

it is all good in the test environment with the same setting (connect account)

twin rain
#

Correct, you have to do it to do a direct charge. You absolutely shold never be doing this ever with Express accounts

glossy hedge
#

but start to get this kind of error from production testing

twin rain
#

sorry you're going a bit too fast and ignoring what I'm saying

#

1/ to be able to use a payment method, you need the Capability to be enabled on that account. If you don't request the capability, it'll never work

#

so have you done that? Because I don't see it on that account at least

glossy hedge
#

I am slow. please help me understand this.
As you said the way we have implemented is not recommended. Is this ever supported by the Stripe?

#

Can you guide us to the page that we need to quest the capability, please?

#

I don't see the request btn beside this feature

#

We have turned this feature on for all of our connected accounts

twin rain
#

yeah sorry you are misunderstnading a lot about all of this

#

turning this on doesn't mean much in this context. You have to explicitly request all the relevant capabilities for every single connected accounts

glossy hedge
#

from the UI, where is the place we can request the afterpay payment option?

twin rain
#

nowhere, this is 100% done with code

glossy hedge
#

oh, I see

#

let me check this again

twin rain
#

There might be a UI in the Dashboard for individual connected accounts to change the capability, but I'm mostly focused on the code here for developers to integrate

glossy hedge
#

ok, got it. I will try this out tonight. Thank you very much, Koopajah