{"_id":"5be62ed55ed2bb000d1243ab","project":"59f79e3c584eb200345ceafc","version":{"_id":"5ba178b00a916500030c6a21","project":"59f79e3c584eb200345ceafc","__v":24,"forked_from":"59f79e3c584eb200345ceaff","createdAt":"2015-09-17T03:47:20.956Z","releaseDate":"2015-09-17T03:47:20.956Z","categories":["5ba178b00a916500030c69a2","5ba178b00a916500030c69a3","5ba178b00a916500030c69a4","5ba178b00a916500030c69a5","5ba178b00a916500030c69a6","5ba178b00a916500030c69a7","5ba178b00a916500030c69a8","5ba178b00a916500030c69a9","5ba178b00a916500030c69aa","5ba178b00a916500030c69ab","5ba178b00a916500030c69ac","5afb6888212c690003ae3d3b","5ba178b00a916500030c69ad","5ba178b00a916500030c69ae","5ba2dcbc99f53f0003b97e2c","5babd73fa0ab3e0003ead030","5bb4038be7222e000334dd97","5bb55954478c1300031a44c2","5bb665a1607307000327c81e","5bb6f90229a7fb0003a0650d","5bb7f9bc29a7fb0003a07ac1","5bba58bd7ba7710003bd901d","5bba6dac7ba7710003bd908d","5bba6e257ba7710003bd9090","5bbac87810189c0003e619ea","5bbb9d02b5862c00036266b2","5bbbadb6219c3e000376c2de","5bc417751d1b0000182bf7f6","5bc59e3b2a5b4f0044db5b97","5bc7bbce2262cc0041f6eff2","5bce6a3580a7250031199f34","5bcfac2c4082510019f2d91b","5bcfac3757bed90030e45d68","5bcfac45d305bc0049941539","5bd2a43548bb6f00289c8fad","5bd3a42a026ebe001f66259e","5bd9d5afffe003005b02f97b","5becb7ee85c6b300557662b6"],"is_deprecated":false,"is_hidden":false,"is_beta":true,"is_stable":false,"codename":"","version_clean":"3.2.0","version":"3.2"},"category":{"_id":"5bce6a3580a7250031199f34","project":"59f79e3c584eb200345ceafc","version":"5ba178b00a916500030c6a21","__v":0,"sync":{"url":"","isSync":false},"reference":false,"createdAt":"2018-10-23T00:24:21.671Z","from_sync":false,"order":18,"slug":"card-number-issuance","title":"Issue Debit Card"},"user":"5557e76e512c300d007730d1","__v":0,"parentDoc":null,"updates":[],"next":{"pages":[],"description":""},"createdAt":"2018-11-10T01:05:25.156Z","link_external":false,"link_url":"","sync_unique":"","hidden":false,"api":{"settings":"","results":{"codes":[]},"auth":"required","params":[],"url":""},"isReference":false,"order":8,"body":"[block:callout]\n{\n  \"type\": \"warning\",\n  \"title\": \"Currently in Beta\",\n  \"body\": \"Our card disputes API is currently live in beta. We welcome your feedback.\"\n}\n[/block]\nIf a user wants to dispute a transaction, use this call to submit the transaction dispute. We recommend building this functionality into your application to automate the dispute workflow.\n\nYour platform is responsible for covering the provisional and final credits from your reserve account. In the event that our partner bank receives a credit from the merchant as a result of the chargeback, it will be applied to your reserve account. See more details on this process below.\n\n##API ENDPOINT\nhttps://uat-api.synapsefi.com/v3.1/users/:user_id/nodes/:node_id/trans/:trans_id/dispute\n\n##PATH PARAMETER\n[block:html]\n{\n  \"html\": \"<div class=\\\"api-manager\\\"> <div class=\\\"param-table\\\"> <div class=\\\"table\\\"> <div class=\\\"tr\\\"> <div class=\\\"td param\\\"><strong>user_id<span class=\\\"colon\\\">:</span></strong> <div class=\\\"required\\\">required</div></div><div class=\\\"td\\\"><strong class=\\\"param-type\\\">string</strong> <div marked=\\\"\\\" class=\\\"ng-isolate-scope\\\"> <p>ID of user owning the card</p></div></div></div>\\n  \\n  <div class=\\\"tr\\\"> <div class=\\\"td param\\\"><strong>node_id<span class=\\\"colon\\\">:</span></strong> <div class=\\\"required\\\">required</div></div><div class=\\\"td\\\"><strong class=\\\"param-type\\\">string</strong> <div marked=\\\"\\\" class=\\\"ng-isolate-scope\\\"> <p>ID of the card node</p></div></div></div>\\n  \\n   <div class=\\\"tr\\\"> <div class=\\\"td param\\\"><strong>trans_id<span class=\\\"colon\\\">:</span></strong> <div class=\\\"required\\\">required</div></div><div class=\\\"td\\\"><strong class=\\\"param-type\\\">string</strong> <div marked=\\\"\\\" class=\\\"ng-isolate-scope\\\"> <p>ID of the disputed transaction</p></div></div></div>\\n  \\n  </div></div></div>\"\n}\n[/block]\n##EXAMPLE REQUEST\n[block:code]\n{\n  \"codes\": [\n    {\n      \"code\": \"PATCH /v3.1//users/594e0fa2838454002ea317a0/nodes/5bdb96d0389f2400afb06fe6/trans/5bdb9baed5faec00e4e9933e/dispute \\nHTTP/1.1\\nHost: uat-api.synapsefi.com\\nX-SP-GATEWAY: client_id_2bb1e412edd311e6bd04e285d6015267|client_secret_2bb1e714edd311e6bd04e285d6015267\\nX-SP-USER-IP: 127.0.0.1\\nX-SP-USER: oauth_1mtgLwhYHDVKop04XOEjyWJSsnQqZbGkfRF5ux9v|e83cf6ddcf778e37bfe3d48fc78a6502062fc\\nContent-Type: application/json\\n\\n{\\n\\t\\\"dispute_reason\\\":\\\"CHARGE_BACK\\\"\\n}\",\n      \"language\": \"http\",\n      \"name\": \"Charge backs\"\n    },\n    {\n      \"code\": \"PATCH /v3.1//users/594e0fa2838454002ea317a0/nodes/5bdb96d0389f2400afb06fe6/trans/5be62c691d3f37345ec9a2e4/dispute \\nHTTP/1.1\\nHost: uat-api.synapsefi.com\\nX-SP-GATEWAY: client_id_2bb1e412edd311e6bd04e285d6015267|client_secret_2bb1e714edd311e6bd04e285d6015267\\nX-SP-USER-IP: 127.0.0.1\\nX-SP-USER: oauth_1mtgLwhYHDVKop04XOEjyWJSsnQqZbGkfRF5ux9v|e83cf6ddcf778e37bfe3d48fc78a6502062fc\\nContent-Type: application/json\\n\\n{\\n\\t\\\"dispute_reason\\\":\\\"CHARGED_TWICE\\\"\\n}\",\n      \"language\": \"text\",\n      \"name\": \"Charged Twice\"\n    }\n  ]\n}\n[/block]\n##EXAMPLE RESPONSE\n[block:code]\n{\n  \"codes\": [\n    {\n      \"code\": \"{\\n    \\\"dispute_form\\\": \\\"https://cdn.synapsepay.com/uploads/2018/10/25/z4owXU1l0xFkJ9CbtWfV7Zu53gBryLEpsKjcdPDI2qTMQ68eGO.pdf\\\",\\n    \\\"provisional_credit_tran\\\": \\\"5bd20bd12073c800fe748fe9\\\",\\n    \\\"success\\\": true\\n}\",\n      \"language\": \"json\",\n      \"name\": \"Charge Back\"\n    },\n    {\n      \"code\": \"{\\n    \\\"dispute_form\\\": \\\"https://cdn.synapsepay.com/uploads/2018/11/10/ebIqPTr12dzGEFJktXR5Nv983KUL0finQ4MVWjwm7hBSCDYZxA.pdf\\\",\\n    \\\"provisional_credit_tran\\\": \\\"5be62cc01d3f37345bc8f15f\\\",\\n    \\\"success\\\": true\\n}\",\n      \"language\": \"json\",\n      \"name\": \"Charged Twice\"\n    }\n  ]\n}\n[/block]\n##Initial Response\nWe will respond within 24 business hours to let you know that we are processing the dispute. If the user sends a dispute to us directly, we will include the platform on our response to the user.\n\nFor any dispute, other than merchant disputes, the card must be reset by the platform. If it is a physical card, please reset and ship the card.\n\n##Provisional Credit\nProvisional credit will be given to the user immediately upon receipt of the completed dispute form. Synapse will transfer these funds from the Platform’s reserve account to the user’s card node. This ensures adherence to the time frames set forth by Regulation E as well as Visa. \n\nSynapse will send notice of the provisional credit directly to the user, via email with the platform cc’d. This will be sent within 2 business days, as required.\n\nThe sole exception to this, is a new account, for which we can take up to 20 days to provide provisional credit. A “New account” is defined as an account that has received its first credit within 30 days of the disputed transaction. If the Platform wishes to withhold provisional credit for the 20 day time period they must state this within the email when they submit the dispute form to Synapse.\n\n##Investigation\nSynapse will facilitate the transmission of the dispute to our partner bank for investigation.\n\nInvestigations can take up to 90 days. Additional information regarding these limitations can be found in section 15 of the cardholder agreement and is also discussed in the required EFT disclosures (in platform’s spec sheet).\n\n##Resolution\nSynapse will notify the user within 3 business days of the completion of the investigation, as required. They will be notified that:\n* the provisional credit is considered final; or\n* the merchant provided evidence that no error occurred, provisional credit has been rescinded and supporting documents used in the investigation are available to them if they’d like to request them. If there are insufficient funds in the account to cover the withdrawal of provisional credit, the transaction will still be processed. The platform may hold the user liable for this amount, and follow charge-off procedures if it is not recovered.","excerpt":"","slug":"dispute-a-transaction-1","type":"basic","title":"Dispute a transaction"}

