#KEITH LARD
1 messages ยท Page 1 of 1 (latest)
I am also sending
'setup_future_usage' => 'off_session'
Checking in to this. Is there a doc of ours that you were referring to for MOTO subscriptions?
I cannot find anything for MOTO specific to subscriptions
I am just making assumptions to be honest beyond the first payment with the setup_future_usage flag
is there anything I can read on this?
Not sure if we will have info on a MOTO specific decline rate for subscriptions. Each bank can have their own policies about that. As long as you have the payment method saved and attached to the subscription we will still be flagging all the proper things to the bank so that it has the best chance of approval
Cool, I am just concerned obviously after the first payment it will no longer be flagged as MOTO?
but we are saving the card for future usage and flagging everything correctly
๐ stepping in
I'd recommend using a SetupIntent here and indicating moto on the SetupIntent to collect the PaymentMethod. Then start the Sub using that PaymentMethod.
The PaymentMethod will be properly flagged for moto if it was created via SetupIntent with moto indicator set
I didn't realise you could use setupintent with moto, the docs just refer to paymentintent
Oh I see it actually
So can I use a setup intent with an existing payment method collected beforehand?
Hmmm that doesn't really make sense.
Sorry I'm confusing myself too
Like if it was already collected then it should have already been indicated as moto when it was collected
I'm using the card element to collect the card details
then charging via the api flagging MOTO
So my current flow.
- Collect and store payment method using card element
- Once successful, hit my API and charge that payment method with MOTO
Ah I see
but obviously if I use setup intent instead could I just not send through that payment method in step 2
and flag usage: off_session etc, for best chance of future success
Well you want to flag as moto since that is what it is, not just usage: off_session
Ye I will do that too sorry
But you should be able to do the same flow you are currently doing but pass the PaymentMethod ID to the SetupIntent
cool, so sorry to clarify one more time.
- Flag setup intent as MOTO
- usage = off_session as subscription will be created immediately.
- Create subscription using setup intent
Should I also send any mandate_data? I just want to make sure I am doing everything possible to reduce failures
Steps would be:
- create PM client-side
- Pass it to server and create/confirm SetupIntent where you pass the PaymentMethod ID and
payment_method_options: { card: { moto: true, }, }, - Create the Sub and set the above PaymentMethod ID as the default payment method for the Sub.
You should not need mandate_data unless you are working with Indian customers
Perfect thanks Ill try it now
the single_use parameter, is that useful?
Our subscriptions may increase in price in the future, if the customer asks for addons etc
No you shouldn't need single_use for a recurring payment
ok thank you for the help ๐