harshitbhargava | Stripe Developers | Page 1

frozen jacinthBOT May 26, 2023, 8:50 AM

#

peak jolt May 26, 2023, 8:50 AM

#

What's the error?

#

And can you share the pi_xxx ID?

pliant parrot May 26, 2023, 8:50 AM

#

Can you please check this RequestId: req_axAqTDYYhH5ex5

peak jolt May 26, 2023, 9:01 AM

#

Checking now

#

The error explains the issue:

mandate_data is not allowed because this payment intent already has a reusable Cash App Pay payment method attached to it.
You ned to remove the payment_method param from your confirmCashappPayment call as the Payment Intent already has a PM assigned

pliant parrot May 26, 2023, 9:06 AM

#

We haven't add this paymentmethod in payment intent, how it comes?

#

It automatically picks cashapp payment method id from customers account?

peak jolt May 26, 2023, 9:09 AM

#

Bear with me

#

I think it's because you passed setup_future_usage here when you created the PI: https://dashboard.stripe.com/test/logs/req_Ef7SNqTcinL4DU

But then you're trying to confirm the payment with an existing CashApp payment method that was already setup

Stripe Login | Sign in to the Stripe Dashboard

Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.

#

If you're confirming the PI with a previously setup Payment Method, then omit the setup_future_usage param

frozen jacinthBOT May 26, 2023, 9:13 AM

#

pliant parrot May 26, 2023, 9:26 AM

#

we are not sending setup_future_usage

#

Suppose we have multiple cash app, then how we are going to decide which cash app we are going to use?
As you suggest to remove payment id

#

For this we need unique identifier

zinc wave May 26, 2023, 9:27 AM

#

Hi! I'm taking over this thread.

#

we are not sending setup_future_usage
In this request you did set setup_future_usage: https://dashboard.stripe.com/test/logs/req_Ef7SNqTcinL4DU

pliant parrot May 26, 2023, 9:28 AM

#

No, I dont know from where it is coming

#

await stripe.confirmCashappPayment(props.clientSecret, {

  payment_method: props.paymentId,

  return_url: <any>

});

#

This is my code

zinc wave May 26, 2023, 9:33 AM

#

yonnoj already explained what you need to change:

You ned to remove the payment_method param from your confirmCashappPayment call as the Payment Intent already has a PM assigned

pliant parrot May 26, 2023, 9:36 AM

#

If you're confirming the PI with a previously setup Payment Method, then omit the setup_future_usage param

In this how we can omit setup future usage

zinc wave May 26, 2023, 9:37 AM

#

I don't understand your question. Have you tried the suggestion above?

remove the payment_method param from your confirmCashappPayment call

pliant parrot May 26, 2023, 9:38 AM

#

yes, then it is saying setupFuture usage is required,

Then I try to send like this
payment_methods: {
type:"cah_app"
}
the the payment is success, but it is taking random PM id from available cashapp payment method

#

I have multiple cash app payment method

zinc wave May 26, 2023, 9:41 AM

#

Can you share request ID of your new tests?

pliant parrot May 26, 2023, 9:45 AM

#

Sorry I lost that requestId,

#

But there is new issue . iw ill explain you

#

In my account, I have multiple cashApp Payment id. Now I am doing payment with one of the payment id
and my code looks like this:

await stripe.confirmCashappPayment(props.clientSecret, {

 payment_method: {

type:"cash_app"
},

  return_url: <any>

});

So it is taking any random paymentId from available payment id of cash app . and make the payment successfull, it is not taking selected payment id

#

How I can resolve that?

zinc wave May 26, 2023, 9:49 AM

#

Can you share a PaymentIntent ID or request ID where you saw this?

pliant parrot May 26, 2023, 9:49 AM

#

yes sure

#

pi_3NBwntInbsls4Aao2IULpU8C

#

In the above PI, I initiated the payment through "pm_1NBwhXInbsls4AaoUu74REMl", but in response the pM id is different

zinc wave May 26, 2023, 9:56 AM

#

As mentioned before, can you try to:

Remove setup_future_usage when you create the PaymentIntent
And also add back payment_method: props.paymentId when confirming the PaymentIntent

#harshitbhargava