Dispute a transaction


[block:callout] { "type": "warning", "title": "Currently in Beta", "body": "Our card disputes API is currently live in beta. We welcome your feedback." } [/block] If a user wants to dispute a transaction, use this call to submit the transaction dispute. We recommend building this functionality into your application to automate the dispute workflow. Your platform is responsible for covering the provisional and final credits from your reserve account. In the event that our partner bank receives a credit from the merchant as a result of the chargeback, it will be applied to your reserve account. See more details on this process below. ##API ENDPOINT https://uat-api.synapsefi.com/v3.1/users/:user_id/nodes/:node_id/trans/:trans_id/dispute ##PATH PARAMETER [block:html] { "html": "<div class=\"api-manager\"> <div class=\"param-table\"> <div class=\"table\"> <div class=\"tr\"> <div class=\"td param\"><strong>user_id<span class=\"colon\">:</span></strong> <div class=\"required\">required</div></div><div class=\"td\"><strong class=\"param-type\">string</strong> <div marked=\"\" class=\"ng-isolate-scope\"> <p>ID of user owning the card</p></div></div></div>\n \n <div class=\"tr\"> <div class=\"td param\"><strong>node_id<span class=\"colon\">:</span></strong> <div class=\"required\">required</div></div><div class=\"td\"><strong class=\"param-type\">string</strong> <div marked=\"\" class=\"ng-isolate-scope\"> <p>ID of the card node</p></div></div></div>\n \n <div class=\"tr\"> <div class=\"td param\"><strong>trans_id<span class=\"colon\">:</span></strong> <div class=\"required\">required</div></div><div class=\"td\"><strong class=\"param-type\">string</strong> <div marked=\"\" class=\"ng-isolate-scope\"> <p>ID of the disputed transaction</p></div></div></div>\n \n </div></div></div>" } [/block] ##EXAMPLE REQUEST [block:code] { "codes": [ { "code": "PATCH /v3.1//users/594e0fa2838454002ea317a0/nodes/5bdb96d0389f2400afb06fe6/trans/5bdb9baed5faec00e4e9933e/dispute \nHTTP/1.1\nHost: uat-api.synapsefi.com\nX-SP-GATEWAY: client_id_2bb1e412edd311e6bd04e285d6015267|client_secret_2bb1e714edd311e6bd04e285d6015267\nX-SP-USER-IP: 127.0.0.1\nX-SP-USER: oauth_1mtgLwhYHDVKop04XOEjyWJSsnQqZbGkfRF5ux9v|e83cf6ddcf778e37bfe3d48fc78a6502062fc\nContent-Type: application/json\n\n{\n\t\"dispute_reason\":\"CHARGE_BACK\"\n}", "language": "http", "name": "Charge backs" }, { "code": "PATCH /v3.1//users/594e0fa2838454002ea317a0/nodes/5bdb96d0389f2400afb06fe6/trans/5be62c691d3f37345ec9a2e4/dispute \nHTTP/1.1\nHost: uat-api.synapsefi.com\nX-SP-GATEWAY: client_id_2bb1e412edd311e6bd04e285d6015267|client_secret_2bb1e714edd311e6bd04e285d6015267\nX-SP-USER-IP: 127.0.0.1\nX-SP-USER: oauth_1mtgLwhYHDVKop04XOEjyWJSsnQqZbGkfRF5ux9v|e83cf6ddcf778e37bfe3d48fc78a6502062fc\nContent-Type: application/json\n\n{\n\t\"dispute_reason\":\"CHARGED_TWICE\"\n}", "language": "text", "name": "Charged Twice" } ] } [/block] ##EXAMPLE RESPONSE [block:code] { "codes": [ { "code": "{\n \"dispute_form\": \"https://cdn.synapsepay.com/uploads/2018/10/25/z4owXU1l0xFkJ9CbtWfV7Zu53gBryLEpsKjcdPDI2qTMQ68eGO.pdf\",\n \"provisional_credit_tran\": \"5bd20bd12073c800fe748fe9\",\n \"success\": true\n}", "language": "json", "name": "Charge Back" }, { "code": "{\n \"dispute_form\": \"https://cdn.synapsepay.com/uploads/2018/11/10/ebIqPTr12dzGEFJktXR5Nv983KUL0finQ4MVWjwm7hBSCDYZxA.pdf\",\n \"provisional_credit_tran\": \"5be62cc01d3f37345bc8f15f\",\n \"success\": true\n}", "language": "json", "name": "Charged Twice" } ] } [/block] ##Initial Response We will respond within 24 business hours to let you know that we are processing the dispute. If the user sends a dispute to us directly, we will include the platform on our response to the user. For any dispute, other than merchant disputes, the card must be reset by the platform. If it is a physical card, please reset and ship the card. ##Provisional Credit Provisional credit will be given to the user immediately upon receipt of the completed dispute form. Synapse will transfer these funds from the Platform’s reserve account to the user’s card node. This ensures adherence to the time frames set forth by Regulation E as well as Visa. Synapse will send notice of the provisional credit directly to the user, via email with the platform cc’d. This will be sent within 2 business days, as required. The sole exception to this, is a new account, for which we can take up to 20 days to provide provisional credit. A “New account” is defined as an account that has received its first credit within 30 days of the disputed transaction. If the Platform wishes to withhold provisional credit for the 20 day time period they must state this within the email when they submit the dispute form to Synapse. ##Investigation Synapse will facilitate the transmission of the dispute to our partner bank for investigation. Investigations can take up to 90 days. Additional information regarding these limitations can be found in section 15 of the cardholder agreement and is also discussed in the required EFT disclosures (in platform’s spec sheet). ##Resolution Synapse will notify the user within 3 business days of the completion of the investigation, as required. They will be notified that: * the provisional credit is considered final; or * the merchant provided evidence that no error occurred, provisional credit has been rescinded and supporting documents used in the investigation are available to them if they’d like to request them. If there are insufficient funds in the account to cover the withdrawal of provisional credit, the transaction will still be processed. The platform may hold the user liable for this amount, and follow charge-off procedures if it is not recovered.