Registering cards does not work in 2.7.1

[cf256]

I've just updated the SDK to 2.7.1 in our app, however registering cards does not seem to work. If I go back to 2.7.0 it works.

In both cases I get a ProcessResult.Success from the SDK, but in 2.7.1 the transactionId is an empty string, whereas in 2.7.0 it is a GUID. I am using the same card in both tests.

I am starting a PaymentProcess.cardTokenization like so:

val cardRegistration = PaymentProcess.cardTokenization(
    merchantInfo,
    cardsToExclude,
    object : CardTokenizationRegistration {
        override fun registerPayment(callbackWithTransaction: TransactionCallback) {
            callbackWithTransaction.successWithTransactionIDAndRedirectURL(transactionId, REDIRECT_URL)
        }
    }
)

PiaSDK.startCardProcessActivity(activityLauncher, cardRegistration, /* isCVCRequired */ true)

This is in the PROD environment. Let me know if you need any more info

[Miss-PiA]

Hi @cf256 Is the card tokenization working for you in TEST env in v2.7.1?

[cf256]

Hi No it is not working there either. Using 4925 0000 0000 0004 12/25 123 - I get an error in the callback: TerminalRequest(terminalRequestError=ResponseContainsError(response=Response{protocol=h2, code=200, message=, url=https://epayment.nets.eu/terminal/default.aspx}))

[Miss-PiA]

From the url property inside ResponseContainsError I can see that you are trying to tokenize the test card i.e. 4925 0000 0000 0004 in production environment. https://epayment.nets.eu/terminal/default.aspx URL is for PRODUCTION terminal call and for TEST it is https://test.epayment.nets.eu/terminal/default.aspx

4925 0000 0000 0004 is supposed to be used only in TEST environment and it won't work in PRODUCTION environment.

But no worries I was able to reproduce the original issue as mentioned by you and I also got empty transaction ID in PRODUCTION env and I'm currently looking for the root cause. I'll update you once there's any progress on the issue

[cf256]

I had an issue on my end that caused me to use the wrong env. Thanks for looking into it!

[AndreasReiff]

When are you expecting a fix for this? Im also experiencing this in production.

[Miss-PiA]

@cf256 @AndreasReiff If you are facing issue in production, we suggest you to use v2.7.0 for now. And we will be making a new release as soon as possible including some other changes also.

[finnhlarsen]

@Miss-PiA We are also facing this issue in production - what are the status on the fix/new release?

[Miss-PiA]

Hi @finnhlarsen,

The issue has been fixed by the development team and the new version v2.7.2 will be release within next week with the bug fix.

Meanwhile you can use v2.7.0 which do not have this issue.

[Miss-PiA]

Hi @cf256 @AndreasReiff @finnhlarsen We have released v2.7.2, can you please check it it solves the original mentioned issue?

[cf256]

@Miss-PiA I've tested this on my end and it seems to be working for me.