Retrieval request
Issuers send Retrieval Requests through the Network to receive documentation from Acquirers. The Issuer may have to request documentation from the Acquirer before a chargeback is filed. The Issuer must allow the Acquirer sufficient time for the fulfilment of the request. The Issuer must also review the received documentation to ensure the intended Chargeback Reason is appropriate.
Pega Foundation for Healthcare
In the Retrieval Request Notification, the Issuer must specify the Retrieval Request Notification Message Reason Code and the Function Code (Document Type).
Retrieval Request - Description
| ISO Message Reason Code | Retrieval Request Notification Reason | Description |
| 6003 | Chargeback Documentation | Issuer is requesting documentation to validate that the transaction qualifies for a first chargeback. |
| 6006 | Legal Request or Fraud Analysis | Issuer is requesting documentation in support of a fraud investigation or as a result of a legal request. |
| 6008 | Cardmember Requests Copy of ROC | Issuer is requesting documentation on behalf of the cardmember requesting a copy of the ROC. |
| 6013 | Repeat Documentation Request | Issuer submitted previous Retrieval Request and is repeating the original request for documentation. |
| 6014 | Cardmember does not recognize Transaction or Transaction Amount | Issuer is requesting documentation on behalf of the cardmember. The cardmember does not recognize the transaction or transaction amount and is requesting documentation to validate authorization of the transaction. |
| 6016 | Cardmember needs for personal records | Issuer is requesting documentation on behalf of the cardmember. The cardmember is not disputing the transaction, but require documentation. |
| 6304 | ATM Journal Roll/Audit Tape Request | Issuer is requesting documentation on behalf of the cardmember. The cardmember is requesting a copy of the ATM Journal Roll/Audit Tape Request. |
Previous topic Rules in inbound pre-arbitration and aribitration Next topic Overview