#aromeral-webhook-connect

1 messages · Page 1 of 1 (latest)

digital steepleBOT
#

Hello aromeral98, we'll be with you shortly! Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
aromeral98, 4 days ago, 6 messages

weary geode
#

@hazy flame There are many ways to integrate Connect depending on the flow of funds and the type of connected accounts. Can you clarify what flow you use exactly?

hazy flame
weary geode
#

aromeral-webhook-connect

hazy flame
#

the problem it's that I want to checkout.session.async_payment_succeeded from connect users Custom users

weary geode
#

Yep sorry there are 2/3 pieces of information that are crucial to help you and for you to fully grasp. They are going to be fundamental whenever you want help from us or support over the next few years

#

So you are using

  1. connected account type: Custom
  2. flow of funds: Destination Charges, Separate Charges and Transfers or Direct Charges?
hazy flame
#

I think it's destination charges
const session = await stripe.checkout.sessions.create({
payment_method_types: ["card"],
customer_creation: "if_required",
line_items: [
{
price_data: {
currency,
product_data: {
name: serviceTitle,
},
unit_amount: totalAmount,
},
quantity: 1,
},
],
payment_intent_data: {
application_fee_amount: feeAmount,
transfer_data: {
destination: stripeAccountId,
},
metadata: {
visit_id: visitId,
},
},
mode: "payment",
success_url: "https://www.google.com/",
cancel_url: "https://www.googles.com/",
});

#

this is my code

weary geode
#

Okay so
1/ You're using Stripe Connect to collect payments on behalf of third-party entities
2/ Connected account type: Custom
3/ Flow of funds: Destination Charges

This is crucial information. Try to remember that vocabulary and explain this when you need help for next time

hazy flame
#

yes

weary geode
#

So with that said: When you use Destination Charges, the activity happens on your own platform account and not on the connected account

#

what this means is that the Checkout Session, the PaymentIntent, etc. all of that is on your account. So the Events woul be sent to your Account webhook endpoint and not to a Connect webhook endpoint

#

that's your problem here you created the wrong type of endpoint

hazy flame
#

oh thank you I will try then

weary geode
#

@hazy flame did you make it work?

hazy flame
#

yes, now it's working thank you very much