#gary4091-future-payments

1 messages ยท Page 1 of 1 (latest)

keen token
#

No, thats included when setting up the card initially, but not on future payments

fluid latch
keen token
#

It's used when authenticating the card up front

fluid latch
#

So STRIPE has ability to authenticate CVC without contacting issuing bank?

#

In other words, without making actual charge or authorization?

keen token
#

What do you mean? Authentication does involve the bank.

fluid latch
#

Understood. I didn't know that Bank can Authenticate the card without receiving the actual charge or authorization on that card

keen token
#

There is an authorization with the bank in that flow

fluid latch
#

We were processing cards in-house for long time and the only way to Authenticate the card for us was to submit a charge on this card ($0.01)

#

So STRIPE has probably a special ability to Authenticate the card without making a charge

#

Thank you very much for clarification!

#

Can I ask you one more question?

keen token
#

Sure!

fluid latch
#

You said that CVC collected during SetupIntent will not be used when charging card later using PaymentIntent. Did I understand your correctly?

keen token
#

Yes, correct

fluid latch
#

So, anytime we confirm card payment with PaymentIntent for the card that was saver earlier (via SetupIntent), Stripe SEND credit card charge request to bank with BLANK CVC?

keen token
fluid latch
#

In this case, does the bank may reject the payment when CVC is not sent?

#

In other words, if we don't re-collect CVC, will it mean that we have more rejected by bank charge? The reason I am asking is that:

#

I never enter CVC in my amazon account

#

only when card for set

keen token
#

It's possible - issuers can reject for any reason they like really

#

I can tell you how to recollect CVC in the SDk or check if it was checked, but can't really speak to optimization like that

fluid latch
#

Amazon does not re-collect CVC, ebay does not recollect CVC

#

Understood!

#

Thank you so much for your help!

#

Sorry, you mentioned that you can help with re-collecting CVC

#

We have the following problem:

#

We are integrating STRIPE in the existing web checkout on our site

#

We save cards for future use and then customer can use saved card to checkout

#

On our current checkout CVC recollection is on one page (Payment Page), and order confirmation is on the next Page (Confirm Order Page)

#

Is it possible to recollect CVC value using Stripe ELEMENT on one page (Payment page), and confirm payment on the other page (Confirm Order page)?

visual venture
#

catching up here one sec

fluid latch
#

When we Create Payment with Recollected CVC token

#

When we call CreatePaymentIntent with recollected CVC token without setting Confirm to TRUE we get an error "The parameter payment_method_options[card][cvc_token] cannot be used when creating a PaymentIntent unless confirm is set to true."

#

However, we can't set Confirm to TRUE on this page because customer confirms the order on the NEXT page

#

sure

visual venture
#

let me try something quickly

fluid latch
#

thank you

fluid latch
#

Just checking ๐Ÿ™‚

fluid latch
#

When we call CreatePaymentIntent with recollected CVC token without setting Confirm to TRUE we get an error "The parameter payment_method_options[card][cvc_token] cannot be used when creating a PaymentIntent unless confirm is set to true."
However, we can't set Confirm to TRUE on this page because customer confirms the order on the NEXT page

#

Is there a way to recollect CVC using STRIPE element on one page and CONFIRM payment intent on the other page?

alpine sparrow
#

in theory, you collect the CVC on the page where the customer confirms/pay

#

if you want to collect it upfront, you have to store this id somewhere on your end and re-use it on the confirm at the next page

fluid latch
#

We can't store CVC when collecting using ELEMENT

#

Also, PCI Complience does not allow to store CVC

alpine sparrow
#

you can store the cvc token

fluid latch
#

Yes

#

We do

alpine sparrow
#

1/ Create the CVC token
2/ Store that token for a few sec in the next page
3/ pass that CVC token at the confirmation step

fluid latch
#

Let me see

#

step 3) Will not work, because Stripe.JS stripe.confirmCardPayment accepts only card.cvc Element as parameter for payment_method_options and returns an error if we try to pass cvc Token as a value for cvc

alpine sparrow
#

let me look

#

Damn you're right this won't work unfortunately. You either have to keep this on the same screen or you'll have to go back to your server to confirm first and then back client-side in case of failures

fluid latch
#

Understood. Thank you very much!

alpine sparrow
#

Sure thing, sorry for the trouble, it's definitely more work in a case like yours ๐Ÿ˜ฆ