#Colby S
1 messages · Page 1 of 1 (latest)
Hello, there isn't really a "best" charge type, it is more a question of which is best for your situation. We have this doc with info on each charge type if it helps you decide https://stripe.com/docs/connect/charges#types
Happy to answer questions about the differences if you have them
Should have been specific on that also we are using direct charge
In that case you will be using the Stripe account header, that is what makes it a direct charge
The on_behalf_of parameter is for destination charges. It basically helps destination charges get some of the benefits of direct charges
So when I set the header, it goes to the page but I get an error after the payment is complete saying SignatureVerificationException: no signatures found for payload.
That error is likely coming from your webhook signing secret. Have you double checked that that value is getting populated in your code and that it is set to the value you expect?
yeah because when I comment out the code for headers it works fine
oh wait
I am sorry i am giving you the wrong exception
InvalidRequestException: no such checkout.session then goes missing resource
Can you check your logs and send me the request ID of a time that you got this error? (req_123)
req_Ob9Ld3kE8OKVz0
Ah I see, so that is happening because you created the checkout session on the connected account but tried to retrieve the session with your platform account. You should include the StripeAccount header again when retrieving the Checkout Session, that should let you look it up properly
Gotcha, I think I may have tried that or maybe I am doing it wrong. But i have a map checkout session and I am setting it there also with setPaymentIntentData then setDestination("childAccountId"). Is this the correct way of doing so?
When you are using direct charges you should not be using set destination, just use the StripeAccount header
setDestination is for destination charges
I do think something may be a bit off with the mapping. In our logs I definitely see your integration using the StripeAccount header to create the session but not to retrieve it