#alyson_renan
1 messages ยท Page 1 of 1 (latest)
Hi ๐ you should not create payments and refund them to test a card's validity for multiple reasons. Card networks do not take kindly to that, and it may impact your standing with them. Stripe fees are not returned for refunded payments, so you will be charged for each payment you run in this fashion.
I would recommend having a flow available that customers can use to recover if the payment method you're trying to use for them cannot be successfully charged, and then direct them to that flow if a payment failure occurs.
Hum, okay! But... is there an alternative method to re-validate those credit cards without requiring any actual payment?
I don't believe so, do you have an example of one of the Payment Methods that you're referring to that I can take a closer look at?
I'm attempting to log in to my Stripe account, but it seems that the website is experiencing some technical difficulties. In order to streamline the process, I'm using Brazilian credit cards.
Unfortunately, I currently only have test card IDs available. However, if it helps, there is an card ID example "pm_1MjR1MDluC21KXx1UqDj6r3B"
Hm, the request to create that payment method looks a little surprising. It looks like you're passing raw card details. I want to make sure you understand that if raw card details touch any of your systems that greatly increases your PCI compliance burden?
Yes, I understand the risks involved in handling raw card details
Not risks, guarantees, you will have a higher compliance burden, but cool ๐
https://stripe.com/guides/pci-compliance
https://stripe.com/docs/security/guide
What's wrong with detecting validity issues at time of payment? Even if you were able to check validity right now, that wouldn't guarantee those details are still valid in the future when you try to process the payment.