Card transaction disputes V1

Card transactions are the most commonly disputed transactions types. This guide explains the card dispute process, how to initiate, manage and monitor until the dispute is resolved.

This is the Version 1 (V1) of the Card transaction disputes guide. For the Version 2 flow, see Card transaction disputes V2.

The planned rollout for Version 2 of Synctera’s Dispute Management is as follows:

• Mastercard programs: September 7 - October 7, 2026:
  • Synctera will notify you about the exact date - until then, please follow this V1 flow
• Visa programs and support for PULSE transactions: TBD
  • Keep following this V1 flow until further notice

Primary regulations

US regulations are strict when it comes to consumer transactions:

• Regulation E applies to consumer debit transactions - it mandates issuance of provisional credit to the customer account while the dispute is under investigation
• Regulation Z applies to consumer credit transactions - it mandates that a transaction that is under dispute is not included in the outstanding/due balances, and is not included in the available credit balance
• These regulations also have strict timelines around customer notifications, which is ultimately the responsibility of the FinTech

There are no specific regulations around commercial transactions.

Card networks also have their own zero liability policies - cardholders won’t be held responsible for unauthorized charges made with their card or card information provided they promptly report the issue.

Best practices

The dispute process is expensive for a FinTech as it carries potential loss of revenue, incurs network fees, and can add management overhead costs. For that reason, it is in the FinTech’s best interest to implement measures to avoid disputes.

The following are best practices for avoiding or resolving disputes:

• Only posted transactions can be disputed, and for card transactions only if within 120 days from the settlement. A pending transaction cannot be disputed.
• Before creating a dispute, advise the customer to contact the merchant directly to resolve the issue. If the issue cannot be resolved, a dispute can be initiated.
• Request supporting documentation, such as receipts or email communication with the merchant and timelines.
• When a card is reported lost, stolen, or compromised, immediately freeze the card to prevent unauthorized transactions.
• A dispute cannot exceed the amount of the original transaction.
• For processing cost reasons, a card transaction dispute below $25 is typically written off and not submitted to the network.
  FinTechs can contact their Synctera representative to change the write-off threshold amount for their program.

Dispute investigation / lifecycle

The image below shows the high-level flow between the different actors in the card transaction dispute lifecycle:

• The cardholder: The customer, initiates or requests the dispute to be initiated
• The issuer: The issuer of the card (FinTech backed by sponsor bank), receives the complaint from the customer and ensures that the dispute is investigated
• The network: Mastercard/Visa, facilitates the communication between the issuer and the acquirer and enforces rules, and acts as the final judge if the case proceeds to the arbitration phase
• The acquirer: The merchant’s bank, manages the dispute process on behalf of the merchant
• The merchant: The business from which the cardholder purchased goods/services, receives notice of the dispute from the acquirer and gathers evidence to fight the chargeback

Responsibilities - FinTech / sponsor bank / Synctera

• Initiating a dispute:
  • The FinTech is responsible for initiating the transaction dispute on behalf of the customer. How to initiate a dispute through the Synctera Console is described here.
  • As part of initiating the dispute, the FinTech provides reason codes and compelling evidence. See this article for more information.
• Reviewing a dispute:
  • Once the FinTech has initiated the dispute, a Dispute case is automatically created on the Synctera platform.
  • From this point, Synctera’s Ground Control team handles the dispute case, and determines whether it should be:
    • denied - not eligible for chargeback
    • written off - low-value transactions
    • submitted to the network for chargeback
• Issuing a provisional credit:
  • The Synctera system will automatically issue a provisional credit when required by regulations - 10 business days from dispute reporting for established accounts and 20 business days from dispute reporting for new accounts.
    FinTech can use the Create - Provisional Credit action for immediate posting of the provisional credit. This action requires additional permissions, which can be requested through a Synctera representative.

• Monitoring dispute progress:
  • The Synctera system automatically updates the case/dispute status based on network progress. The Synctera Ground Control team ensures that any required actions are taken within investigation deadlines that the system sets automatically based on regulations.
• Dispute resolution:
  • When a case resolution is reached, the Synctera system automatically updates the case and does the necessary postings, including reversing provisional credit and posting a final credit, when applicable.
• Notifying customer according to regulations:
  • The FinTech is responsible for all customer communication, including sending notifications to customers at different stages of the dispute as per regulations - see details here.
  • The FinTech can monitor the dispute status through Dispute webhooks - see details here

As described above, there is no involvement required from the sponsor bank in the dispute review process.

The dispute flow on the Synctera platform

The below flow diagram shows the different actions that the issuer and the acquirer can take throughout the transaction dispute lifecycle. It also shows what dispute lifecycle status and decision status is at each stage in the flow.

1. Dispute a transaction:

• FinTech (representing the issuer) receives a dispute request from cardholder, and initiates a dispute on the Synctera platform, which automatically creates a dispute case.

2. Issuer action:

• If the dispute amount is below the set write-off $-threshold ($25 by default), the dispute is automatically written off
• If the dispute amount is above the write-off $-threshold, the Synctera Ground Control team investigates the dispute and determines, with the help of the system, whether it is eligible for a chargeback.
  • If not eligible, the dispute is denied and the case closed.
  • If eligible, the Ground Control team either:
    • Submits a network chargeback by sending a notice to the acquiring bank through the card network.
      • In case a refund is received from the merchant after the chargeback is initiated, the dispute can be reversed by Ground Control or automatically rejected by the network.

3. Chargeback initiated -> acquirer action:

• If the issuer submitted the chargeback to the network, the acquiring bank informs the merchant of the chargeback. The merchant reviews the chargeback information and decides whether to accept or file a representment.
• If the merchant chooses to dispute the chargeback, they respond to the acquiring bank with evidence to support their case.

