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) »
  • Authorize.net fraud detection suite and CiviContribute
Pages: [1]

Author Topic: Authorize.net fraud detection suite and CiviContribute  (Read 561 times)

SarahG (FountainTribe)

  • Ask me questions
  • ****
  • Posts: 782
  • Karma: 29
  • CiviCRM version: 4.4.7
  • CMS version: Drupal 6, Drupal 7
  • MySQL version: 5.5
  • PHP version: 5.3
Authorize.net fraud detection suite and CiviContribute
September 30, 2012, 10:01:21 pm
Authorize.net offers an optional fraud detection suite.  The way it works is that some transactions are put on hold until a human being at the non-profit organization either approves or declines the transaction, using admin tools in their Authorize.net account.  (The rules for which transactions are put on hold have some defaults, and the non-profit can also customize the rules.)

What I have observed in CiviCRM  when a transaction falls into this "on hold" category:    The return code from Authorize.net  is "1: 252 Your order has been received. Thank you for your business! "  Unfortunately, CiviContribute treats this as a failed transaction, so there is no record of the contribution in CiviContribute.   Worse yet, if this happened when an end-user was signing up for a paid event or using a CiviContribute page, there is no record of the data that they provided in the profile.   But because the message includes the words "Thank you for your business" the end-user thinks everything is fine.

What I think should be done in this situation: CiviContribute should create a contribution record (and also capture whatever data was typed into the profile). The status of the contribution record should be "pending" or "in progress".    If the transaction is later approved (and therefore processed), then Authorize.net will send an update to the "silent post URL".  When the CiviCRM silent post URL is called, CiviCRM should update the existing contribution record's status to "completed"
« Last Edit: September 30, 2012, 10:05:58 pm by Sarah Gladstone »
Did I help you? Please donate to the Civi-Make-It-Happen campaign  CiviCRM for mobile devices! 

Coleman Watts

  • Administrator
  • I’m (like) Lobo ;)
  • *****
  • Posts: 2346
  • Karma: 183
  • CiviCRM version: The Bleeding Edge
  • CMS version: Various
Re: Authorize.net fraud detection suite and CiviContribute
October 01, 2012, 03:44:21 am
Totally agree. Please share your code for this when you get it working, or even if it doesn't work share anyway and we can collaborate.
Try asking your question on the new CiviCRM help site.

Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Using CiviCRM »
  • Using CiviContribute (Moderator: Donald Lobo) »
  • Authorize.net fraud detection suite and CiviContribute

This forum was archived on 2017-11-26.