#onkel_api
1 messages Β· Page 1 of 1 (latest)
π 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/1273936837752393791
π Have more to share? Add more details, code, screenshots, videos, etc. below.
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.
- onkel_api, 1 day ago, 40 messages
This probably covers it: https://docs.stripe.com/payments/paymentintents/lifecycle
I cant find any thing on the topic. i can only find this in the api docs:
https://docs.stripe.com/api/payment_intents/confirm
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
Capturing referenced on that page:
If youβre separately authorising and capturing funds, your PaymentIntent can instead move to requires_capture. In that case, attempting to capture the funds moves it to processing.
https://docs.stripe.com/payments/place-a-hold-on-a-payment-method
Confirmation is generally the payment 'attempt' which will create an auth/charge with the card and handle 3DS/auth is requested by the bank
The capture process is if you're capturing the hold placed on the card later, post-confirmation
I Denmark, shops arent allowed to withdraw money from the customers bank accounts, before we fullfill the order.
I our scenario its like "click and collect", so the store owner will manually click a "Delivered" button in our app.
Concept of capturing is not relevant for a lot of merchants, it's kind of common in lodging etc (think a hotel when you check-in β they place a hold on you card and then bill you when you check out)
Then you probably want to look at off-session payments for that
i.e. the customer authorises you to save their card on checkout, and you can initiate a transaction for the amount when the order is delivered
But isnt it normal practice in EU too first withdraw the money from the customer, when you either ship the products or hand them out in the store?
i thought it would be supported by the "normal" flow
How it generally works here, yes (UK)
I don't know what you're asking me tbh
Both flows are possible with Stripe, and they utilise the same concepts/APIs you'd just pass differing parameters and may need to make additional requests
Sorry, if I'm unclear. The terminology is new for me.
What i''m asking is whats the last step called, where you tell Stripe that we gave the customer his/hers products? π
e.g. this payment
You'd jsut create an 'off-session' (MIT) Payment Intent with the previously saved card details. It'll probably look something like this:
- Customer in your checkout flow has an order for β¬100
- You save their card on checkout with the intention of charging them later (on delivery). This is done via a Setup Intent: https://docs.stripe.com/payments/save-and-reuse
- Order is shipped/fulfiled, you have logic that then creates an off-session Payment Intent using the card saved in step 2 for the β¬100: https://docs.stripe.com/payments/save-and-reuse?platform=web&ui=elements#charge-saved-payment-method
Ok! I will look into that. I thought the "SetupIntent" was for subscriptions and saving creditcard info for easy checkout for next purchase π
It's used to facilitate the saving/setting up of cards with the intention of them being used for MIT (merchant initiated transactions). As long as you're verbose with customers about that usage and they agree to it, then it's fine for your use case
This is just regular Checkout Session payment that was confirmed/paid whilst customer was on-session so not really sure how that fits with the Danish scenario you described
The 'capture' was done at confirmation time in the case of that payment
Well i guess it doesnt. But i have misunderstod how to use the api.. i guess..
i'm a bit confused on why the default functionality of the api captures the payment immediatly if EU countries have rules that prohibit withdrawing money before the order is fullfilled. but i'm novice at this, sry π
I thought you created at PaymentIntent and then there would be and Api call to finalized the payment and withdraw the money, when the orders is fullfilled
if EU countries have rules that prohibit withdrawing money before the order is fullfilled
I'm not aware what rule you're referring to here.
would be and Api call to finalized the payment and withdraw the money, when the orders is fullfilled
you can do that, it's an optional way to integrate(authorise a payment (same way hotels etc hold funds on your card) and capture it later); if you want.
But you need to do the Capture before 7 days, right?
what happens if you have a longer delivery period?
it's 7 days for most businesses yes
what happens if you have a longer delivery period?
you decide what's appropriate. For example you can attempt to charge the saved card again(the 3 steps my colleague previously explained).
you can also charge upfront and then just refund if for whatever reason you can't fulfill the order, there are many possible ways of building these flows
Okay. I will have to discuss with my team. We thought the periode from authorize and capture was longer π