Skip to content

api calls to be made between EFT POS (card terminal) devices and ECR systems #2461

Description

@danielflorearadu

Hi,

we have serious problems regarding EFT POS - our ERP.

the problems are different, either on a unique session-id we get a response like transaction failed, but in the viva portal as well as on the receipt it is successful,

either it appears to us that it is successful but in the portal it appears as having failed.

we don't use webhooks, we just initiate a sale and periodically query its status every few seconds: Initiate a Sales Request + Retrieve Session by Id.

we watch that Sales Request response is 200, Successful Response then we search for Retrieve Session by Id json for value success=true or false

Specifically, we have session id JzzoyGeg46, unique transaction 5e787e4c-5f51-4598-94bd-0cc0d2946c2d

And now if I query the status, it displays Transaction canceled by user

But in the Viva Portal the transaction is successful

another transaction

session id 16304888_11369 ... even now we receive succes = false, and in Viva portal is it with success.

Suma: 160.74
abortAckTime: null
abortOperation: false
abortSuccess: false
amount: 16074
authorizationId: null
cashRegisterId: "SH00001455"
message: "Invalid card"
orderCode: "0"
referenceNumber: 0
retrievalReferenceNumber: null
sessionId: "16304888_11369"
shortOrderCode: "0"
success: false
terminalId: "16304888"
tid: "16304888"
transactionDateTime: null
transactionId: null
transactionTypeId: null

once again, we rely on the fact that there is a unique session id, managed by us, to which we want an answer: success true/false

maybe the pos_ul automatically generates another transaction in addition to the first one
how do we know to identify it as being in conjunction with ours?

if we get success=true ... and yet it is false, how do we know to consider the transaction completed?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions