Dispute API
- Product review
- Documents
  - Authentication Service
    - Login Method ValidateToken Method Logout Method
  - BpEngineApi Service
    - CreateBp Method Download Method Upload Method GetBpItem Method GetBpList Method ProcessAction Method Method GetBpItemActions Method ProccessMerchantStageAction GetComments Method AddComment Method
  - Reporting Service
    - Disputes Method
  - Business logic
    - Dispute case
      - Dispute Case Incoming Case Response Review of the Response Cooling-off Period
    - Fraud case
      - Fraud Case Response to a Case Review of the response Review of the Issuer’s response Cooling-off period
    - Compliance case
      - Compliance Case Response to a Case Review of the response Cooling-off period
    - Good Faith case
      - Good Faith case Responce Good Faith case
  - Service SiomAPI
    - Method GetDetail Method GetPacketStatus Method Send Method GetSiomList
- Technical support
Search

Dispute API documentation

Compliance case

Compliance Case

Compliance is designed to resolve unconventional disputes that cannot be resolved using other dispute cases.
To initiate a case sample, call the CreateBp method by sending to it the following fields as input parameters:

Name	Code	Field type	Visibility (yes unless otherwise indicated)	Necessity (no unless otherwise indicated)	Comments
Compliance description	f_ComplianceDescription	Row		Yes
Dispute amount	f_DisputeAmount	Money		Yes	By default - Original transaction amount. The dispute amount can’t be more than the transaction amount
Reason behind discrepancy between the Regulations violation date and the violation detection date	f_LateRevealReason	Row	Yes if Regulations violation date and Regulations violation detection date are not equal	Yes
Comments	f_Comment	Row
Documents	f_Docs	Files
Clearing status
Regulations violation date	f_ViolationDate	Date		Yes	The Regulations violation date cannot be earlier [RY1] than the transaction date The Regulations violation date cannot be later than the current date
Regulations violation detection date	f_RevealDate	Date		Yes	The violation detection date cannot be earlier than the Regulations violation date The violation detection date cannot be later than the current date
Clearing status	f_AdjClearingStatus	AdjClearingStatus

Decline

Name	Code	Field type	Necessity (no unless otherwise indicated)
Justification	f_DeclineReason	Text	Yes
Documents	f_Docs	Files
Comments	f_Comment	String

Accept Violation

Name	Code	Field type	Visibility (yes unless otherwise indicated)	Necessity (no unless otherwise indicated)
Adjustment amount	f_AdjAmount	Money		Yes
Amount justification	f_Reason	Text	Yes if Adjustment amount is less than Dispute amount	Yes
Documents	f_Docs	Files
Comments	f_Comment	String

Accept Violation

Name	Code	Field type	Necessity (no unless otherwise indicated)
Resolution Method	f_SetlMethodAuthDescription	Text	Yes
Documents	f_Docs	Files
Comments	f_Comment	String

Data Types

Money Type

Code	Data type	Value
amount	Decimal	Amount
currencyCode	Row	Numeric currency code according to the Russian Classification of Currencies (e.g., the Russian ruble is 643)

File Type

Code	Data type	Value
fileName	Row	File name
content	Row	File content in base64