Case overview / read first

One record.
Questions still open.

This archive examines the card-renewal, delivery, and data-security record involving Riyad Bank and Aramex, together with subsequent correspondence with Mastercard. It separates the author’s allegations, documented institutional statements, and questions that require further evidence.

Last updated:

Two cards and a delivery record

The published material concerns two card numbers in a renewal and replacement sequence, alongside two courier waybills. The relationship between each card and shipment requires careful matching of the underlying records.

Two Amazon-related alerts

The archive documents reported Amazon-related events on May 14 and May 22, 2025. An alert does not, by itself, establish a completed purchase, a financial debit, or the source of the card data.

A contact-data admission

Aramex correspondence acknowledged that an incorrect mobile number was attached to one documented shipment. The source of that number and its operational use remain questions for the relevant records.

An unavailable tracking trail

Tracking records had previously been visible and acknowledged. Under Case 130955673, Aramex Customer Service stated on September 7, 2026 that both shipment numbers did not appear in its system. That response does not, by itself, establish deletion from the underlying systems or archives.

The payment-network correspondence

Mastercard: four submissions and an unresolved follow-up

The Mastercard record contains distinct stages: an issuer-compliance complaint, a later request for records, and two website follow-ups. These stages should not be treated as identical requests or as proof of an undisclosed investigative outcome.

October 2025

Complaint and investigation confirmation

An initial website submission on October 17 was followed by requests for information and an escalation. On October 25, Mastercard confirmed an internal investigation concerning the issuer’s compliance with regulations.

Reference:5388285

February 9, 2026

A request for technical records

A records request cited the earlier case. Mastercard referred the author to the issuing bank. He replied that he sought technical and processing records, not account administration. He did not receive the requested logs in the correspondence presented.

Reference:5607950

August 19, 2026

A further website submission

The author submitted another request through Mastercard’s website concerning the case and associated evidence. According to his documentation as of September 2, 2026, he had received no subsequent reply to this submission.

August 26, 2026

Another website follow-up

A further request was submitted through Mastercard’s website. According to the author’s documentation as of September 2, 2026, no subsequent reply had been received. This does not independently establish that no internal processing occurred.

Questions the record still asks

What a complete answer must address

  1. Data provenance: How did card details become associated with the reported Amazon activity, and which records can establish the timing and source?
  2. Contact integrity: Who supplied the incorrect mobile number, and which system was its source?
  3. Custody: Where were the physical cards at each documented handoff, and which records establish the issuer, production, courier, and return stages?
  4. Record retention: Were the unavailable waybill records deleted, archived, migrated, or merely inaccessible through the public and support interfaces?
  5. Complaint and regulatory review: Which underlying records were requested and examined when the complaints were assessed, closed, or archived?
  6. Mastercard follow-up and access to evidence: Were the later requests linked to the original compliance matter, what status can be disclosed, and which record holders and procedures are relevant to obtaining evidence?

Recommended reading path

Follow the record, not the rhetoric