antonioricardof_api

[potent crater]

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

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

[small oar]

Hi 👋 I would suggest using one of the flows shown this guide, which walks through the process for collecting payment method details with the intention of charging the resulting Payment Methods in the future:
https://docs.stripe.com/payments/save-and-reuse

These flows leverage Setup Intents and Stripe-provided UIs for collecting payment method details.

[true arrow]

Hey @small oar, okay!
But anyway, the customer needs to fill out the form with their payment details on the frontend, right?
With that said, what would the raw card data problem look like?

[small oar]

That's correct.

Can you elaborate on what you're referring to by "the raw card data problem"? If you need to process raw card details, you must complete the presented forms to indicate that you are PCI compliant and able to satisfy those compliance burdens.

You don't have to process a payment with the details to be obligated to PCI compliance, as far as I understand though I'm not a legal expert, but rather if raw card details touch any part of your system you must be PCI compliant.

[true arrow]

I'll try to explain it to you:

We are a marketplace, where people can sell and buy "assets".

To sell as soon as you sign up to our platform, we use oauth connect to connect your Stripe business account.

And soon after, we also wanted to link your main payment method to your stripe "buyer" account.

Because once this is done, all transactions are carried out asynchronously and we don't want to use a checkout for each offer you make, etc.

What would be the best way to resolve this using your API? I don't know if I understand, but if I'm going to use "sessions" for example, I need a checkout, right? And what would this look like due to several checkouts because you may want to buy several assets.

We wanted a way to attach the "buyer's" payment method directly to you, like with oauth connect, without us being in the middle. Is there such a possibility?

[small oar]

We wanted a way to attach the "buyer's" payment method directly to you, like with oauth connect, without us being in the middle.
I don't understand what you're trying to convey here, I don't know who "you" is in this context.

Did you look at the three options shown in the guide I linked for integration paths that can be used for collecting payment method details to create Payment Methods that you can charge in the future? Is there a limitation that I'm not aware of yet that is preventing you from leveraging one of those?

It sounds like the best way to handle this, is to use one of the flows shown there to collect payment method details from your Customer, then you can create payments using the resulting Payment Method in the future.

[true arrow]

I mean, "You" is an user.

[small oar]

Hm, I'm really not grasping that line then.

[true arrow]

Okay, I'll try to implement one of those ways you sent before. Probably the embedded form. And if I got some problem can I return in this thread?

[small oar]

Absolutely! If the thread's been closed, as we close out idle threads, you're always welcome to ask about the problem you're running into as a new question and whoever is staffing the server will help take a look.

[true arrow]

Another question, can I add our frontend developer here, in case he has questions?

Okay, seems like I can't.

[small oar]

Yup, they can certainly join this thread.