#test1964-Sepa

1 messages · Page 1 of 1 (latest)

twin sedge
#

Um that's the SetupIntent flow and you don't specify an amount there

#

so yes it doesn't actually charge any money

rancid burrow
#

ok, what are the mandatory customer details that would be required in this flow?

twin sedge
#

I don't have the list to share, but I am sure our SDK will collect it for you

#

you don't need to to worry about the details

#

Only know that information here will be available

rancid burrow
#

ok, what API call we'll need to make to capture payment for the SEPA direct debit mandate with mandatory params?

twin sedge
#

Follow the Doc you linked earlier

# 
    <div id="iban-element">
      <!-- A Stripe Element will be inserted here. -->
    </div>
#

Then mount this div and call confirmSepaDebitSetup from Stripe Element

rancid burrow
#

the capture of payment will happen after the checkout seesion, so we wont have the stripe element

#

it would be an API call

twin sedge
#

Oh are you using Checkout?

#

Then I think Checkout would automatically does that for you too

rancid burrow
#

your earlier resposne 'Um that's the SetupIntent flow and you don't specify an amount there
so yes it doesn't actually charge any money'

twin sedge
#

Sorry if I misunderstood your question. To clarify, you are using Checkout in setup mode, for Sepa Direct Debit, right?

rancid burrow
#

yes, but in that session, we'll only capture bank details & create a mandate, we wont capture any payment

#

we want to capture payment from backend

twin sedge
#

Because it's a SetupIntent, it won't generate a payment anyway

rancid burrow
#

yes

#

now we want to capture the payment after few days

#

for that which API call we should make & what are the mandatory params for that

twin sedge
#

When you specify the Setup mode Checkout, what parameter you used to not capture right away?

#

Just aligning

rancid burrow
#

exploring that part but as you said its a setupIntent & a paymentMethod object so there wont be capturing payment

#

we will be capturing the payment every month on a specific date, for that should we make PaymentIntent call from backend system ?

twin sedge
#

its a setupIntent & a paymentMethod object so there wont be capturing payment
Yes exactly!

#

capturing the payment every month on a specific date,
Yes, make a PaymentIntent, specify the PaymentMethod (pm_xxx) that is saved inside the SetupIntent object

rancid burrow
#

ok, what are mandatory params in the PaymentIntent call to capture payment for SetupIntent object

twin sedge
rancid burrow
#

so apart from, payment_method, amount, currency & confirm params, should be also add the customer param ?

#

Understanding what are the mandatory params here is very important for us, that is why repeating the same question 🙂

twin sedge
#

Customer is to identify the same person you want to charge

#

But really the saved payment_method already attached to a specific Customer, so if you pass in a different person the API will error out

rancid burrow
#

ok, so the customer id param is not mandatory only payment_method, amount, currency & confirm params are enough

twin sedge
#

Yeah. I recommend testing and exploring in Test mode

rancid burrow
#

ok, thanks for your help