diff --git a/includes/classes/vendors/square/connect/.gitignore b/includes/classes/vendors/square/connect/.gitignore
deleted file mode 100644
index c74952daa5..0000000000
--- a/includes/classes/vendors/square/connect/.gitignore
+++ /dev/null
@@ -1,4 +0,0 @@
-vendor
-composer.lock
-composer.phar
-travis-ci/accounts.json
diff --git a/includes/classes/vendors/square/connect/.release b/includes/classes/vendors/square/connect/.release
deleted file mode 100644
index cb52eb32bf..0000000000
--- a/includes/classes/vendors/square/connect/.release
+++ /dev/null
@@ -1 +0,0 @@
-Release 3.20200528.1
diff --git a/includes/classes/vendors/square/connect/.version b/includes/classes/vendors/square/connect/.version
deleted file mode 100644
index b012b54f7c..0000000000
--- a/includes/classes/vendors/square/connect/.version
+++ /dev/null
@@ -1 +0,0 @@
-3.20200528.1
diff --git a/includes/classes/vendors/square/connect/CHANGES.md b/includes/classes/vendors/square/connect/CHANGES.md
deleted file mode 100644
index a95cc74d41..0000000000
--- a/includes/classes/vendors/square/connect/CHANGES.md
+++ /dev/null
@@ -1,656 +0,0 @@
-# Change Log
-
-## Version 3.20200528.1 (2020-05-28)
-## Square SDK - PHP
-Square is excited to announce the public release of customized SDK for PHP
-
-To align with other Square SDKs generated for SQUARE API version 2020-05-28, the initial version of this PHP SDK is 5.0.0.20200528
-
-## Version 3.20200528.0 (2020-05-28)
-## API releases
-
-* Loyalty API (beta):
- * For an overview, see [Loyalty Program Overview](https://developer.squareup.com/docs/loyalty/overview).
- * For technical reference, see [Loyalty API](https://developer.squareup.com/reference/square/loyalty-api).
-
-## Existing API updates
-
-* Orders API
- * [CalculateOrder (beta)](https://developer.squareup.com/reference/square/orders-api/calculate-order) endpoint. Use the endpoint to calculate adjustments (for example, taxes and discounts) to an order for preview purposes. In response, the endpoint returns the order showing the calculated totals. You can use this endpoint with an existing order or an order that has not been created.
- The endpoint does not update an existing order. It only returns a calculated view of the order that you provided in the request. To create or update an order, use the [CreateOrder](https://developer.squareup.com/reference/square/orders-api/create-order) and [UpdateOrder](https://developer.squareup.com/reference/square/orders-api/update-order) endpoints, respectively.
- * [Order](https://developer.squareup.com/reference/square_2020-05-28/objects/Order) type. Two fields are added in support of the Loyalty API integration. For more information, see [Deferred reward creation](https://developer.squareup.com/docs/loyalty-api/overview#deferred-reward-creation). For an example, see [Redeem Points](https://developer.squareup.com/docs/loyalty-api/walkthrough1/redeem-points).
- * `Order.rewards` represents rewards added to an order by calling the [CreateLoyaltyReward](https://developer.squareup.com/reference/square/loyalty-api/create-loyalty-reward) endpoint.
- * `Order.discount.reward_ids` indicates that a discount is the result of the specified rewards that were added to an order using the `CreateLoyaltyReward` endpoint.
-
-* Customers API
- * The [Search Customers](https://developer.squareup.com/reference/square/customers-api/search-customers) endpoint supports search by email address, phone number, and reference ID with the following additional query filters:
- * The [`email_address` query filter](https://developer.squareup.com/docs/customers-api/cookbook/search-customers#search-by-email-address) (beta) supports an [exact](https://developer.squareup.com/docs/customers-api/cookbook/search-customers#exact-search-by-email-address) or [fuzzy](https://developer.squareup.com/docs/customers-api/cookbook/search-customers#fuzzy-search-by-email-address) search for customer profiles by their email addresses.
- * The [`phone_number` query filter](https://developer.squareup.com/docs/customers-api/cookbook/search-customers#search-by-phone-number) (beta) supports an [exact](https://developer.squareup.com/docs/customers-api/cookbook/search-customers#exact-search-by-phone-number) or [fuzzy](https://developer.squareup.com/docs/customers-api/cookbook/search-customers#fuzzy-search-by-phone-number) search for customer profiles by their phone numbers.
- * The [`reference_id` query filter](https://developer.squareup.com/docs/customers-api/cookbook/search-customers#search-by-reference-id) (beta) supports an [exact](https://developer.squareup.com/docs/customers-api/cookbook/search-customers#exact-search-by-reference-id) or [fuzzy](https://developer.squareup.com/docs/customers-api/cookbook/search-customers#fuzzy-search-by-reference-id) search for customer profiles by their reference IDs.
- * The [`created_at`](https://developer.squareup.com/reference/square/objects/Customer#definition__property-created_at), [`updated_at`](https://developer.squareup.com/reference/square/objects/Customer#definition__property-updated_at), and [`id`](https://developer.squareup.com/reference/square/objects/Customer#definition__property-id) attributes on the [Customer](https://developer.squareup.com/docs/S%7BSQUARE_TECH_REF%7D/objects/customers) resource are updated to be optional. As a result, they no longer are required input parameters when you call the Square SDKs to create a `Customer` object. You might need to update the dependent SDKs to the latest version to mediate breaking your existing code.
-
-
-## Square Webhooks
-
-* [Square Webhooks](https://developer.squareup.com/reference/square_2020-05-28/webhooks) (formerly v2 Webhooks). The status is changed from beta to general availability (GA).
-* [v1 Webhooks](webhooks-api/v1-tech-ref). The v1 Inventory and Timecards webooks are now deprecated and replaced by [inventory.count.updated](https://developer.squareup.com/reference/square_2020-05-28/webhooks/inventory.count.updated) and [labor.shift.updated](https://developer.squareup.com/reference/square_2020-05-28/webhooks/labor.shift.updated).
-
-
-
-## Version 3.20200422.2 (2020-04-25)
-## Existing API updates
-
-* **OAuth API**
- * [Obtain Token](https://developer.squareup.com/reference/square/oauth-api/revoke-token) endpoint: Removed the `scopes` property from the request body.
-
-
-## Version 3.20200422.1 (2020-04-22)
-## API releases
-* **Customer Segments API (beta).** `limit` field removed from **ListCustomerSegments** endpoint.
-
-
-**Note:** This release fixes a bug introduced on the [April 22, 2020](changelog/connect-logs/2020-04-22) release of the Square API.
-
-
-## Version 3.20200422.0 (2020-04-22)
-## API releases
-* **Terminal API.** The new Terminal API lets a custom third-party POS app integrate with the Square Terminal to send terminal checkout requests to collect payments.
- * For an overview, see [Overview](/terminal-api/overview).
- * For technical reference, see [Terminal API](https://developer.squareup.com/reference/square/terminal-api).
-
-* **Devices API.** The new Devices API lets a custom third-party POS app generate a code used to sign in to a Square Terminal to create a pairing that lets the POS app send terminal checkout requests. For technical reference, see [Devices API](https://developer.squareup.com/reference/square/devices-api).
-
-* **Customer Groups API (beta).** The new Customer Groups API (Beta) enables full CRUD management of customer groups, including the ability to list, retrieve, create, update, and delete customer groups. Previously, this functionality was only available through the Square dashboard and point-of-sale product interfaces.
- * For an overview, see [Overview](/customer-groups-api/what-it-does)
- * For technical reference, see [Customer Groups](https://developer.squareup.com/reference/square/customer-groups-api).
-
-* **Customer Segments API (beta).** The new Customer Segments API (Beta) lets you list and retrieve customer segment (also called smart groups) information. Coupled with the new `segment_ids` field on the customer resource, this API lets you better understand and track the customer segments to which a customer belongs.
- * For an overview, see [Overview](/customer-segmentss-api/what-it-does)
- * For technical reference, see [Customer Segments]( https://developer.squareup.com/reference/square/customer-segments-api).
-
-
-* **New webhooks.** v2 Webhooks (beta) now supports webhooks for the following APIs:
- * Orders API. `order.created`, `order.updated`, and `order.fulfillment.updated`
- * Terminal API. `terminal.checkout.created` and `terminal.checkout.updated`
- * Devices API. `device.code.paired`
-
- For more information, see [Subscribe to Events](webhooks-api/subscribe-to-events).
-
-## Existing API updates
-* **Customers API**
- * [AddGroupToCustomer](https://developer.squareup.com/reference/square/customers-api/add-group-to-customer) endpoint. Added to add customer memberships to a customer group.
- * [RemoveGroupFromCustomer](https://developer.squareup.com/reference/square/customers-api/remove-group-from-customer) endpoint. Added to remove customer memberships from a customer group.
- * [Customer](https://developer.squareup.com/reference/square/obects/Customer) object. Updated as follows:
- * [`group_ids`](https://developer.squareup.com/reference/square/obects/Customer#definition__property-group_ids) field. Added to designate groups the customer is in.
- * [`segment_ids`](https://developer.squareup.com/reference/square/obects/Customer#definition__property-segment_ids) field. Added to designate segments the customer is in.
- * [`groups`](https://developer.squareup.com/reference/square/obects/Customer#definition__property-groups) field. Deprecated to be replaced by `group_ids` and `segment_ids`. It remains supported for one year from this release.
- * [CustomerQuery](https://developer.squareup.com/reference/square/objects/CustomerQuery) object's `filter` parameter. Updated as follows:
- * `group_ids` filter. Added to search for customers based on whether they belong to any, all, or none of the specified groups.
-
-
-* **Orders API**
- * [OrderFulfillmentPickupDetails](https://developer.squareup.com/reference/square/objects/OrderFulfillmentPickupDetails) type updated to support curbside pickup:
- * `is_curbside_pickup`. This Boolean field indicates curbside pickup.
- * `CurbsidePickupDetails`. This type provides supporting information for curbside pickup, including a buyer description (for example, "buyer is in a red car") and a timestamp when the buyer arrived for the pickup.
-
-
-* **OAuth API**
- * [RevokeToken](https://developer.squareup.com/reference/square/oauth-api/revoke-token) endpoint. Added a new field called [revoke_only_access_token](https://developer.squareup.com/reference/square/oauth-api/revoke-token#request__property-revoke_only_access_token). This field allows a client to revoke an access token but leave the parent authorization active.
- * [ObtainToken](https://developer.squareup.com/reference/square/oauth-api/obtain-token) endpoint. Added a new field called [scopes](https://developer.squareup.com/reference/square/oauth-api/obtain-token#request__property-scopes). This field lets a client change the set of permissions for an access token when making a request to refresh the token.
-
-
-* **Catalog API**
- * [CatalogQuickAmountsSettings](https://developer.squareup.com/reference/square/objects/CatalogQuickAmountsSettings) type. Added to support predefined custom payment amounts in the Square Register checkout dialog box.
- * ENUM`CatalogItemProductType`. The ENUM value `GIFT_CARD` is now deprecated.
-
-* **Payments API.** See [Take Payments and Collect Fees](/payments-api/take-payments-and-collect-fees) for updated information about permission requirements, Square reporting of the application fee collected by an app, and how to collect fees internationally.
-
-
-
-
-
-## Version 3.20200325.0 (2020-03-25)
-## Existing API updates
-* **[Payments API](https://developer.squareup.com/reference/square/payments-api).** In support of the existing [Delayed capture](payments-api/take-payments) for payments, the following fields are added to the [Payment](https://developer.squareup.com/reference/square/objects/Payment) type:
- * `delay_duration`. In a [CreatePayment](https://developer.squareup.com/reference/square/payments-api/create-payment) request, you can set `autocomplete` to false to get payment approval but not charge the payment source. You can now add this field to specify a time period to complete (or cancel) the payment. For more information, see [Delay capture](payments-api/take-payments).
- * `delay_action`. Defines the action that Square takes on the payment when the `delay_duration` elapses. In this release, the API supports only the cancel payment action.
- * `delayed_until`. Provides the date and time on Square servers when Square applies `delay_action` on the payment.
-
-
-## Version 3.20200226.0 (2020-02-26)
-## API releases
-* **GA release**: All SDKs have been updated to support the new Bank Accounts and CashDrawerShifts APIs.
-
-* **Beta release**: All SDKs have been updated to support the new Disputes API.
-
-
-## Existing API updates
-
-All SDKs have been updated to support the following changes:
-
-* **Catalog API**
- * Batch upsert catalog objects endpoint — The `batches` field is now required and the array must have at least one element.
- * CatalogModifier — Two fields added:
- * `ordinal` to support custom ordering in a modifier list
- * `modifier_list_id` to reference the parent modifier list
- * CatalogModifierList — New field added: `ordinal` to support custom ordering in a list of **CatalogModifierList** objects.
-
-* **Customers API changes**
- * SearchCustomers endpoint — `limit` size reduced from 1000 to 100 to improve the endpoint performance.
-
-* **Orders API changes**
- * CreateOrderRequest — Previously these request fields were deprecated: `line_items`, `taxes`, `discounts`. These fields are no longer available. Instead you now use the `Order` object in the request. For example, `Order.line_items`, `Order.taxes`, and `Order.discounts`.
- * OrderLineItem type — There are two changes:
- * The `taxes` field that was previously deprecated is no longer available. Instead, you now use the `OrderLineItem.applied_taxes` field. This also now requires that you set the `OrderLineItemTax.scope` field.
- * The `discounts` field that was previously deprecated is no longer available. Instead, you now use the `OrderLineItem.applied_discounts` field. This also now requires that you set the `OrderLineItemDiscount.scope` field.
-
-* **Shared object updates**
- * **Card object** — New fields added: `card_type`, `prepaid_type`. Currently, only the Payments API responses populate these fields.
-
-## Version 2.20200122.1 (2020-02-12)
-**Documentation Changes**
-
-* Minor updates for Payments API descriptions
-* Deprecation & retirement dates added for Transactions API endpoints
-
-
-## Version 2.20200122.1 (2020-02-04)
-* Addresses bug that doesn't allow `getV1BatchTokenFromHeaders` to retrieve batch_token
-
-## Version 2.20200122.0 (2020-01-22)
-* New field: The **Employee** object now has an `is_owner` field.
-* New field: The **Card** enumeration has a new `SQUARE_CAPITAL_CARD` enum value to support a Square one-time Installments payment.
-
-* New request body field constraint: The **Refund Payment** request now required a non-empty string when the `payment_id` is supplied.
-
-
-## Version 2.3.0.20191217 (2019-12-17)
-!!!important
-Square is excited to announce the public release of customized SDKs for [Java](https://github.com/square/square-java-sdk) and [.NET](https://github.com/square/square-dotnet-sdk). For more information, see [Square SDKs](/sdks).
-!!!
-
-* __GA release:__ SDKs updated to support new `receipt_url` and `receipt_number` fields added to the [Payment](https://developer.squareup.com/reference/square/objects/Payment) type.
-
-* __Beta release:__ SDKs updated to support the new [CashDrawerShifts](cashdrawershift-api/reporting) API.
-
-* Square now follows the semantic versioning scheme that uses three numbers to delineate MAJOR, MINOR, and PATCH versions of our SDK. In addition, the SDK version also includes the API version so you know what Square API version the SDK is related to. For more information, see [Versioning and SDKs](build-basics/versioning-overview#versioning-and-sdks).
-
-
-## Version 2.20191120.0 (2019-11-20)
-!!!important
-Square has begun the retirement process for Connect v1 APIs. See the [Connect v1 Retirement](/migrate-from-v1) information page for details.
-!!!
-
-* __GA releases:__ SDKs now support the new `modify_tax_basis` field to Discounts and v2 Sandbox
-* __BETA releases:__ SDKs now support the Shifts API webhooks for Labor shift created, updated, deleted, CreateLocation endpoint, and the ability to customize statement description in Payments API.
-* **Deprecated**: Support for v1Items API and v1Locations API is fully deprecated.
-
-
-
-
-## Version 2.20191023.0 (2019-10-23)
-* **GA release**: Merchants.ListMerchant is GA for all SDKs.
-* **Beta release**: All SDKs support new Locations API endpoint, CreateLocation.
-* **Beta release**: All SDKs support exclusion strategies for pricing rules.
-
-
-## Version 2.20190925.0 (2019-09-25)
-
-* **GA release**: All SDKs have been updated to support the new Merchants API.
-
-* **Beta release**: All SDKs have been updated to support the new endpoints (RetrieveLocation, UpdateLocation) added to the Locations API.
-
-* **Beta release**: All SDKs have been updated to support the new field (`mcc`) added to the `Location` type.
-
-* **GA release**: All SDKs have been updated to support the new field (`bin`) added to the `Card` type.
-
-* **GA release**: All SDKs have been updated to support the new `CardPaymentDetails` fields (`verification_results`, `statement_description`, and `verification_method`).
-
-* **GA release**: All SDKs have been updated to support the new `Payment` field, (`employee_id`).
-
-
-## Version 2.20190814.2 (2019-08-23)
-
-* **Bug fix**: Fixed path parameters for `UpdateOrder`
-
-## Version 2.20190814.1 (2018-08-16)
-
-* **Bug fix**: Removed a currentlyunsupported API object type
-## Version 2.20190814.0 (2019-08-15)
-
-* **New functionality**: All SDKs have been updated to support the Sandbox v2 BETA release
-* **Deprecated functionality**: All Transactions API functionality is deprecated in favor of Payments API and Refunds API functionality.
-* **New functionality**: All SDKs have been updated to support the Payments API GA.
-* **New functionality**: All SDKs have been updated to support the Refunds API GA.
-* **New functionality**: All SDKs have been updated to support Orders API updates:
- * Pickup Fulfillments, SearchOrders, and ServiceCharges move from BETA to GA.
- * New BETA endpoint: Orders.UpdateOrder — use the UpdateOrder endpoint to update existing orders.
- * New BETA functionality: Create shipment-type fulfillments.
-* **New functionality**: Locations.RetrieveLocation — use the RetrieveLocation endpoint to load details for a specific Location.
-
-## Version 2.20190724.0 (2019-07-24)
-
-* **BETA releases**:
- * Catalog API: supports item options with datatypes and enums for item options and item option values.
-
-## Version 2.20190710.0 (2019-07-10)
-
-* **Retired functionality** — The `CatalogItem.image_url` field (deprecated under `Square-Version` YYYYMMDD) is retired and no longer included in Connect SDKs.
-
-## Version 2.20190612.1 (2019-06-26)
-
-* **Bug fix**: `Transaction.Charge` and `Customers.CreateCustomerCard` request objects — now include the `verification_token` required for [Strong Customer Authentication](https://developer.squareup.com/docs/sca-overview).
-
-## Version 2.20190612.0 (2019-06-12)
-
-* **BETA releases**:
- * Orders API: supports service charges with a new field and datatype.
- * Catalog API: supports measurement unites for item variation quantities with a new field and datatype.
-* **New functionality**: `Order` entities — now include a `source` field that contains details on where the order originated.
-* **Improved functionality**: ListLocations — Expanded business information available through the Locations API, including business hours, contact email, social media handles, and longitude/latitude for physical locations.
-
-## Version 2.20190508.0 (2019-05-08)
-
-## Details
-
-* **Beta functionality**: Orders API — support for fractional quantities,
- expanded metadata, and embedded information on payments, refunds, and returns.
-* **Beta functionality**: Inventory API — support for fractional quantities.
-* **New functionality**: `Locations.business_hours` — read-only field with
- information about the business hours at a particular location.
-
-## Version 2.20190410.1 (2019-04-24)
-
-## Details
-
-* **New functionality**: Employees API (Connect v2) — New fields to
- capture contact information for employee profiles.
-* **New functionality**: `V1Tender.CardBrand` — New V1 enum to represent
- brand information for credit cars.
-
-## Version 2.20190410.0 (2019-04-10)
-
-## New features: Orders API beta
-
-* The Connect v2 Orders object now includes an OrderSource field (`source`)
- that encapsulates the origination details of an order.
-
-## Improvement: Connect v2 Catalog IDs in Connect v1 objects
-
-* The following Connect v1 data types now include a `v2_id` field that makes it
- easier to link information from Connect v1 endpoints to related Connect v2
- Catalog objects:
- * V1Discount
- * V1Fee
- * V1Item
- * V1ModifierList
- * V1ModifierOption
- * V1Variation
-
-## Version 2.20190327.1 (2019-03-29)
-
-## Bug Fix: Catalog API
-* Add `image_id` to `CatalogObject`
-
-## Version 2.20190327.0 (2019-03-27)
-
-## New features: Catalog API
-* Deprecated `image_url` field in `CatalogItem` in favor of a richer
- `CatalogImage` data type.
-* Image information is now set, and returned, at the `CatalogObject` level.
-
-## Version 2.20190313.1 (2019-03-21)
-
-### Bug Fix: Connect v1
-
-* Change `timecard_id` as path parameter for `ListTimecardEvents` endpoint
-* Change `ended_at` to string type for `V1CashDrawerShift` type
-
-## Version 2.20190313.0 (2019-03-13)
-
-## New API: Labor API
-
-The Labor API now includes functionality
-that gives a Square account the ability to track and retrieve employee labor hours
-including multiple hourly wage rates per employee, work shift break tracking, and
-standardized break templates.
-
-See the Connect v2 Technical Reference.
-
-## New API: Employees API
-
-The Employees API includes the ability to list employees for a Square
-account and retrieve a single employee by ID.
-
-See the Connect v2 Technical Reference.
-
-## Improvement: Simplified OAuth access token renewal
-
-The RenewToken endpoint is now deprecated and replaced with new functionality in ObtainToken.
-ObtainToken now returns a refresh token along with an access token. Refresh
-tokens are used to renew expired OAuth access tokens.
-
-## Version 2.20190213.0 (2019-02-13)
-
-## New feature: Order fulfillment BETA
-
-The Orders API now includes beta
-functionality that supports in-person fulfillment through Square Point of Sale
-for orders placed online.
-
-## Improvement: New CreateOrder request structure
-
-The `CreateOrderRequest` datatype now groups order details under a single
-object.
-
-
-## Improvement: CreateOrder requests preserve order-level price adjustment objects
-
-The `CreateOrderResponse` datatype now retains structure of order-level
-price adjustments in addition to converting them to scoped, line-item price
-adjustments. Previously, `CreateOrderResponse` did not preserve the original
-order-level price-adjustment objects.
-
-## Version 2.20181212.0 (2018-12-12)
-
-## Improvement: ListCustomers return set expanded
-
-Requests to the ListCustomers endpoint now returns all available customer profiles. Previously, ListCustomers only returned customer profiles explicitly created through the Customers API or Square Point of Sale.
-
-## Version 2.20181205.0 (2018-12-05)
-
-## New feature: Idempotent customer profile creation in Connect v2
-
-Requests to the CreateCustomer endpoint now include a `idempotency_key` field to
-ensure idempotent creation of new profiles.
-
-## New feature: Refund Adjustment fields for Refunds in Connect v1
-
-The Connect SDK now supports refund adjustments for the Connect v1
-Refunds API with the addition of multiple new fields in the `Refund` data type
-
-## Version 2.20180918.1 (2018-10-24)
-
-### New feature: Support for Partial Payments in Connect v1
-
-The Connect SDK now supports partial payment functionality for the Connect v1 Transactions API with the addition of a new `Payment` field:
-* `Payment.is_partial` — Indicates whether or not the payment is only partially paid for. If `true`, the payment will have the tenders collected so far, but the itemizations will be empty until the payment is completed.
-
-`Tender` also includes 2 new fields to help resolve timing around payments with multiple tenders. Invoices that involve partial payment (e.g., requiring a deposit) may include tenders settled well before the entire payment is completed:
-* `Tender.tendered_at` — The time when the tender was accepted by the merchant.
-* `Tender.settled_at` — The time when the tender was captured, in ISO 8601 format. Typically the same as (or within moments of) `tendered_at` unless the tender was part of a delay capture transaction.
-
-The change also makes some behavioral changes to the Connect v1 Payment endpoints:
-* **Create Refunds** rejects requests for invoices that have partial payments pending.
-* **List Payments** takes a new request field, `include_partial` to indicate whether partial payments should be included in the response.
-
-## Version 2.20180918.0 (2018-09-18)
-
-We have added Connect v2 Inventory API and birthdays in `Customer` entities.
-
-### New API: Inventory API (Connect V2)
-
-The Connect v2 Inventory API replaces the Connect v1 Inventory API
-and introduces new functionality:
-
-* Moving item variations quantities through predefined states
- (e.g., from `IN_STOCK` to `WASTE`).
-* Viewing the inventory adjustment history for an item variation.
-* Batch inventory adjustments and information retrieval.
-
-### New feature: Customer Birthdays (Connect V2)
-
-* Customer profiles now include a `birthday` field.
- Dates are recorded in RFC-3339 format and can be
- set through the `CreateCustomer` and `UpdateCustomer` endpoints.
-## Version 2.20180712.2 (2018-08-21)
-
-The Connect SDK now includes functionality for the OAuth API. The Square OAuth API lets applications request and obtain permission from a Square account to make API calls on behalf of that account. Applications can request individual permissions so that users do not need to grant full access to their Square accounts.
-
-### OAuth API
-
-* `ObtainToken` endpoint — Exchanges the authorization code for an access token. After a merchant authorizes your application with the permissions form, an authorization code is sent to the application's redirect URL (See [Implementing OAuth](https://docs.connect.squareup.com/api/oauth#implementingoauth) for information about how to set up the redirect URL).
-
-* `RenewToken` endpoint — Renews an OAuth access token before it expires. OAuth access tokens besides your application's personal access token expire after __30 days__. You can also renew expired tokens within __15 days__ of their expiration. You cannot renew an access token that has been expired for more than 15 days. Instead, the associated merchant must complete the [OAuth flow](https://docs.connect.squareup.com/api/oauth#implementingoauth) from the beginning. __Important:__ The `Authorization` header you provide to this endpoint must have the following format: ``` Authorization: Client APPLICATION_SECRET ``` Replace `APPLICATION_SECRET` with your application's secret, available from the [application dashboard](https://connect.squareup.com/apps).
-* `RevokeToken` endpoint — Revokes an access token generated with the OAuth flow. If a merchant has more than one access token for your application, this endpoint revokes all of them, regardless of which token you specify. If you revoke a merchant's access token, all of the merchant's active subscriptions associated with your application are canceled immediately. __Important:__ The `Authorization` header you provide to this endpoint must have the following format: ``` Authorization: Client APPLICATION_SECRET ``` Replace `APPLICATION_SECRET` with your application's secret, available from the [application dashboard](https://connect.squareup.com/apps).
-
-## Version 2.20180712.1 (2018-08-02)
-
-We have added MobileAuthorization API.
-
-### New endpoint: MobileAuthorization API
-
-* `CreateMobileAuthorizationCode` endpoint — Generate a mobile authorization code for an instance of your application. Mobile authorization credentials permit an instance of your application to accept payments for a given location using the Square Reader SDK. Mobile authorization codes are one-time-use and expire shortly after being issued.
-
-## Version 2.20180712.0 (2018-07-12)
-
-We introduce Square API versions. `Square-Version` is 2018-07-12 for this SDK.
-
-### How versioning works
-
-Square API versions (`Square-Version`) track changes in the evolution of Connect
-v2 APIs. The `Square-Version` naming scheme is `YYYY-MM-DD`, which indicates
-the date the version was released. Connect v1 APIs are not versioned. Square
-continues to support Connect v1, but future releases will focus on improving
-Connect v2 functionality.
-
-By default, new Square applications are pinned to the version current at the
-time the application was created in the Square Application Dashboard. Pinning an
-application sets the default `Square-Version` for the application. The default
-`Square-Version` of an application can be reviewed and updated at any time on
-the settings pages for the application.
-
-
-### Versioning and SDKs
-
-When a new `Square-Version` is released, new Connect SDKs are publish on GitHub
-and various package management systems. SDK updates follow the version
-convention of the associated language and manager but include the related
-`Square-Version` in the SDK version. For example, Connect SDKs tied to version
-`2018-01-04` might look like `{SDK_VERSION}.20180104.{VERSION_INCREMENT}`.
-
-While SDK versions can be mapped to a related Square-version, SDK versions
-follow an independent, incremental versioning scheme to allow updates and
-improvements to the SDKs outside of `Square-Version` updates.
-
-
-### Migrating to new versions
-
-In most cases, Square-version migration should be straightforward, with known
-differences listed in the related Change Log.
-
-To test migrations, developers can override the default `Square-Version` of an
-application by explicitly setting the preferred `Square-Version` in the HTTP
-header of the Connect v2 API request for REST calls. Requesting an API version
-that does not exist returns an error. Successful API responses include the
-`Square-Version` header to indicate the API version used to process request.
-
-Connect SDK versions are locked to specific API versions and cannot be
-overwritten. Instead, the SDK must be upgraded to work with new API versions.
-
-## Version 2.9.0 (2018-06-28)
-
-We have added search functionality to the Connect v2 Customer API.
-
-### New features and Improvements: Customer API (Connect v2)
-
-* `SearchCustomers` endpoint — retrieves groups of customer profiles
- based on a related characteristic. For example, retrieving all customers
- created in the past 24 hours.
-* `creation_source` field is now available on `Customer` entities. The creation
- source exposes the process that created a customer profile. For example, if
- a customer is created using the API, the creation source will be
- `THIRD_PARTY`.
-* **Instant Profiles** are now exposed in the following endpoints:
- `RetrieveCustomer`, `SearchCustomers`, `UpdateCustomer`, `DeleteCustomer`.
-
-### Fixes: Inventory SDK (Connect v1)
-
-* Fix SDK request property `adjustment_type` in V1 Adjust Inventory.
-
-## Version 2.8.0 (2018-05-24)
-
-We have added sorting functionality to the Connect v2 Customer API, updated
-the Connect v1 Payments API to include information about surcharges and
-improvements to the Item data type.
-
-### New feature: Customer API (Connect v2)
-
-* **ListCustomers** endpoint — now provides the ability to sort
- customers by their creation date using the `sort_field` and
- `sort_order` parameters.
-
-### New features: Payments API (Connect v1)
-
-The Payments API now returns information about surcharges applied to payments.
-The new functionality introduces the following new data types:
-
-* **SurchargeMoney** datatype — The total of all surcharges applied
- to the payment.
-* **Surcharges** datatype — A list of all surcharges associated with
- the payment.
-* **Surcharge** datatype — A surcharge that is applied to the payment.
- One example of a surcharge is auto-gratuity, which is a fixed-rate surcharge
- applied to every payment, often based on party size.
-
-We are constantly evaluating new languages to add. In the meantime, if the
-language you need is not supported, you can use our
-[Swagger pipeline](<%= articles__client_libraries_path%>#generatingwithswagger)
-to generate a custom SDK or continue sending JSON to the endpoint URLs directly.
-
-### Improvement: Item (Connect v1)
-
-**Item** will now provide two new properties:
-
-* `category_id` — indicates if an item can be added to pickup orders
- from the merchant's online store
-* `available_for_pickup` — indicates the item's category (if any).
-
-## Version 2.7.0 (2018-04-26)
-
-### New features: Transactions API and Payments API
-
-The Transactions API in Connect v2 now includes payment and refund information from exchanges.
-
-* `ListTransactions` now includes payment information from sales and exchanges and refund
-information from returns and exchanges.
-* `ListRefunds` now includes refunds that result from exchanges in addition to partial refunds and
-itemized returns through Square's Point of Sale applications.
-
-The Payments API in Connect v1 now includes payment and refund information from exchanges.
-
-* `ListPayments` now includes refunds that are generated from exchanges to account for the
-value of returned goods.
-* `ListRefunds` now returns an approximate number of refunds (default: 100, max: 200).
-The response may contain more results than the prescribed limit when refunds are made
-simultaneously to multiple tenders in a payment or when refunds are generated from exchanges
-to account for the value of returned goods.
-* `is_exchange` is added to `V1Refund` and `V1Tender`. Refunds and tenders marked in this way
-represent the value of returned goods in an exchange, rather than actual money movement.
-
-## Version 2.6.1 (2018-03-28)
-
-* Updates user-agent header
-
-## Version 2.6.0 (2018-03-27)
-
-### Improvements: Orders API
-
-* `BatchRetrieveOrders` will now return uncharged orders.
-
-### New features: Orders API
-
-* For Catalog-backed line items, setting `CreateOrderRequestLineItem.base_price_money` will now override
- the catalog item variation's price.
-* `CreateOrderRequestModifier`s may now be created ad hoc using the new `name` and `base_price_money` fields.
-
-## Version 2.5.1 (2017-11-10)
-
-* `ordinal` is added to `CatalogItemVariation`
-* `website_url` is added to `Location`
-* `tip_money` is added to `Tender`
-* Changed `object_type` and `placeholder_type` from lists to single values in `V1PageCell` to mirror data model
-
-## Version 2.5 (2017-11-02)
-
-### New features: Transaction API and Reporting API
-
-The Transaction API now supports the following request objects:
-
-* `additional_recipients` — data type representing an additional recipient
- (in other words, a recipient other than the merchant or Square) receiving a
- portion of a tender.
-
-The new Reporting API includes two endpoints that let you pull information about distributions you have received as an additional recipient:
-
-* `AdditionalRecipientReceivables` — returns a list of receivables (across
- all source locations) representing monies credited to the given location ID by
- another Square account using the `additional_recipients` field in a transaction.
-
-* `AdditionalRecipientReceivablesRefunds` — returns a list of refunded
- transactions (across all source locations) related to monies credited to the
- given location ID by another Square account using the `additional_recipients`
- field in a transaction.
-
-## Version 2.4 (2017-09-27)
-
-### New features: Register Domain for Apple Pay
-
-* `RegisterDomain` endpoint activates a domain for use with Web Apple Pay.
-
-### Other Changes
-
-* `Location.type` used to indicate whether or not the location object represents a physical space.
-
-## Version 2.3.1 (2017-09-15)
-
-### New features: Charge Orders
-
-* `Charge` endpoint can charge a specific Order.
-
-## Version 2.3.0 (2017-09-13)
-
-### New features: Orders API
-
-* `CreateOrder` endpoint creates an itemized order which can be referenced in messages to the `Charge` endpoint.
-* `BatchRetrieveOrders` retrieves order objects referenced in one or more transactions based on the provided `order_id`.
-
-**Note:** at this point, `BatchRetrieveOrders only` returns information on paid orders made through Square's eCommerce APIs (Transactions, Checkout).
-
-### Other Changes
-
-* `order` is removed from Transaction
-* `order_id` is added to Transaction
-* `OrderLineItemDiscountType.UNKOWN` renamed to `OrderLineItemDiscountType.UNKOWN_DISCOUNT`
-* `OrderLineItemTaxType.UNKOWN` renamed to `OrderLineItemDiscountType.UNKOWN_TAX`
-* `ChargeRequest.idempotency_key` is restricted to max length 192
-* `ChargeRequest.card_nonce` is restricted to max length 192
-* `ChargeRequest.customer_card_id` is restricted to max length 192
-* `ChargeRequest.reference_id` is restricted to max length 40
-* `ChargeRequest.note` is restricted to max length 60
-* `ChargeRequest.customer_id` is restricted to max length 50
-* `CreateCheckoutRequest.redirect_url` is restricted to max length 800
-* Added `phone_number` and `business_name` to Location
-
-## Version 2.2.1 (2017-08-11)
-
-* Documentation style and links fixes
-* Document Getters and Setters for protected properties
-* Support for pagination on V1 endpoints
-* Include refund detail fields on V1 Refund model
-
-### Version 2.0.2 (2017-01-20)
-
-* Bug Fixes for List Locations endpiont.
-
-### Version 2.0.1 (2017-01-19)
-
-* Add functionality for Square Checkout.
-
-### Version 2.0.0.1 (2016-05-19)
-
-* Improve error messaging for API connection failures.
-
-## Version 2.0.0 (2016-03-30)
-
-* Initial release of the SDK
diff --git a/includes/classes/vendors/square/connect/CONTRIBUTING.md b/includes/classes/vendors/square/connect/CONTRIBUTING.md
deleted file mode 100644
index ac9c96a284..0000000000
--- a/includes/classes/vendors/square/connect/CONTRIBUTING.md
+++ /dev/null
@@ -1,5 +0,0 @@
-Contributing
-============
-
-We are not be accepting bug reports, feature requests, or code contributions to
-this repository.
diff --git a/includes/classes/vendors/square/connect/LICENSE.txt b/includes/classes/vendors/square/connect/LICENSE.txt
deleted file mode 100644
index 7a4a3ea242..0000000000
--- a/includes/classes/vendors/square/connect/LICENSE.txt
+++ /dev/null
@@ -1,202 +0,0 @@
-
- Apache License
- Version 2.0, January 2004
- http://www.apache.org/licenses/
-
- TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
- 1. Definitions.
-
- "License" shall mean the terms and conditions for use, reproduction,
- and distribution as defined by Sections 1 through 9 of this document.
-
- "Licensor" shall mean the copyright owner or entity authorized by
- the copyright owner that is granting the License.
-
- "Legal Entity" shall mean the union of the acting entity and all
- other entities that control, are controlled by, or are under common
- control with that entity. For the purposes of this definition,
- "control" means (i) the power, direct or indirect, to cause the
- direction or management of such entity, whether by contract or
- otherwise, or (ii) ownership of fifty percent (50%) or more of the
- outstanding shares, or (iii) beneficial ownership of such entity.
-
- "You" (or "Your") shall mean an individual or Legal Entity
- exercising permissions granted by this License.
-
- "Source" form shall mean the preferred form for making modifications,
- including but not limited to software source code, documentation
- source, and configuration files.
-
- "Object" form shall mean any form resulting from mechanical
- transformation or translation of a Source form, including but
- not limited to compiled object code, generated documentation,
- and conversions to other media types.
-
- "Work" shall mean the work of authorship, whether in Source or
- Object form, made available under the License, as indicated by a
- copyright notice that is included in or attached to the work
- (an example is provided in the Appendix below).
-
- "Derivative Works" shall mean any work, whether in Source or Object
- form, that is based on (or derived from) the Work and for which the
- editorial revisions, annotations, elaborations, or other modifications
- represent, as a whole, an original work of authorship. For the purposes
- of this License, Derivative Works shall not include works that remain
- separable from, or merely link (or bind by name) to the interfaces of,
- the Work and Derivative Works thereof.
-
- "Contribution" shall mean any work of authorship, including
- the original version of the Work and any modifications or additions
- to that Work or Derivative Works thereof, that is intentionally
- submitted to Licensor for inclusion in the Work by the copyright owner
- or by an individual or Legal Entity authorized to submit on behalf of
- the copyright owner. For the purposes of this definition, "submitted"
- means any form of electronic, verbal, or written communication sent
- to the Licensor or its representatives, including but not limited to
- communication on electronic mailing lists, source code control systems,
- and issue tracking systems that are managed by, or on behalf of, the
- Licensor for the purpose of discussing and improving the Work, but
- excluding communication that is conspicuously marked or otherwise
- designated in writing by the copyright owner as "Not a Contribution."
-
- "Contributor" shall mean Licensor and any individual or Legal Entity
- on behalf of whom a Contribution has been received by Licensor and
- subsequently incorporated within the Work.
-
- 2. Grant of Copyright License. Subject to the terms and conditions of
- this License, each Contributor hereby grants to You a perpetual,
- worldwide, non-exclusive, no-charge, royalty-free, irrevocable
- copyright license to reproduce, prepare Derivative Works of,
- publicly display, publicly perform, sublicense, and distribute the
- Work and such Derivative Works in Source or Object form.
-
- 3. Grant of Patent License. Subject to the terms and conditions of
- this License, each Contributor hereby grants to You a perpetual,
- worldwide, non-exclusive, no-charge, royalty-free, irrevocable
- (except as stated in this section) patent license to make, have made,
- use, offer to sell, sell, import, and otherwise transfer the Work,
- where such license applies only to those patent claims licensable
- by such Contributor that are necessarily infringed by their
- Contribution(s) alone or by combination of their Contribution(s)
- with the Work to which such Contribution(s) was submitted. If You
- institute patent litigation against any entity (including a
- cross-claim or counterclaim in a lawsuit) alleging that the Work
- or a Contribution incorporated within the Work constitutes direct
- or contributory patent infringement, then any patent licenses
- granted to You under this License for that Work shall terminate
- as of the date such litigation is filed.
-
- 4. Redistribution. You may reproduce and distribute copies of the
- Work or Derivative Works thereof in any medium, with or without
- modifications, and in Source or Object form, provided that You
- meet the following conditions:
-
- (a) You must give any other recipients of the Work or
- Derivative Works a copy of this License; and
-
- (b) You must cause any modified files to carry prominent notices
- stating that You changed the files; and
-
- (c) You must retain, in the Source form of any Derivative Works
- that You distribute, all copyright, patent, trademark, and
- attribution notices from the Source form of the Work,
- excluding those notices that do not pertain to any part of
- the Derivative Works; and
-
- (d) If the Work includes a "NOTICE" text file as part of its
- distribution, then any Derivative Works that You distribute must
- include a readable copy of the attribution notices contained
- within such NOTICE file, excluding those notices that do not
- pertain to any part of the Derivative Works, in at least one
- of the following places: within a NOTICE text file distributed
- as part of the Derivative Works; within the Source form or
- documentation, if provided along with the Derivative Works; or,
- within a display generated by the Derivative Works, if and
- wherever such third-party notices normally appear. The contents
- of the NOTICE file are for informational purposes only and
- do not modify the License. You may add Your own attribution
- notices within Derivative Works that You distribute, alongside
- or as an addendum to the NOTICE text from the Work, provided
- that such additional attribution notices cannot be construed
- as modifying the License.
-
- You may add Your own copyright statement to Your modifications and
- may provide additional or different license terms and conditions
- for use, reproduction, or distribution of Your modifications, or
- for any such Derivative Works as a whole, provided Your use,
- reproduction, and distribution of the Work otherwise complies with
- the conditions stated in this License.
-
- 5. Submission of Contributions. Unless You explicitly state otherwise,
- any Contribution intentionally submitted for inclusion in the Work
- by You to the Licensor shall be under the terms and conditions of
- this License, without any additional terms or conditions.
- Notwithstanding the above, nothing herein shall supersede or modify
- the terms of any separate license agreement you may have executed
- with Licensor regarding such Contributions.
-
- 6. Trademarks. This License does not grant permission to use the trade
- names, trademarks, service marks, or product names of the Licensor,
- except as required for reasonable and customary use in describing the
- origin of the Work and reproducing the content of the NOTICE file.
-
- 7. Disclaimer of Warranty. Unless required by applicable law or
- agreed to in writing, Licensor provides the Work (and each
- Contributor provides its Contributions) on an "AS IS" BASIS,
- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
- implied, including, without limitation, any warranties or conditions
- of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
- PARTICULAR PURPOSE. You are solely responsible for determining the
- appropriateness of using or redistributing the Work and assume any
- risks associated with Your exercise of permissions under this License.
-
- 8. Limitation of Liability. In no event and under no legal theory,
- whether in tort (including negligence), contract, or otherwise,
- unless required by applicable law (such as deliberate and grossly
- negligent acts) or agreed to in writing, shall any Contributor be
- liable to You for damages, including any direct, indirect, special,
- incidental, or consequential damages of any character arising as a
- result of this License or out of the use or inability to use the
- Work (including but not limited to damages for loss of goodwill,
- work stoppage, computer failure or malfunction, or any and all
- other commercial damages or losses), even if such Contributor
- has been advised of the possibility of such damages.
-
- 9. Accepting Warranty or Additional Liability. While redistributing
- the Work or Derivative Works thereof, You may choose to offer,
- and charge a fee for, acceptance of support, warranty, indemnity,
- or other liability obligations and/or rights consistent with this
- License. However, in accepting such obligations, You may act only
- on Your own behalf and on Your sole responsibility, not on behalf
- of any other Contributor, and only if You agree to indemnify,
- defend, and hold each Contributor harmless for any liability
- incurred by, or claims asserted against, such Contributor by reason
- of your accepting any such warranty or additional liability.
-
- END OF TERMS AND CONDITIONS
-
- APPENDIX: How to apply the Apache License to your work.
-
- To apply the Apache License to your work, attach the following
- boilerplate notice, with the fields enclosed by brackets "[]"
- replaced with your own identifying information. (Don't include
- the brackets!) The text should be enclosed in the appropriate
- comment syntax for the file format. We also recommend that a
- file or class name and description of purpose be included on the
- same "printed page" as the copyright notice for easier
- identification within third-party archives.
-
- Copyright [yyyy] [name of copyright owner]
-
- Licensed under the Apache License, Version 2.0 (the "License");
- you may not use this file except in compliance with the License.
- You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
- Unless required by applicable law or agreed to in writing, software
- distributed under the License is distributed on an "AS IS" BASIS,
- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
- See the License for the specific language governing permissions and
- limitations under the License.
\ No newline at end of file
diff --git a/includes/classes/vendors/square/connect/README.md b/includes/classes/vendors/square/connect/README.md
deleted file mode 100644
index 3dca359f16..0000000000
--- a/includes/classes/vendors/square/connect/README.md
+++ /dev/null
@@ -1,207 +0,0 @@
-![Square logo]
-
-# Square Connect PHP SDK - RETIRED
-
----
-
-[](https://travis-ci.org/square/connect-php-sdk)
-[](https://badge.fury.io/ph/square%2Fconnect)
-[](https://www.apache.org/licenses/LICENSE-2.0)
-==================
-
-## NOTICE: Square Connect PHP SDK retired
-
-The Square Connect PHP SDK is retired (EOL) as of 2020-06-10 and will no longer
-receive bug fixes or product updates. To continue receiving API and SDK
-improvements, please follow the instructions below to migrate to the new
-[Square PHP SDK].
-
-NOTE THAT THE NEW PHP SDK REQUIRES PHP 7.1+, and will NOT work on PHP 5
-
-
-The old Connect SDK documentation is available under the
-[`/docs` folder](./docs/README.md).
-
-";
- print_r($result);
- echo " ";
-} catch (ApiException $e) {
- echo "Caught exception!Response body: "; var_dump($e->getResponseBody()); echo " ";
- echo "Response headers: "; var_dump($e->getResponseHeaders()); echo " ";
-}
-```
-
-Now consider equivalent code using the new `square/square` library:
-
-```php
-$payments_api = $api_client->getPaymentsApi();
-
-$money = new Money();
-$money->setAmount(100);
-$money->setCurrency('USD');
-$create_payment_request = new CreatePaymentRequest($nonce, uniqid(), $money);
-try {
- $response = $payments_api->createPayment($create_payment_request);
- if ($response->isError()) {
- echo 'Api response has Errors';
- $errors = $response->getErrors();
- exit();
- }
- echo '';
- print_r($response);
- echo ' ';
-} catch (ApiException $e) {
- echo 'Caught exception!Get more information, or Sign up for an account Log In To Your Square Account ',
- 'MODULE_PAYMENT_SQUARE_TEXT_ADMIN_TITLE' => 'Square',
- 'MODULE_PAYMENT_SQUARE_TEXT_CATALOG_TITLE' => 'Credit Card',
- 'MODULE_PAYMENT_SQUARE_TEXT_NOTICES_TO_CUSTOMER' => '',
- 'MODULE_PAYMENT_SQUARE_TEXT_CREDIT_CARD_POSTCODE' => 'Postal Code:',
- 'MODULE_PAYMENT_SQUARE_TEXT_CREDIT_CARD_NUMBER' => 'Card Number:',
- 'MODULE_PAYMENT_SQUARE_TEXT_CREDIT_CARD_EXPIRES' => 'Expiry Date:',
- 'MODULE_PAYMENT_SQUARE_TEXT_CVV' => 'CVV Number:',
- 'MODULE_PAYMENT_SQUARE_TEXT_CREDIT_CARD_TYPE' => 'Credit Card Type:',
- 'MODULE_PAYMENT_SQUARE_TEXT_ERROR' => '(SQ-ERR) Your transaction could not be completed because of an error: ',
- 'MODULE_PAYMENT_SQUARE_TEXT_MISCONFIGURATION' => 'Your transaction could not be completed due to a misconfiguration in our store. Please report this error to the Store Owner: SQ-MISCONF',
- 'MODULE_PAYMENT_SQUARE_TEXT_COMM_ERROR' => 'Unable to process payment due to a communications error. You may try again or contact us for assistance.',
- 'MODULE_PAYMENT_SQUARE_ERROR_INVALID_CARD_DATA' => 'We could not initiate your transaction because of a problem with the card data you entered. Please correct the card data, or report this error to the Store Owner: SQ-NONCE-FAILURE',
- 'MODULE_PAYMENT_SQUARE_ERROR_DECLINED' => 'Sorry, your payment could not be authorized. Please select an alternate method of payment.',
- 'MODULE_PAYMENT_SQUARE_ENTRY_TRANSACTION_ACTIONS' => 'Actions ',
- 'MODULE_PAYMENT_SQUARE_TEXT_UPDATE_FAILED' => 'Sorry, the attempted transaction update failed unexpectedly. See logs for details.',
- 'MODULE_PAYMENT_SQUARE_TEXT_REFUND_CONFIRM_ERROR' => 'Error: You requested to do a refund but did not check the Confirmation box.',
- 'MODULE_PAYMENT_SQUARE_TEXT_INVALID_REFUND_AMOUNT' => 'Error: You requested a refund but entered an invalid amount.',
- 'MODULE_PAYMENT_SQUARE_TEXT_REFUND_INITIATED' => 'Refunded ',
- 'MODULE_PAYMENT_SQUARE_TEXT_CAPTURE_CONFIRM_ERROR' => 'Error: You requested to do a capture but did not check the Confirmation box.',
- 'MODULE_PAYMENT_SQUARE_TEXT_TRANS_ID_REQUIRED_ERROR' => 'Error: You need to specify a Transaction ID.',
- 'MODULE_PAYMENT_SQUARE_TEXT_CAPT_INITIATED' => 'Funds Capture initiated. Transaction ID: %s',
- 'MODULE_PAYMENT_SQUARE_TEXT_VOID_CONFIRM_ERROR' => 'Error: You requested a Void but did not check the Confirmation box.',
- 'MODULE_PAYMENT_SQUARE_TEXT_VOID_INITIATED' => 'Void Initiated. Transaction ID: %s',
-];
-
-// Check current directory to see if SquareWebpay is installed have include lang.square_webPay.php in case it changes before Square is fully removed from zen cart
-// This prevents the duplication message as square_webPay defines all below as constants.
-if (file_exists(dirname(__FILE__) . '/square_webPay.php') === false && file_exists(dirname(__FILE__) . '/lang.square_webPay.php') === false) {
- $defineExtra = [
- 'MODULE_PAYMENT_SQUARE_ENTRY_TRANSACTION_SUMMARY' => 'Transaction Summary ',
- 'MODULE_PAYMENT_SQUARE_ENTRY_REFUND_TITLE' => 'Refund Transaction ',
- 'MODULE_PAYMENT_SQUARE_ENTRY_REFUND' => 'You may refund money to the customer here:',
- 'MODULE_PAYMENT_SQUARE_TEXT_REFUND_CONFIRM_CHECK' => 'Check this box to confirm your intent: ',
- 'MODULE_PAYMENT_SQUARE_ENTRY_REFUND_AMOUNT_TEXT' => 'Enter the amount you wish to refund',
- 'MODULE_PAYMENT_SQUARE_ENTRY_REFUND_TEXT_COMMENTS' => 'Notes (will show on Order History):',
- 'MODULE_PAYMENT_SQUARE_ENTRY_REFUND_DEFAULT_MESSAGE' => 'Refund Issued',
- 'MODULE_PAYMENT_SQUARE_ENTRY_REFUND_SUFFIX' => 'You may refund an order within 120 days, up to the original amount tendered. You must supply the original transaction ID and tender IDinformation on Square refunds .',
- 'MODULE_PAYMENT_SQUARE_ENTRY_REFUND_BUTTON_TEXT' => 'Do Refund',
- 'MODULE_PAYMENT_SQUARE_ENTRY_CAPTURE_TITLE' => 'Capture Transaction ',
- 'MODULE_PAYMENT_SQUARE_ENTRY_CAPTURE' => 'You may capture previously-authorized funds here:',
- 'MODULE_PAYMENT_SQUARE_TEXT_CAPTURE_CONFIRM_CHECK' => 'Check this box to confirm your intent: ',
- 'MODULE_PAYMENT_SQUARE_ENTRY_CAPTURE_TEXT_COMMENTS' => 'Notes (will show on Order History):',
- 'MODULE_PAYMENT_SQUARE_ENTRY_CAPTURE_DEFAULT_MESSAGE' => '',
- 'MODULE_PAYMENT_SQUARE_ENTRY_CAPTURE_SUFFIX' => 'Captures must be performed within 6 days of the original authorization. You may only capture an order ONCE.',
- 'MODULE_PAYMENT_SQUARE_ENTRY_CAPTURE_BUTTON_TEXT' => 'Do Capture',
- 'MODULE_PAYMENT_SQUARE_ENTRY_VOID_TITLE' => 'Voiding Transaction ',
- 'MODULE_PAYMENT_SQUARE_ENTRY_VOID' => 'You may void an authorization which has not been captured.',
- 'MODULE_PAYMENT_SQUARE_TEXT_VOID_CONFIRM_CHECK' => 'Check this box to confirm your intent:',
- 'MODULE_PAYMENT_SQUARE_ENTRY_VOID_TEXT_COMMENTS' => 'Notes (will show on Order History):',
- 'MODULE_PAYMENT_SQUARE_ENTRY_VOID_DEFAULT_MESSAGE' => 'Transaction Cancelled',
- 'MODULE_PAYMENT_SQUARE_ENTRY_VOID_SUFFIX' => '',
- 'MODULE_PAYMENT_SQUARE_ENTRY_VOID_BUTTON_TEXT' => 'Do Void',
- ];
- $define = array_merge($define, $defineExtra);
-}
-
-
-if (IS_ADMIN_FLAG === true) {
- $define['MODULE_PAYMENT_SQUARE_TEXT_NEED_ACCESS_TOKEN'] =
- 'ALERT: Access Token not set: ' . str_replace(array('index.php?main_page=index' => 'http://'), array('square_handler.php' => 'https://'), zen_catalog_href_link(FILENAME_DEFAULT)) . ' Click here to login and Authorize your account Square Payments Module ' . $this->moduleVersion . ' ';
- $this->description .= ' (not configured; API details needed) ';
- if (MODULE_PAYMENT_SQUARE_ACCESS_TOKEN == '') {
- $this->title .= ' (Access Token needed) ';
- $this->description .= "\n" . ' (Sandbox mode) ';
- $new_version_details = plugin_version_check_for_updates(156, $this->moduleVersion);
- if ($new_version_details !== false) {
- $this->title .= '' . ' - NOTE: A NEW VERSION OF THIS PLUGIN IS AVAILABLE. [Details] ' . ' ';
- }
- }
- $this->tableCheckup();
- }
-
- // determine order-status for transactions
- if (defined('MODULE_PAYMENT_SQUARE_ORDER_STATUS_ID') && (int)MODULE_PAYMENT_SQUARE_ORDER_STATUS_ID > 0) {
- $this->order_status = MODULE_PAYMENT_SQUARE_ORDER_STATUS_ID;
- }
- // Reset order status to pending if capture pending:
- if (defined('MODULE_PAYMENT_SQUARE_TRANSACTION_TYPE') && MODULE_PAYMENT_SQUARE_TRANSACTION_TYPE == 'authorize') {
- $this->order_status = 1;
- }
-
- $this->_logDir = DIR_FS_LOGS;
-
- // module can't work without a token; must be configured via OAUTH handshake
- if (!defined('MODULE_PAYMENT_SQUARE_ACCESS_TOKEN') || ((MODULE_PAYMENT_SQUARE_ACCESS_TOKEN == '' || MODULE_PAYMENT_SQUARE_TOKEN_EXPIRES_AT == '') && MODULE_PAYMENT_SQUARE_TESTING_MODE == 'Live')) {
- $this->enabled = false;
- }
-
- // check for zone compliance and any other conditionals
- if ($this->enabled && is_object($order)) $this->update_status();
- }
-
-
- public function update_status()
- {
- global $order, $db;
- if ($this->enabled == false || (int)MODULE_PAYMENT_SQUARE_ZONE == 0) {
- return;
- }
- if (!isset($order->billing['country']['id'])) return;
-
- $check_flag = false;
- $sql = "SELECT zone_id FROM " . TABLE_ZONES_TO_GEO_ZONES . " WHERE geo_zone_id = '" . (int)MODULE_PAYMENT_SQUARE_ZONE . "' AND zone_country_id = '" . (int)$order->billing['country']['id'] . "' ORDER BY zone_id";
- $checks = $db->Execute($sql);
- foreach ($checks as $check) {
- if ($check['zone_id'] < 1) {
- $check_flag = true;
- break;
- } elseif ($check['zone_id'] == $order->billing['zone_id']) {
- $check_flag = true;
- break;
- }
- }
- if ($check_flag == false) {
- $this->enabled = false;
- }
- }
-
- public function javascript_validation()
- {
- return '';
- }
-
- public function selection()
- {
- // helper for auto-selecting the radio-button next to this module so the user doesn't have to make that choice
- $onFocus = ' onfocus="methodSelect(\'pmt-' . $this->code . '\')"';
-
- $selection = array(
- 'id' => $this->code,
- 'module' => $this->title,
- 'fields' => array(
- array(
- 'field' => '' . MODULE_PAYMENT_SQUARE_TEXT_NOTICES_TO_CUSTOMER . '
',
- ),
- array(
- 'title' => MODULE_PAYMENT_SQUARE_TEXT_CREDIT_CARD_NUMBER,
- 'field' => '
',
- ),
- array(
- 'title' => MODULE_PAYMENT_SQUARE_TEXT_CVV,
- 'field' => '
',
- ),
- array(
- 'title' => MODULE_PAYMENT_SQUARE_TEXT_CREDIT_CARD_EXPIRES,
- 'field' => '
',
- ),
- array(
- 'title' => MODULE_PAYMENT_SQUARE_TEXT_CREDIT_CARD_POSTCODE,
- 'field' => '
',
- ),
- array(
- 'title' => '',
- 'field' => '
',
- ),
- array(
- 'title' => '',
- 'field' => '