Closed rouwe111 closed 4 years ago
Hi rouwe111,
This is a known issue relating to the use of a clientKey
in components version >= 3.11.0
with test cards on our Test servers.
Using the clientKey, as opposed to the originKey, allows the /binLookup
functionality to activate.
However the databases on Test aren't as complete as the ones on Live so some test cards are not recognised.
But merchants shouldn't experience issues with real cards in production.
We are currently looking into the configuration of our Test databases to see if these test cards can be added to prevent this issue in the future
Hi rouwe111, This is a known issue relating to the use of a
clientKey
in componentsversion >= 3.11.0
with test cards on our Test servers. Using the clientKey, as opposed to the originKey, allows the/binLookup
functionality to activate. However the databases on Test aren't as complete as the ones on Live so some test cards are not recognised. But merchants shouldn't experience issues with real cards in production. We are currently looking into the configuration of our Test databases to see if these test cards can be added to prevent this issue in the future
@sponglord Thank you for the quick reply. Is it safe to set the originKey
instead of the clientKey
for now? We would like to test it first before using it in our production environment.
Yes. That would be the best solution for now.
The issue with Bancontact numbers has been resolved
Describe the bug I am unable to use the test card numbers from your documentation in the Bancontact (bcmc) checkout form starting at version 3.11.0. The number is working fine on version 3.10.1 and below.
To Reproduce Steps to reproduce the behavior:
Expected behavior The test card numbers are working and I will be able to pay with them.
Screenshots
Desktop (please complete the following information):
Additional context When I check the binLookup request, the detected brand is mc instead of bcmc.