CiviCRM Community Forums (archive)

*

News:

Have a question about CiviCRM?
Get it answered quickly at the new
CiviCRM Stack Exchange Q+A site

This forum was archived on 25 November 2017. Learn more.
How to get involved.
What to do if you think you've found a bug.



  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Using CiviCRM »
  • Using CiviContribute (Moderator: Donald Lobo) »
  • Access Denied on Payment Processor Failure
Pages: [1]

Author Topic: Access Denied on Payment Processor Failure  (Read 350 times)

qjensen

  • I post frequently
  • ***
  • Posts: 141
  • Karma: 11
    • Scaled Solutions
  • CiviCRM version: 4.5
  • CMS version: Drupal 7
  • MySQL version: 5.5
  • PHP version: 5.3
Access Denied on Payment Processor Failure
February 11, 2014, 10:38:41 pm
I have a contribution page setup that is working great. Members sign up and all goes smoothly until there is a problem with the payment (AVS failure, CVV failure, etc). The user gets an Access Denied page when the payment fails like this. If they hit the back button they will see a payment processor error on the page, but most people just throw in the towel when they see the access denied page.

The payment processor is Authorize.net, and we aren't seeing any errors on that end (except the expected failure messages). I checked the CiviCRM error log and didn't see anything there. Am I missing a permission in my Drupal setup or is there something else I need to configure so credit card processing failures don't result in an access denied page?

Thanks for your help,
Quint
Quint Jensen
Web Developer
Scaled Solutions
--" Remove the 'I want you to like me' notes from your forehead and place them where they truly will do the most good -- on your mirror!" Author Unknown

Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Using CiviCRM »
  • Using CiviContribute (Moderator: Donald Lobo) »
  • Access Denied on Payment Processor Failure

This forum was archived on 2017-11-26.