Skip to main content
When you create a case with a test mode API key (prefix test_), Decisionly recognizes special values for the issuer explanation and file category that bypass AI analysis and return mock Evidence Review results. Use these to exercise both the pass and fail branches of your workflow rules without crafting realistic evidence and documents.
These overrides only take effect on accounts using a test_ API key. In live mode they’re treated as regular values.

​
Evidence Review and Fraud Liability overrides

Include one of the values below anywhere in issuer_explanation on the case’s issuer_evidence to replace the AI Evidence Review result and/or Fraud Liability result for the case. For all dispute reasons:
issuer_explanation containsEvidence Review result
valid_evidenceAll conditions for the dispute reason marked met
invalid_evidenceAll conditions for the dispute reason marked not met
For fraud disputes, you can additionally control Fraud Liability:
issuer_explanation containsFraud Liability result
merchant_liableLiability assigned to the merchant (chargeback rights exist)
issuer_liableLiability assigned to the issuer (no chargeback rights)

​
Documentation Review overrides

Set a file’s category to one of the values below when uploading the file to replace the AI Documentation Review result for that file. The relevance check is skipped entirely.
File category valueDocumentation Review result
valid_documentFile marked as valid and relevant
invalid_documentFile marked as invalid
This is a per-file override — you can mix valid_document and invalid_document files in the same case.

​
Example

Upload a file with the valid_document category, then create a case that references it and uses invalid_evidence to force conditions review to fail: 
# 1. Upload a file with the valid_document test category
curl https://api.decisionly.com/v2/issuer/files \
  -u test_d0019b48d05849a6: \
  -F "category=valid_document" \
  -F "file=@receipt.pdf"

# Response: { "id": "file_abc123", "category": "valid_document", ... }

# 2. Create a case that forces the conditions check to fail
curl https://api.decisionly.com/v2/issuer/cases \
  -u test_d0019b48d05849a6: \
  -H "Content-Type: application/json" \
  -d '{
    "dispute": { "reason": "product_not_received" },
    "issuer_evidence": {
      "issuer_explanation": "invalid_evidence",
      "documentation": ["file_abc123"]
    }
  }'

Evidence Review

How Documentation Review and Conditions Review work in production

Workflow Rules

Configure how cases are handled based on evidence review results