#Pedru - Credt Card Validation
iron radish
Yep
I integrated with stripe to create subscriptions consuming certain endpoints directly in JS code on the front end, however I had problems saving some variables due to memory problems in some browsers. So I decided to create everything in services consuming only one URL but I created the service in node with TS in firebase functions and did some tests on the two integrations and realized that the integration in node with TS allows me to save the card with the year of wrong expiration but the old integration did not allow and gave error. I would like to know why this is happening.
dense isle
Do you have any request IDs that I could take a look at?
Here's how you can find a request ID: https://support.stripe.com/questions/finding-the-id-for-an-api-request
iron radish
Now it cames an error
hahaha
It's everything right, but i swear it cames a success with the wrong cvc
iron radish
It's everything right, but i swear it cames a success with the wrong cvc
And with a wrong exp year
dense isle
Well if you can find an example I'd be happy to take a look
iron radish
req_bnYU5MwnHhyzMZ
In this request it returned successes even with the wrong exp year
dense isle
Woah this /v1/tokens....that's an old API
iron radish
Ok hahaha
which api do you suggest I consume to create subscriptions?
I'm open to suggestions
dense isle
Well the ones I"m most familiar with use Stripe.JS to create payment elements (which triggers a client side request to /payment_methods
iron radish
Let me explain to you what I do
First I consume v1/costumers -> v1/tokens -> v1/customers/(customer Id)/sources -> stup_intents -> v1/subscriptions
Would it be possible for me to reduce this consumption of api, perhaps consuming less api?
dense isle
When you say "consume" could you be more specific? Are you creating customers, creating tokens, assigning tokens to customers, generating setup intents, then generating subscriptions? Are these calls all part of single worklfow?
iron radish
When you say "consume" could you be more specific? Are you creating customers, ...
You're right in everything
dense isle
Honestly there is so much that could be changed, I would start with our most current Subscription doc and review how these changes would impact you application: https://stripe.com/docs/billing/subscriptions/build-subscription?ui=elements
iron radish
I did it this way because I don't want to use anything from the stripe just the URLs
I mean, no stripe graphics
dense isle
That means you are handling raw card #s. You should be extremely certain you are PCI compliant
One of the highest value propositions of using Stripe.JS is you offload very high risk PCI compliance (i.e. transmitting raw card info) to Stripe so we can worry about that for you
dense isle
You're very welcome!