karsh-upe-fields | Stripe Developers | Page 1

normal sleet Aug 15, 2022, 8:30 AM

#

Maybe: https://stripe.com/docs/js/elements_object/create_payment_element#payment_element_create-options-fields-billingDetails-name

Stripe JS Reference

#

But some PMs may require that fields, so it can't be omitted

limpid rivet Aug 15, 2022, 8:34 AM

#

Thank you!
If I understand correctly, in those cases I can still omit them yet I need to pass the same data to stripe.confirmPayment ?

normal sleet Aug 15, 2022, 8:35 AM

#

Yes: https://stripe.com/docs/js/payment_intents/confirm_payment#confirm_payment_intent-options-confirmParams-payment_method_data-billing_details

Stripe JS Reference

#

So you could use the value from your own separate form in that case

limpid rivet Aug 15, 2022, 8:36 AM

#

So then what you said:

But some PMs may require that fields, so it can't be omitted

turns out to be incorrect, right?
Just want to make sure I understand you 100% 🙂

normal sleet Aug 15, 2022, 8:45 AM

#

There are some instances where the PE will always render fields even if you specify never

#

But:

options = {
  fields: {
    billingDetails: {
      name: 'never'
    }
  }
}

#

Works for iDEAL

limpid rivet Aug 15, 2022, 8:52 AM

#

Ah I see, where can I see a list of these instances? Or is the only way by trying out all payment methods by myself with the above option?

normal sleet Aug 15, 2022, 8:57 AM

#

Not sure I understand

limpid rivet Aug 15, 2022, 9:03 AM

#

Let me try agian.

In our use case, we want a 2-step checkout, using the payment element + orders api.

On our we first ask (step 1) for: name + email.
In step 2 we load the payment element.
We will allow our connect accounts to determine which payment methods to accept. So many different payment methods will be used.

After your help I'll make sure to load the payment element with:

options = {
  fields: {
    billingDetails: {
      name: 'never',
      email: 'never
    }
  }
}

Everything should work as we want, which is: step 2 shouldn't ask for the name or email in any case

However you write:

There are some instances where the PE will always render fields even if you specify never

This seems like an exception? I'm curious to know with which payment methods the PE will still render these fields

normal sleet Aug 15, 2022, 9:09 AM

#

We will allow our connect accounts to determine which payment methods to accept
Why not use automatic payment methods?

#

This seems like an exception? I'm curious to know with which payment methods the PE will still render these fields
This isn't publicly documented anywhere, however I believe it mostly pertains to postal code for card payments

limpid rivet Aug 15, 2022, 9:13 AM

#

Why not use automatic payment methods?

I think we do , but please correct me if I'mw rong: what I mean is that the connected account can enable payment methods in the dashboard. And we don't set specific payment methods when we create the order (Server side)

#

This isn't publicly documented anywhere, however I believe it mostly pertains to postal code for card payments
If that's the case, great! Just concerned about the name and email still showing up 🙂

normal sleet Aug 15, 2022, 9:13 AM

#

Ah, yes. Got it

limpid rivet Aug 15, 2022, 9:27 AM

#

Different question: is there a good overview page to see what is possible with which api combined with the PE?

For example we want to build certain features into our system (coupons, one click upsell, starting subscriptions with ideal). Now I have done my research before and this should all be possible.