4. Representment -> issuer action:

• If the merchant filed a representment, the issuer is notified of the representment. Ground Control evaluates the merchant’s response and decides whether to accept or dispute the representment by submitting a pre-arbitration request.

5. Pre-arbitration:

• During the pre-arbitration step, the issuing bank and acquiring bank attempt to agree on the chargeback.
• The merchant can decide to accept the loss or rebut the pre-arbitration request.
• If the issuer agrees agrees with the merchant’s pre-arbitration response, they reverse the request. Alternatively, they can take the case to arbitration with the network.
  Issuers and acquirers generally choose to avoid arbitration as it involves fees as high as $500 or more per case in addition to any other fees associated with the dispute.

6. Arbitration:

• Unless merchant or issuer agree on a resolution, the network (arbitrator) reviews the chargeback and makes a final decision, either in favor of the issuer or the merchant. The decision is final and binding on both the merchant and the issuing bank.

How to submit a card transaction dispute?

To dispute a cleared/posted transaction in the Synctera Console, go to Posted Transactions and Actions in the top right corner of the screen.

If a transaction has already been disputed, a link to the related dispute case is shown on the Cases-tab.

If there is an ongoing dispute case for the transaction, the action to Dispute transaction is disabled.

To submit the dispute, the following information must be provided before clicking Submit:

• Note:
  • Information about the dispute, typically what the customer provides when submitting the dispute to the FinTech
• Dispute reason:
  • The reason for the dispute - this reason may be overridden with a more appropriate/correct reason by the team reviewing the dispute
  • For dispute reasons, see here
• Date reported:
  • The date reported by customer is important for establishing the correct deadlines for provisional credit and investigation
• Disputed amount:
  • This will be defaulted to the amount of the transaction being disputed on, in case of a partial dispute, to the remaining undisputed amount

Submit the dispute:

• When the dispute is submitted, a dispute record is automatically created, and subsequently also the Synctera Dispute Case.
• Any updates to the dispute status are automatically reflected in the Synctera Dispute Case.

What’s displayed for Card Dispute cases

Case status

The case status is shown at the top of the Dispute case - to the right of the case description.

Note that the Synctera Case status is different from the dispute Lifecycle status, which is described further below.

The following Case statuses are available:

Customer and Account

Shows information about the Customer and the Account to which the disputed transaction applies - click on the three dots in the right corner on each tile to view full customer or account details:

Transaction

Shows information about the Transaction being disputed - click on the transaction amount or the three dots in the right corner to view full transaction details:

All postings related to the dispute, both customer- and settlement-related postings, can be listed by going to Transactions - Posted and searching by the Reference ID. For example:

Card

Shows information about the Card to which the disputed transaction belongs - click on the card number or the three dots in the right corner to view full card details:

Lifecycle status, Decision and Credit status

Together, the Lifecycle status, Decision and Credit status tell you where the dispute is at.

• The Lifecycle status tells you in which step in the dispute flow the dispute is
• The Decision tells you if a decision has been reached
• The Credit status tells you if a provisional credit or a final credit was posted or not

Also, the note that was entered when the case was submitted is shown under Note.

*Decision “None” means that the dispute was denied, i.e. neither written off nor submitted to the network, or that the network rejected the chargeback and case was closed without case resubmission  

General Info / submission details

Information about Disputed date, Disputed amount, Reason code and Investigation deadline, which is calculated automatically based on network timelines.

Applicable regulations and provisional credit requirements

Applicable regulation and provisional credit requirements are populated automatically based on the type of transaction (for example, consumer/commercial, debit/credit).

Eligibility and other parameters impacting the dispute flow

There are various other parameters that impact the dispute flow and eligibility.

• Disputed through:
  • Marqeta, when direct integration between Synctera and the network is not available
  • Mastercard, for Mastercard transactions that can be disputed through Synctera’s integration with Mastercard
• 3DS authentication: If a transaction was authenticated through 3DS, it is not eligible for a chargeback with the network (i.e. will get rejected by the network).
• Digital wallet token transaction: If a transaction was processed using a digital wallet token, it is not eligible for a chargeback with the network (i.e. will get rejected by the network).
• Card form: It is of importance to know whether a physical or a virtual card was used for the transaction, as it may impact the decision.
• Card category: Rules and regulations are different for consumer and commercial cards.
• Card type: Rules and regulations are different for debit and credit cards.

Action history

Shows all dispute lifecycle transitions/events:

Related Cases

The second tab on the Dispute case shows Related cases, that is, other dispute cases opened for the same customer. This may help indicate whether a fraud pattern can be established for the customer.

History

The third tab on the Dispute case shows the case History, i.e. all the status transitions of the Synctera Dispute Case.

Case assignment and document upload

As for other case types, the Dispute case provides the ability to add an assignee and assign a priority to the case.

In addition, documents/attachments can be uploaded to the case at any time, along with notes.

How to action a case

The system will automatically determine/display the case- and dispute-actions that are available based on the dispute status (lifecycle status / decision).

Unless FinTechs manages their provisional credit, all actions are taken by Synctera system or Ground Control team.

Take Dispute Action

As long as the dispute decision has not been reached, a dispute action can be taken. For all available dispute actions, see this section in the API Guide for Card Transaction Disputes.

Additional notes:

• Posting of provisional credits is done automatically, if required by regulations, within 10 business days for established accounts and within 20 business days for new accounts. However, there is an action, PROVISIONAL_CREDIT - CREATE, that can be used for immediate posting of the provisional credit.

Close case

In the scenario where a decision has been reached (Decision = Won / Lost / Resolved) or case worker decides to deny the dispute, the case can be closed.