Denied refund.

Jul 2Details My name is Isaac Moses Modise Tsela

Incident:*** I paid R100 into an incorrect customer code : *** instead of customer ***. I have provided all the necessary proofs regarding this transactions and I was requested what is not available as far as the the transaction was processed. The transaction is not an EFT, therefore an EFT proof does not exists. Therefore the R100 is sitting into a suspended customer code, it cannot realized by self nor anyone as the customer code was linked to a decoder and that decoder is no more. Initially I requested that the funds be transferred to another customer code. The customer codes belongs to the same person. However to date my requests have been declined. Either MultiChoice creates convinient way to make payments and in return rob people because it cannot be coorect that without an EFT slip the funds cannot be realized by the rightfull owner. The bank has even confirmed the transaction which this proof has been provided. As an example a petrol car cannot be sold where diesel only exists. This is what MultiChoice Is doing. The platform used to make payment is that you go on to the MultiChoice website choose a bank, punching your ID, then the amount, and the payment will request authorisation on a bank app, then the transaction is concluded. This method is not an EFT. So a normal EFT payment slip will never be generated, hense my bank digital transaction team provided a letter conforming the transaction. With all of this information provided I cannot have this funds transferred to the other customer code and I cannot have this funds refunded. On the very same month I made another payment in order to be able to continue with my subscription. I was only enlightened that the other customer code which according to me was closed and no longer exist, in their books the information is still there and active as it was able to receive funds. This customer code back dating 10 years back.

I have explained various circumstances querying this long 10 year customer code incident *** dated 30- August 2015