#lukez_best-practices

1 messages ยท Page 1 of 1 (latest)

solar pulsarBOT
#

๐Ÿ‘‹ Welcome to your new thread!

โฒ๏ธ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

โฑ๏ธ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

๐Ÿ”— This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1296275704207642727

๐Ÿ“ Have more to share? Add more details, code, screenshots, videos, etc. below.

latent ravine
#

Because here in the EU we have to guarantee a refund within the first 14 days after payment.

grim dock
#

hello! I'm afraid we can't really help with this. We mainly help with developers who want to integrate directly with the Stripe API here on this channel and can't advice on questions that relate to regulations

latent ravine
#

Ah okay I see but where is the best place to ask?

#

Stripe Support?

grim dock
#

I don't think this is something that Stripe can help you with in general since EU regulations say that you have refund within the first 14 days after payment. You may need to consult with your legal team on what can be done with regards to abuse of the refund policy first instead

latent ravine
#

well, it's not about the legal side but rather a question about how to prevent this kind of behaviour.
Because the consequences are already clear.

grim dock
#

I can't think of any way of how to prevent this behaviour that wouldn't go against the regulation itself. If you have specific ideas in mind, we can help with how to implement them (in Stripe if possible)

latent ravine
#

Well, I was thinking of checking the refunds regularly for suspicious activity (once per month or something like that).
Checked are the refunds for the customers and if they requested more or equal than 2 refunds in a certain time period for the same guild I have in my database in relation to that subscription id I could prohibit them in the next 3 months from subscribing again.
Is this something I should better do with my database (since I store all subscriptions in the database with the subscription, product, customer, user and guild id) or with Stripe?

#

Oh, and can I somehow block a certain customer from subscribing again?
since creating multiple Discord accounts is very easy.

#

-# Now I'm done xD

grim dock
#

hrm, gimme a second to check on a feature to see if it works for you

latent ravine
#

sure

grim dock
#

it'll be better for you to implement this logic on your own DB. For context, I was looking at Radar for Fraud Teams (RFFT) which allows you to set rules to define what kinds of charges to block. However, looking at the list of rules we support for this feature : https://docs.stripe.com/radar/rules/supported-attributes, it doesn't cover what you want which is to block customers who have x refunds within a certain timeframe from subscribing.

#

I'd like to point out that RFFT is also a paid feature (so it's not free too)

latent ravine
latent ravine
# grim dock it'll be better for you to implement this logic on your own DB. For context, I w...

Ah okay, thank you anyways ๐Ÿ‘Œ๐Ÿป

Btw. I have two other questions regarding refunds, strictly speaking

  1. how to handle multiple sources of refund requests (stripe directly from the user and API on my side).
    Is there a Webhook event for when the user requests a refund?
  2. How to enforce my refund policy with requests, not from the API but directly on stripe.
    Or is there a way to disable this so users have to use (in this case) my app for automatic refunds or contact me via e-mail so I can manually process their refund request?
grim dock
#

I don't quite understand stripe directly from the user - maybe can you share an example?

latent ravine
#

Iirc a customer can request a refund directly via the stripe website/dashboard.

#

And of I remember this also correctly, it's not possible to enforce any policy there, right?

grim dock
#

by user , do you mean the customer who pays?

latent ravine
#

Yes, my bad

grim dock
#

that's not possible. A customer cannot request for a refund via Stripe

#

the customer needs to always request for a refund via the merchant

latent ravine
#

Oh, so either manually via an e-mail to me or "sort of automatically" in my app and the "merchant" is represented by an API request there?

#

For example

grim dock
#

yep!

#

the merchant i.e. you can initiate a refund to the customer either via the Dashboard or via the API

latent ravine
#

Ah okay, this is some good news ๐Ÿ‘๐Ÿป

#

Because the code I've already written already implements the automatic refunds perfectly.
Only the security measures are missing now ๐Ÿ‘๐Ÿป