#alex-terminal

1 messages · Page 1 of 1 (latest)

oak stone
#

hi, what's the question?

bronze wave
#

ok, first one, regarding bank transfers, is there any failure reason or timeout that we can get as result once we have initiated the payment intent and receive the next_action[display_bank_transfer_instructions] ?

oak stone
#

that has nothing to do with ipv6 😅

#

or Terminal

bronze wave
#

that's why I said I have some questions

#

some are regarding bank transfers

#

other are regarding Stripe Terminal

oak stone
#

ok let me reset my brain a bit then

#

which bank transfer exactly? we support multiple payment methods there, which one are you asking about?

bronze wave
#

I'm asking about SEPA transfers, I know this is in beta, which we are a part of

oak stone
#

I'm not immediately familiar with next_action[display_bank_transfer_instructions] or which integration that is, it would help to link the docs you're reading so we're on the same page

#

ah I know nothing about SEPA CT, as you say its' a very limited beta

bronze wave
#

however I'm not asking about specifics about SEPA

#

I'm asking in general about bank transfers, ok we can get success if it is paid with the exact amount

#

and we also have use cases and webhooks for overpaid and underpaid transfers

oak stone
#

as far as I know at least there's no timeout

bronze wave
#

but is there any possible curse of action for a failure or timeout?

oak stone
#

the PaymentIntent just stays in requires_action forever if the customer never pushes the funds

bronze wave
#

ok I see

#

so it either requires_action, or it succeeds

#

right?

oak stone
#

not sure really

#

I assume it works that way based on my knowledge of how Stripe works in general, but I don't know about this beta SEPA CT integration on PaymentIntents, you should ask our support team who can ask the product team running the beta, my team only really has knowledge of public features of the API

bronze wave
#

ok I see, will do

#

now speaking about the Terminal 🙂

#

next question

#

some months back I asked if you had any issues with IPv6 and you said no, no problem

#

but the fact is that a lot of our customers are in France and using Free ISP, that works nearly entirely with IPv6

#

and now we have a user report this:

#

so now the readers clearly state that ipv6 addresses are not supported

#

keep in mind this is auto config coming from DHCP from the router

#

some months back, when we first received a report of these problems thiis error was not there:

#

So my question again: do you have some incompatibility with IPv6 and smart readers connected through Internet (using js SDK)?

#

what should we tell our users to do?

oak stone
#

yep we don't support IPv6 on a LAN for the reader unfortunately

#

we got clarification on that and updated the firmware to call it out more explicitly based on feedback(quite possible it was you)

bronze wave
#

So, are you telling me that you don't support Terminals for the second largest ISP in France? Really? https://en.wikipedia.org/wiki/Free_(ISP)

Free (ISP)

Free is a French telecommunications company, subsidiary of Iliad that provides voice, video, data, and Internet telecommunications to consumers in France. Its head office is in the 8th arrondissement of Paris and it is the second-largest ISP in France.
Free provides ISP services in France and in the 30 OECD countries. It was the first company to...

oak stone
#

well it's more about the settings on the LAN

#

but yes I suppose some ISPs give routers that assign ipv6 addresses to devices on the LAN and that could be a problem!

bronze wave
#

exactly that is the case

oak stone
bronze wave
#

ok thanks, this is now crearer for me, however I'm still not sure I understand, as the reader has a local IPv4 address (the address with IPv6 is the one of the router), and as long as we instruct our customers to change their DNSs on their POS (the computer where they use running our web, that connects to the reader) so that they can resolve and reach that IP, it should be enough right?

#

or am I missing something?

oak stone
#

as the reader has a local IPv4 address
it should work then

bronze wave
#

so even if it shows the error?

#

ok I'll raise a ticket for support because I really think you should give better out of the box support to a major ISP in France for Terminal, this is no isolated report, we are receiving quite a lot of complains and it will probably only get worse as we deploy more and more readers

#

ok thanks that's all for today

#

thanks for help and clarifications 🙂