#samiya_webhooks
1 messages ¡ Page 1 of 1 (latest)
đ 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/1424632252935176194
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- samiya_api, 5 days ago, 75 messages
Hi there, there's no built-in mechanism to limit 1 subscription per credit card. You can consider writing your own radar rule to block certain transactions basd on card usage https://docs.stripe.com/radar/rules/supported-attributes?payment-method=card#card-usage
Can we write a radar rule to block duplicate transactions from a card even if the card is in trialing subscrption yet
Can you share more context? there's no transaction if the subscription is still trialing.
I have 3 domains, and on each domain I have a landing page where I am using Stripe subscription (7-day trial using setup intent to store the card) and then recurring transactions after that. What I want is that, e.g someone subscribes for a subscription on one domain using a card, then if the user tries to submit another form using the same card either on the same domain or another domain, it should throw an error
Are you using the same Stripe account for all these 3 domains?
Ok. So basically you want to block a transaction if the same credit card has been used in another subscription, am I right?
yes
https://docs.stripe.com/radar/rules/supported-attributes?payment-method=card#card-time
If you want to allow the first transaction but block subsequent ones, you could use this rule to only block transactions after a certain time period has passed since the card was first used:
Block if :seconds_since_card_first_seen: > 0
However, it may not work for trial subscription since no payment is involved. You'll want to test it out.
But this will block the the recurring payments as well I guess?
I just want to not have duplicate subscriptions with one card
You can combine the rule with the is_recurring attribute. For example
Block if :seconds_since_card_first_seen: > 0 AND NOT :is_recurring: to avoid blocking recurring payments.
So this will block duplicate transactions from a card but not the first recurring payment?
Yes you are right. To be clear, the first payment that your customer completed in checkout isn't considered as "recurring payment".
When I submit a form with a card for the first time its subscription will works correctly but if I use the same card again, it will block the form submission?
Have you tried? What's the subscription ID?
No I didnt try it yet. I was just confirming before trying
I'd suggest you to test it out in sandbox environment and let me know if you encounter problelms