#hendie_eftops-not-accepted
1 messages ยท Page 1 of 1 (latest)
๐ Welcome to your new thread!
โฒ๏ธ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
โฑ๏ธ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
๐ This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1266469747814567958
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- hendie_hendie-eftpos-error, 20 minutes ago, 6 messages
- hendie_api, 1 hour ago, 5 messages
- hendie_unexpected, 2 days ago, 6 messages
We don't even get to confirm the transaction, the terminal tells us "Not Accepted, try another card" Subsequent comms with the terminal would be via Stripe.js
I cannot find clear documentation on your website, but found this on a 3rd party website commenting on Stripe services: In Australia, the card terminals only accept Visa, Mastercard, American Express, Apple Pay and Google Pay in AUD currency only. eftpos acceptance and least-cost routing are coming soon. Until then, only eftpos cards co-branded with Visa or Mastercard can be accepted (over the Visa/Mastercard network)
Hi ๐ looking at the intent that you shared, I'm only seeing the request to create it. Can you tell me more about where in your flow you're seeing the "not accepted" error/message being surfaced?
we are using your Stripe.js SDK to talk to the terminal. The creation of the PI you're seeing is to get the client_secret to further talk to the terminal via the SDK. So we're not even getting to a point where further comms with your backend is required. The SDK is called to arm the terminal and ask for a swipe. It's when we swipe the Stripe-supplied eftpos test card that we get the error I mentioned. My question is what flags or parameters we need to provide when creating the PI to enable us to use an eftpos card.
Gotcha, so this isn't a server-driven integration, and it sounds like the message is being encountered during the flow triggered when you call collectPaymentMethod.
What reader are you using for your terminal flow?
WisePOSE
Alright, that reader should support them, so that's likely not the concern here:
https://docs.stripe.com/terminal/payments/collect-card-payment/supported-card-brands#in-person-brand-capabilities:~:text=All-,eftpos,-Australia
hmm, so why do we get "Not Accepted, try another card"?
I don't know, I'm still looking. Are you seeing any more information in the logs from interacting with our JS SDK?
What is the ID of the reader object you're using?
I'll have to look it up, hang on ...
Also, are you running into this behavior for all of your test Connected Accounts? There are some MCC restrictions for accepting eftops cards that could be involved here:
https://docs.stripe.com/payments/eftpos-australia#availability
So far I'm not seeing an MCC on the involved accounts that could prevent this from being supported, but am curious if there are accounts not encountering this that we could compare to the failed the attempts.
tmr_FpzuqQlgxt3GbL
finding out if it was on more than one account, we did encounter it on acct_1OjtBpQnKhsI877Z
Ah, I think it's the capture method you're using.
You're using manual currently, which isn't supported by eftops:
https://docs.stripe.com/terminal/payments/regional?integration-country=AU#:~:text=a separate request.-,manual,-Set
I believe if you change to automatic or manual_preferred, those may progress, but please let me know if that doesn't change the behavior you're seeing.
so of course when we set up that payment intent we do not know whether an eftpos card will be swiped, and we prefer manual for credit cards. I assume manual_preferred will still do manual for regular credit cards?
Yup, this is the excerpt from the table in the doc that I linked to for the manual_preferred row:
eftpos card payments will be authorized and captured in a single step.
Non-eftpos card payments will be authorized only. To capture the funds, make a separate request.
Any time! Let me know if that doesn't do the trick and I'll be happy to take another look.
can I get a hold of you again if I need to follow up?
(easier than to explain everything again to someone new)
I'll keep this thread open while I'm around, but I'm only around for another hour or so today.
ok, let's see how it goes