#CheckMate
wanton karma
naive cape
Could you elaborate a bit more? Do you have a request id (req_xxx) and where do you see the mandate doesn't get created?
winter cargo
How do I get the request id??
req_AVZxpy9ReGakA0
this is the request id
Hi are you there ?
naive cape
Hi, sorry I am juggling between threads. Will be looking soon!
winter cargo
cool
naive cape
Hey just looked at req_AVZxpy9ReGakA0 and I see a PaymentIntent created correctly with setup_future_usage. Where do you refer to by saying the mandate doesn't get created?
winter cargo
In the response the mandate field is null
I even captured the payment req_fcuURHxWMI4vsi but still mandate is null.
Also can I capture using client_secret ?
naive cape
No Capture need to be done with secret key, on server side
Going back to the previous question, why do you expect mandate with normal Confirmation and Capture calls? If you are just accepting card payment, you don't need that mandate
winter cargo
No , I want to store the payment_method for future usage , For that I need a madate right ?
naive cape
No mandate_data is for some specific/special Payment Method (ie. in cards in India). Normally you only need setup_future_usage as outlined on this Doc: https://stripe.com/docs/payments/save-during-payment?platform=web#charge-saved-payment-method
winter cargo
Okay then payment_method id should not get created if I put setup_future_usage off_session right ?
But it still gets created .
naive cape
why? It should get created because you will use it for next time
winter cargo
Okay cool but shouldn't it be created only in the case of off_session , it shouldn't be created in case of on_session right ?
Anyways , I have another question regarding auth and capture, Does auth move money out of customers account , since the amount - amount_to_capture is refunded by stripe ?
naive cape
Yes Auth will hold the fund from the Customer account
It's explained in this Doc: https://stripe.com/docs/payments/place-a-hold-on-a-payment-method
setup_future_usage doesn't matter on creating the PM or not, it only attach the PM to the customer after confirmation, and optimize for SCA. See https://stripe.com/docs/api/payment_intents/create#create_payment_intent-setup_future_usage
full basalt
Hey, taking over here. Let me know if there's any follow-up Qs I can answer!
full basalt
No, by default you can do only one capture
winter cargo
Cool
winter cargo
What happens if I try to cancel a payment_intent when it is being processed ?
full basalt
What do you mean by 'processed' ? the payment is achieved successfully?
winter cargo
no it is showing loading symbol
It is in the way of being processed meaning stripe calls the bank api's etc.
full basalt
Could you please share the Id of the related PaymentIntent ?
full basalt
Actually you can cancel a PaymentIntent unless the related status is in one of those:
requires_payment_method, requires_capture, requires_confirmation, requires_action, or processing.
Once canceled, no additional charges will be made by the PaymentIntent and any operations on the PaymentIntent will fail with an error
winter cargo
But what if a request call goes to confirm a payment_intent, and while the request is still being processed , I mean I am yet to get a response for the request from stripe, if someone sends a cancel request , How would stripe handle it ?