Expedited Billing Dispute Resolution

SDAA automatically generates EBDR forms at three key trigger points in the dispute lifecycle. Understanding these trigger points helps you know when forms will be created and attached to your cases. 

Chargeback submission 
When you submit a chargeback for dispute reason codes that require EBDR documentation, SDAA automatically generates the appropriate form. For example, if you select a dispute reason during the customer interview that maps to reason code 4853, the system generates EBDR form 1221.

Pre-arbitration initiation
If the chargeback reason code changes during pre-arbitration initiation and the new reason code mandates EBDR generation, SDAA creates a new form. SDAA also generates EBDR when the specific pre-arbitration reason requires a new form, even if the reason code remains unchanged.

Pre-compliance or compliance initiation
When you initiate outbound pre-compliance or compliance cases, the system automatically generates EBDR form 1185, regardless of the chargeback reason code. This ensures compliance with Mastercard requirements for these specific case types.

Each Mastercard dispute reason code corresponds to a specific EBDR form. The following table shows which form SDAA generates for each reason code: 

SDAA automatically populates common fields across all EBDR forms using data from your clearing API and Case information. This automation reduces manual data entry and ensures consistency. Common fields include the acquirer reference date, merchant name, transaction date, and dispute amount. Each field sources its data from specific properties in the clearing API or calculated values from the dispute processing workflow.