Chronology / documented sequence
Chronology connects the published records while distinguishing the author’s allegations, institutional statements, and questions that require further evidence. An investigation acknowledged in the past is not a finding of liability or confirmation of its current status.
Last updated:
A bank notice states that a replacement card would be delivered through the authorized courier. The notice date does not, by itself, establish when the courier physically received the card.
The initiating record pairs the first waybill history with an Amazon-related alert for the first card. The alert does not, by itself, establish a completed purchase or a financial debit.
The record includes a second Amazon-related alert concerning the replacement card, alongside a second waybill. The relationship between the card events and the delivery records requires technical examination.
In Case 76532739, Aramex states that the mobile number attached to waybill 49715021705 was incorrect.
A Riyad Bank complaint response states that the card was reissued and remained unactivated at the time of the response.
The public tracking images show both waybills updated to “Returned to Shipper” in the same recorded minute. The matching timestamps raise a question about how the events were recorded; they do not independently establish tampering.
The author submitted a report through Mastercard’s website concerning the security of two Riyad Bank cards and requested a review of issuer compliance and payment-data protection standards. The submission contained the author’s allegations, not Mastercard findings.
Ask Mastercard requested additional details and the first six digits of the card numbers. The author supplied a detailed account and supporting material that day.
Under reference 5388285, Mastercard stated that the inquiry had been escalated to the relevant team to investigate a potential violation and determine appropriate action. It explained that resulting actions would not be reported to the consumer.
Following the author’s October 22 follow-up, Mastercard confirmed an internal investigation concerning the issuer’s compliance with regulations. This establishes what Mastercard said about the case at that time—not a finding against Riyad Bank or confirmation of a penalty.
The author sent a follow-up describing developments in the domestic handling of the complaint and requesting review of the evidence. He clarified that the concern was card-data activity rather than reimbursement for a completed payment.
A records request under reference 5607950 cited the earlier case, 5388285. Mastercard explained that it does not issue cards or manage cardholder accounts and referred the author to the issuer. He replied that he was seeking technical and processing records, not account administration. He did not receive the requested logs in the correspondence presented.
The author submitted a further request through Mastercard’s website concerning the existing case and associated evidence. According to his documentation as of September 2, 2026, he had received no subsequent reply to this submission. This was a website request, not an email.
The author made another submission through Mastercard’s website. According to his documentation as of September 2, 2026, he had received no subsequent reply. The absence of a reply does not independently establish that no internal processing occurred or that an applicable legal deadline was exceeded.
HD.39 publishes a focused notice addressed to Mastercard and Riyad Bank. It requests the procedural path of Case 5388285 without asserting an undisclosed investigative result or seeking access to confidential deliberations.
HD.39 publishes a group-level review request based on two waybills, Aramex’s written contact-data admission, the shared recorded return minute, and the later record-availability question. The article expressly distinguishes those facts from allegations that remain unproven.
Under Case 130955673, Aramex Customer Service stated that waybills 49715021705 and 49715146165 did not appear in its system and referred the inquiry to the sender. The response establishes the result communicated by Customer Service on that date; it does not independently define the status of archives or internal audit records.
These entries are presented separately to avoid implying a chronological position that the available summary does not establish.
Inquiry date not specified in this summary
A waybill previously acknowledged in writing was later described as not found or unavailable in the queried system. This event is listed separately because its inquiry date is not established here.
During 2026
HD.39 publishes source documents, competing statements, technical analysis, and requests for accountable answers.