# Square AI integration on Definable > Square provides payment processing, POS systems, invoicing, and e-commerce tools, enabling sellers to accept card payments and manage their business ## What this connects Square provides payment processing, POS systems, invoicing, and e-commerce tools, enabling sellers to accept card payments and manage their business Vendor: https://squareup.com ## Tools available **96** tools available. First 12: - `SQUARE_ACCEPT_DISPUTE` — Accept Dispute — Accept a dispute and acknowledge liability, returning funds to the cardholder. When you accept a dispute, Square debits the disputed amount from your account and updates the dispute state to ACCEPTED. This action is irreversible - once accepted, a dispute cannot be challenged. Only use after reviewing all evidence and determining that challenging the dispute is not viable. Note: Requires DISPUTES_WRITE permission scope. - `SQUARE_ADD_GROUP_TO_CUSTOMER` — Add Group to Customer — Tool to add a customer to a customer group. Use when you need to associate a customer with a specific group for targeted marketing, loyalty programs, or customer segmentation. - `SQUARE_CALCULATE_ORDER` — Calculate Order — Tool to preview order pricing without creating an order. Use when you need to calculate the total cost, taxes, discounts, and other pricing details for an order before finalizing it. Particularly useful for integrating rewards, discounts, and complex pricing scenarios. - `SQUARE_CANCEL_INVOICE` — Cancel Invoice — Cancels a Square invoice, preventing further payments from being collected. Requirements: - Invoice must be in SCHEDULED, UNPAID, or PARTIALLY_PAID state - Cannot cancel invoices in DRAFT state or terminal states (PAID, REFUNDED, CANCELED, FAILED) - Requires INVOICES_WRITE and ORDERS_WRITE OAuth scopes - Version number must match the current invoice version to prevent conflicts After cancellation, the associated order status is set to CANCELED and webhook events are triggered. - `SQUARE_CANCEL_PAYMENT` — Cancel Payment — Cancels (voids) a payment that is in APPROVED status. This is typically used in delayed capture scenarios where a payment was authorized but not yet captured, allowing you to void the authorization before settlement. Important: Only payments with APPROVED status can be canceled. Attempting to cancel a payment in any other status (COMPLETED, PENDING, CANCELED, FAILED) will result in an error. Once canceled, the payment status changes to CANCELED and the card details status changes to VOIDED. Required permissions: PAYMENTS_WRITE - `SQUARE_CREATE_BULK_CUSTOMERS` — Create Bulk Customers — Tool to create multiple customer profiles in a single request. Use when you need to efficiently create up to 100 customers at once. Each customer is identified by a unique idempotency key. - `SQUARE_CREATE_CARD` — Create Card — Tool to create a card on file. Use when you need to securely store a customer's card for future payments. Requires a valid nonce or payment ID. - `SQUARE_CREATE_CUSTOMER` — Create Customer — Tool to create a new customer profile in Square. Use when you need to add a customer to the Square account. At least one of given_name, family_name, company_name, email_address, or phone_number is required. - `SQUARE_CREATE_CUSTOMER_CUSTOM_ATTRIBUTE_DEFINITION` — Create Customer Custom Attribute Definition — Tool to create a customer-related custom attribute definition. Use when you need to define a new custom attribute that can be applied to customer profiles. Custom attributes allow storing additional structured data on customers beyond the standard fields. - `SQUARE_CREATE_CUSTOMER_GROUP` — Create Customer Group — Tool to create a new customer group for a business. Use when you need to organize customers into groups for targeted marketing or segmentation. - `SQUARE_CREATE_DISPUTE_EVIDENCE_FILE` — Create Dispute Evidence File — Tool to upload a file as dispute evidence. Use when you need to attach supporting documents (PDF, image, etc.) to an existing dispute. Use after creating or retrieving a dispute. - `SQUARE_CREATE_DISPUTE_EVIDENCE_TEXT` — Create Dispute Evidence Text — Upload text evidence for a dispute challenge. Use this to submit textual information (up to 500 characters) that supports your case in a payment dispute. After uploading all evidence, you must call SubmitEvidence to finalize the dispute challenge. Endpoint: POST /v2/disputes/{dispute_id}/evidence-text ## Auth Auth schemes: `OAUTH2`. Managed by Definable: `OAUTH2` — no client credentials required from the user. ## How agents use Square Inside a Definable workflow, Square is one of the tools the **Distributor specialist** can call. Example coordination patterns: - **Researcher → Square** — the Researcher (GPT-5.5) pulls context from Square (records, threads, documents), synthesises findings, and briefs the rest of the team. - **Writer → Distributor → Square** — the Writer (Claude Opus 4.7) drafts copy in brand voice, the Verifier passes it, then the Distributor writes the result into Square (create record, post message, draft email). - **Designer / Engineer → Distributor → Square** — the Designer ships an asset or the Engineer ships a code change, the Distributor delivers it via Square (attach file, open PR comment, post status). The Verifier checks every Square call. On rate limit, schema drift, or auth refresh it self-heals and retries — the workflow completes without manual intervention. ## Categories - payment processing — https://definable.ai/apps/category/payment-processing/ - ecommerce — https://definable.ai/apps/category/ecommerce/ ## Related - HTML page: https://definable.ai/apps/square/ - Same category (payment processing): https://definable.ai/apps/category/payment-processing/ - All integrations: https://definable.ai/apps/ - Workflow (multi-agent loop): https://definable.ai/workflow/ - Apps llms.txt index: https://definable.ai/llms-apps.txt