#JBC2022&BEYOND
karmic kite
lament kindle
Which integration type are you using now? Payment Intent with Payment Element?
@pastel mountain Let's use this thread to continue the discussion
today they are using Payment intent.. this new guy is doing it differently
Can you share the example payment intent ID (pi_xxx) from the old and new reservation system, so that I can check their integration differences?
pastel mountain
Thank you.
Yes please one moment.. yes!
This is from the new one... no name, no email, pi_3NDuavGDZHeLkHfc0m8AtI1r",
This is one of the original. pi_3NDws9GDZHeLkHfc00huE8NJ
To be perfectly honest, it also appears that all of my security measures are bypassed in that first one as well. But the name and email are my main concern right now.
lament kindle
Checking them now
In old Payment Intent creation request https://dashboard.stripe.com/logs/req_E64n0vwHCpfRx1, customer field was set
In new Payment Intent creation request https://dashboard.stripe.com/logs/req_qzA92nmeoElvRr, customer field wasn't set
To have customer information available, customer field should be set
pastel mountain
Yes, I understand that.. i showed that to them..Also email is not set.. they say this is a PROJECT.. to do this..
lament kindle
This will integration changes on your new SAAS system. To ensure that the flow works the same, the new request should be in the same format as the old one. Unless the new SAAS sends Stripe those information, it won't be available in Stripe
pastel mountain
I agree - thus my question, how difficult a project is this... we see the fields that should be filled in.. we are inquiring as to how difficult is it for this to be changed? Could he do it for my account and no other accounts be effected? How long, how much work?
lament kindle
I don't know how your new SAAS system works, so we can't justify the effort of changes. From Stripe's perspective, it's just a parameter to be set, but it might be a big change from SAAS end like how their workflow should be changed
pastel mountain
OK, that is what I need to understand. I'm being advised this is extraordinary... and i don't agree. I've been doing it this way for 10 years.. that is the case. Thank you.
lament kindle
No problem! I'd recommend talking to your SAAS system. From Stripe's end, we just need those parameters to be set
pastel mountain
Yes, we have a meeting in the AM, I was hoping to persuade him with some context from this convo with you.. but again, no one is able to set difficulty level but him so we will see.. Can I ask one more question... Is the name and the client email normally sent over? It is so strange to see no client information.. do many do it without this information?
Thank you very much guys. Have a good night.
lament kindle
It's up to the business use case. If the payment method is set up to be saved, then customer object should be created. If it's just one-time payment without saving payment method for future usage, then customer creation and information aren't required
pastel mountain
Can. you look at the security checks I mentioned.. It seems that he is not doing zip code, not doing 3 digit code, not doing these, Can you advise what security settings are being used?
lament kindle
[Old SAAS] In the payment method creation https://dashboard.stripe.com/logs/req_dhvsN8o06imjJK, it used Setup Intent and Stripe Element to collect the payment method details, zip code and CVV - this is the recommended integration
[New SAAS] In the payment method creation https://dashboard.stripe.com/logs/req_h1y5tfg6Aciw8v, the SAAS collects the payment method details themselves (instead of using Stripe Element and Setup Intent) that zip code and CVV aren't collected - this is not recommended
I'd recommend sharing this Setup Intent integration doc with your new SAAS and suggest to them to migrate to the recommended integration flow: https://stripe.com/docs/payments/save-and-reuse?platform=web&ui=elements
pastel mountain
Thank you very much.