Hendie

[winter patrol]

Hello 👋
I believe the API is throwing the error because interac_persent doesn't support setting up for future usage

The API at the moment relies on the information passed in with the request rather than omit the parameter own our end.

As a workaround (don't know if it fits your usecase), you could ask you customers if they're going to be paying using an interac payment method, if so create the PaymentIntent that doesn't have setup_future_usage: true

[wise ridge]

That's the thing, I know from experience that many merchants where I shop never ask me what I want to pay with. That would be an extra step that we feel will negatively impact the user experience.

[winter patrol]

I see. Unfortunately, that's the only workaround at the moment that I know of.
You can log a feature request by writing into our support ([e-mail]).

I def understand the user experience piece of it.

[wise ridge]

thanks @winter patrol appreciate the feedback. I will follow up with support.

[winter patrol]

NP! 🙂 Good luck