johnduffs_docs

[ornate cape]

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

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

[flat goblet]

• is the current card workflow correct ?
  Which part specifically? The card part seems overly complex – then tokenization is redundant, you should just create/confirm a Setup Intent: https://docs.stripe.com/payments/save-and-reuse

That same flow above will work for SEPA

[wispy ginkgo]

ok, I see.

We can in fact create directly the payment method (card or sepa_debit)
https://docs.stripe.com/api/payment_methods/create

Then reuse the existing code with SetupIntent to validate the payment method.
And finally, we can use the existing PaymentIntent system.

What about our current production datas ?

I understand that sepa datas can be migrated using a tool in the dashboard
https://support.stripe.com/questions/reusable-object-migration-from-sources-to-payment-intents

Is it required to migrate the card saved with token in any way ?

[flat goblet]

We can in fact create directly the payment method (card or sepa_debit)
https://docs.stripe.com/api/payment_methods/create
Yeah but that's not really recommended (and is mostly redundant – it jsut tokenises the details without ever validating them)

Overall, this is optimal integration:

• Create Setup Intent
• Initialise Payment Element with the intent
• Collect payment details
• Confirm the intent via Stripe.js – this handles the 3DS/auth aspect and generates the reusable pm_xxx object

[wispy ginkgo]

I will not use Payment Element as we already have our own frontend library.

If we start from the form where we collect the payment details (card infos or sepa iban);

We send the infos to the backend (php/lararavel), using an ajax call.

In this situation, I should be able to pass the payment detail in the SetupIntent creation parameters.

first problem: In the API doc, I see the payment_method_data.sepa_debit datas but I cannot find payment_method_data.card ? Is is similar to Payment Method data ?

from the created SetupIntent, I then use the next_action.redirect_to_url for the 3DSecure in a modal window.

In the end, I got a background process to check the intent callback.

[severe lava]

hi! I'm taking over this thread.

If we start from the form where we collect the payment details (
which form are you using to collect cards details? your own custom form? we strongly recommend not doing this, since it would require your company to be PCI compliant.

[wispy ginkgo]

we have mainly used stripe.js until recently.
I have to check this PCI situation with the rest of the team.

[severe lava]

are you using Stripe.js with the Card Element or the Payment Element? if so, no need to be PCI compliant. but if you use your own custom inputs, then you'll have to be PCI compliant.

[wispy ginkgo]

ok I understand, so we have to go back to stripe.js integration

[severe lava]

either using Stripe.js, or using our hosted solutions like Checkout Session. these are our recommended options.