#hamid-card

1 messages · Page 1 of 1 (latest)

torn plaza
#

Hi! What exactly is your question?

wary ledge
#

okie, so I added a card in stripe checkout page

#

its authorized against the customer

#

i got autorization code, which i used later to charge

#

that customer

#

its in live/production mode

#

the problem is

#

next time when i tried again it does fail on wrong cc number but doesn’t fail on wrong security code or expiry date

torn plaza
#

If you are doing tests with cards payment, then you must use test mode. Otherwise you might get errors.
And if this is a real customer issue, then you need to contact Stripe support directly here: https://support.stripe.com/?contact=true

wary ledge
#

this is happening in live mode

#

I specifically said, this is happening with live key in production mode

torn plaza
#

Exactly, if you are doing tests you shouldn't be using live mode.

wary ledge
#

so its strange

#

its not lie

#

mode is live

#

giving real credit cards

#

so

#

it does fail on wrong cc number but doesn’t fail on wrong security code or expiry date

#

it authorize it

torn plaza
#

hamid-card

#

Are you doing this to check that you Stripe integration is working, or is this an issue that one of your customer is having?

wary ledge
#

we are have this behaviour

#

in live mode

#

we have tried our real card

#

I am developer for a project and owner did that

torn plaza
#

Exactly, so you are doing some tests in live mode. You should not do this, because Stripe might block some of your payments.

#

Instead, if you want to test you payment flow, use test mode.

wary ledge
#

this is third time bro :), we are using live cards in live modes as per our business flow

#

so when we add wrong card on stripe checkout page, it gives errors and do not approves it

#

but if we give wrong date or code, it do not give error and approves/authorize it

torn plaza
#

I think we have some difficulties to understand each other. Let me try again 😅

#

we are using live cards in live modes as per our business flow
You should NOT use live cards with live mode in order to test your payment flow.
To test your payment flow, use test cards in test mode.

wary ledge
#

oh my GOD, we are not testing, we are provding live cards

#

but entering wrong date or code

#

it should not authorize card

#

no?

#

so we are charging cards/real cards

#

and it happened mistakenly but it approved the card

#

then we intentionally added wrong date and wrong code and it aslo approved

#

approve/authorized

patent gulch
#

can you give an example? Like a PaymentIntent/SetupIntent you're using?

#

anyway, no point saying more unless you have an example to share, so I'll wait for that!

wary ledge
#

we did that yesterday

#

let me find if we have something solid

patent gulch
#

you haven't posted in this channel since Jan 22 and I don't see you asking about this before.

wary ledge
#

no no, I am saying, We experienced this behaviour yesterday

#

let me find something

patent gulch
#

cool

wary ledge
#

not finding any, so i think your above link is quite explainatory

#

so basically it authorizes quickly, but triple check while charging?

patent gulch
#

yes. I'd assume it's my link indeed

#

we don't always check the card details upfront because it's unnecessary to contact the bank until you actually charge them

wary ledge
#

yea that's the answer i was looking for 😉

#

thanks

patent gulch
#

especially we might skip the checks and contacting the bank, if it looks like potential fraud or card-testing (and you testing your own live cards is more likely to look that way, which again is why you're not supposed to test in live mode)

wary ledge
#

perfect, thanks. 🙂

#

so it could be authorized but can't be charged?

#

so even if date or csv is wrong, it will be tested again while charging?

#

as its approved/authorized in the first step, so basically that authorization is partial, not 100%

#

100% will be done while charging.

patent gulch
#

it's up to the bank what happens when the charge is actually made, but what you say is accurate enough.

#

anyway, please direct follow ups to our support team, these are not API/coding questions.