Problem with Blik payments on Adyen, no IPv6 support?

[remcotolsma]

Hi there, we have set up Adyen on our Gravity Forms and it works perfectly with card payments, but our Blik payments keep failing. We have the following error:

Adyen has sent us the following but I dunno what is causing it as we're using your plugin:

We just saw that you're receiving "ER_TX_NOTFOUND" as an acquirer response to your BLIK transactions (i.e. 1829454437223636).

This is most likely since BLIK's system currently only supports a maximum of 25 characters in their IP address parameter.

We would therefore recommend using IPv4 formatting. Hope this helps!

What do we need to sort on the plugin to get this working?

Internal HelpScout ticket: https://secure.helpscout.net/conversation/1797287842/23584/

It seems that Adyen has no restrictions on the shopperIP parameter:
https://docs.adyen.com/api-explorer/#/CheckoutService/v68/post/payments__reqParam_shopperIP

The shopper's IP address. In general, we recommend that you provide this data, as it is used in a number of risk checks (for instance, number of payment attempts or location-based checks).

If Blik doesn't allow IPv6 Adyen should fix their integration with Blik?

5c2e8f4

[remcotolsma]

I just submitted a request to Adyen via https://www.adyen.help/hc/en-us/requests/new:

Hello Adyen,

We have a customer with Blik payments issues when shopperIP contains a IPv6 value, apparently Blik only allows IP values with max length of 25 characters. Can you fix your Blik integration?

#4

Remco Tolsma
Pronamic

---

Your request is logged with Ticket ID #2768733 and will be reviewed by our support staff. We typically respond to tickets within 24 business hours, however one of our agents will try to get back to you as soon as possible.

---

Our customer is also requested to contact Adyen about this issue se we can revert 5c2e8f4.

Internal HelpScout ticket: https://secure.helpscout.net/conversation/1797287842/23584/

[remcotolsma]

We received a response from Adyen:

Hi Remco,

Thank you for raising this.

The 25-characters-max limitation is something that has been implemented by the Blik payment method. We have encountered this issue before and raised it with them, but the limitation still applies. For the time being we would recommend you to use IPv4 formatting. We are sorry for the inconvenience.

I hope the above helps, please reach out if you have any more questions.

Kind regards,
Efthymis
Adyen Tech Support

Already replied back:

Thanks for your response. As far as I know the Adyen shopperIP parameter is optional and has no limitations according to your documentation. If the Blik payment method has a 25-characters-max limitation you should solve that problem in the communication between Adyen and Blik. The Adyen development team could implement something like 'if shopperIP length > 25 don't pass IP info to Blik'. Or 'if shopperIP is IPv6 address don't pass IP info to Blik'. Our Adyen clients use Adyen so they don't have to deal with all these payment method specific exceptions. In my experience this is your responsibility and you need to resolve this.

[remcotolsma]

This looks more like it:

Hi Remco,

Thank you for your response.

Upon some inquiring internally further, I was notified that the case has also been raised within our developing team and it is being currently worked on. However, we don't have an ETA for the fix yet.

Kind regards,
Efthymis
Adyen Tech Support

[sianjones]

Is there any further update on this? We would really like to use Blik

[remcotolsma]

Is there any further update on this? We would really like to use Blik

I haven't heard from Adyen since March, if you want to know more, it's best to contact Adyen yourself.

[remcotolsma]

As we are currently working on the Adyen integration, we asked Adyen Support (support@adyen.com) for an update:

Hello Efthymis,

It's been a while since we had contact about a problem with Blik payments and IPv6 on Adyen, we are curious whether there have been any developments in this regard.

[remcotolsma]

Hello Remco,

Thank you for getting in touch. I checked on the issue and it seems there is still no ETA.
We will make sure to, internally, follow up again with the product team.

Let us know if you need anything else.

Kind regards,
Mihaela Vacarus
Technical Support Engineer

[rvdsteege]

Asked Adyen support if this issue has been resolved:

Hello Mihaela,

Can you confirm if the issue with IPv6 and BLIK (see #4) has been resolved since March? Thank you.

[rvdsteege]

Reply from Adyen support:

Thank you for getting in touch. I checked on the issue and there is still no ETA on when a fix will be implemented.
I have reached out to the product team to find out when a fix will be implemented.

Let us know if you need anything else.
Kind regards,

Olamide
Adyen Tech Support

[rvdsteege]

My Adyen support ticket #3377001 was marked as solved, without ETA.

My reply:

I see the ticket status is 'Solved', but as you have reached out to the product team, I'm actually still waiting for the ETA. Thank you :-)

And then got the following reply from Adyen:

Thanks for following up. Unfortunately, there is still no timeline on when a fix will be implemented.

Kind regards,

Olamide
Adyen Tech Support

[rvdsteege]

As Adyen is not going to treat IPv6 addresses any different for Blik, I contacted Blik directly via https://blik.com/en/blik-contact-for-business. Awaiting their reply.

Hello,

I'm one of the developers of Pronamic Pay, a payments plugin for the WordPress platform (https://wordpress.org/plugins/pronamic-ideal/). Our plugin supports Blik through the PSP Adyen. We send the customer IP address to Adyen on payment start.

Unfortunately, there seems to be an issue with Blik not supporting IPv6 IP addresses. We've had an issue open about this since early 2022 at #4. From what we understand, IP addresses are limited to 25 characters at Blik. Usually, these addresses are 39 characters (or even more). Adyen support mentioned they have already raised the issue with you, but it seems this issue has still not been resolved. Adyen also seems to be waiting for you to fix the issue as they don't treat IPv6 IP addresses for Blik differently any different. This makes Blik payments with IPv6 IP addresses impossible.

I'm not sure if it helps, but our Adyen support tickets about this issue are #2768733 and #3377001 (also mentioned in the issue at Github).

Is this indeed a known issue? If so, can you please let us know when the issue will be resolved? Thank you.

Best regards,

Reüel van der Steege
Pronamic