juan.angel | Posts: 6

"Status" parameter values from "Get transaction" response

0 votes

Hi Team, I hope you're doing well.

Here at our InfoSec area, we would like to know which are all the possible values the "status" parameter can take in the "Get transaction" response when we send the HTTP request with Postman, to the OneSpan's API. I attach a screenshoot of the parameter in mention.

Also, could you please tell us if this "status" parameter only takes the value of "completed" when a transaction is successfully completed or if it can take other values?.

Thank you in advance.


Approved Answer
Duo_Liang | Posts: 3776

Reply to: "Status" parameter values from "Get transaction" response

0 votes

Hi Juan,

 

As per the JSON schema, below are the possible values for the "status" field:

  • new
  • cancelled
  • expired
  • workflow_in_progress
  • workflow_completed
  • error
  • autosigned
  • vaulted
  • completed
  • post_processing

 

Duo


juan.angel | Posts: 6

Reply to: "Status" parameter values from "Get transaction" response

0 votes

Hi Duo, thank you for your answer, it's very helpful.

Additionally, Is there any information related to the question I send you in the original message?

We're looking forward to your update.


Duo_Liang | Posts: 3776

Reply to: "Status" parameter values from "Get transaction" response

0 votes

Hi Juan,

 

I see your concern now - Our support agent told me that there was an issue last week where "finalized" was not changing to "true" which may have affected your integration. Could you kindly confirm that the issue was fixed last Friday and the product should behave as expected again?

Hence if you are looking for an alternative way of telling if a transaction has been completed instead of depending on "finalized", "status":"completed" could be your option I believe.

 

Duo


juan.angel | Posts: 6

Reply to: "Status" parameter values from "Get transaction" response

0 votes

Hi Duo, you're right. Last week, we were looking for another way to fix the automated process from our side, as a contingency plan. But, as you said, the OneSpan support team was able to resolve the issue with the "finalized" parameter, so we're going to keep the initial solution without changes.

Thank you!


Hello! Looks like you're enjoying the discussion, but haven't signed up for an account.

When you create an account, we remember exactly what you've read, so you always come right back where you left off