Title: Square Terminal SAVE_CARD for Automatic Monthly Memberships

Questions
1

Message:

We operate Boopertone Tanning Salon and have developed our own membership management application using Square.

Our Square Terminal is successfully paired in production, its software is up to date, and our production webhooks include terminal.action.updated and terminal.checkout.updated.

We want customers to tap or insert their cards into our Square Terminal during signup, securely save those cards with Square, and authorize automatic monthly membership payments.

Could you please confirm:

  1. Is Terminal API SAVE_CARD available for production use in the United States without special beta approval?
  2. If approval is required, how do we request it?
  3. What additional permissions or configuration do we need?
  4. Can customers without email addresses use this feature?

We want to verify everything before accepting live payments.

Thank you!

3
  1. SAVE_CARD is a Beta Terminal action, and the US is a supported market. The Terminal API itself needs no special access.
  2. You don’t need to request approval.
  3. Make sure your access token has the following scopes: PAYMENTS_WRITE, PAYMENTS_READ, CUSTOMERS_READ and CUSTOMERS_WRITE.
  4. Yes. A customer profile only needs one of name, company, email or phone, so an email address isn’t required.

See the following guide for more details: Save a Card on File with the Terminal API .