Answers:
Why, then, does the "Payment body" in the box always pull up with the total amount of the order (you can't delete it).
As I understand it, if the checkbox "It is necessary to pay for the order" is not worth it, then the body of the payment should be equal to zero.
Judging by the documentation, the cod_amount parameter in this case is 0
At the moment, even manually registering the payment body = 0 in the box itself is impossible
It turns out that we pass the parameter cod_amount with a value equal to the amount of the order
Previously, when creating a TTN, this was not the case, the payment body was 0
12.04.2021, 19:36
Original comment available on version: ru
Sergey, you can try adding an additional field to the order and adjust its calculation depending on the payment method, for example, and select it in the settings
13.04.2021, 13:32
Original comment available on version: ru
Andrew, I already tried that. What happens - in the body of the payment it really shows 0, I was delighted to go to Justin. They opened it on their computer and they say "You have an overlay" you need to redo the entire TTN
13.04.2021, 13:39
Original comment available on version: ru
As far as I know, no.
If it is necessary that when the checkbox is not checked (by default in general) the payment body is not substituted (and when the checkbox is checked, it is substituted) - this is a refinement of the integration.
And they can indicate on the basis of what parameters passed in the request they determined that the overlay?
13.04.2021, 17:17
Original comment available on version: ru
That is not, of course, this is the usual department where an ordinary operator sits, he doesn’t even know the word what a “parameter” is. He scanned my created ttn - information was opened in it in the program, where the overlay was indicated. Regarding the checkbox, it doesn’t matter to me whether the payment body is substituted or not. Here you just need to give the opportunity to normally do ttn from boxing, and if they are done crookedly, then obviously not a single manager will do them in boxing
13.04.2021, 19:03
Original comment available on version: ru
Max checked.
order_payment_is_required":false
but here order_amount": 690 - the cost of the overlay, nevertheless, according to the logic, 0 should be passed if there is no overlay
1. Once again, I will check with the operator whether the overlay is displayed
2. I'll write to technical support Justin - I'll let you know
14.04.2021, 20:14
Original comment available on version: ru
I also want to write about the idea that Andrey suggested
Made an additional field with a null value
In fact, the body of the payment is still set
And I can assure you 100% before the new year, this was not the case, I could set the body of the payment manually and it was zero by default. And justin worked great
15.04.2021, 12:12
Original comment available on version: ru
No, there is no answer, no hello, deaf.
Once again I checked at my department - there is an overlay.
Still, it would be easier to do as before - to give the opportunity to edit the "payment body" from the box and set any, and not as it is now - what the box has set and cannot be corrected to its value. Previously, there was no such problem and the "payment body" could be edited, respectively, you set it to 0 manually and there are no problems
20.04.2021, 12:04
Original comment available on version: ru
There was actually a topic where, at the request of the client, this was implemented
https://crm-onebox.com/ru/support/logistics-and-delivery-services/1463-justin---... to-bred-vo-vkladke-ubiraet-gorod-i-stavit-ne-pravilnuyu-summu/
I can appreciate the improvement of the logic, but I need to decide how to do it so that all parties are satisfied... Perhaps it is worth finalizing the setting in the integration so that the payment body is not automatically calculated? And then, at the first entry, the body will be formed as it is now, and with the checkbox on, it can be specified as 0, and in the future it will be displayed this way. If this option is suitable, it will take 2 hours to implement.
21.04.2021, 15:48
Original comment available on version: ru
And why not do that if the body of the payment and the amount from the additional field are taken, then do not count automatically, and if the field is empty, then count or give the opportunity to specify manually? This is how it works in integration with NP
21.04.2021, 16:37
Original comment available on version: ru
Let's take it one more time with an example:
Default option: unchecked
If the checkbox "It is necessary to pay for the order" is not worth it
"order_payment_is_required" parameter: false
Accordingly, "payment body" = 0
"order_amount" parameter: 0
If the checkbox is enabled - enabled the manager when creating TTN
Accordingly, "payment body" = the amount of the order balance, i.e.
Parameter order_amount": order balance
BUT, THE MOST IMPORTANT - the manager can change the amount of the payment body under any circumstances
Confirm if I understood everything correctly
22.04.2021, 19:03
Original comment available on version: ru
Addition:
Probably the correct condition would be:
If the manager manually changed the "payment body" for some amount, the checkbox "It is necessary to pay for the order" is automatically checked
"order_payment_is_required" parameter: True
Otherwise, the manager will think I put the overlay - I did everything right
23.04.2021, 15:03
Original comment available on version: ru
Sergey, Andrey - let's you agree on the logic that suits you, like the majority of those participating in the question, and provide it to me in one message - I'll tell you if it's possible and appreciate it.
23.04.2021, 15:44
Original comment available on version: ru
I send again, confirm this logic you propose?
Default option: unchecked
If the checkbox "It is necessary to pay for the order" is not worth it
"order_payment_is_required" parameter: false
Accordingly, "payment body" = 0
"order_amount" parameter: 0
When manually changing the "payment body" to a number greater than 0, the order_payment_is_required" parameter: true
If the checkbox is enabled, the manager turned it on when creating the TTN
Accordingly, "payment body" = the amount of the order balance, i.e. this field is
Parameter order_amount": order balance
BUT, THE MOST IMPORTANT - the manager can change the amount of the payment body under any circumstances
23.04.2021, 16:37
Original comment available on version: ru
In my imagination, the ideal scheme looks like this:
1) Since the checkbox "It is necessary to pay for the order" can either always be on or not be on, then always set it or ignore it altogether if we create it with an action
2) To impose or not to determine based on the amount in the "Payment Body" field, if 0 - we transfer without an overlay, if more than 0 - we transfer an overlay, and the amount in the field is the amount of the overlay.
3) Calculate "Payment body" and "Declared value", if it is selected in the account settings - based on additional ones. fields, and transmit what is selected there, otherwise why choose them at all then. This is convenient for automatic creation when switching to a stage.
4) For manual creation - make sure that in any case you can change the value when creating
The bottom line is that I do not have a client to financially support this refinement, so choose what you like best or don't choose. I only suggest.
23.04.2021, 16:46
Original comment available on version: ru
Maxim, then let's go according to Andrey's version
screenshot attached
In principle, the main thing is that it would be possible to create TTN without glitches, and we will adjust the rest of the subtleties
And most importantly, point 4 - the manager can change the value
26.04.2021, 12:32
Original comment available on version: ru
Maxim, then let's go according to Andrey's version
screenshot attached
In principle, the main thing is that it would be possible to create TTN without glitches, and we will adjust the rest of the subtleties
And most importantly, point 4 - the manager can change the value
26.04.2021, 12:32
Original comment available on version: ru
This thread has been answered. The problem was not observed by anyone else.
The key is possibly.
Or maybe someone deleted it somehow.
I don't block anyone. You've just wasted every opportunity to ask questions on the forum.
I already answered in the topic I mentioned above. You can write as much as you like in any topic and demand something (if you have nowhere to spend your time) - this will not work. I gave you exactly here the information that I could, in view of the lack of data.
29.04.2021, 15:50
Original comment available on version: ru
I will describe how I see it:
1. When entering the manual creation of a TTN, we start from the presence of the integration setting "Order payment required" - if it is, we consider the payment body, if not, we do not.
If set/removed - the calculation is turned on/off in the same way when the data changes inside the TTN creation window. Or, for this, you can make a setting in the integration to disable the dynamic calculation when editing the TTN, so that you can set the Payment body yourself even if the "Order payment required" checkbox is enabled
2. If it is indicated to count based on additional fields (and the TTN with its values \u200b\u200bis not saved) - pull it up from additional fields, otherwise - we calculate according to the process data (depending on the specified checkbox in paragraph 1)
In terms of time, it will take all the same 2 hours that I estimated above.
29.04.2021, 16:01
Original comment available on version: ru
If there is a checkbox "Need to pay", and in the additional field "Payment body" is 0 and we create an invoice automatically, will it not count the overlay?
If I understand correctly, then it should be very clear, you can’t send a tick that you need to pay, but at the same time send the amount 0.
29.04.2021, 16:12
Original comment available on version: ru
then parameters will be passed to Justin API accordingly. We don’t know how they already react to this at home, and judging by the attempts to get information from them above, we can only find out by experience))
well then means not to put a tick by default?
especially since we still haven’t received a response from Justin how they react to this parameter
30.04.2021, 16:01
Original comment available on version: ru
Hi guys. We also have this problem on 2 boxes, the stupid manager thought, he constantly forgets to uncheck the box when manually creating, but no ...
"If set / removed - the calculation is turned on / off in the same way when the data changes inside the TTN creation window." - it is necessary that when the "Order payment required" checkbox is unchecked, the payment body is reset to zero
Default option: unchecked
If the checkbox "It is necessary to pay for the order" is not worth it
"order_payment_is_required" parameter: false
Accordingly, "payment body" = 0
"order_amount" parameter: 0
If the checkbox is enabled, the manager turned it on when creating the TTN
Accordingly, "payment body" = the amount of the balance on the order, i.e. this
Parameter order_amount": order balance
I support the solution that Andrey described and am completely for getting away from the checkbox "It is necessary to pay for the order" in the interface for manually creating TTN. Rename the checkbox in the integration to "It is necessary to pay for the order (for manual creation)"
1. When entering the manual creation of a TTN, we start from the presence of the integration setting "Order payment required" - if it exists, we consider the payment body, if not, we do not. The miscalculation needs to be done only once at the entrance. Then give the opportunity to edit the field "Payment body"
To impose or not to determine on the basis of the amount in the "Payment body" field, if 0 - we transfer without an overlay, if more than 0 - we transfer an overlay, and the amount in the field is the amount of the overlay.
2. If it is indicated to count based on additional fields (and the TTN with its values \u200b\u200bis not saved) - pull it up from additional fields, otherwise - we calculate according to the process data (depending on the specified checkbox in paragraph 1)
3. When creating in automatic mode, read the "Payment body" and "Declared value", if selected in the account settings - based on additional ones. fields, and transmit what is selected there.
4. For manual and automatic modes, the parameter "Need to pay for the order" is passed to Justin based on the value of the "payment body":
If "payment body" = 0, "It is necessary to pay for the order" =0
If "payment body" >0, "It is necessary to pay for the order" =1
ps Avoiding linking to the checkbox in the integration "It is necessary to pay for the order" will allow not to produce Justin integration accounts for automatic creation of TTN. We registered in the BP the logic for the additional field, which is transferred to the "Payment body" and happiness. And those who manually create, still double-check everything. I don't think that they prescribe the logic for Justin's accounts to change, for substituting the checkbox "It is necessary to pay for the order" during manual creation.
Guys, you need to finish the coordination of the TOR and make a revision. Calling Justin every time in a fever to remove the overlay is already pretty tired
18.05.2021, 12:48
Original comment available on version: ru
Removed redundant text above.
Hi guys. We also have this problem on 2 boxes, the stupid manager thought, he constantly forgets to uncheck the box when manually creating, but no ...
I support the solution that Andrey described and am completely for getting away from the checkbox "It is necessary to pay for the order" in the interface for manually creating TTN. Rename the checkbox in the integration to "It is necessary to pay for the order (for manual creation)"
1. When entering the manual creation of a TTN, we start from the presence of the integration setting "Order payment required" - if it exists, we consider the payment body, if not, we do not. The miscalculation needs to be done only once at the entrance. Then give the opportunity to edit the field "Payment body"
To impose or not to determine on the basis of the amount in the "Payment body" field, if 0 - we transfer without an overlay, if more than 0 - we transfer an overlay, and the amount in the field is the amount of the overlay.
2. If it is indicated to count based on additional fields (and the TTN with its values \u200b\u200bis not saved) - pull it up from additional fields, otherwise - we calculate according to the process data (depending on the specified checkbox in paragraph 1)
3. When creating in automatic mode, read the "Payment body" and "Declared value", if selected in the account settings - based on additional ones. fields, and transmit what is selected there.
4. For manual and automatic modes, the parameter "Need to pay for the order" is passed to Justin based on the value of the "payment body":
If "payment body" = 0, "It is necessary to pay for the order" =0
If "payment body" >0, "It is necessary to pay for the order" =1
ps Avoiding linking to the checkbox in the integration "It is necessary to pay for the order" will allow not to produce Justin integration accounts for automatic creation of TTN. We registered in the BP the logic for the additional field, which is transferred to the "Payment body" and happiness. And those who manually create, still double-check everything. I don't think that they prescribe the logic for Justin's accounts to change, for substituting the checkbox "It is necessary to pay for the order" during manual creation.
Guys, you need to finish the coordination of the TOR and make a revision. Calling Justin every time in a fever to remove the overlay is already pretty tired
18.05.2021, 12:49
Original comment available on version: ru
Someone asked Justin tech support why they have this parameter in the API, if in fact it does not affect the order payment? Does this affect only the presence of the payment body in 100% of cases?
18.05.2021, 14:51
Original comment available on version: ru
I think that this parameter is needed for the api, most likely it is mandatory, but it makes no sense for us to set it manually in the box, so I stated in the proposal that I propose to remove it from the interface, but leave it in the request for creating a TTN, let it go.
In any case, the one who pays, he orders the music. And to make sure, you can throw a request in postman and send it with and without a parameter, but this is a waste of time, it is obvious that they will create an invoice without an overlay, if you do not pass a check mark, this has already been confirmed by tests when creating an invoice with the action /
Their API may not be ideal, but this does not force us to do the same game in the interface, fewer checkboxes that can objectively be closed with other functionality will only benefit
18.05.2021, 15:51
Original comment available on version: ru
The parameter is needed for the API - we make a request to the API.
Actually, the question for contacting Justin technical support is needed in order to understand the whole picture of how their API works.
After you receive an answer, based on it, the final decision will be made on how we will implement this moment in OneBox (if the checkmark is not needed at all, we will remove it) and I will adjust the assessment if necessary.
18.05.2021, 16:32
Original comment available on version: ru
I correspond directly with Justin. To fix the problem, they asked to send the request in full
type in JSON format, and what url goes to. Can we provide them with this?
08.06.2021, 12:12
Original comment available on version: ru
Sergey, in the attachment there are logs (I made 2 invoices just in case), please send to Justin. It's already enough to call in a fever to cancel the overlay ....
01.07.2021, 18:13
Original comment available on version: ru
I'm sorry, this is the file. In the previous logs for the whole day. This left only the creation of 2 waybills. (as far as I understood logically)
01.07.2021, 18:22
Original comment available on version: ru
Good afternoon, Maxim. You can get involved in the correspondence with Justin, I don't understand what they want.
The problem is getting worse every day.
20.07.2021, 16:25
Original comment available on version: ru
One of the clients also approached Justin with this problem - let's wait to see if he gets the information.
I understand your pain, I don't mind solving it - but I need information from Justin to solve the problem, not create new ones.
21.07.2021, 09:29
Original comment available on version: ru
Security cancel) I checked the last 4 shipments, there is no overlay. Looks like they got through to Justin. I'll watch it for a week and report back.
21.07.2021, 09:48
Original comment available on version: ru
I wrote to TP Justin today to figure out why he's creating cash on delivery.
He wrote that we are passing in "order_payment_is_required" - "false", but creates a TTN with cash on delivery, to which he received an answer, they do not understand why in this case we also pass "order_amount" - "39.8", "redelivery_amount" - " 15.8", "redelivery_payment_is_required" - "true," why send this if there is no overlay - here is the screen -
I also asked them why the "order_payment_is_required" parameter in the API is needed, if in fact it does not affect the overlay, I asked if only the presence of the payment body affects the overlay, and about the order_amount field, I asked if we do not send this value, it will Is there an error that it is not filled in (since this field is required based on the documentation). I'm waiting for an answer.
I suggest, when overlaying, send: order_amount and redelivery_amount value 0 (which is logical)
21.07.2021, 15:22
Original comment available on version: ru
strange API) works as it should for some, not for others)
you can modify such a check if there is no check mark for payment - it will take about 2 hours
21.07.2021, 16:04
Original comment available on version: ru
Anton, I also need this revision. We agreed with Yulia that I will pay for one hour and you will pay for one hour. I'm also waiting for the bill.
27.07.2021, 14:21
Original comment available on version: ru
Thanks, it's working now
But there are nuances / questions:
1. Created TTN here
https://baza.cn.ua/admin/customorder/order/48411/justininvoice/Specified "Post-payment return form" = bank card
In "Post-payment return card number" pulled the card from the settings
https://baza.cn.ua/admin/shop/integrations/justin-integration-4/control/But after creating the TTN, in the field "Post-payment return card number" some incomprehensible code "2147 ******" was put down (I closed it with asterisks because it is not clear what kind of code it is)
After the TTN was deleted, the strange code remained in this field "Postpayment return card number", that is, if you create a new TTN, the system already writes "There was a pardon. Field "cod_card_number" Not Valid" and you need to enter the card number manually
If you enter a new order
https://baza.cn.ua/admin/customorder/order/48424/justininvoice/ then the card is pulled up correctly there
Can you fix this bug?
2. It was not possible to get from the system the opportunity to prescribe the amount of the overlay (Pіslyaplata) I tried it in different ways, but it writes empty in the TTN, with what combinations of the values \u200b\u200bof this can be achieved?
14.08.2021, 22:01
Original comment available on version: ru
This topic has not been discussed in this thread.
search for a relevant topic or create a new one
What was implemented on this topic is indicated above in the corresponding comment
16.08.2021, 15:14
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