Square is normally a one-click connector: one shared Caddi application authorizes every seller, so there is nothing to register and nothing for an administrator to configure. Organizations that prefer to use their own Square application can configure one instead.
Square asks which account to authorize, every time. If you have several, read the account name on the consent screen before approving.
Before you start
You'll need:
A Square account for the seller location the work involves
A Caddi account
Step 1: Connect your account
In Caddi, open Settings, then Integrations, and go to the My Connections tab.
Find Square and click Connect +.
Sign in to Square and choose the account to authorize.
Review the permissions Square lists and click Allow.
You'll be returned to Caddi with the connection active.
Using your own Square application
If your organization would rather hold the Square application itself, an owner or admin can configure one. Caddi then uses your application for everyone in the organization instead of the shared one.
In the Square Developer Dashboard, create an application.
Add
https://app.trycaddi.com/oauth-callbackas the application's redirect URL.Copy the Application ID and Application Secret from the application's Credentials page.
In Caddi, open Settings → Integrations, find Square - Custom OAuth App under Connectors you can configure, and click Configure.
Enter the Application ID and Application Secret, then click Save Configuration.
A custom integration replaces the standard one for your organization. Members will be disconnected from the shared connection and will only see the option to connect through your application.
How the connection behaves
One connection, one merchant. The connection is keyed to the Square merchant that authorized it, so it is always clear which seller a loop is acting for. Several Square accounts means several connections.
Access tokens last 30 days and are renewed in the background well before that. Square refresh tokens stay valid until revoked, so the connection continues to renew without action from you.
Permissions are fixed at authorization. Square grants exactly what was requested on the consent screen; changing the permissions means reconnecting and approving the new request.
Troubleshooting
Caddi connected to the wrong Square account
Disconnect and connect again. Square will ask which account to authorize — it does not reuse the previous choice.
A loop fails with an insufficient-permissions error
The consent screen granted a narrower set than the loop needs. Disconnect, reconnect, and approve the full request.
Square rejects the redirect URL when you configure your own application
The application's redirect URL must be exactly https://app.trycaddi.com/oauth-callback. Square matches it literally.
Everything authorizes but API calls are rejected
Check you created a production application rather than a sandbox one — sandbox credentials only work against Square's sandbox environment.
Still stuck? Contact Caddi support with the exact error message you're seeing and the time it occurred.
Sources
OAuth API overview — Square developer docs
