#sambindoff

1 messages · Page 1 of 1 (latest)

arctic siloBOT
fast ore
#

Hi! Let me help you with this.

azure phoenix
#

Hey Vanya, thanks very much for your time

fast ore
azure phoenix
#

Sure, for the first error:

The parameter `moto` cannot be passed as part of `payment_method_options` unless the SetupIntent is being confirmed.

Request - req_ukTZ8VRDrLFYYZ

fast ore
#

Can you try this, or without payment_method_options at all:

const setupResponse = await this.stripe.confirmSetup({
    elements,
    confirmParams: {
        payment_method_data: { payment_method_options: { card: { moto: true } } },
    },
    redirect: 'if_required',
});
azure phoenix
#

For the second:

You cannot confirm this SetupIntent because it's missing a payment method. Update the SetupIntent with a payment method and then confirm it again.

Request - req_rYbys5bDAJTtWm

#

Let me give your suggestion a try

#

I'm now seeing:

Received unknown parameter: payment_method_data[payment_method_options]
#

Request - req_YbjQ1FdGk8iU9o

fast ore
#

Thanks for the details!
I haven't seen moto being used for SetupIntents, so please give me some time to investigate.

azure phoenix
#

No worries, thanks Vanya

late granite
#

Now that is more difficult with the Payment Element as there's no direct createPaymentMethod available

#

That will give you a pm_xxx you can use when you create the SI, and pass the MOTO params

#

A few things to glue together there, but it should work

#

MOTO is weird because it's a rare instance where you're obviously keying in card details for the user, but still want to use our payment UIs for PCI compliance

azure phoenix
#

That's great, just hopped on another call so will give all this a go shortly, thanks a million ynnoi and vanya, will feed back any issues