#iggna_best-practices

1 messages ¡ Page 1 of 1 (latest)

ruby heathBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always 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/1290761716984053902

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

weak fiber
#

Hello
Are these 3 stripe accounts connected to each other somehow? Like through a platform using Stripe connect?

tropic perch
#

Hi Hanzo, no, they are not connected, they are all 3 individual stripe accounts with their own API keys.

weak fiber
#

Gotcha. In that case, I don't believe there is a way aside from using raw PANs or asking customer to provide the details separately

tropic perch
#

how that use case would be? could you explain deeper into the first option? how is the approach of asking customer to provide the details separately? thanks

weak fiber
#

First option is where you accept raw card information and then create payment method objects using the API. This flow requires PCI compliance and approval from Stripe.

Second option is the thing you mentioned - input the information 3 times with a stripe UI element

tropic perch
#

I see, what would require on our end to be PCI compliant?

weak fiber