Transaction Matching
2 min
\<font color="#b6c7cb">\</font> topic type concept purpose explain how chargeback transactions are matched and updated in the audience api integrators and client developers implementing chargeback response workflows applies to clients using the management api to accept disputes, submit evidence, or create chargeback records does not apply to clients searching for chargebacks or performing fraud or risk evaluation when you perform the accept , dataevidence , or imageevidence actions, the searches for a matching case using the mid number and the purchase transaction id if the transaction is found, we update the record if the transaction is not found, we create a new one at the user hierarchy matching scenarios if the finds one match then the updates the order and overrides whatever fields were not sent in the dispute more than one match for the same mid at the same hierarchy updates the most recent order based on the import time no matches returns an error code 400 validation failed a match but the order is resolved returns an error code 400 validation failed in this scenario, the order was already resolved which means, the representment has already been sent to the bank or the dispute was accepted updating the once you receive a code 200 update response from us, the api will update the record on the the data and image updates may take up to one hour to be seen in the platform and, based on the action, it will close the record if no finalmessage of true is sent, the record will not close until 48 hours later for more information see api responses