But I keep getting confused and stuck because certain things are not compatible with eachother (not sure if true, but for example: starting subscriptions with ideal (https://stripe.com/docs/payments/ideal/set-up-payment) is not compatible with the orders API))

I need to know all the limitations of these different api's and features

Use iDEAL to set up future SEPA Direct Debit payments

Learn how to save bank details from an iDEAL payment and charge your customers later with SEPA Direct Debit.

coral sorrel Aug 15, 2022, 9:28 AM

#

👋 Taking over this thread

#

We have integration options doc here which explains the payment methods/feature supported under different integration types: https://stripe.com/docs/payments/payment-methods/integration-options

limpid rivet Aug 15, 2022, 9:33 AM

#

THanks, reading it now.
One question coming to mind: is Orders replacing paymentIntents?

coral sorrel Aug 15, 2022, 9:33 AM

#

Nope. Orders use PaymentIntent under the hook

#

Orders is for Stripe Tax support with PaymentIntent integration

limpid rivet Aug 15, 2022, 9:35 AM

#

Hmm okay thanks!

coral sorrel Aug 15, 2022, 9:36 AM

#

No problem! Happy to help 🙂

limpid rivet Aug 15, 2022, 9:37 AM

#

Is it possible to use this https://stripe.com/docs/payments/ideal/set-up-payment
with stripe tax?

#

Second question: we can not use PE with this, can we?
It is talking about idealBank element

coral sorrel Aug 15, 2022, 9:41 AM

#

This integration doc is for individual element, i.e. integrate standalone iDeal. Payment Element is unified for all payment method supported and you shouldn't require a separate integration as Payment Element will take care of it.

limpid rivet Aug 15, 2022, 9:44 AM

#

Sorry I don't fully understand. I want to be able to sell subscriptions using ideal. So instead of them filling in their SEPA bank details, they make a 0.01 payment using ideal.

I believe this doc shows how to do it, but are you saying that I don't need to follow it because the PE already does this?

coral sorrel Aug 15, 2022, 9:44 AM

#

To support Stripe Tax on iDeal using Payment Element, the process will be:

Use Orders, and it will generate a Payment Intent client secret (pi_xxx): https://stripe.com/docs/orders/create-and-process
Pass the client secret to the frontend to process payments that will include payment methods supported in Payment Element

#

Ah wait!

#

Can you explain more what you want to achieve?

limpid rivet Aug 15, 2022, 9:51 AM

#

Sure, let's say we sell a subcription: 'membership X' for 99 euro / month.

Right now we have 'stripe checkouts' integrated and on the checkout page it shows input fields to enter your bank account information.

Instead of those input fields, we want to get the bank details by leting the user complete an ideal payment of 0.01 euro

#

I'm pretty sure the page I linked tells me how to do that. However, I'm confused if I can do this with the Payment Element instead of the 'iDeal bank' element

coral sorrel Aug 15, 2022, 10:01 AM

#

This is possible with SetupIntent on Payment Element (instead of using ideal bank element): https://stripe.com/docs/payments/save-and-reuse

#

After ideal is collected, then you can payment method ID (pm_xxx) as described from Step 6 onwards: https://stripe.com/docs/payments/ideal/set-up-payment?platform=web#charge-sepa-pm

Use iDEAL to set up future SEPA Direct Debit payments

Learn how to save bank details from an iDEAL payment and charge your customers later with SEPA Direct Debit.

limpid rivet Aug 15, 2022, 10:13 AM

#

Okay thanks I looked at the docs, so essentially I can follow steps 1-5 from https://stripe.com/docs/payments/save-and-reuse and then continue from step 6 with the other doc?

coral sorrel Aug 15, 2022, 10:16 AM

#

Yup! I'd suggest trying it out in test-mode first

limpid rivet Aug 15, 2022, 10:20 AM

#

Okay great thanks that helps!

If I understand ita ll correctly, I can do the following right?

Subscriptions

Use Stripe Tax
Let user start a subscription with 0.01 ideal payments
Let user use coupons
Use payment element for all of the above

To do all of this I need:

Subscription API
To use setupIntents
Payment Element

One time payments

Use Stripe Tax
Let user use coupons
Use payment element for all of the above

To do all of this I need:

Orders API
To use paymentIntents
Payment Element

coral sorrel Aug 15, 2022, 10:33 AM

#

Looks right to me!

limpid rivet Aug 15, 2022, 10:41 AM

#

Thanks agian, will make more proof of concepts now 🙂

#karsh-upe-fields