#hendrix_code
echo forumBOT
👋 Welcome to your new thread!
⏲️ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can 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/1252766288808513647
📝 Have more to share? Add details, code, screenshots, videos, etc. below.
teal gazelle
like authenticate the cards and do a $1 or $1.5 authentication charge to make sure the card is not a fake card
golden pelican
Got it. So there's no way to force an authentication charge on Stripe, and card networks discourage creating a small charge to "validate" a card
teal gazelle
golden pelican
When you use Checkout to create a Subscription and the amount is non zero, we'll the Session will prompt a customer for their payment details and those payment details will be used to both pay for the first invoice and save those payment details for future off-session payments
Placing a hold is different. It's not an authentication charge but an actual "hold" for a charge amount on a card. Once you're ready to charge that customer that amount, you capture the full amount (or subset) as needed.
Holds wouldn't really apply for a Subscription
However, if you want to place a hold on a payment, you can but only for Checkout Sessions in payment mode: https://docs.stripe.com/api/checkout/sessions/create#create_checkout_session-payment_intent_data
capture_method would be manual
teal gazelle
I see. So how can I prevent a fake card if I have a free plan for my product.
The free plan of my product contains 2 prices: $0 to get started and a usage-based subscription which will be charged in the next billing date.
I have some customers who just put a fake card to start a free plan, then I can't charge their usage.
golden pelican
We'll always collect payment method details for subscription mode: https://docs.stripe.com/api/checkout/sessions/create#create_checkout_session-payment_method_collection
A fake card shouldn't work 🤔
We'll still attempt to set up that payment method for future usage. Do you have an example Subscription or customer where this happened?
teal gazelle
yes
1sec
We set up a $0.5 charge to prevent a fake card. He paid the $0.5, and changed to a fake billing detail
golden pelican
Could you share the customer ID?
golden pelican
Okay, let's take a step back first
In this case, it appears that the issuing bank is flagging that their security code is incorrect. This is even after the initial invoice charge succeeded, which is possible
Taking a step back, would you be open to creating a pricing model that includes a flat rate price + usage based?
teal gazelle
yeah we have a paid plan that includes a flat price + usage based
But a free plan is for some poeple who want to try out our product first
why is possible if the initial incoice charge succeeded, since the billing detail like security code should be right?
echo forumBOT
crimson wedge
hello! give me a while to get back to you!
teal gazelle
sure
crimson wedge
It's possible that a bank may return a decline reason may not match up with why the card is actually declined. We don't really have any control or insights as to why a card is declined other than what the bank shared, so unfortunately don't really have any better answers for you here
teal gazelle
Gothca, so do you have any suggestions to prevent such situation?
crimson wedge
hrm, after the trial period, it's a paid plan which is a flat price + usage based right?
crimson wedge
ah, so the flat price isn't really a problem since you're charging up front. For the usage based which you're charging for later, one idea that comes to mind for me is to consider charging when they hit a particular threshold : https://docs.stripe.com/billing/subscriptions/usage-based/pricing-models#monetary-threshold. Another idea that comes to mind is to charge a one-time tiny flat fee upfront to make sure the credit card can really be billed, you can then add this amount to the customer balance to be applied to their next upcoming invoice - keep in mind that this adds complexity to your integration and can be confusing to your customers
teal gazelle
yes, that is what we're doing now. Charge $1.5 up front and give them equal credits. I just thought there might be a better way.
crimson wedge
nothing that comes to mind 😅
teal gazelle
anyway, thanks for your help!