CiviCRM Community Forums (archive)

Are you using Paypal as your payment processor? If so, please see this issue:

http://issues.civicrm.org/jira/browse/CRM-2685

Are you on CiviCRM 2.0 and the latest release? If yes to all of the above, then you should add a comment to the issue saying it's still not working (again, verify you are on the latest CiviCRM 2.0 release).

I'm pretty sure eway is not a paypal standard type processor. it is more like authorize.net/paypal pro

Civi makes the incorrect assumption that your billing contact name is the same as the contact name (for paypal pro / eway / auth type processors). As such if we collect the billing name and do not see the first name being collected on the form, we assume that billing name is the same as first name.

To avoid this, you can collect both billing name and real name. In that case we will not overwrite the data.

Yes, we do realize this is not ideal, but this is what we have in the system now

lobo

Lobo,

I've changed my code to capture the cardholder name, but I was wondering if I might contribute this back into the baseline code?

I'd like to know if you think this is worthwhile, and how my change might be made generically useful.

These are the changes I've made ...

• CRM_Core_Payment_Form - setCreditCardFields() - added a field for credit_card_holder which is required, and made the billing name and address optional
• templates/CRM/Event/Form/Registration/Register.tpl - added credit_card_holder and changed the comment on the billing name and address to say they are optional
• CRM_Core_Payment_eWAY - doDirectPayment() - changed the payment processor to use credit_card_holder rather than the billing name, and to deal with the case of partial or missing address details

An interesting benefit of making the billing name and address optional is that the "bug" of overwriting real names with credit card names becomes a useful feature because the user has the opportunity of giving us their real name in addition to the name on the credit card.

To make this a generic feature that is useful to others, it seems we need to ...

• Make the existing behaviour the default, so we "do no harm"
• Make the feature dependent on the payment processor used (PayPal couldn't use it, but eWay etc can)
• Allow administrators to decide whether to use billing name (3 fields) or cardholder name (1 field) when they configure the payment processor (3 fields would be the default)
• Allow administrators to decide what is mandatory and what is not when they configure the event or contribution (for instance, I might not want a billing address when processing a donation, but I might for an event where I need to send participants an information pack). The default is that billing name and billing address are both mandatory.

I'm happy to do some more work to make that happen, if people think that's worthwhile. I'll just need some guidance in what to change and how to submit that for review.

Ken

2.1 fixes the billing name / real name issue. if a name exists in the DB it will not be overwritten by the billing name. If the name does not exists, we use the billing name as the name of the contact. At some stage, we will want to store the billing name in the db and associate it with the transaction

lobo