Closed (fixed)
Project:
Ubercart Atos/Sips
Version:
6.x-1.1
Component:
Code
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
16 Jul 2010 at 09:37 UTC
Updated:
28 Apr 2017 at 13:30 UTC
Jump to comment: Most recent
Comments
Comment #1
anrikun commentedWhat was displayed on the page cart/checkout/complete after the successful payment?
Are you sure Atos/Sips sent its autoresponse to the right URL? Please check your configuration.
Comment #2
anrikun commentedThis is not a bug yet :-)
Comment #3
fancdc commentedThank you anrikun for your reply
for me Atos/Sips sent the right URL, if not, the page will go back to 'cart', won't it?
here is the messge i got in the page complete:
Your order is complete! Your order number is XXX.
Thank you for shopping at XXXX. While logged in, you may continue shopping or view your current order status and order history.
Return to the front page.
Comment #4
anrikun commentedNo, that just means that the order was validated and that the payment was successful.
But that does not mean that in the background, any autoresponse from ATOS/SIPS was actually received.
This is because it might happen (very unlikely though) that ATOS/SIPS takes some time to send its autoresponse and that customer returns to the shop before it is received.
In your case, it is very likely that ATOS/SIPS autoresponse is not received by your server.
Check admin/reports/dblog: is there any error?
Is your server accessible from the outside?
Comment #5
anrikun commentedClosed due to inactivity.
Comment #6
miaoulafrite commentedHello Anrikun,
what would then be the "right url"?
Comment #7
miaoulafrite commentedand i would reopen this issue
i believe some more documentation would be helpful
Comment #8
anrikun commentedIs your site on a local computer or on a real server, accessible from the outside?
It needs to be accessible from the outside so that UC/ATOS can send its autoresponse.
Comment #9
miaoulafrite commentedDear anrikun,
thanks for your answer.
the site is accessible from outside.
you can run a test here: https://intranet.synertal.fr/mycontemporary-dev/fr/products/produit-de-t...
(configured in test environment, you can use the following credit card to test a successful payment:
4974934125497800, expire on November 10, no cryptogram)
i have no idea on how to configure the files, can you please tell me what url should be written where? herebelow the code of the paracomfile
Comment #10
anrikun commentedYou should not have to change the parmcom file.
Again, please read the documentation that came with your bank kit.
I cannot provide support about that part as it is not related to the module but to the kit itself.
Read the document called GuideProgrammeurApiPlugin_Webaffaires.doc.
It is written that:
So you must not use the https protocol.
Comment #11
miaoulafrite commentedi'll try that, which is likely to work, thanks.
the problem is that the "documentation" for the module is reduced at its really minimum, a few lines only. so i found it hard to understand which side (the module or the bank API) is generating the problem.
i can propose my help if needed to make a more detailed documentation for the module (for example: do not change what is included in the paramcom file)
Comment #12
anrikun commentedYou're welcome to write a documentation if you have some time for it!
Comment #13
miaoulafrite commentedokay.
our team is working on it.
Comment #14
anrikun commentedThanks!
Comment #15
SashaMag commentedHi all,
I am having the same issue as mentionned above and none of the solutions suggested work.
Please help.
Thank you in advance.
Comment #16
anrikun commentedThis is a support request so there is nothing to review.
Also you don't give any information about your configuration, so it is impossible to help you this way.
Comment #17
SashaMag commentedDear anrikun,
Sorry for the wrong settings on my previous post. I am new to loading issues on this site.
I have installed the ATOS/SIPS API and everything seems to be fine.
I installed the Ubercart Atos module, chose the ATOS/SIPS as default payment methods and filled in the correct server paths for the files request, response and pathfile.
When I make a payment I get through the whole process and see that the payment has been completed (when I click on the 'retrun to the shop' button, the cart is empty, I get a message saying the payment is completed).
However,
- the order status is still In_checkout instead of completed or payment received
- No email messages have been sent to customer or to my store
- the transactions report received from my online bank says AUTORESPONSE_STATUS has FAILED.
I browse the net searching for a solution:
- the request and response files are executable,
- the parcomfile is set as the one indicated by miaoulafrite above
Please help.
Comment #18
anrikun commentedCan you send me credentials to connect to your site using my contact form?
Comment #19
anrikun commentedThis is because access to your site is protected by .htaccess.
Comment #20
eme commentedI can confirm the hook_order (op : submit) is never called. And some modules rely on this hook to perform operations.
Only uc_cart_complete_sale is called.
See #700270: Remove hook_uc_order('submit') as it is never called for redirected payment methods to see other discussion on a close matter.
Comment #21
eme commentedComment #22
anrikun commented@eme:
I think that #20 is a different issue.
Please post it as a new separate one.
Comment #23
anrikun commentedComment #24
cedric_aI had this problem too and realize while reading this thread that I was working with my website in offline mode... It's better online. Thanx
Comment #25
kenjil commentedSince i had same kind of problem and end up reading this thread, i provide here the full check list in case autoresponse does not seem to respond correctly (which causes the lack of automatic order's status update).
5.3. LA REPONSE AUTOMATIQUE NE FONCTIONNE PAS
• L'URL doit être accessible depuis un accès Internet extérieur. Un login/password, ou un firewall sont susceptibles de bloquer l'accès à votre serveur.
• Vous ne devez pas utiliser de protocole https.
• Contrôlez les log d'accès de votre serveur (historique).
• Si vous utilisez un port non standard, ce dernier doit se situer dans la plage de 80 à 9999.
• Vous ne devez pas passer de variables de session avec l'URL, pour transférer des informations utiliser les champs CADDIE (2048 caractères) et RETURN_CONTEXT (256 caractères).
• Si vous avez validé le fait que le serveur Scellius appelle bien votre URL automatic_response_url, il y a sans doute une erreur de programmation dans votre cgi_autoresponse. La similitude entre les réponses manuelle et automatique permet de déboguer facilement le cgi_autoresponse. Il suffit pour cela de renseigner l’URL normal_return_url avec l’URL du cgi_autoresponse. Ainsi, ce dernier sera déclenché par le bouton « RETOUR A LA BOUTIQUE » du ticket électronique, et ce dans un navigateur. La présence de ce navigateur vous permettra d’ajouter des affichages tout au long du traitement pour tracer les commandes défectueuses (pensez à la directive « Content-type »). Bien entendu, ces affichages seront à supprimer quand vous paramétrerez le cgi_autoresponse dans l’URL automatic_response_url.
• Enfin, si votre code de réponse automatique fonctionne quand il est appelé via l'URL de réponse manuelle, mais ne fonctionne pas via l'URL de réponse automatique, il y a probablement un cookie, une redirection, ou toute autre chose nécessitant la présence d’un navigateur dans le code de votre cgi_autoresponse.
Of course, when using uc_atos, one should check all this on the path
cart/atos/autoresponse.Comment #26
jvieille commentedActually, this crazy ATOS / SIP gateway does not support SSL, though it is required for us to run SSL...
This will never work as the autoresponse URL will necessarily by https
I solved this issue by not running my site full ssl but using secure page to selectively serve cart and checkout pages with https and do not lose the session when going to and back https / http.
Then I changed the code in uc_atos.module around line 603:
Hope this helps other suffering this odd ATOS/SIP requirement
Comment #27
jvieille commentedUsing a full https site, I used 443 session with cart/atos/autoresponse as exception
However, this does not always work.
I enforced that in the apache :80 and :443 virtual servers by adding this redirect
RewriteCond %{HTTPS} on
RewriteRule ^cart/atos/autoresponse$ http://yoursite.tld/cart/atos/autoresponse [R=301,L,QSA]
Comment #28
anrikun commentedComment #29
jvieille commentedI finally made it!
In the file parmcom.xxx, change
to
This allowed my site to be 100% https, no neeed for securepage or 443 session. The site is at last recognized by Search engines as secured.