Payment success - payment details page timeout / hide

[MaozShahaf]

Hello, We are using API version 1.9 using web browser (sdkUsed = false) and after the payment's action of authenticate \ fingerprint there is a Payment success / payment details page, can we make it hidden or to change its timeout to 0 to make it disappear faster? this page is misleading our app users because after this actions we are finalizing the payment in our side.

[Mspisar]

Hello,

your request has been registered and has been forwarded to a responsible service technician. You will be contacted as soon as possible.

Kind regards

Milan Spisar 1st level support - Team Leader

[MaozShahaf]

Hello, do you have any answer?

[dmarek]

Hello, if (device) fingerprint is required (i.e. data is returned in response of */init method in actions.fingerprint.browserInit, the customer has to create 1px iframe on the e-shop side and open the relevant url in it). This fingerprint check takes some time (aprox. 2-3 sec), The authentication process waits cca max 10 secs (timeout in configuration) for fingerprint to complete.

The authentication (after payment confirmation is completed) and then subsequent authorization takes also some time (aprox. in seconds), the payment gateway has to wait to receive the authorization result from the card issuer. There is no way how to speed up the whole process.

[MaozShahaf]

Hi Daniel, We don't want to speed up the whole process, just the Success page.. it means after you already confirmed the payment...

[dmarek]

You mean to speed up the final redirect (from the page with the info that the payment was successful) back to eshop page? (= wait time before the iframe is closed)

[MaozShahaf]

yes... or to make it not appear.. and just iframe close..

[dmarek]

Hello, we will prepare a change to be able to reconfigure the timeout of the final redirect for @shop methods.

[pepakriz]

@dmarek Happy to hear that. And please allow hiding not just the success page, but also the error page. We have our own logic to inform our customers about payment results.

Btw see this page. This happened in our testing environment, but in reality, the payment was successful (based on the API call). I'm a little scared if these inconsistencies could occur in the production. Either way, these problems will be solved by hiding your ending pages :)

payId: 292fabfe802b@IA, merchant: M1MIPS7146

[jgrmelova]

Hello,

I checked transaction 292fabfe802b@IA. I see in log two requirements "payment/process" for this transaction (This is wrong). The 2nd requirement finished with RC 150 - Payment not in valid state:

1st _2023-01-10 15:03:06,913 INFO [qtp181314206-325527][REQ_IN] - REQ_IN Address: ./api/v1.9/oneclick/process ... 2023-01-10 15:03:06,985 INFO [qtp181314206-325527][RESP_OUT] - RESPOUT Payload: {"payId":"292fabfe802b@IA","resultCode":0,"resultMessage":"OK","dttm":"20230110150306",...,"paymentStatus":2}

2nd _2023-01-10 15:03:10,309 INFO [qtp181314206-325527][REQ_IN] - REQIN Address: .../api/v1.9/oneclick/process ... Payload: {"payId":"292fabfe802b@IA","resultCode":150,"resultMessage":"Payment not in valid state","dttm":"20230110150310",...,"paymentStatus":0}