aMember and Verotel!

Does aMember actually work with Verotel? I have been going back and forth with support for a week and a half and still having problems. I have a membership website with multiple sets of photos, each as its own purchase. When an account is created in aMember, Verotel only allows the member to join 1 set before giving this error: "The username selected does already exist for this website. Please go back and select another username". Support doesnt seem to be getting anywhere with this. I really need software for the site. Any help??

support id: AEI-52717-602

I too am starting to wonder.

On January 1 started a site using verotel plug-in. and now about 1/3 of all members are being denied and getting automatic refunds. The funny part is others are going through without any problems at all. I have 6 items and all items have working members and all items have items that fail if that makes any sense.

Looking at the amembers error log all I can see is this:
VEROTEL ERROR: finish_waiting_payment error: Incorrect amount for payment (Details: invoice:689)

and I have checked and rechecked and the amounts in amember and in verotel are the same. Amember and verotel both tell me that it isn't their problem. Neither can tell me what data gets passed so that I can trouble shoot.

AAARRRRGGGG! The odd part is that the amember membership accounts are being created but no subscriptions. And VEROTEL hold on to the customer's fund for up to 4 weeks to do the refunds.

I've started to wonder should I go to the VEROTEL script and drop amembers?

HELP!

Oh and another thing, is anyone using the VEROTEL with user names longers that 12 characters?

Is anyone using VEROTEL??

If so are you doing one product per one "verotel site ID"??

Here's a little information concerning your error. When someone chooses a product in aMember, for let's say, 25.00, and then click through to pay for it on Verotel's side, the customer is shown the default price. So if the default price is 10.00 and the customer doesn't catch this, or changes the selection once on Verotels site, Verotel will process the amount. However, when Verotel reaches back to aMember and finds that there is a difference in the amount, they will cancel and refund the amount to the client. And yes, it can take up to 4 weeks for them to refund.

Solution is to make a note on the payment page that people must make sure the purchase amount is the same on Verotels site as to what they want to purchase within your site.

Cheers,

Mike

Why not check the amount and if different change the payment record to the product the user selected in the Verotel server.
If setup correctly the amount should match with one of the products defined in Amember since those should be setup the same way as in the Verotel server.

At the moment I scan the payments and if different change it manually to the correct product ID. (removed the amount checking, so would not lose payments)
Am trying to find a way to do this automatically and any help here would be appreciated.

I am using the Verotel plugin on a site and it is working smoothly except for this problem.

Thanks Alexander
My problem is solved and this is working perfectly for me. It just needs a couple of extra lines in the ipn script. Only problem in de future might arise when you have 2 products with the same price, but as long as you have not it should not be any problem.

To avoid the problem you have when Verotel is testing your plugin just add a few lines to create the user (if there is no product ID)
They do this basic test and it is also good to see yourself that amember is working and adding the user instead of getting an error message
Acceptance of the website by Verotel was no problem at all and done within 12 hours. No questions asked.

We have all ready over 150 users with only one refund due to the fact the Verotel server missed the approved message from our server when in fact the message was received. In that case the Verotel server will send the message again and again for half an hour until it receives an approved message. In this case it never came because amember replied with the message that the payment was received. The Verotel server had no clue and thought it was an error message.
So we changed here the IPN a bit to avoid this situation by just accepting the message and replying it as approved.

Although we had some small issues it went quite smoothly.

What changes did you or anyone make. I'm still stuck with the error messages when trying to test user management, and I get the same messages when trying to do a test signup. My verotel classic account is Live and fully functional. But obviously there is a problem with the IPN. Can anyone please provide the details for the changes I have to make to the IPN to get this whole thing working.

Am not sure if this works for the verotel classic, am using the ticketclub
the script I changed to avoid the dreadfull error by just adding the user.. nothing else

PHP:

case 'add':
  if ($payment_id){ 
      $payment = $db->get_payment($payment_id); 
    if($payment[amount] != $amount){
        foreach($db->get_products_list() as $pr){
            if($pr[price]==$amount){
                $payment[product_id] = $pr[product_id];

                $product = get_product($pr[product_id]);
                $begin_date    = $product->get_start();
                if ($product->config['is_recurring']) {
                    $expire_date = '2012-12-31';
                } else {
                    $expire_date = $product->get_expire($begin_date);  
                }
                $payment[begin_date] = $begin_date;
                $payment[expire_date] = $expire_date;    
                $payment[amount] = $amount; 
                $db->update_payment($payment_id, $payment);
            }
        }
    } 
    $err = $db->finish_waiting_payment($payment_id, 'verotel', 
    $pnref, '', $vars);
    if ($err AND (!$err == 'Payment is already completed')) {
        verotel_error("finish_waiting_payment error: $err");
    }

    // set expire date to infinite
    $p = $db->get_payment($payment_id);    
    $product = $db->get_product($p['product_id']);
    if ($product['is_recurring'])
        $p['expire_date'] = '2012-12-31';
    $db->update_payment($payment_id, $p);
  } Else {
    $attr['login'] = $vars['usercode'];
       $attr['pass0'] = $vars['passcode'];
    $member_id = $db->add_pending_user($attr);
  }
    break;