Dispute Transaction

Status Changelog Dashboard Create a Ticket
Search…
Dispute Transaction
patch
https://api.synapsefi.com
/v3.1/users/:user_id/nodes/:node_id/trans/:tran_id/dispute
Dispute
Card Transactions
If you wish to learn more about Card Disputes, see: Card Disputes Guide.
Dispute Reasons
Code
Description
Chargeback‎_Rights
INCORRECT_AMOUNT
Incorrect Amount was charged on the card.
Yes. No if the transaction is a VALID EMV transaction.
INCORRECT_AMOUNT|ATM
User attempted to withdraw money from ATM and received incorrect amount.
Yes, but only for the amount not dispensed.
UNAUTHORIZED|CARD_LOST
Unauthorized transaction made and user has reported a lost or stolen card.
Yes. No if the transaction is a VALID EMV transaction or online transaction as this defaults to chip-liability shift, which is not applicable to MOTO transactions, or at an ATM.
UNAUTHORIZED|CARD_IN_HAND|SHARED
Unauthorized transaction made while user has card in their possession and card is shared with other users.
Yes. No if the transaction is a VALID EMV transaction, or disputed transactions was authorized by other users of the card, or at an ATM.
UNAUTHORIZED|CARD_IN_HAND|NOT_SHARED
Unauthorized transaction made while user has card in their possession and card is not shared with other users.
Yes. No if the transaction is a VALID EMV transaction, or at an ATM.
CHARGED_TWICE|CREDIT_NOT_PROCESSED|DUPLICATE
There was a duplicate transaction but the merchant did not process a credit to correct the error. This typically occurs when when a merchant a merchant fails to correct a previously acknowledged error. This can also occur when a cardholder attempts to return a purchased item or cancel services but is not compliant with the merchant's return policy (e.g. expired receipt or warranty issue).
Yes. No if the transaction is a VALID EMV transaction, or no duplicate posts to same account.
CHARGED_TWICE|CREDIT_NOT_PROCESSED|PAID_BY_OTHER_MEANS
There was a duplicate transaction in which the original debit settled on the card even though the original card transaction was canceled. Occurs when the cardholder chose to use another payment method (e.g. cash or a different card).
Yes. No if the transaction is a VALID EMV transaction, or there is not supporting evidence of a charge elsewhere.
CANCEL_RECURRING_PMT
Canceling recurring payment (i.e. a recurring payment was debited after cancellation).
Yes. No if the transaction is a VALID EMV transaction, or cancellation was within three days of charge authorization.
MERCHANT|DEFECT_OR_NOT_AS_DESC
Merchandise/service not as described or defective merchandise/service.
Yes. No if the transaction is a VALID EMV transaction.
MERCHANT|NOT_RECEIVED
Did not receive merchandise or services (not a quality issue).
Yes. No if the transaction is a VALID EMV transaction, or if merchant hasn't been allowed 15 calendar days for items to arrive or to provide a date of expected arrival.
MERCHANT|QUALITY
Issue with quality of services or merchandise.
Yes. No if the transaction is a VALID EMV transaction, or services were paid for after service was rendered.
MERCHANT|DAMAGED_MERCH
Damaged merchandise.
Yes. No if the transaction is a VALID EMV transaction.
MERCHANT|RETURNED_MERCH
Returned merchandise.
Yes. No if the transaction is a VALID EMV transaction, or there is no supporting evidence of a return.
Dispute Meta
Currently Dispute Meta is only required for Card Transaction. Following are the fields allowed in dispute_meta:
Key
Type            
Required Dispute Reasons
Description                                                                
amount_debited
Float
INCORRECT_AMOUNT
Amount debited in Number.
amount_received
Float
INCORRECT_AMOUNT|ATM
Amount received in Number.
lost_date
Int
UNAUTHORIZED|CARD_LOST
Date lost (milliseconds since Unix epoch time).
how_lost
String
UNAUTHORIZED|CARD_LOST
Description of how card was lost or stolen.
last_use
String
UNAUTHORIZED|CARD_IN_HAND|SHARED
UNAUTHORIZED|CARD_IN_HAND|NOT_SHARED
Transaction ID for last use of card (i.e. need transaction ID to know where and when card was last used).
people_allowed_use
String
UNAUTHORIZED|CARD_IN_HAND|SHARED
Person(s) who cardholder shared card with (i.e. allowed to use card) and their relationship(s) with cardholder.
contact_date
Int
CANCEL_RECURRING_PMT
Contact date (milliseconds since Unix epoch time).
contact_method
String
CANCEL_RECURRING_PMT
Contact method (e.g. PHONE).
trans_on_same_card
Boolean
CHARGED_TWICE|CREDIT_NOT_PROCESSED|DUPLICATE
CHARGED_TWICE|CREDIT_NOT_PROCESSED|PAID_BY_OTHER_MEANS
Are both transactions on the same card? true or false.

