goup_api

[serene marsh]

👋 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/1334893378802024578

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

[civic sparrow]

Hi, taking a look here

We talk about it here: https://docs.stripe.com/checkout/fulfillment

Specifically for payment methods that are async, https://docs.stripe.com/checkout/fulfillment?payment-ui=stripe-hosted#create-payment-event-handler you might need to handle it differently

[pine hazel]

Good afternoon!

I've actually never gotten a checkout.session.async_payment_succeeded event in my webhook from creating a checkout session with a payment_intent defined like so:

    application_fee_amount: STRIPE_APPLICATION_FEE, 
    capture_method: 'manual',
    metadata: {
      visioId: visioId,
    },
  },
```

[civic sparrow]

You will need to use of the async payment methods to test that. Depending on the country your account is in you might be eligible to offer one of these: https://docs.stripe.com/payments/bank-debits

Please review that carefully and test it on your end

[pine hazel]

This is quite different from what my client needs, as the end customers are individuals and not companies. Mandates like this are a bit too formal. This is what we want to use: https://docs.stripe.com/payments/place-a-hold-on-a-payment-method

sorry, this part of the documentation is more specific to what we need: https://docs.stripe.com/payments/accept-a-payment?platform=web&ui=stripe-hosted#auth-and-capture

[civic sparrow]

You mentioned success_url which I assumed you were using Stripe Checkout.

Stripe Checkout does support this auth and captrure flow as well

You can set that here: https://docs.stripe.com/api/checkout/sessions/create#create_checkout_session-payment_intent_data-capture_method

[pine hazel]

To my understanding we are indeed using Stripe Checkout. I have managed to integrate that flow in my application:
Customer enters card details in Checkout session -> Card imprint is made -> Webhook listens for payment_intent.amount_capturable_updated and updates DB if requires_capture is true -> Later on I call an enpoint that will manually capture the funds

What I am trying to figure out here, is whether the redirection to success_url is enough to tell my customer that the imprint was successful, or if on that success_url page, i should retrieve the information my webhook got to give my customer a final answer on the status of the imprint

[tepid echo]

What do you mean by status of the imprint

That's not a Stripe term, so I just want to be clear

[pine hazel]

If the imprint was successful I guess

That we are indeed holding funds on their card

[tepid echo]

Reaching the success_url should be enough I think. Assuming you're talking about card payments

[pine hazel]

yes

That's all I needed to know about, thanks for your answers !