Are Credit Card Numbers Stored in aMember DB for NON-Recurring Sales?

I currently use Paypal for my recurring subscriptions. I am now thinking about offering NON-recurring, one-time payment subscriptions. However, since I am on a shared server, I do not want to have any numbers stored on my server. I have MerchantAnywhere as a payment processor, which aMember supports. However, when I tested it with a false number (one that did not process), I was able to find that number in the member's payment record.

Does this mean that even for non-recurring billing, aMember will still store credit card numbers for some of the payment processors like MerchantAnywhere? This is a general question, since I need to know if I need to use a solution like 2CheckOut to avoid having numbers stored on my site.

Also, there is some sort of credit card fraud protection (MaxMind) option on the aMember MerchantAnywhere plugin. I'm not sure if that does anything regarding this issue.

Thanks to any help on this.

Jeff

Hello,

That is suprising because looking at the code if the product was really not marked as recurring it looks like it would not store the cc info. Did the user record exist before?

Anyway I guess I don't understand the code at all then.

Jimmy

Yep, if you are processing the credit cards yourself, then amember will store the numbers.

David

Hello,

Well I just verified that if a new member signed up for a non-recurring subscription that the credit card information was not stored in the members record in the amember db. If a new member signed up for a recurring subscription then the credit card information was stored encrypted in the members record in the amember db. This is the behaviour I would expect because there would be no reason to store cc info for a member that had never bought a recurring subscription. This behaviour should apply to all payment plugins that amember does rebilling for. So it is weird to me if this is not the behaviour others are seeing.

Okay I re-read the original question and he said the cc info was stored in the payment record not the user's record. The best I can tell this part will be payment plugin specific. After payment whether succesful or not, information from a log record created by the payment plugin is written to payment record as additional data. I assume this is done in order to log information for that particular transaction. What gets written to log record and hence payment record is payment plugin specific. You should be able to modify what the payment plugin writes to this log record if you do not like the default values.

The more I use and investigate the internals of Amember the more I love it. With a little bit of customization you can make it do just about anything you want.

Jimmy