Overview
This document catalogs the error messages the Square integration can record in the iPaaS.com error logs, grouped by the flow that produces them. Each entry lists the error's code, the message exactly as it appears in the log, what causes it, and how to resolve it. Errors appear in iPaaS.com under Dashboard > Integration Monitoring > Error Logs.
Every Square error carries a code in the form SQUP-{category}-{number} — for example SQUP-BIZL-1003. The code is stable: the wording of a message may be improved over time, but its code will not change. Search this page for the code shown in your error log to find the matching entry.
Some resolutions below refer to your Managed Integration Service Provider (MiSP) — the partner who configures and maintains your integration, including its mappings, credentials, and data reconciliation. If your organization does not work with a MiSP, these steps belong to whoever administers your iPaaS.com subscription.
iPaaS.com categorizes errors by families. You can learn more about that categorization at Understanding iPaaS.com API Error Codes.
Supported Flows
Customer TO iPaaS.com
Order TO iPaaS.com
Product FROM iPaaS.com
Authorization
All flows
Error Collection
Customer TO iPaaS.com
Duplicate customer link
SQUP-BIZL-1003 - Unable to dynamically link to an existing Square customer using the email address. This may result in duplicate customer records.
Description: When a Square customer is not yet linked to iPaaS.com, the integration looks for an existing iPaaS.com customer with the same email address and links the two records. This error is recorded when that link cannot be completed, which can leave duplicate customer records.
Resolution: Check whether the Square customer's email address is used by more than one iPaaS.com customer. If it is, merge or correct those records so the address identifies a single customer, then re-transfer the Square customer.
Order TO iPaaS.com
Order products do not exist in iPaaS.com
SQUP-NFND-1001 - The following SKUs do not exist in iPaaS.com: [SKUs]. Please ensure all SKUs are created in iPaaS.com before processing Square transactions.
Description: An order is held back until every product on its line items exists in iPaaS.com. The listed SKUs were not found as either an iPaaS.com product or an iPaaS.com product variation.
Resolution: Create a product or product variation in iPaaS.com for each SKU listed in the message. This includes any fixed SKUs your Square account uses for non-catalog charges such as service charges, fees or surcharges. Once every listed SKU exists, re-transfer the order.
Location not in the allowed list
SQUP-BIZL-1007 - Location '[location name]' does not exist in the list defined within this formula. Please update the list or the formula, or exclude these locations from transfers using a mapping collection filter.
Description: The Square Location Id mapping on the Order mapping collection checks each order's Square location against a list of permitted location names held inside the mapping's formula. The order's location is not on that list, so the order was not transferred.
Resolution: Add the location name shown in the message to the permitted list in the Square Location Id mapping, or exclude that location from transfers using a mapping collection filter. Note that the integration ships this list with example entries, so it must be replaced with your own Square location names before go-live. Your MiSP normally maintains this list.
Duplicate transaction link
SQUP-BIZL-1004 - Unable to dynamically link to an existing Square transaction using the Id. This may result in duplicate transaction records.
Description: When a Square order is not yet linked to iPaaS.com, the integration looks for an existing iPaaS.com transaction carrying the same Square order identifier and links the two records. This error is recorded when that link cannot be completed, which can leave duplicate transaction records.
Resolution: Check whether the Square order identifier is used by more than one iPaaS.com transaction. If it is, remove or correct the duplicate so the identifier matches a single transaction, then re-transfer the order.
Order customer could not be recorded
SQUP-BIZL-1005 - The order references a Square customer that could not be recorded in iPaaS.com, so the order was not transferred.
Description: Before an order is recorded, the customer it references must exist in iPaaS.com. The integration transfers that customer first, and stops the order transfer if the customer cannot be recorded — most commonly because the Square customer has no email address, which iPaaS.com requires.
Resolution: Open the Square customer referenced by the order and confirm it has an email address, then re-transfer the order. The error log usually records a separate customer error alongside this one; that entry names the specific reason the customer was rejected.
Product FROM iPaaS.com
Duplicate product link
SQUP-BIZL-1001 - Unable to dynamically link to an existing Square product using the iPaaS.com SKU: [SKU]. This may result in duplicate product records.
Description: Before writing a product, the integration looks for an existing Square item with the same SKU and links the iPaaS.com product to it. This error is recorded when that link cannot be completed, which can leave duplicate product records in Square.
Resolution: In Square, check whether the SKU shown in the message is used by more than one item. If it is, correct the duplicate so the SKU identifies a single item, then re-transfer the product.
Duplicate product variation link
SQUP-BIZL-1002 - Unable to dynamically link to an existing Square product variation using the iPaaS.com SKU: [SKU]. This may result in duplicate product variation records.
Description: The same matching step runs for each product variation: the integration looks for an existing Square variation with the same SKU and links the iPaaS.com variation to it. This error is recorded when that link cannot be completed, which can leave duplicate variation records in Square.
Resolution: In Square, check whether the SKU shown in the message is used by more than one item variation. If it is, correct the duplicate so the SKU identifies a single variation, then re-transfer the product.
Product could not be created
SQUP-EXTN-1001 - Unable to create Product in Square from iPaaS.com
Description: Square did not accept the new product, and the integration could not complete the create. This is the general failure recorded when the product write does not succeed.
Resolution: Look for a SQUP-EXTN-1003 entry recorded at the same time — it quotes the reason Square gave, which is what needs correcting. Common causes are a price currency that does not match the Square account, an incomplete variation, or a required value that is empty. Correct the underlying cause and re-transfer the product.
Product could not be updated
SQUP-EXTN-1002 - Unable to update Product in Square from iPaaS.com
Description: Square did not accept the changes to an existing product, and the integration could not complete the update.
Resolution: As above, look for the SQUP-EXTN-1003 entry recorded at the same time for Square's own explanation, correct the underlying cause, and re-transfer the product.
Product could not be re-read after writing
SQUP-NFND-1002 - Unable to retrieve the product from Square after it was written, so its external Ids could not be recorded.
Description: After creating or updating a product, the integration reads it back from Square to record the identifiers that link the two systems. This error is recorded when that read does not return the product. The product may exist in Square even though the link was not stored.
Resolution: Re-transfer the product. The read-back is normally successful on a second attempt. If the error repeats for the same product, check in Square whether the product was in fact created, and raise it with your MiSP so the link can be reconciled rather than creating a duplicate.
Circular reference in a Square category
SQUP-BIZL-1006 - Circular reference detected for categoryId=[category id]
Description: When assigning a product's categories, the integration walks each Square category's parent chain. This error is recorded when that chain forms a loop — a category is, directly or indirectly, its own parent.
Resolution: In Square, open the category shown in the message and correct its parent hierarchy so it does not eventually reference itself, then re-transfer the product.
Authorization
Access Token not configured for webhook setup
SQUP-VALD-1001 - Webhook access failed: Public Access Token is not configured in the subscription preset. Please add the Access Token to proceed.
Description: Registering the Square webhook that drives automatic order transfers requires the subscription's Access Token setting to be populated. This error is recorded when webhook setup runs before that token has been entered.
Resolution: Enter the Access Token on your subscription's settings page, following the Square Connections and Settings article, then retry. Once the Access Token is present the webhook can be registered.
No authorization code returned
SQUP-AUTH-1001 - The Square authorization could not be completed because no authorization code was returned by Square.
Description: Connecting to Square uses an authorization you grant inside Square, which returns a short-lived code to iPaaS.com. This error is recorded when the authorization finished without that code — typically because the authorization screen was cancelled or closed before it completed.
Resolution: Repeat the authorization steps in the Square Connections and Settings article, allowing the Square screen to complete and return to iPaaS.com without interruption.
Authorization code could not be exchanged
SQUP-AUTH-1004 - The Square authorization could not be completed because the temporary authorization code could not be exchanged for an access token.
Description: The authorization returned a code, but Square did not accept it when the integration exchanged it for a lasting access token. The code is short-lived, so this most often means too much time passed before the exchange, or the authorization was withdrawn in Square in the meantime.
Resolution: Repeat the authorization steps in the Square Connections and Settings article, completing them in one sitting. If the authorization still does not complete, contact iPaaS.com Support at support@ipaas.com and include the date and time of your attempt.
Client Id not configured
SQUP-AUTH-1002 - The Square authorization could not be completed because the Client Id is not configured for this integration version.
Description: Authorizing with Square requires application credentials that are registered against the Square integration itself, not against your subscription. This error indicates the Client Id is missing from that registration.
Resolution: This is not a setting you can change from your subscription. Contact iPaaS.com Support at support@ipaas.com, quoting this code and the name of your Square subscription.
Client Secret not configured
SQUP-AUTH-1003 - The Square authorization could not be completed because the Client Secret is not configured for this integration version.
Description: As above, the application credentials registered against the Square integration are incomplete — in this case the Client Secret is missing.
Resolution: This is not a setting you can change from your subscription. Contact iPaaS.com Support at support@ipaas.com, quoting this code and the name of your Square subscription.
All flows
Square rejected the request
SQUP-EXTN-1003 - Error calling Square while performing [operation][details] (Http Code: [status])
Description: Square returned an error for a request the integration made. The message names the operation that was attempted, quotes Square's own response, and gives the HTTP status Square returned. This entry can accompany any transfer in either direction. Common causes are a record referenced by the transfer no longer existing in Square, the connection no longer being authorized or lacking permission for the operation, and a value on the record being rejected by Square's own validation.
Resolution: Read the quoted Square response in the message — it identifies what Square objected to. Correct the record or setting it names and re-transfer. If the response reports an authorization or permission problem, re-authorize the connection using the Square Connections and Settings article.
Square could not be reached
SQUP-EXTN-1004 - [transport error reported by the connection]
Description: The request to Square did not complete at the network level, so no response was received. The message carries the underlying connection error. This is usually a temporary condition such as a timeout or a break in connectivity.
Resolution: Re-transfer the affected record. If the errors continue across several attempts, check the Square status page for a reported outage before investigating further, then raise it with your MiSP.
Batch of Square calls failed
SQUP-EXTN-1005 - Received an exception during the batch run of [action]. [first exception message]
Description: The integration sends some work to Square in batches. This error is recorded when a call within a batch fails and the batch is configured to stop rather than continue. The message names the action being batched and quotes the first underlying failure.
Resolution: The quoted message is the error that actually needs resolving — find its entry in this article and follow that resolution. Once the underlying cause is corrected, re-transfer the affected records.