#lutthein_interac-payment-scenarios
glacial urchinBOT
👋 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/1343615495739281499
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
gentle isleBOT
turbid flare
Hi there 👋 is this a Terminal integration, or an integration for accepting payments online?
I'm asking because you mentioned Terminal, but the Setup Intent you shared is accepting payment_method_types of card, which is for online payments, rather than card_present.
mortal storm
Hi Toby, I'm working with @scarlet heron on this integration. This is a hybrid integration in that we are gathering a payment method with Terminal, but we are conditionally charging off-session at a later date. We are following the guide for saving cards directly without charging: https://docs.stripe.com/terminal/features/saving-cards/save-cards-directly?terminal-sdk-platform=react-native
turbid flare
Gotcha. Is the card you're using for testing a co-branded Interac card, which should be supported, or a single-branded one that isn't supported by this flow?
https://docs.stripe.com/terminal/features/saving-cards/save-cards-directly?terminal-sdk-platform=react-native#:~:text=You can use SetupIntents to collect card details on Visa%2C Mastercard%2C American Express%2C Discover%2C co-branded Interac%2C and co-branded eftpos cards. Single-branded Interac cards and single-branded eftpos cards aren’t supported.
scarlet heron
It is a co-branded visa+interact card.
turbid flare
Hm, can you share the ID of the request that encountered an error?
mortal storm
we're going to generate a new test to get some up to date IDs for you, one second
Also, noting that we are currently testing in test mode but with a live/real card, is that compatible?
turbid flare
No. The flow should detect that you aren't using a testcard, and should fail the payment because you can't use real cards in testmode.
mortal storm
OK that makes sense
turbid flare
Interac test cards can be ordered from our terminal shop:
https://docs.stripe.com/terminal/references/testing#interac-test-card
Or you can try to use a simulated one with a simulated reader:
https://docs.stripe.com/terminal/references/testing#standard-test-cards
scarlet heron
Here is the setupIntentID I created in test mode
seti_1Qw4XsBb49XQ2DGyjy3jQRSx
Here is the error message in the screen
mortal storm
No. The flow should detect that you aren't using a testcard, and should fail the...
Is that specific to interac? According to @scarlet heron, he is able to use a real credit card with tap to pay to attach the payment method to a setup intent.
^ OK apologies, update, apparently using a real card is not actually finishing the workflow
scarlet heron
Yeah, using a real card created the following event of SetupIntent.failed
evt_1Qw4apBb49XQ2DGyd2Fjly6v
But yeah, anyway, we were wondering if there are any other configurations we require to be able to accept co-branded cards in our workflow.
turbid flare
Not that I'm aware of
mortal storm
ok, so basically our tests failed because we are using an actual Interac card, in order to test in test mode, we need to order an Interac test card from Stripe, or run a test in production.
Co-branded interac cards, for the purpose of attaching a payment method to a setup intent, will behave like any another credit card. Single branded Interac cards will fail to attach to the setup intent because the Interac system cannot be used to save to charge later.
glacial urchinBOT
mortal storm
A question that arises from this is we also have a workflow that uses Stripe Elements to collect a payment method and attach it to a customer. Should we expect single-branded Interac to work in that scenario?
paper pagoda
Hi 👋
I'm stepping in as my colleague needs to go soon.
When you say "single-branded Interac" cards, you mean they are not co-branded to operate over other debit/credit rails e.g. Visa/Mastercard, correct?
mortal storm
yes
paper pagoda
I think we only support interac_present (meaning Terminal)
Otherwise, the only Canadian debit cards we process are PADs through ACSS
https://docs.stripe.com/payments/acss-debit
mortal storm
interac_present being "charge on card tap" and no option to save for later, correct?
paper pagoda
interac_present is the payment method assigned when a customer pays using Stripe terminal with an Interac card. It means that card is physically present at the time of the transaction.
Our doc for saving cards with Terminal doesn't explicitly call out whether or not this is supported with Interac
mortal storm
Right, what we are seeing is that for that workflow only co-branded Interac will successfully setup for future use.
My question is, for instances when a user shows up with a single branded interac card, do we have a way to support that user? We have a workflow built using Stripe Elements for such cases (more of an app signup workflow), and I'm trying to assess if we can rely on that workflow to support single branded Interac card holders.
paper pagoda
My question is, for instances when a user shows up with a single branded interac card, do we have a way to support that user?
Based on our public docs, I think this is only supportable with Stripe Terminal (physical card readers).
mortal storm
OK, but in that case, only for payments right, not for setup for future use?
paper pagoda
Correct
mortal storm
ok, thanks, that clarifies, we'll take it from here!
paper pagoda
Happy to shed what 💡 I can 🙂