Using observer after credit card response

[badarac]

I'm making a mod to a site that sells both subscription and non-subscription products. I've got the part that splits the subscription item into the correct monthly amount and adjusts the price in the shopping cart and product info page. When added to the cart all totals are correct and the credit card is processed (authorize.net aim).

Now I need to handle the creation of one or more subscriptions. According to authorize this needs to be a separate transaction. I decided to use the notifiers so that I don't mess with the payment module. I followed the instructions in the tutorial https://www.zen-cart.com/wiki/index....ials#Checkout: and I can't get it to function at the NOTIFY_PAYMENT_AUTHNET_POSTSUBMIT_HOOK. I want to do it there to ensure that the credit card captured the one time charges (including the first month subscription fees) prior to creating the subscriptions. I've tried a number of other notifiers and the only one that seems to work is NOTIFY_HEADER_START_CHECKOUT_SUCCESS. I can see using notifier trace that NOTIFY_PAYMENT_AUTHNET_POSTSUBMIT_HOOK is executing and it contains the response from authorize.net.

At this point all I'm trying to do is echo a message to the screen to indicate that I'm in the update. It does it on the construct but not the update. This is the beginning of the code in the observer directory:

class build_subscription extends base {

  function __construct() {
    $this->attach($this, array('NOTIFY_PAYMENT_AUTHNET_POSTSUBMIT_HOOK'));
  }

  function update(&$class, $eventID)
  {
    echo "HERE I AM ON THE CONSTRUCT";
    if ($eventID == 'NOTIFY_PAYMENT_AUTHNET_POSTSUBMIT_HOOK')
    {
          global $db, $messageStack, $order, $messageStack; 

The autoloader (I've tried multiple load points):

if (!defined('IS_ADMIN_FLAG')) {
 die('Illegal Access');
}
$autoLoadConfig[10][] = array('autoType'=>'class',
                              'loadFile'=>'observers/class.build_subscription.php');
$autoLoadConfig[190][] = array('autoType'=>'classInstantiate',
                              'className'=>'build_subscription',
                              'objectName'=>'build_subscription'); 

I need this to run while I still have access to the data required for authorize.net such as the credit card number, expiration, cvv...

Can somebody point me in the right direction with this?

[lat9]

You're not going to see any echo'd information on-page, since the submittal function is occurring during the transitional checkout_process page.

Better to use something like trigger_error:

trigger_error('Got here', E_USER_WARNING);

and you'll see your progress recorded in a myDEBUG-*.log file.

As a suggestion, make a slight modification to your observer-class:

class build_subscription extends base {
  var $submit_data = false;
  function __construct() {
    $this->attach($this, array('NOTIFY_PAYMENT_AUTHNET_PRESUBMIT_HOOK', NOTIFY_PAYMENT_AUTHNET_POSTSUBMIT_HOOK'));
  }

  function update(&$class, $eventID, $p1, &$p2, &$p3)
  {
    echo "HERE I AM ON THE CONSTRUCT";
    if ($eventID == 'NOTIFY_PAYMENT_AUTHNET_POSTSUBMIT_HOOK')
    {
          //- Got here, post-submit.  $p2 contains the response data
          global $db, $messageStack, $order, $messageStack;  
          ...
    } else {
        //- Got here, pre-submit.  $p2 contains the submit_data array contents.  Save those locally for use in the post-submit processing
        $this->submit_data = $p2;
    }

[badarac]

I knew a different set of eyes and experience would help. Thanks so much!!

[mc12345678]

Also understand that with the extra parameters assigned that way that the code won't work on ZC 1.5.1 or below if it were desired/needed to apply to such an older version of ZC. Also would suggest placing comments to identify how the notifier is arranged so that if it changes between versions you can quickly identify the difference(s).

[badarac]

Also understand that with the extra parameters assigned that way that the code won't work on ZC 1.5.1 or below if it were desired/needed to apply to such an older version of ZC. Also would suggest placing comments to identify how the notifier is arranged so that if it changes between versions you can quickly identify the difference(s).

This is for a 1.5.5e install.

[DrByte]

Also note that if you prefer to have separate class methods for each hook, you can skip the update() method and simply have specific updateHookNameHere() methods for each hook.

ie: updateNotifyPaymentAuthnetPostsubmitHook()
and updatenotifyPaymentAuthnetPresubmitHook()
and updateNotifyHeaderStartCheckoutSuccess()
etc ... matching whatever hooks you've attached to.

Saves having a bunch of complicated if/elseif/elseif/elseif or switch statements.

[badarac]

That's actually the way I wound up doing it. I found that I needed to use the presubmit hook to get the credit card info and had to use a hook later in the process to get the order record after it was written. Now if I could figure out why I'm getting an invalid id(error 13) or key from authorize.net using the same ones as the initial transaction I'll be a happy camper. This would have been much easier if I could have strung multiple transactions together but they don't allow that.

[badarac]

Does anybody have a link to documentation for the x_ parameter array values? Authorize.net's now forces you to use composer and provides no documentation for other methods. I can't find the ARB values documented anywhere. I was able to find an old post using google that provided some help. It executed the transaction but I'm not sure if it actually created the subscription. I see the transaction in the dashboard of the sandbox but nothing in the recurring billing section. I'm not sure if this will not happen until 2am when the transactions process. For info this is what I provided (edited to remove sensitive info).

$params = array(

			'x_login'				=> '',
			'x_tran_key'			=> '',
			'x_ref_id'				=> '123456',
			'x_subsc_id'			=> false,
			'x_subsc_name'			=> 'test subscription',
			'x_length'				=> '1',
			'x_unit'				=> 'months',
			'x_start_date'			=> '080817',
			'x_total_occurrences'	=> '5',
			'x_trial_occurrences'	=> '',
			'x_trial_amount'		=> '',
			'x_first_name'			=> 'John',
			'x_last_name'			=> 'Smith',
			'x_card_num'			=> '4111111111111111',
			'x_amount'				=> '132.05',
			'x_exp_date'			=> '1218',
			'x_delim_data' => 'true',
            'x_relay_response' => 'FALSE' // AIM uses direct response, not relay response
 );

[lat9]

Is this link helpful? http://developer.authorize.net/api/r...urring-billing

[badarac]

Is this link helpful? http://developer.authorize.net/api/r...urring-billing

No that is documentation of their new api that requires using composer. I've actually got it working using the xml api. Now to finish testing , package it up, and move it to the client site.