Speedie

Thanks for the reply. Would you have any interest in coding a correctly functioning PayflowPro (PayPal) reference payments gateway module on a paid basis? Apparently I would have to pay to get source code access to attempt to fix the non-functioning included module (!) so I would prefer to spend that money on something that I know will work and comes with some accountability and support. The PPP transaction fees are considerbly lower than Stripe's it seems.

I was hoping to hear from someone else that it actually works before going through the process of applying for another merchant account, but alas nothing. At this point the most likely outcome is dumping WHMCS in favor of something that works as advertized and is actually supported (2 replies in 10 days to the ticket about the other gateway, neither of which suggest that anything is actually being done to resolve the problems).

Is anyone using Authorize.net with the CIM module, and if so, is it working correctly please? Specifically is it working to pass tokens back and forth for recurring payments, and allowing customers to update their cards in the client area? Basically I need to get a tokenized gateway that works out of the box. The WHMCS module for PayPal Payflow Pro has all manner of problems, and of course 6 days after opening a support ticket I have the sum total of a single reply 3 days ago. At this point I just need to get something up and running that works. Not that I should have to switch gateways to accomodate a piece of software that I just paid $325 for, and which advertizes support for PayPal Payflow Pro reference transactions, but given how non-existent WHMCS support is these days is seems to be the only option. Thanks in advance for any shared experiences with Authorize.net CIM.

Confirmed as a bug in ticket BYC-595712 and sent to the developers as case 2009.

Same here, seems to be client details only.

1) The gateway password is stored in plain text in tblpaymentgateways (seriously?). 2) With reference payments enabled, if a client updates their credit card information from the client area, the whole card number is stored. What SHOULD be happening is an auth for a tiny amount and the resulting transaction ID gets stored. WHMCS storing the whole credit card number for an updated card rather negates the point of a tokenized gateway, not that it really matters because... 3) Reference payments are not processing correctly at all despite being enabled in PayPal Manager and in the module itself. Verified in tblpaymentgateways that usereftrans is on. Steps to reproduce: a) Create new client account and initiate an order. b) Pay with credit card and allow storage. This payment should work fine, and Client Profile -> Summary -> Credit Card Information should show something like this: ------------------------------------------- Remote Gateway Token xxxxxxxxxxxxxxx * Only the last 4 digits of the credit card are stored locally since a token based remote storage module is being used ------------------------------------------- c) Attempt to place another order using the stored card. The transaction will be declined and Billing -> Gateway Log will show something like this: Invoice ID => nnnnn User ID => nnnn Amount => n.nn RESULT => 23 PNREF => xxxxxxxxxx RESPMSG => Invalid account number Which is strange as no account number should be passed, it should be the transaction ID for the original charge which, if incorrect, would spit back RESULT => 19 and not 23. 4) If a client has a card on file, but chooses to use a different card at checkout but not store it for future use, the token stored in tblclients.gatewayid is updated anyway. I believe that if the client then attempted to use their on-file card, the wrong card would be charged as a reference to the non-stored card would be passed to the gateway. Of course I can't verify this because of (3) above.

Confirmed. Checked a client with 20+ invoices paid, they show up in Billing -> Invoices -> Paid, but nothing in the client's invoices tab.

Steps to reproduce: - In client area, my domains (clientarea.php?action=domains) check one or more domains. - Choose "With Selected" -> "Edit Contact Information" - Receive "Invalid Access Attempt" error. I have been able to reproduce this with default, classic, and portal templates, and also within the WHMCS demo site.