#jitendra

1 messages · Page 1 of 1 (latest)

sonic adderBOT
tender plover
#

👋 happy to help

#

would you mind sharing the request ID?

tender ruin
#

req_PBnusy9zwclu5m

#

I have many requests, if it's asking for authorisatino then it should be during "stripe.paymentIntents.create"
i am using below params while creating payment intent.
confirmation_method = 'automatic'
confirm = true
payment_method_options = { card: { moto: true } };

tender plover
#

instead of attaching the payment method after the PaymentIntent succeeds

#

why not just use setup_future_usage: 'off_session' ?

tender ruin
#

I am attaching payment method before PaymentIntent success

tender plover
#

you don't need to attach the PM separately

#

that's what I'm trying to say

tender ruin
#

ok setup_future_usage=off_session will automatically take this payment method next time?

#

what's difference if i use off_session and on_session?

tender plover
#

ok setup_future_usage=off_session will automatically take this payment method next time?
no this attaches the PM to the customer for future usage

#

you'd still have to pass in the PM ID each time

#

off_session means the customer is not present to authenticate the PI and on_session the customer is there

tender ruin
#

ok, setup_future_usage will automatic attach payment method to customer right?

tender plover
#

yes correct

tender ruin
#

thanks for your help, i will try to integrate this.
setup_future_usage i will set only in case of
payment_method_options = { card: { moto: true } };

#

i am taking payment by three way

  1. SEPA direct debit
  2. through mail order telephone order
  3. through online, customer direct pay from our website

so i believe in 1st and 3rd method i have to continue use "stripe.paymentMethods.attach" method. correct me if i am wrong

woven acorn
#

Hi! I'm taking over from my colleague. Please, give me a moment to catch up.

#

Which of 3 was failing initially?

tender ruin
#

2nd is failing since last 10days
i can't about 3rd one because i didn't hear any complaint from out customers

#

10days agp eveything was working fine with same implementation

woven acorn
#

What's your flow with the moto payments currently?

tender ruin
#
  1. Create customer
  2. Create payment method
  3. Attach payment method to customer
  4. Create payment intent by cusotmer id and payment method id
#

if customer already exist then i am just creating payment method and attach to customer and then follow step 3 and 4

woven acorn
#

Isn't MOTO payments supposed to be typed in by you?

#

Can you just create a Customer, then a PaymentIntent and save the PM for future usage?

tender ruin
#

If i use future usage then how it will impact SEPA direct debit and online customer payment (Non MOTO payments)

woven acorn
#

Do you need future usage actually? Are you planning to charge Customers multiple times?

tender ruin
#

Do i have to pass future usage for all three payment methods with either onSesion and offSession

tender ruin
woven acorn
#

But will they be typing the card every year? Or will you let them select the saved one?

tender ruin
#

yes we are typing their card. no card selection

woven acorn
#

Then no need to save the Payment Method

tender ruin
#

ok then how can i pass card details in create payment intent object?

woven acorn
#

You should not do this, unless your app is PCI-compliant.

#

You can use Payment Element to securely collect the payment method details on the frontend.

tender ruin
#

We are not storing any payment/card details into our system. we are just pass the card object to stripe API

tender ruin
sonic adderBOT
woven acorn
#

It's a Stripe provided UI kit that securely and compliantly collects payment method details.

tender ruin
#

ok so if i use this UI then directly paymet goes without card autenticity error?

#

what if i have to track payments or see payment records or refund payment, will all they work as it is?

woven acorn
#

This is just a basic way to accept payments with Stripe. If the customer pays, they might be prompted with 3DS authentication pop-up, the Payment Element will take care of it. If you use payment_method_options = { card: { moto: true } } and type the details yourself in it, it will be skipped.

tender ruin
#

ok perfect for to develop this page it will take some time to prepare and test in all cases

#

meanwhile how can i fix my current issue?

#

Your card was declined. This transaction requires authentication.
req_PBnusy9zwclu5m

woven acorn
#

I don't think this Payment Method can be used off-session now.

novel dust
#

👋 stepping in here

#

That PaymentMethod requires 3DS

#

It should be attached to a Customer via a SetupIntent

#

So 3DS can be completed

#

Or, you attach it during the payment flow

#

By passing setup_future_usage

tender ruin
#

this is my test connected account. acct_1Mri7PQoWw98s5ro
here i have filled all required details then why i am getting this error?
No such destination: 'acct_1Mri7PQoWw98s5ro'"

novel dust
#

Can you provide the request ID where you see that error?

tender ruin
#

i can't find any request ID in my logs

novel dust
#

Have you gotten approval for MOTO on your account?

#

If not, you need to reach out to our Support team to get approval

tender ruin
#

it is already enabled

#

i have taken many payments like pi_3NVu7MJkpaQoy0Za1rfjm2O3

tender ruin
novel dust
#

Can you give me the request ID where you see this error?

tender ruin
#

request id is not available that's what i am trying to say.

novel dust
#

That can't be true really.

#

Do you have multiple accounts?

#

It sounds like maybe you mixed up your keys or you are looking at the wrong Dashboard?

#

That would cause the "no such destination account"

#

And cause the param to be invalid if the other account isn't approved for MOTO

tender ruin
#

Sorry my bad. you are right. multiple accounts creating an issue

#

as of now i have set setup_future_usage and it seems working fine

#

tomorrow i will do some more testing

#

thank you for your help