1b.app
Link copied -

Can't send checks to Chek Box

Нужно настроить интеграцию с ChekBox ?
Есть необходимость организации РРО на предприятии ?
У нас есть готовые решения! Посмотреть решения
During the process of transferring the check, it writes an incorrect access token.
Help me to understand.
From the side of Checkbox, as their specialist answered, there are no problems. They say that this token should be updated in the crm.
""""
checkbox
The token can be obtained independently via api, https://api.checkbox.in.ua/api/redoc#operation/sign_in_cashier_via_signature_api...
11:02
checkbox
As a rule, module developers must process this, receive the token, and revoke the token after the work is completed. That is, request a new token for a session
""""
Expert answer.
Original question is available on version: ru

Answers:

Good afternoon!
At the moment, a member of the technical department is working on a solution to the problem. The approximate deadline for solving the arisen complexity is 03/16/2021 if there are no additional questions in terms of the operation of the specified service.
15.03.2021, 12:45
«Один юрист із портфелем у руках награбує більше, ніж банда автоматників» Original comment available on version: ru

Do you open a shift before printing a check so that you have an up-to-date token?
For we have dozens of clients using this integration - and they did not have such problems.
16.03.2021, 16:03
Original comment available on version: ru

The procedure for working with the check box
1. We open a shift on the check box website
2. When placing an order in the CRM, we simply press the send button to the check box (at the same time, the check box signature program is launched)
3. All transferred checks are displayed on the site in the personal account of the check box
4. At the end of the shift, we simply close the shift on the site. (it has been working for more than 2 months in the checkbox) there were no such problems.
All the actions that we do in the box are just pressing a button to send information to the checkbox.
ps the course of action has never changed.
16.03.2021, 16:18
Original comment available on version: ru

Now if you open a shift and immediately try to fiscalize a check, do you get the above error?
16.03.2021, 17:37
Original comment available on version: ru


Kastyrin Alexander Nikolaevich wrote:
4. At the end of the shift, we simply close the shift on the site. (it has been working for more than 2 months in the checkbox) there were no such problems.
All the actions that we do in the box are just pressing a button to send information to the checkbox.

why not an action in the system?
16.03.2021, 17:39
Original comment available on version: ru


Tyndyk Maxim Vadimovich wrote:
Now if you open a shift and immediately try to fiscalize a check, do you get the above error?

Yes, that's right, the error is still there. 4th day we cannot send checks, the check box refers to you that he gave all the information to your programmers, and everything seemed to be agreed. but no result since friday
16.03.2021, 18:29
Original comment available on version: ru


Tyndyk Maxim Vadimovich wrote:

Kastyrin Alexander Nikolaevich wrote:
4. At the end of the shift, we simply close the shift on the site. (it has been working for more than 2 months in the checkbox) there were no such problems.
All the actions that we do in the box are just pressing a button to send information to the checkbox.

why not an action in the system?

As everything was initially set up, we are working, we didn’t touch anything, we didn’t change anything, we did everything according to the instructions as the check box gave.
16.03.2021, 18:30
Original comment available on version: ru


Tyndyk Maxim Vadimovich wrote:
Now if you open a shift and immediately try to fiscalize a check, do you get the above error?

If communication is not possible through the forum, it is better to call immediately in order to expedite the process of solving the problem.
0633823169
16.03.2021, 18:31
Original comment available on version: ru


Kastyrin Alexander Nikolaevich wrote:
Yes, that's right, the error is still there. 4th day we cannot send checks, the check box refers to you that he gave all the information to your programmers, and everything seemed to be agreed. but no result since friday

It references correctly - after all, if you OPEN a shift through OneBox - the token is cached until you CLOSE the shift through OneBox.

As everything was initially set up, we are working, we didn’t touch anything, we didn’t change anything, we did everything according to the instructions as the check box gave.

If for some reason you do not want to close the shift through OneBox - I can offer the following revision - at the time of the request, if the above error occurs - we can re-authorize to receive a new token and repeat the request.
To do this only for the action of fixing the ceca - it will take 2 hours.
Do this for all actions (fiscalization / receiving a check / printing an HTML check) - 6 hours.
Let me know if any of the solutions suits you and we will issue an invoice.

Kastyrin Alexander Nikolaevich wrote:
If communication is not possible through the forum, it is better to call immediately in order to expedite the process of solving the problem.
0633823169

To do this, the site has a description of paid technical support https://crm-onebox.com/ru/prices/#support
17.03.2021, 13:09
Original comment available on version: ru

Good afternoon.
here is a link to the task https://megazayka.crm-onebox.com/admin/customorder/issue/8582/edit/
here is the stage where the action is when clicked, we get an error, here is the stage where this action is located https://megazayka.crm-onebox.com/admin/shop/workflowstatus/140/action/new/
We cannot close the session. Above described from the words of your integrator.
We don't have any reason. We have been working in this mode for almost 3 months and there were no problems ...
17.03.2021, 13:33
Original comment available on version: ru


Kastyrin Alexander Nikolaevich wrote:
We don't have any reason. We have been working in this mode for almost 3 months and there were no problems ...

I do not think that you have been working in this mode for 3 months.
I'll explain what happened:
1. You opened a shift in OneBox or fixed a check after opening a shift in the Checkbox personal account, thus we received a new access token and saved it for ourselves for subsequent requests.
2. You fixed the checks, and then closed the shift not through OneBox (as needed), but through the personal account - thus the token became inactive for them, but for us it was saved.
3. Trying to make a request - we get an error, because our shift was not closed and, accordingly, the old token is used.
And now, even if we delete the old token, you probably won't be able to re-open the shift through OneBox, since it will actually be opened in the Checkbox.
I added a couple of checks - try reopening the shift in OneBox.
17.03.2021, 14:35
Original comment available on version: ru

And for the future - open and close the shift daily through OneBox - then you will not have such problems - and we will always have an up-to-date access token.
17.03.2021, 14:40
Original comment available on version: ru


Kastyrin Alexander Nikolaevich wrote:
We don't have any reason. We have been working in this mode for almost 3 months and there were no problems ...

I do not think that you have been working in this mode for 3 months.
Good afternoon. I assure you, they worked from January 2 to the day until a problem occurred, this can be seen from the logs.
Thanks for helping me solve the problem. The point is clear.
We have already tested opening and closing a shift through CRM, now you do not need to do this action on the site.
This is how we will continue to work.
There was an unresolved issue with resetting the cash register daily. While we are resetting the cash register through the site. Let's contact our integrator, maybe he can help.
20.03.2021, 13:15
Original comment available on version: ru

Please join the conversation. If you have something to say - please write a comment. You will need a mobile phone and an SMS code for identification to enter. Log in and comment