Hi Oleg,

Thank you for the response. That's fine if that page needs all those fields to be compatible with the various gateways. The fields should still auto-populate from the contact's profile. And perhaps administrators should be allowed to determine which of these fields should be required each time they run a card, so that they can match the requirements of their particular gateway. Thanks again, and I look forward to this being put in the development queue.

Hi, Liz

Thanks for elaborate comment.

Some payment gateways require billing address, some allow customization of required information for each merchant, like yours, etc. Currently, we use unified payment page for all variations of all gateways. This is simple, but not very user friendly solution, indeed.

This problem is in our backlog right now, but no estimates yet.

Oleg, Product designer @ Payments crew

I am in the process of setting up Stripe and was very surprised to find that manual credit card payments require typing in not only the address, but also the phone number. It auto-populates the name field, so it’s clearly possible to auto-populate fields on the credit card payment page. It would be great to be able to specify custom fields to pull the address fields from (or make address a compound system field). I see no reason why the phone number currently can’t be auto-populated.

It’s one thing to make end-users type in this information – they likely have it memorized and so this would be a minor inconvenience (although, one that should still be fixed!). But we will also be accepting phone orders, meaning frequent manual card entry by administrators. This process is prohibitively long while a customer is waiting on the other end. We basically will have to copy/paste the info from their profile to notepad, then click forward to the payment screen, then copy/paste the info into the fields. It would be bad customer service to ask them for this info, seeing as how we already have it. It’s a long time to ask someone to wait on the phone while we go through this cumbersome process. Also, Stripe only requires the zip code and security code…so why are the phone and full address fields required on the WA interface?

Would love to have this and it would help us have more members paying by credit card.

That's a very good and proper idea, the problem is that WA doesn't know anything about billing address of your member: all member profile fields are same and there is no (easy) way to extract billing related details from them. To address this properly, we will have to implement something like special system field for billing details or have some kind of mapping page for payments, where admin can map member profile fields to billing fields on credit card payment page.

+1. It's important to make member transactions as smooth as possible.

[quote user="epgremill3"]We'd even be happy to name our address fields something standardized (e.g. same as Wild Apricot payment page) to get this to work.
[/quote]

Seems like this is a simple solution to avoid another form.

You could have and state clear rules. For example, the first field that contains "zip" would be the zip code. The first member field that contains "address" but not "email" or "e-mail" would be the street address. This would accommodate many - not all - choices of field names. If our field names didn't work with your rules we'd have the choice of changing them or not enabling the feature.

Then give members a checkbox "Use member's mailing address" on the credit card form. Give admins the ability to enable/disable this.

We are also interested in this functionality. It would be helpful for manual entry as well as for members, etc. when signing up for events or making donations.

We'd even be happy to name our address fields something standardized (e.g. same as Wild Apricot payment page) to get this to work.

Hello! We would also like to see the outcome of this. We take phone calls for registrations and renewals and are charged per minute. Having to re-enter in the address takes me time per call and thus costs us more money. I'll keep checking back to see how this develops. I am glad to see others are interested in it too!

Sure - not knowing your whole architecture makes it hard for me to offer advice; I just wanted to put that out there. :)

That was the first thought in my mind too but I'm kind of reluctant to add one more setting screen (especially with fields mapping) - it's too technical and complicated to understand in general.

Though thanks for the comments.

If it's a matter of mapping and every user name have different field names for their addresses, etc, it seems pretty easy - just give them a setting/interface to map their address fields to the CC charge address fields. Then just turn that admin interface on/off based on whether they can charge CC or not.

It's a good point, thank you. Actually, we just introduced the ability to charge CC through WA and we agree that it's not ideal yet. We implemented fast and easy solution - give administrator same interface as for member.

Your suggestion is very logical but the problem is in fields mapping - to make pre-population possible, we have to find a way to map your contact database fields to credit card screen fields. Unfortunately, it's almost not possible to make it automatically - Wild Apricot (as a system) does not know which of your fields are address fields (they can be named differently). There are different ways of resolving this problem, we will consider them as soon as we can (not soon, sorry).

Or may be I'm missing something obvious here and somebody can suggest quick and easy idea for automatic mapping?

We use Paypal Payflow Pro to process online payments, but when a member tries to pay by credit card, they are asked to enter the card info as well as the billing address.

Would you be able to add the option to take their mailing address registered within the WA hosted site and send it to the Paypal page (like a check box that we often see in shopping carts, i.e. "Check here if billing is same as shipping address") so they do not need to type in their full address every time they register for an event?

I do understand Paypal is controlling the process, so it is not easy to link the two, but I am hoping it can be done one day.

Thank you!

We've recently upgraded to PayPal Pro so we can charge CCs through Wild Apricot. The problem right now is that it needs the address entered when entering the card info.

At an event, I'd like to be able to get the card info (via old-fashioned knucklebuster imprint) and then manually run the card later. But as it is, I also have to get the full address when I get the card info, and it's going to slow walk-in registration considerably.

If the system could auto-populate the registrant's address in the fields when I go to charge the card, it would save a ton of time and allow for smoother registrations. I can always go back and call someone on the off chance that the address didn't match the card and I couldn't process it.

Please let me know if this is possible.