#conor-terminal-issue

1 messages · Page 1 of 1 (latest)

dapper summitBOT
hollow atlas
#

What issue are you facing exactly?

muted tundra
#

When I call stripe.terminal.readers.processPaymentIntent
it sends to the reader correctly however everytime I tap the physical test card to pay it fails. It doesnt give me a reason and it doesnt send a webhook

hollow atlas
#

What does the reader show when it fails?

muted tundra
#

Card Declined
Try a different payment method

hollow atlas
#

Can you share the reader serial number?

muted tundra
#

serial_number: WSC513142091435

#

Did you see the video i send? That's all that happens and I dont know how to debug that

hollow atlas
#

I see it

#

Looking into it

muted tundra
#

Great thanks

daring seal
#

Hello 👋
Can you share the PaymentIntent ID you're working with as well?

muted tundra
#

pi_3NbU4jCid27yITco01MT5FbT

daring seal
#

Interesting, I am not seeing a decline coming from the API

Can you try tapping a diff card and see if the SDK behaves any differently?
I wonder if its a buggy test card

muted tundra
#

You mean a real credit card?

daring seal
#

yes, since you're using a test mode payment intent the SDK should return an error

muted tundra
#

ok

daring seal
#

Also, if you have a diff test card by any chance then try tapping that one too

muted tundra
#

I tapped my real visa. I also have an interac test card and tapped it too

#

Got same error as before

daring seal
#

Does it only decline on tap or does the insert decline too?

#

What account is the reader registered to?
It seems like you're trying to create a direct charge w/ an express account

muted tundra
muted tundra
#

Yes its an express account

#

that must be the problem?

daring seal
#

I am not sure, as express accounts can technically do direct charges.

Do you mind running a quick test by:
1/ Registering the reader on the platform account
2/ Try and process the payment as the platform (without stripe-account header)

muted tundra
#

Ok

daring seal
#

This would help make sure the reader isn't buggy

muted tundra
#

Also, I think i've been doing direct charges on my express accounts for online payments

daring seal
muted tundra
daring seal
#

Gotcha. How exactly are you connecting to the express account?

#

Are you using Oauth or just connect onboarding?

muted tundra
#

connect onboarding

daring seal
#

Were you connected in test mode or live mode? OR both?

muted tundra
#

I dont understand the question

daring seal
#

Like when you created the account link for onboarding, was it in test mode?

muted tundra
#

I think so, but not 100% sure

daring seal
#

Have you rolled your API keys recently by any chance?

muted tundra
#

Yes I think a few months ago

daring seal
#

Gotcha. Can you try passing in a diff connected account in the stripe-account header?
I suspect this has something to do with connected account only being "connected" to the platform in live mode.

#

You'd likely need to register the reader to the same account

muted tundra
#

I used a different connected account that I could see in test mode in the stripe dashboard acct_1MxDSECa6bIX3BuX

daring seal
#

perfect

muted tundra
#

Ok thank you very much

#

I will just stop using that other connected account for testing anymore

daring seal
#

👍 Will also recommend reading the support article I attached above regarding Direct charges with Express accounts.

muted tundra
#

Yes will do

#

thanks

daring seal
#

NP! 🙂 Happy to help

dapper summitBOT