#manish_api

1 messages ¡ Page 1 of 1 (latest)

karmic flintBOT
dark coyoteBOT
#

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.

karmic flintBOT
#

👋 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/1245820666008178890

📝 Have more to share? Add details, code, screenshots, videos, etc. below.

stark wagon
#

howdy

turbid ridge
#

Hola Amigo

stark wagon
#

What you're describing doesn't add up -- what does creating a payment method with raw card details have to do with creating a payment link? Can you explian the flow here?

turbid ridge
#

I see it in two ways Either of them works for me

  1. i create a payment link and the customer proceeds with the payment
  2. the customer provides the raw card details in my web app and we create a payment method for them in their account
stark wagon
#

These are very different things

#

And you should not collect raw card details directly, you should use Elements

turbid ridge
#

So if i create a payment link using the sdk, then the payment method gets stored in the customers data right?

stark wagon
#

What are you trying to do ultimately? Use the details later?

the payment details needs to be stored in the customerData.
Can you explain this more?

turbid ridge
#

Okay so i have my web app its a customized erp
so when an order comes into the system we wish to create a payment link so that customer can proceed with the payment
if a customer has already done a payment on any of the previous order then he should be charged again for other order without entering the payment details again

stark wagon
#

If the payment is for a specific customer for specific items, you might want to use the Checkout Sessions API directly, instead of payment links, because you can specify the customer ID here and have the payment method saved for later use

turbid ridge
#

So all the payment methods are saved using checkout session or only one?

stark wagon
#

Customers can have multiple payment methods attached, or you can detach them, thats up to you

#

Then you'd retrieve those later to handle the future payments

turbid ridge
#

in case of checkout session i dont need PCI compliance right?

stark wagon
#

(because you'd never have access to the card details, there are fewer requirements)

turbid ridge
#

i see

#

if i dont pass the customer_id while creating the checkout session, how it will identify if a customer with that info already exists? what will be the primary key?

stark wagon
#

It doesn't, it will create a new one (if necessary, based on the session configuration)

turbid ridge
#

even if a customer with same details already exists it will create a new one

stark wagon
#

Yes

turbid ridge
#

Understood

stark wagon
turbid ridge
#

Thanks @stark wagon
I will create a new thread if i have any other doubts