#shahid

1 messages ยท Page 1 of 1 (latest)

unkempt apexBOT
raven bolt
#

Hi there

#

So you are trying to authorize cards by using manual capture and then canceling immediately? Is that correct?

bleak relic
#

yes I do

#

But when I do that, user get notification of payment Deduction.

#

That I do not do, we aren't deducting any payment.

#

Now you get my point ?

#

is there any alternative to verify user's card with payment Method ID?

raven bolt
#

So yeah this is really not a recommended way of validating paynent methods. You are creating a real authorization without any intent of charging which is against card network regulations.

#

There is no way to prevent the notification as it is a real authorization for the amount you are "charging" on their card and then won't get released for several days.

#

The correct method is to use SetupIntents like you are already doing.

#

Then if the actual payment fails later on then you need to bring the customer back on-session and collect a different payment method

bleak relic
#

Can you explain setupIntent ? I have implemented setup intent:

                    await stripe.paymentMethods.attach(paymentMethod.id, {
                        customer: customer_id,
                    });
                    const setupIntent = await stripe.setupIntents.create({
                         customer: customer_id, // Replace with the actual customer ID
                         usage: 'off_session',
                         confirm:true,
                        payment_method:pm
                         });
#

but it allows some card that are expired, or that were only valid cards for lets say 200USD usage.

bleak relic
raven bolt
#

So a SetupIntent triggers a card validation with the issuer for that card to be charged in the future. It is up to them to tell us whether that validation will be approved or not. That said, this initial card validation doesn't make any guarantee that a future charge against that card will be successful. The future charge will trigger an authorization with the issuer where they once again will decide on whether to approve/decline.

You are doing everything correctly right now. The reality is that you can't guarantee that future charges will be approved. However, by using a SetupIntent you are ensuring that a better rate will be approved than if you were not using a SetupIntent.

bleak relic
#

Thank you for your answer dear, So there is nothing we can do otherthan setupIntent ?

raven bolt
#

Correct. You already are doing the right process.

bleak relic
#

Thanks for telling me sir.

raven bolt
#

Happy to help

bleak relic
#

Can i get a moment from you?

#

I have seen jasper.ai, they are don't know doing what, our wrong cards were captured with their method.

raven bolt
bleak relic
#

They are also using stripe, is there any other way to get payment information i.e., card information, cvc etc? So that we can use third party service to verify the cards?

raven bolt
#

We don't recommend handling this data yourself as it requires a high PCI burden to have it on your server.

#

But if you want to undergo that PCI burden then you could reach out to our Support team to enable you to handle passing raw PANs to our API for your account.

bleak relic
#

we are having too many issues due to this ๐Ÿ˜ฆ

bleak relic
raven bolt
#

๐Ÿ‘

bleak relic
#

Thank you sir