#kaeshk-mandate-mit
1 messages · Page 1 of 1 (latest)
Hey! Mandates are often/sometimes required for certain PM types to facilitate a MIT (off-session payment)
What are you trying to do exactly?
we would call payment_intent ,with some extra info if needed to denote that user's payment instrument will be stored and would be charged as and when needed, like a subscription use case, but the trigger resides in our side
so first payment intent, would require action for user to complete payment on the bank page
after above successful step, for future subscription payments, we will call payment_intent (probably with the pi id of first payment and customer id), the user should be directly charged on that payment method ( no authorization is needed from user)
another api to cancel this arrangement, if user/merchant (us) needs
we would call payment_intent ,with some extra info if needed to denote that user's payment instrument will be stored and would be charged as and when needed, like a subscription use case, but the trigger resides in our side
That's what'setup_future_usageis: https://stripe.com/docs/payments/save-during-payment