Square Payment Integration: ability to populate more user fields in Square integration

I want to populate more fields in Square Customer Directory from the form when the customer signs up for my beer club. Birthday and phone-number, specifically. I also want the Group attribute in Square to be assigned the same fixed value of "Beer Club" when a customer signs up. How can I pass these values through to Square using your integration?

We would like to apologize for any inconvenience. I'm afraid that the feature you are looking for in our Square payment field isn't available. The Square integration settings only have the following Additional Gateway Settings.

To my understanding, what you are looking for is similar to what our Authorize.Net and Stripe payment integrations offer.

But if what you are looking for to use is Square, we can forward a feature request to our developers on your behalf. However, we cannot guarantee that it will be implemented anytime soon.

Feel free to let us know if you need any further assistance.

Yes, please make it a feature request. And include your insight from the Authorize.net example. On the Square dashboard side of things, your current method creates an Item and a Customer, but the transaction is no different than a purchase for any old item. And your side manages the 'recurring payments' aspect.

This really should be EMPHASIZED when telling people about your Square 'recurring payments' integration. I've read the threads and that really is the source of the confusion. People fill out a form in testing, then got look in their Square Dashboard for what the 'think' should be set up: which is a recurring Square Invoice, or a Square Subscription, neither of which you currently do.

Where you're missing the mark is that Square Invoices are what should be getting created and set to recur within the Square framework. And definitely add the ability to tap into more Customer identifying fields.

I wouldn't bother exploring the Square Online Payments route. That has the 'Subscriptions' in it as an option, but it is too clunky in my opinion. Better to stick with Invoices and Customer API.

Thank you for the additional details.

We will now escalate this feature request to our developer's team for further review. Please note that we cannot guarantee when this feature will be implemented nor can we guarantee if it will be implemented at all.

However, our developers will take a look and take this feature into consideration. If we decide to implement the feature changes, we will inform you immediately.

Thank you for your patience and understanding, we will be in touch shortly.