> This page is for Cash App Pay Partner API. > For clean Markdown of any page, append .md to the page URL. > For a complete documentation index, see https://developers.cash.app/llms.txt. > For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://developers.cash.app/_mcp/server. ### Schema (`response.body`) ```yaml openapi: 3.1.0 info: title: API version: 1.0.0 paths: /disputes/{dispute_id}/evidence-text: post: operationId: subpackageDisputes_create-dispute-evidence-text summary: Create dispute evidence text description: >- Creates a piece of evidence for the given dispute from a blob of plain text, which can then be submitted with the [challenge dispute](Network-API.v1.yaml/paths/~1disputes~1{dispute_id}~1challenge) endpoint. If you have more than 500 characters of text to submit as evidence, split it into multiple pieces where possible. Uploading evidence does not challenge the dispute. Make sure to call the [challenge dispute](Network-API.v1.yaml/paths/~1disputes~1{dispute_id}~1challenge) endpoint before the `response_due_at` timestamp, or else the merchant will automatically "lose" the dispute. **This endpoint is not rate limited.** Scopes: `DISPUTES_WRITE` tags: - subpackage_disputes parameters: - name: dispute_id in: path description: ID of the dispute. required: true schema: type: string responses: '201': description: Created content: application/json: schema: $ref: >- #/components/schemas/disputes_CreateDisputeEvidenceTextResponse '400': description: Bad Request content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '404': description: Not Found content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' requestBody: content: application/json: schema: type: object properties: idempotency_key: $ref: '#/components/schemas/IdempotencyKey' evidence: $ref: >- #/components/schemas/disputes_CreateDisputeEvidenceTextRequestEvidence description: Details about the evidence to create. required: - idempotency_key - evidence tags: - name: subpackage_disputes servers: - url: https://api.cash.app/network/v1 description: Production - url: https://sandbox.api.cash.app/network/v1 description: Sandbox components: schemas: IdempotencyKey: type: string minLength: 1 maxLength: 64 description: >- A unique identifier which can be used by Cash App to de-duplicate retries of this request, making it idempotent. For more information, see [Idempotency](/cash-app-pay-partner-api/guides/technical-guides/api-fundamentals/idempotency). title: IdempotencyKey disputes_CreateDisputeEvidenceTextRequestEvidenceCategory: type: string enum: - GENERIC_EVIDENCE - ONLINE_OR_APP_ACCESS_LOG - AUTHORIZATION_DOCUMENTATION - CANCELLATION_OR_REFUND_DOCUMENTATION - CARDHOLDER_COMMUNICATION - CARDHOLDER_INFORMATION - PURCHASE_ACKNOWLEDGEMENT - DUPLICATE_CHARGE_DOCUMENTATION - PRODUCT_OR_SERVICE_DESCRIPTION - RECEIPT - SERVICE_RECEIVED_DOCUMENTATION - PROOF_OF_DELIVERY_DOCUMENTATION - RELATED_TRANSACTION_DOCUMENTATION - REBUTTAL_EXPLANATION - TRACKING_NUMBER description: >- Describes what type of information is contained in this piece of evidence. Current values: - `GENERIC_EVIDENCE`: Default evidence type used if no other category applies. - `ONLINE_OR_APP_ACCESS_LOG`: Server or activity logs that show proof of the cardholder’s identity and that the cardholder successfully ordered and received the goods (digitally or otherwise). Example evidence includes IP addresses, corresponding timestamps/dates, cardholder’s name and email address linked to a cardholder profile held by the seller, proof the same device and card (used in dispute) were previously used in prior undisputed transaction, and any related detailed activity. - `AUTHORIZATION_DOCUMENTATION`: **[File Only]** Evidence that the cardholder did provide authorization for the charge. Example evidence includes a signed credit card authorization. - `CANCELLATION_OR_REFUND_DOCUMENTATION`: Evidence that the cardholder acknowledged your refund or cancellation policy. Example evidence includes a signature or checkbox showing the cardholder’s acknowledgement of your refund or cancellation policy. - `CARDHOLDER_COMMUNICATION`: **[File Only]** Evidence that shows relevant communication with the cardholder. Example evidence includes emails or texts that show the cardholder received goods/services or demonstrate cardholder satisfaction. - `CARDHOLDER_INFORMATION`: Evidence that validates the customer's identity. Example evidence includes personally identifiable details such as name, email address, purchaser IP address, and a copy of the cardholder ID. - `PURCHASE_ACKNOWLEDGEMENT`: Evidence that shows proof of the sale/transaction. Example evidence includes an invoice, contract, or other item showing the customer’s acknowledgement of the purchase and your terms. - `DUPLICATE_CHARGE_DOCUMENTATION`: **[File Only]** Evidence that shows the charges in question are valid and distinct from one another. Example evidence includes receipts, shipping labels, and invoices along with their distinct payment IDs. - `PRODUCT_OR_SERVICE_DESCRIPTION`: A description of the product or service sold. - `RECEIPT`: A receipt or message sent to the cardholder detailing the charge. Note: You do not need to upload the Square receipt; Square submits the receipt on your behalf. - `SERVICE_RECEIVED_DOCUMENTATION`: Evidence that the service was provided to the cardholder or the expected date that services will be rendered. Example evidence includes a signed delivery form, work order, expected delivery date, or other written agreements. - `PROOF_OF_DELIVERY_DOCUMENTATION`: Evidence that shows the product was provided to the cardholder or the expected date of delivery. Example evidence includes a signed delivery form or written agreement acknowledging receipt of the goods or services. - `RELATED_TRANSACTION_DOCUMENTATION`: Evidence that shows the cardholder previously processed transactions on the same card and did not dispute them. - `REBUTTAL_EXPLANATION`: An explanation of why the cardholder’s claim is invalid. Example evidence includes an explanation of why each distinct charge is a legitimate purchase, why the cardholder’s claim for credit owed due to their attempt to cancel, return, or refund is invalid per your stated policy and cardholder agreement, or an explanation of how the cardholder did not attempt to remedy the issue with you first to receive credit. - `TRACKING_NUMBER`: The tracking number for the order provided by the shipping carrier. If you have multiple numbers, they need to be submitted individually as separate pieces of evidence. title: CreateDisputeEvidenceTextRequestEvidenceCategory Metadata: type: object additionalProperties: type: string description: >- Freeform key-value pairs of arbitrary data associated with this resource. Keys and values must be passed as strings and not contain any personally identifiable information (PII). Min keys: `0` Max keys: `50` > Note: Nested keys are not supported. title: Metadata disputes_CreateDisputeEvidenceTextRequestEvidence: type: object properties: category: $ref: >- #/components/schemas/disputes_CreateDisputeEvidenceTextRequestEvidenceCategory description: >- Describes what type of information is contained in this piece of evidence. Current values: - `GENERIC_EVIDENCE`: Default evidence type used if no other category applies. - `ONLINE_OR_APP_ACCESS_LOG`: Server or activity logs that show proof of the cardholder’s identity and that the cardholder successfully ordered and received the goods (digitally or otherwise). Example evidence includes IP addresses, corresponding timestamps/dates, cardholder’s name and email address linked to a cardholder profile held by the seller, proof the same device and card (used in dispute) were previously used in prior undisputed transaction, and any related detailed activity. - `AUTHORIZATION_DOCUMENTATION`: **[File Only]** Evidence that the cardholder did provide authorization for the charge. Example evidence includes a signed credit card authorization. - `CANCELLATION_OR_REFUND_DOCUMENTATION`: Evidence that the cardholder acknowledged your refund or cancellation policy. Example evidence includes a signature or checkbox showing the cardholder’s acknowledgement of your refund or cancellation policy. - `CARDHOLDER_COMMUNICATION`: **[File Only]** Evidence that shows relevant communication with the cardholder. Example evidence includes emails or texts that show the cardholder received goods/services or demonstrate cardholder satisfaction. - `CARDHOLDER_INFORMATION`: Evidence that validates the customer's identity. Example evidence includes personally identifiable details such as name, email address, purchaser IP address, and a copy of the cardholder ID. - `PURCHASE_ACKNOWLEDGEMENT`: Evidence that shows proof of the sale/transaction. Example evidence includes an invoice, contract, or other item showing the customer’s acknowledgement of the purchase and your terms. - `DUPLICATE_CHARGE_DOCUMENTATION`: **[File Only]** Evidence that shows the charges in question are valid and distinct from one another. Example evidence includes receipts, shipping labels, and invoices along with their distinct payment IDs. - `PRODUCT_OR_SERVICE_DESCRIPTION`: A description of the product or service sold. - `RECEIPT`: A receipt or message sent to the cardholder detailing the charge. Note: You do not need to upload the Square receipt; Square submits the receipt on your behalf. - `SERVICE_RECEIVED_DOCUMENTATION`: Evidence that the service was provided to the cardholder or the expected date that services will be rendered. Example evidence includes a signed delivery form, work order, expected delivery date, or other written agreements. - `PROOF_OF_DELIVERY_DOCUMENTATION`: Evidence that shows the product was provided to the cardholder or the expected date of delivery. Example evidence includes a signed delivery form or written agreement acknowledging receipt of the goods or services. - `RELATED_TRANSACTION_DOCUMENTATION`: Evidence that shows the cardholder previously processed transactions on the same card and did not dispute them. - `REBUTTAL_EXPLANATION`: An explanation of why the cardholder’s claim is invalid. Example evidence includes an explanation of why each distinct charge is a legitimate purchase, why the cardholder’s claim for credit owed due to their attempt to cancel, return, or refund is invalid per your stated policy and cardholder agreement, or an explanation of how the cardholder did not attempt to remedy the issue with you first to receive credit. - `TRACKING_NUMBER`: The tracking number for the order provided by the shipping carrier. If you have multiple numbers, they need to be submitted individually as separate pieces of evidence. text: type: string minLength: 1 maxLength: 500 description: The blob of text to upload as evidence. metadata: $ref: '#/components/schemas/Metadata' required: - category - text description: Details about the evidence to create. title: CreateDisputeEvidenceTextRequestEvidence disputes_DisputeEvidenceCategory: type: string enum: - GENERIC_EVIDENCE - ONLINE_OR_APP_ACCESS_LOG - AUTHORIZATION_DOCUMENTATION - CANCELLATION_OR_REFUND_DOCUMENTATION - CARDHOLDER_COMMUNICATION - CARDHOLDER_INFORMATION - PURCHASE_ACKNOWLEDGEMENT - DUPLICATE_CHARGE_DOCUMENTATION - PRODUCT_OR_SERVICE_DESCRIPTION - RECEIPT - SERVICE_RECEIVED_DOCUMENTATION - PROOF_OF_DELIVERY_DOCUMENTATION - RELATED_TRANSACTION_DOCUMENTATION - REBUTTAL_EXPLANATION - TRACKING_NUMBER description: >- Describes what type of information is contained in this piece of evidence. Current values: - `GENERIC_EVIDENCE`: Default evidence type used if no other category applies. - `ONLINE_OR_APP_ACCESS_LOG`: Server or activity logs that show proof of the cardholder’s identity and that the cardholder successfully ordered and received the goods (digitally or otherwise). Example evidence includes IP addresses, corresponding timestamps/dates, cardholder’s name and email address linked to a cardholder profile held by the seller, proof the same device and card (used in dispute) were previously used in prior undisputed transaction, and any related detailed activity. - `AUTHORIZATION_DOCUMENTATION`: **[File Only]** Evidence that the cardholder did provide authorization for the charge. Example evidence includes a signed credit card authorization. - `CANCELLATION_OR_REFUND_DOCUMENTATION`: Evidence that the cardholder acknowledged your refund or cancellation policy. Example evidence includes a signature or checkbox showing the cardholder’s acknowledgement of your refund or cancellation policy. - `CARDHOLDER_COMMUNICATION`: **[File Only]** Evidence that shows relevant communication with the cardholder. Example evidence includes emails or texts that show the cardholder received goods/services or demonstrate cardholder satisfaction. - `CARDHOLDER_INFORMATION`: Evidence that validates the customer's identity. Example evidence includes personally identifiable details such as name, email address, purchaser IP address, and a copy of the cardholder ID. - `PURCHASE_ACKNOWLEDGEMENT`: Evidence that shows proof of the sale/transaction. Example evidence includes an invoice, contract, or other item showing the customer’s acknowledgement of the purchase and your terms. - `DUPLICATE_CHARGE_DOCUMENTATION`: **[File Only]** Evidence that shows the charges in question are valid and distinct from one another. Example evidence includes receipts, shipping labels, and invoices along with their distinct payment IDs. - `PRODUCT_OR_SERVICE_DESCRIPTION`: A description of the product or service sold. - `RECEIPT`: A receipt or message sent to the cardholder detailing the charge. Note: You do not need to upload the Square receipt; Square submits the receipt on your behalf. - `SERVICE_RECEIVED_DOCUMENTATION`: Evidence that the service was provided to the cardholder or the expected date that services will be rendered. Example evidence includes a signed delivery form, work order, expected delivery date, or other written agreements. - `PROOF_OF_DELIVERY_DOCUMENTATION`: Evidence that shows the product was provided to the cardholder or the expected date of delivery. Example evidence includes a signed delivery form or written agreement acknowledging receipt of the goods or services. - `RELATED_TRANSACTION_DOCUMENTATION`: Evidence that shows the cardholder previously processed transactions on the same card and did not dispute them. - `REBUTTAL_EXPLANATION`: An explanation of why the cardholder’s claim is invalid. Example evidence includes an explanation of why each distinct charge is a legitimate purchase, why the cardholder’s claim for credit owed due to their attempt to cancel, return, or refund is invalid per your stated policy and cardholder agreement, or an explanation of how the cardholder did not attempt to remedy the issue with you first to receive credit. - `TRACKING_NUMBER`: The tracking number for the order provided by the shipping carrier. If you have multiple numbers, they need to be submitted individually as separate pieces of evidence. title: DisputeEvidenceCategory disputes_DisputeEvidenceFileContentType: type: string enum: - application/pdf - image/heic - image/heif - image/jpeg - image/png - image/tiff description: |- The MIME type of the uploaded file. Current values: - `application/pdf` - `image/heic` - `image/heif` - `image/jpeg` - `image/png` - `image/tiff` title: DisputeEvidenceFileContentType disputes_DisputeEvidenceFile: type: object properties: filename: type: string minLength: 1 maxLength: 40 description: >- Name of the uploaded file. It should be descriptive enough to indicate what type of information is contained in the uploaded file. content_type: $ref: '#/components/schemas/disputes_DisputeEvidenceFileContentType' description: |- The MIME type of the uploaded file. Current values: - `application/pdf` - `image/heic` - `image/heif` - `image/jpeg` - `image/png` - `image/tiff` required: - filename - content_type description: >- If the evidence is of type `FILE`, contains metadata about the binary file uploaded as evidence. title: DisputeEvidenceFile disputes_DisputeEvidenceType: type: string enum: - FILE - TEXT description: |- Indicates if the evidence is a file or plain text. Current values: - `TEXT`: The evidence is a blob of text under 500 characters. - `FILE`: The evidence is an uploaded binary file. title: DisputeEvidenceType disputes_DisputeEvidence: type: object properties: id: type: string minLength: 1 maxLength: 128 description: |- A unique identifier for the dispute evidence issued by Cash App. Min length: `1` Max length: `128` dispute_id: type: string minLength: 1 maxLength: 128 description: |- ID of the dispute this evidence is associated with. Min length: `1` Max length: `128` category: $ref: '#/components/schemas/disputes_DisputeEvidenceCategory' description: >- Describes what type of information is contained in this piece of evidence. Current values: - `GENERIC_EVIDENCE`: Default evidence type used if no other category applies. - `ONLINE_OR_APP_ACCESS_LOG`: Server or activity logs that show proof of the cardholder’s identity and that the cardholder successfully ordered and received the goods (digitally or otherwise). Example evidence includes IP addresses, corresponding timestamps/dates, cardholder’s name and email address linked to a cardholder profile held by the seller, proof the same device and card (used in dispute) were previously used in prior undisputed transaction, and any related detailed activity. - `AUTHORIZATION_DOCUMENTATION`: **[File Only]** Evidence that the cardholder did provide authorization for the charge. Example evidence includes a signed credit card authorization. - `CANCELLATION_OR_REFUND_DOCUMENTATION`: Evidence that the cardholder acknowledged your refund or cancellation policy. Example evidence includes a signature or checkbox showing the cardholder’s acknowledgement of your refund or cancellation policy. - `CARDHOLDER_COMMUNICATION`: **[File Only]** Evidence that shows relevant communication with the cardholder. Example evidence includes emails or texts that show the cardholder received goods/services or demonstrate cardholder satisfaction. - `CARDHOLDER_INFORMATION`: Evidence that validates the customer's identity. Example evidence includes personally identifiable details such as name, email address, purchaser IP address, and a copy of the cardholder ID. - `PURCHASE_ACKNOWLEDGEMENT`: Evidence that shows proof of the sale/transaction. Example evidence includes an invoice, contract, or other item showing the customer’s acknowledgement of the purchase and your terms. - `DUPLICATE_CHARGE_DOCUMENTATION`: **[File Only]** Evidence that shows the charges in question are valid and distinct from one another. Example evidence includes receipts, shipping labels, and invoices along with their distinct payment IDs. - `PRODUCT_OR_SERVICE_DESCRIPTION`: A description of the product or service sold. - `RECEIPT`: A receipt or message sent to the cardholder detailing the charge. Note: You do not need to upload the Square receipt; Square submits the receipt on your behalf. - `SERVICE_RECEIVED_DOCUMENTATION`: Evidence that the service was provided to the cardholder or the expected date that services will be rendered. Example evidence includes a signed delivery form, work order, expected delivery date, or other written agreements. - `PROOF_OF_DELIVERY_DOCUMENTATION`: Evidence that shows the product was provided to the cardholder or the expected date of delivery. Example evidence includes a signed delivery form or written agreement acknowledging receipt of the goods or services. - `RELATED_TRANSACTION_DOCUMENTATION`: Evidence that shows the cardholder previously processed transactions on the same card and did not dispute them. - `REBUTTAL_EXPLANATION`: An explanation of why the cardholder’s claim is invalid. Example evidence includes an explanation of why each distinct charge is a legitimate purchase, why the cardholder’s claim for credit owed due to their attempt to cancel, return, or refund is invalid per your stated policy and cardholder agreement, or an explanation of how the cardholder did not attempt to remedy the issue with you first to receive credit. - `TRACKING_NUMBER`: The tracking number for the order provided by the shipping carrier. If you have multiple numbers, they need to be submitted individually as separate pieces of evidence. file: $ref: '#/components/schemas/disputes_DisputeEvidenceFile' description: >- If the evidence is of type `FILE`, contains metadata about the binary file uploaded as evidence. text: type: string minLength: 1 maxLength: 500 description: >- If the evidence is of type `TEXT`, contains the blob of text created as evidence. Min length: `1` Max length: `500` type: $ref: '#/components/schemas/disputes_DisputeEvidenceType' description: |- Indicates if the evidence is a file or plain text. Current values: - `TEXT`: The evidence is a blob of text under 500 characters. - `FILE`: The evidence is an uploaded binary file. created_at: type: string format: date-time description: >- When this evidence was created, in [RFC 3339](https://datatracker.ietf.org/doc/html/rfc3339) format (UTC). metadata: $ref: '#/components/schemas/Metadata' required: - id - dispute_id - category - type - created_at title: DisputeEvidence disputes_CreateDisputeEvidenceTextResponse: type: object properties: evidence: $ref: '#/components/schemas/disputes_DisputeEvidence' title: CreateDisputeEvidenceTextResponse ErrorCategory: type: string enum: - API_ERROR - AUTHENTICATION_ERROR - BRAND_ERROR - DISPUTE_ERROR - MERCHANT_ERROR - INVALID_REQUEST_ERROR - PAYMENT_PROCESSING_ERROR - RATE_LIMIT_ERROR - WEBHOOK_ERROR - API_KEY_ERROR - GRANT_ERROR description: The high-level reason the error occurred. title: ErrorCategory Error: type: object properties: category: $ref: '#/components/schemas/ErrorCategory' description: The high-level reason the error occurred. code: type: string description: >- A unique identifier for the specific type of error that occurred. For more information, see [Error Code Reference](/cash-app-pay-partner-api/guides/technical-guides/api-fundamentals/errors/error-code-reference). Min length: `1` detail: type: string description: >- Human-readable description of why the error occurred and how to resolve it. Min length: `1` field: type: string description: >- The field in the request that caused the error, using array and object dot notation. Min length: `1` required: - category - code description: Represents an error encountered during a request to the API. title: Error ErrorResponse: type: object properties: errors: type: array items: $ref: '#/components/schemas/Error' description: |- A list of errors that occurred while processing the request. Min number of items: `1` required: - errors title: ErrorResponse ``` **`Example`** ```json Example { "id": "EVD_dbdda8e161b7bad8519f7f73", "dispute_id": "DSPT_1fbjn9dg7rmz1xeyv6gkyh8vg", "category": "GENERIC_EVIDENCE", "file": { "filename": "string", "content_type": "application/pdf" }, "text": "string", "type": "FILE", "created_at": "2022-01-01T12:00:00Z", "metadata": { "my-meta": "meta-value" } } ```