Hi Tim,
The easiest-to-deal-with of the possible problems you could be facing
would be lack of mathematically valid credit card number or future
expiration date.
Obviously you don't need to test with a *real* credit card number, but
credit card numbers have a checkdigit algorithm (much like barcodes),
and I know that even in test mode the payment gateways expect valid
check digits. A simple, mathematically valid MasterCard number is
5555555555554444.
If you already knew all that and it isn't the problem, my next step
would be taking Evergreen out of the picture and making sure you can
contact the payment gateway using a simple perl script and the
Business::OnlinePayment::Paypal module. The
CREDIT_PROCESSOR_DECLINED_TRANSACTION event that Evergreen generated
should mean contact was established with the payment processor and they
didn't like something you submitted, so it's probably a data problem you
could figure out with experimentation.
Hope this helps!
Lebbeous
On 04/13/2012 03:10 PM, Tim Spindler wrote:
I have started doing a little testing to see how fines paid to a paypal
developers account and get the following error and I'm not sure if this is
due to the configuration of the client or something about the test account
in paypal.
-------------
FIXME: If you encounter this alert, please inform your IT/ILS helpdesk
staff or your friendly Evergreen developers.
Fri Apr 13 2012 15:01:39 GMT-0400 (Eastern Daylight Time)
Bill payment likely failed
CREDIT_PROCESSOR_DECLINED_TRANSACTION
The credit card processor has declined the transaction.
----------------------------
We are running Evergreen 2.2 Alpha 3
Library org settings
Allow Credit Card Payments: True
Enable PayPal payments: True
Name default credit processor: PayPal
PayPal login: XXXX
PayPal Password: xxxxx
PayPal Signature: xxxxx
--
Lebbeous Fogle-Weekley
| Software Developer
| Equinox Software, Inc. / Your Library's Guide to Open Source
| phone: 1-877-OPEN-ILS (673-6457)
| email: [email protected]
| web: http://www.esilibrary.com
