Skip Menu |

Preferred bug tracker

Please visit the preferred bug tracker to report your issue.

This queue is for tickets about the Business-OnlinePayment-CyberSource CPAN distribution.

Report information
The Basics
Id: 40631
Status: rejected
Priority: 0/
Queue: Business-OnlinePayment-CyberSource

People
Owner: Nobody in particular
Requestors: wonko [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: Wishlist
Broken in: 2.00
Fixed in: (no value)



Subject: Scary error message
Most of the time when there are errors the messages provided by B::OP::CyberSource are helpful to our end users for tracking down the problem. However, this one is scary: Something REALLY bad happened. Your transaction may have been processed or it could have blown up. Check the business center to figure it out. Good Luck... More Information:28 : SSL connection timeout Raw Error: Probable Request ID: Can we make it a little less so? Something like: An error has occurred. Your transaction may or may not have been processed. Please log in to the CyberSource Business Center to see whether your transaction was successfully processed. More Information: Raw Error: XXX Probable Request ID: XXX
Okay - Maybe it is a little too scary, but it is accurate. There is no way to know what happened. That it happens at all is a problem usually caused by CS being too slow on the uptake, although there are other possible reasons for timeouts/being dropped from the internet. -Peter
BTW - did this ticket come in from CyberSource?
On Mon Nov 03 11:08:35 2008, PBOWEN wrote: Show quoted text
> BTW - did this ticket come in from CyberSource?
Nope, from one of our clients. We have a UI to show them failed payments as well as email alerts for critical errors. They started to freak out when this message came across in the email. I work for http://plusthree.com/
On Mon Nov 03 11:07:02 2008, PBOWEN wrote: Show quoted text
> Okay - Maybe it is a little too scary, but it is accurate. There is no > way to know what happened.
I agree that it's accurate. But all of the other error messages are safe for admin user consumption (not end-users who are trying to give money, but non-technical admins who look at the reports, etc). We could intercept this one error before it get's that far and then translate it ourselves, but I thought it might be more beneficial to have it be nicer for everyone and also save us the headache if you ever change the format of this message in the future.
This code was completely rewritten