v1CreateDisputeRequest
- Properties: 7customerType:
- orgType: string
Uuid - Properties: 4questionnaireType:
Answers - reasonType: enum
DisputeReason is the dispute reason category. GetDisputeReasons returns the applicable parent categories; the specific sub-reason is resolved server-side from the questionnaire answers at Create time, so callers only ever submit a parent reason. Legacy reason values are normalized to this set before they reach the API, so these are the only values integrators see.
- DISPUTE_REASON_ACH_ISSUE: Unauthorized ACH debit. Other ACH problems use the more specific DISPUTE_REASON_ACH_* values.
- DISPUTE_REASON_ACH_CREDIT_ISSUE: Dispute about an ACH credit (incoming or outgoing credit entry), as opposed to the ACH_ISSUE_* family, which covers consumer debit disputes.
values- D
I S P U T E _ R E A S O N _ U N K N O W N - D
I S P U T E _ R E A S O N _ U N A U T H - D
I S P U T E _ R E A S O N _ M E R C H A N T _ I S S U E - D
I S P U T E _ R E A S O N _ A T M _ I S S U E - D
I S P U T E _ R E A S O N _ A C H _ I S S U E - D
I S P U T E _ R E A S O N _ T R A N S F E R _ I S S U E - D
I S P U T E _ R E A S O N _ A T M _ I S S U E _ C A S H _ N O T _ D I S P E N S E D - D
I S P U T E _ R E A S O N _ M E R C H A N T _ I S S U E _ G O O D S _ O R _ S E R V I C E S _ N O T _ R E C E I V E D
- transactionType:
Details Properties: 17Legacy: full caller-supplied transaction data, still supported for existing integrations. New integrations should use transaction_ids. Provide exactly one of the two.
- transactionType: array of string
Ids transaction_ids selects the transactions to dispute by id, using the transaction_id values returned by ListDisputableTransactions. Ids that fail the eligibility rules (unknown, already disputed, mixed rails) are rejected. Mutually exclusive with transaction_details.