#lutthein_unexpected

1 messages · Page 1 of 1 (latest)

crystal turtleBOT
#

👋 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/1433860087516238007

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

lucid sable
#

👋 taking a look

#

This is happening with the card inserted? Not tap to pay?

#

It sounds like it fromthe description just want to be certain.

stiff totem
#

Yes this is happening with card inserted, Tap to Pay would not work at all with Interact

#

And yes, thats the flow we are currently using in our app+api
All the setup intent logic lives in the API side

lucid sable
#

is this happening on multiple cards or just one?

#

do you have the id of the setup intent I could look at?

stiff totem
#

this one I believe is the failed one
seti_1SOLq7Bb49XQ2DGyTx4FbpzC

lucid sable
#

have you encountered this with more than one Interact cobranded card?

stiff totem
#

yes, all we have tried have the same behavior

#

Most of them are Scotiabank Visa Interact debit cards

crystal turtleBOT
ebon falcon
#

👋 Taking over this thread, catching up now

#

Thanks for waiting! Interact should be supported on the Stripe terminal integration. The issue is unlikely due to the integration issue if non-Interact cards can be made successfully. If this authentication error was mainly thrown from Scotiabank specifically, I'd recommend asking the card holder to check with the bank the why they declined the payment.

#

If the declines happen for all Interac cards, i.e. no successful setup at all and not limited to Scotiabank, can I suggest you writing to Support https://support.stripe.com/contact, so that they can check with relevant team what could the reason be?

stiff totem
#

It doesnt have to do with the fact that we are creating the setup intent as card_present instead of interact_present

#

Just wondering

ebon falcon
#

That's a very good point! Let me double check!

#

Have you had any successful Interac transactions at all?

#

So yes, you're right! interac_present should be included during Setup Intent creation

stiff totem
#

That seems to be for payment intents, not setup intents, thats why I was wondering.

ebon falcon
#

Setup Intent works the same way as the Payment Intent

#

So this will apply to Setup Intent as well

stiff totem
# 
    return this.stripe.setupIntents.create({
      payment_method_types: ['card', 'card_present'],
      use_stripe_sdk: true,
    });
  }```
#

like, should I add interact_present in the payment methods types?

ebon falcon
#

Yes, that's right!

stiff totem
#

we had it there but removed it when we went from payment intent to setup intent

#

Just wondering, would there be any implications of using this for non interact cards? or is there any concern regarding refunds for these kind of cards? Can we pre auth interact cards like we do with all other cards?

ebon falcon
#

Interac cards don't support separate auth and capture since Interac only supports single message behavior (auth and capture at the same time)

#

For Setup Intent, it shouldn't matter since no actual amount is included. For the Payment Intent with a charge amount, manual capture flow can't be supported since Interac only supports automatic capture

stiff totem
#

What about refunds? can we refund a captured transaction from an interact card from the stripe dashboard?

upper cobalt
#

Hi, jumping in here as @stiff totem 's coworker who is following along.

Interac cards don't support separate auth and capture
Regarding this comment, is this a distinct flow from "setting up future use"?

ebon falcon
#

https://docs.stripe.com/terminal/payments/regional?integration-country=CA#refund-an-interac-payment:

In-person refunds are mandatory for Interac transactions in Canada. You can’t create refunds in the API or in the Dashboard for these payments. In this flow, the reader prompts the cardholder to present the card used in the original charge. After the card details are read successfully, your application processes the refund. Like online refunds, you can perform partial refunds by passing in an amount less than the transaction value.

Regional considerations

Learn about regional considerations for integrating Terminal in different countries.

#

Regarding this comment, is this a distinct flow from "setting up future use"?
Auth and capture means that the payment method is pre-auth first with an amount first, then capture later. This is used in Payment Intent flow. Set up for future usage is a different flow which doesn't include any charge amount.

#

So yes, they are different flows

stiff totem
#

Ok, I just reviewed our implementation and we are currently creating the setup intent client side

As soon as I add the payment method types prop to it

    paymentMethodTypes: ["card", "interac_present"],
  });```

It starts giving me this error message

The PaymentMethod provided (card_present) is not allowed for this SetupIntent. Please attach a PaymentMethod of one of the following types: card. Alternatively update the allowed payment_method_types for this SetupIntent to include "card_present".
crystal turtleBOT
ebon falcon
stiff totem
#

seti_1SONGwBb49XQ2DGyZMShfX20 is the setup intent id, I dont see any req_xxx

#

req_VapC72x06v2Nme?t=1761936126 I think I found it

iron stone
#

That's why you're getting the above error

#

You need to pass a list of ["card", "card_present", "interac_present"]

#

If you want to accept both card_present and interac payments as well

stiff totem
#

That was my first attempt, but it was giving me the same error,

    paymentMethodTypes: ["card_present", "interac_present", "card"],
  });```

This is prompting the same error, is there anything we need to setup in our stripe dashboard account for this to work? seems like this configuration for "card" only like you mention might be coming from somewhere else.
iron stone
#

That was my first attempt, but it was giving me the same error,
Please share the request id so I can see what's wrong

#

seems like this configuration for "card" only like you mention might be coming from somewhere else.
It's not. It's passed in the code

stiff totem
#

sounds good, one sec Im creating one with all 3 method types

#

req_8Lb8AoP6xCkmHV

iron stone
#

That one only has card as well