#subin_error

1 messages · Page 1 of 1 (latest)

empty thicketBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always 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/1345975102080155710

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

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

icy fable
flat kernel
#

req_kbAvQVfjvquAEu

#

first mesage need to be deleted.
there is user datas.

#

i dont want those to be public.

icy fable
#

i have redacted the data in the first message

#

looking into the request now

#

You can't attach a payment method directly without using Setup Intent or Payment Intent for India issued card. From the request, I see that you're using a WooCommerce plugin. Are you the plugin developer or the merchant using the plugin?

empty thicketBOT
flat kernel
#

plugin developer

crude sable
#

It's a legacy integration. You would want to use PaymentIntent or SetupIntent, with the new PaymentElements instead

flat kernel
#

is this issue comes in payment or saving the card?

crude sable
#

Both. Payment should in PaymentIntent. Saving the card should use SetupIntent

flat kernel
#

yes iam doing like that.

#

$intent_args = [
'payment_method' => $token,
'customer' => $customer,
'confirm' => true,
'payment_method_types' => ['card'],
'usage' => 'off_session', // Required for saving cards in India
];

            $setup_intent = \Stripe\SetupIntent::create($intent_args);

using for saving card

#

i have a doubt above given error related to payment or saving the card?

is the payment get completed?
issue reported by client and the information from client side is limited.

#

can i able to test it test mode?
i cant able to this issue in test mode.

IS there is way to test the issue with out using live cards?
Such regulations is only for indian cards?
is there any other cards have such an issues?

crude sable
#

First you can only test in Test mode

#

And by SetupIntent, you want to create the SetupIntent first, then confirm it client-side. Not the way you are doing by passing the collected token to the SetupIntent

'payment_method' => $token,
flat kernel
#

currently iam creating payment int first after that i am crating the setup intent.
$token is the payment method in the payment intent.

i need to change the flow?
first create a setupintent to save card after that i need create the payment intent do i need to change like that?

#

iam currently doing it in the old flow. And i faced issue with card issued in india.

#

I tested it with card issued by india in test mode and the issue not replicated.

crude sable
#

That doesn't sound right. If you create a PaymentIntent first, you can use setup_future_usage to save the collected PM to the customer

flat kernel
#

if so there is no need to create a setup intent if i use setup_future_usage to save the collected PM to the customer in payment intent in the firstpalce?

crude sable
#

Yes