Configuration: Square SDK Upgrade

Overview

The Square Web Payments SDK is a JavaScript browser-client SDK that provides a secure payment-card entry method, along with other secure payment methods. The SDK is the client part of the client/server Square payment solution. The SDK produces a secure one-time-use payment token that the application web client sends to the backend, where it is processed as a payment with the Square Payments API. Within Aspenware Commerce you will see this change in the card-entry checkout module. The payment module now dynamically changes according to input fields. See below for examples of the payment module changes and admin changes, as well as upgrade and implementation requirements.

Feature Detail

Dynamic Input Validation

Validation for each input field is processed by Square on keystroke, providing real-time feedback to the customer when input errors are detected.

Single Credit Card Element

The Web Payments SDK provides a single credit card element for all credit card inputs. Square no longer supports the positioning of individual credit card fields. Square has found that the single credit card element results in a higher conversion to payment.

Dynamic Postal Code Behavior

The Web Payments SDK shows a postal code input field on the payment form after the SDK determines the country that issued the buyer's credit card. The Web Payments SDK displays the proper form label for the postal code based on the country:

  • For US, the form displays "ZIP".

  • For CA, the form displays "Postal Code".

  • For UK, the form displays "Postcode".

If the payment form displays the postal code field, then the payment requires a postal code for the buyer to proceed. The Web Payments SDK enforces input field validation for the postal code depending on the country.

Configuration Guide

Setup Checklist

1. COMMERCE TASKS

 

1. COMMERCE TASKS

 

  1. Confirm Square Plugin Configuration. required

  2. Obtain Access Token (if in a stage environment). optional

  3. Check Location ID and Update if needed. REQUIRED

  4. Switch to the production environment. required

Detailed Setup

Detailed Setup Guide

  1. Confirm Square Plugin Configuration.

  2. Obtain Access Token (if in a stage environment)

  3. Check Location ID and Update if needed

  4. Switch to the production environment

NOTE: Because a new Square payment token may be required, this upgrade may require some downtime.

This SDK Upgrade may require steps to be taken by the resort while deploying and in communication with your Aspenware Service Representative (support@aspenware.com).

1. Confirm Square Plugin Configuration

  • Go to Configuration > Payment methods in Commerce Admin

  • Select Configure in the Square Payment Gateway plugin.

2. Obtain Access Token (if in a stage environment)

  • Follow the instructions for “Obtain Access Token” in this document.

  • Click APPROVE when requested to “Accept New API”.

3. Check Location ID and Update if needed

  1. If your location ID is no longer present, do the following:

3. Switch to the Production Environment

Common Troubleshooting Guide

Q: My credit card input UI looks different and I no longer see the zip code field.

A: The new credit card module is dynamic, which means depending on the resort location and the credit card provider and location, different fields will be shown. The best practice would be to test with credit cards from different locations.