I would like an enhancement of the bundle admin/member rights setup. I would like to have all members of a bundle be able to pay the yearly dues. As it is now only one member, the admin, has access to the invoice payment portal through the member profile. In my experience the person who is attempting to pay may randomly be the non admin and they will run into a roadblock in the member profile and not know why they cannot pay. The fallback is that they write a check and mail it to me which is the situation that the website was created to alleviate.
An easy solution (possibly) is to simply give all bundle members the rights that would allow them to see the "pay invoice" button in their profile. No matter which bundle member pays, the status changes to active which prevents other bundle members from double paying.
To address the alternative of "why doesn't the other member pay"? The answer is that my "bundles" are actually homes in a development containing husbands and wives who are both members and who both have busy lives of their own. I am lucky if they take 5 min. to address this issue. They are not going to try to understand the rules of programming logic or try to figure out work arounds, and they shouldn't have to. Paying dues should be an easy task for my members and not an exercise in technology. I hope you can help me with this.

Thank you.

When credit cards are processed in person using the Affinipay Mobile Swiper and the Admin app, the credit card billing address should not be required as the "Card Present" is verification enough, in addition to the input of the CCV.

Today, the platforms requires the billing address for all credit cards, with no requirement to turn that off. However, Affinipay does not require this for cases where credit card is present for the transaction. The organization should have the opportunity to disable this setting.

We process guest fees to our events as well as raffle ticket sales. The billing address requirement is a barrier as event attendees will not want to enter billing address for a $5 or $10 charge. This is made worse by some attendees previously having entered an address when performing an online payment, but that value does not pre-populate, forcing them to enter billing address or experience a declined card transaction.

At the very least, an organization should be able to disable the billing address for a card present transaction, but also should be given the option to disable for online transactions if so desired, and/or force zip code only (on both the above requirements).

Add instructions for the correct format of the postal code:

If a certain postal code format is accepted, and the other formats cause errors, this needs to be made clear to the customer when they are paying. I've had so much frustration having customers contact me when they are not able to process payments and it's often a browser or postal code format issue.

Customers should have access to info that allows them to easily see the accepted format and info that they can use to troubleshoot so that they don't get so frustrated.

This issue has taken up so much of my time because I'm the one who ends up trying to troubleshoot things and has lost me customers.

I converted to Wild Apricot Payments/Affiinipay a couple of months ago and so far have not experienced any issues and actually like gateway better than Paypal. That being said, I have one request... when the Affinipay payment page is displayed there does not appear to be any method of including our business logo on the page.

My preferred solution would be to integrate the Affinipay payment page within our website template as an "iframe" or create a "gadget" so the header and footer for our webdsite would always be displayed and the "theme" of the website is maintained.

Currently the Affinipay payment page displays the name of our organization and the payee has the impression they have navigated away from our website to a third party site not much different than how paypal worked (except they do not have to login or have an Affinipay account).. There needs to at least include the ability to add our logo and include a custom message.

Currently, a member level fee is required to enable automatic recurring payments, even when there is a required extra cost. In other words, if the "level fee" is set to $0.00, then the option of recurring payments for Extra Charges is not even available.

Our dues are based on Tiers and it works best by using Required Radio Buttons to represent the Tier Options. We've tried several workarounds, but the best for us is to make the Member Level fee one penny (0.01) and the explain why there is an extra one cent cost of membership.

It would be really helpful if the determining criterion for Automatic Recurring Payments was based on a total of level fee AND extra cost used for renewal, AND is greater than $0.00.

This would greatly improve flexibility for designing Membership Levels.

Create the ability to support multiple payment systems at the same time with the ability to assign a payment type to a given payment system. This would solve the issue of having only one configured payment system which does not support a payment type you need. We need to have PayPal, credit cards and bank transfers at a minimum. As we are based in Europe, it seems the best option is PayPal Express Checkout. It supports all 3, but we have members who refuse to use PayPal and will not create a PayPal account. Using a bank account requires the member to create a PayPal account. Some will not even use the credit card option because they refuse to use PayPal at all. We either need a supported payment system which supports PayPal in addition to credit cards and bank transfers with no signup required, or the ability to configure multiple payment systems. Supporting multiple payment systems is the preferred option and would solve most of the feature requests for payment systems.