#celebdil_unexpected
lapis abyssBOT
đ 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/1397267981997834302
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
slim arrow
hello! can you share an example payment intent?
midnight jungle
pi_3Rnjz8PVZzhWGZc11Yy06w3S
This one is created confirmation_method=manual and payment_method_data={type='revolut_pay'}
Its status should be "requires_confirmation"
Tell me when I can confirm it
You should see their is no redirect url for completing the payment (by the user) provided in the current status
This only is available after confirming the intent
slim arrow
give me just a little bit, working on reproducing
ok, so i've been able to reproduce the behavior you're describing. let me triple check to make sure that's not the intended flow for this.
slim arrow
ok yes, i think this is expected. what you're doing here is essentially saying "i want to confirm this manually and i want to limit this to being paid via revolut_pay", so in this case there isn't any other "next action" other than confirming, which then returns the revolut pay link to you
midnight jungle
Okay
It would be very helpful to have a step of confirmation after the user authorised the payment (after the redirect)
Is there something like this?
capture_method=manual could be used I guess, but I don't know if the fees are already charged when cancelling after authorization before capturing. Do you know this?
slim arrow
capture_method=manual would indeed work. i'm pretty sure we don't charge fees until the payment is captured but let me double check that
ok, i just ran a quick test and verified that fees are only created when the funds are captured
midnight jungle
Ok, good to know. Thank you
slim arrow
which makes sense because, let's say you're doing partial capture and only capture 50%, we aren't going to charge for the full amount
midnight jungle
Unfortunately there is a problem with capture_method=manual I just encountered: It isn't supported by SEPA Direct Debit
So if I want to accept revolut and SEPA payments, I can't use capture_method=manual. For SEPA confirmation_method=manual would work, because there is no additional step, but it isn't working for revolut
Is there a way to combine this (a way to only process payments after the last step of the user)?
slim arrow
hmm, i don't think there are any other options here aside from capture_method: manual
can you share more about why you want to delay finalization after they've completed the revolut flow?
midnight jungle
I want to offer other payment methods not using Stripe and thus in case more than one payment attempt is made I serialize these attempts and only accept the first one (in my backend)
Imagine you start a payment via Stripe and something seems to go wrong (maybe bad network connection), you restart the payment and use a different payment method and finish it succesfully but in this moment Stripe returns a success message as well
Then only one of these should be processed and the other one cancelled
slim arrow
gotcha, that makes sense in theory, but yeah i don't think we have another option in the case of revolutpay. you might just need to go down the route of building out different pathways for different payment methods unfortunately