#idhruv

1 messages · Page 1 of 1 (latest)

wicked hornetBOT
errant marsh
#

Hi there, what do you mean by future dated ?

raven estuary
#

it means if the subscription is set to trigger at some date in the future

#

In this case the user made the booking on November 10th for a subscription that was scheduled to get active on November 14th, but on that day i.e. 14 nov his payment was unsuccessful, what exactly is the reason?

obtuse kindle
#

👋 taking over for my colleague. Let me catch up.

#

looking into this, please bear with me

raven estuary
#

sure. ty

raven estuary
#

hey, any findings so far?

obtuse kindle
#

I'm still not sure, sorry, what I was able to find till now is that the customer doesn't have any Payment Methods(PM) attached to them

#

ok so that explains this, the Subscription Schedule you created for that customer expects to charge_automatically the customer, where in fact they don't have any PM attached to them and you haven't specified how this subscription will be paid

raven estuary
#

yes the collection method is set to charge automatically, but it is expected that they are making the charge using their credit card so why pm is not getting attached?

#

or to put this simply, how should i solve this issue entirely?

#

let subscriptionObj:any = { customer: String(customer.id), end_behavior: 'cancel', metadata: {'data': String(dataId)}, phases: [ { items: [ { price: price.id, quantity: 1, } ], application_fee_percent: percent, collection_method: "charge_automatically", default_payment_method: payload.cardId, transfer_data: { destination: stripeAccountId }, iterations: monthlyIterations, proration_behavior: 'none' }, ] }

obtuse kindle
raven estuary
#

okay

#

if that is provided, will this issue be solved? you sure?

obtuse kindle
#

on an unrelated topic, why are you using Subscription Schedules instead of Subscriptions?

#

is it because of this iterations: monthlyIterations?

raven estuary
#

hey, yes

#

because we are dealing with future payments here and subscription has no option to allot future dates

#

we want subscription to also be dated to some date in the future.

#

otherwise it would only work on that phase

can you please elaborate this? in my case i want to assign application_fee_percent for all the phases, so that is why i assigneddefault _payment_method, collection_method and application_fee_percent under phases

surreal yarrow
#

Hey! Taking over for my colleague. Let me catch up.

raven estuary
surreal yarrow
#

can you please elaborate this? in my case i want to assign application_fee_percent for all the phases, so that is why i assigneddefault _payment_method, collection_method and application_fee_percent under phases
My colleague was talking about the default_payment_method you need should instead set it at the subcription_schedule level and not the phase level.
Otherwise, you can set it for each phase. Be aware that if a future phase don't has a default_payment_method and its collection method is charge_automatically then the subscription will be incomplet and you need to deal with charging your customer for that phase. At the end, you can set this properties at the phase level, no problem with that

raven estuary
#

as per what you said i have modified the object to this, so can you please tell me if this application_fee_amount will be charged for each phase? as i have taken out the default payment method related attribute from phases

#

and secondly, transfer_data will this give out destination charges for every phase as depicted in the figure?

#

these two params are super imp.

surreal yarrow
surreal yarrow
surreal yarrow
raven estuary
#

okay

#

got it, i am trying this with test clock right now. thanks

wanton locust
#

Hey, taking over here. Let me know if there's any follow-up Qs I can answer!