Proof of other transaction required in dispute_attachments
merch_given_attempt_to_resolve
Boolean
CHARGED_TWICE|CREDIT_NOT_PROCESSED|DUPLICATE
CHARGED_TWICE|CREDIT_NOT_PROCESSED|PAID_BY_OTHER_MEANS
Was the merchant given the chance to resolve? true or false.
contact_name
String
CANCEL_RECURRING_PMT
Name of contact.
contact_response
String
CANCEL_RECURRING_PMT
Response from contact.
ACH Transactions
Dispute Reasons
Code
Description
R07
Authorization Revoked by Customer
R08
Payment Stopped
R10
Customer Advises Not Authorized
R29
Corporate Customer Advises Not Authorized
R23
Credit Refused by Receiver
Example Request
HTTP
cURL
Python
JS
PHP
GO
1
PATCH /v3.1/users/605a7a6a7562967ff8c12413/nodes/605125f47e08875d713557ed/trans/6045135016ba41408ece9c25/dispute HTTP/1.1
2
Host: uat-api.synapsefi.com
3
X-SP-USER-IP: 255.127.79.76
4
X-SP-USER: oauth_xg3WXDFu5jNRLlz1ohf6qsU0waJ4BGYbMdrC07pO|e83cf6ddcf778e37bfe3d48fc78a6502062fc
5
Content-Type: application/json
6
​
7
{
8
  "dispute_reason": "CHARGE_BACK",
9
  "dispute_meta": {
10
    "type_of_merchandise_or_service": "groceries",
11
    "merchant_contacted": true,
12
    "contact_method": "phone",
13
    "contact_date": 1563474864000
14
  },
15
  "dispute_attachments": [
16
    "data:image/gif;base64,SUQs=="
17
  ]
18
}
Copied!
1
curl --location --request PATCH 'https://uat-api.synapsefi.com/v3.1/users/605a7a6a7562967ff8c12413/nodes/605125f47e08875d713557ed/trans/6045135016ba41408ece9c25/dispute' \
2
--header 'X-SP-USER-IP: 255.127.79.76' \
3
--header 'X-SP-USER: oauth_xg3WXDFu5jNRLlz1ohf6qsU0waJ4BGYbMdrC07pO|e83cf6ddcf778e37bfe3d48fc78a6502062fc' \
4
--header 'Content-Type: application/json' \
5
--data-raw '{
6
  "dispute_reason": "CHARGE_BACK",
7
  "dispute_meta": {
8
    "type_of_merchandise_or_service": "groceries",
9
    "merchant_contacted": true,
10
    "contact_method": "phone",
11
    "contact_date": 1563474864000
12
  },
13
  "dispute_attachments": [
14
    "data:image/gif;base64,SUQs=="
15
  ]
16
}'
Copied!
1
//
Copied!
1
//
Copied!
1
//
Copied!
1
//
Copied!
​
Dispute Chargebacks
Next - API References
Subscriptions
Last modified 1mo ago
Export as PDF
Copy link
Contents