#fundrise_evan
1 messages ยท Page 1 of 1 (latest)
Hello! To clarify, you're referring to this setting, correct?
Yes, That's the setting.
That setting only applies to Subscription payments. You said you created an Invoice which isn't associated with a Subscription, correct?
No, it created an invoice for the subscription.
The invoice was then disputed because I used the fraudulent card number above.
Can you give me the Invoice ID so I can take a look?
in_1M9YvI2XRZBXnduIjcauckaN
Hi taking over for Rubeus as they have to step out. Taking a look now
I see your account settings actually have that setting set to "leave the subscription as is"
Can you check that setting again?
It's currently set to that now, when I initially tested the subscription it was "cancel the subscription immediately without prorating"; I tried to use this invoice with test clock to test the workflow.
Hm I don't see a test clock tied to that subscription
But this is strange
Let me see if I can get a coworker to take a look
๐ looking also
Thank you.
I see the dispute on the invoice payment, but agree it doesnt appear that subscription ( sub_1M9YvI2XRZBXnduIUuj9Bbjg ) used a test clock, though I don't think that should be related anyways
Let me try with my own account
This subscription was created via Connect using the direct charge approach (with the stripe account header/option)
Where did you set the dispute treatment setting, the platform or the connected account?
It looks like this was set on the platform
Was it about a week ago you turned that on?
Yes it was the platform, and yes.
I still need to test, but i suspect this is because its a standard account with direct charges, and that setting would be taken from the connected account, not the paltform
Ah, so the connected account has it's own dispute treating setting?
Yes, they have the same options available in their dashboard settings
and since the subscription "belongs" to them, along with the dispute liability, they can decide how to treat those
Ah, thank you. I'll attempt to retest that; I tried to do it on the platform level as well; with this invoice in_1M7252FYG4bVri12qzbaypmI via test clock, but it also did not change the subscription status even when the invoice was disputed.
alllmost have my test set up
going to try a different test, as i am getting the same result currently
When you pick the cancel option, there's text that appears with:
Cancelation will only take effect if the opened dispute is for the full amount on a recurring card payment.
And i only tested on the first payment
going to try on the renewal
Hmm my renewal test didnt do this as i expected either ๐ค
Ooof; Hmmm... would you recommend handling it manually?
Setting it "leave subscription as is", and handling subscription cancellation via api calls.
That's one option, managing via webhooks on disputes