When Records Vanish: Riyad Bank, Aramex, and the Missing Shipment Trail

In the world of digital forensics, there is a golden rule: records do not disappear on their own. When they do, someone made them disappear.

This article documents how records attributed to Riyad Bank and Aramex conflict: waybills acknowledged in formal correspondence later became unavailable through the channels queried by the customer.

The Official Records

Riyad Bank, in formal responses to the Saudi Central Bank (SAMA), confirmed the shipment of two credit cards and referenced the following waybill numbers:

• 49715021705
• 49715146165

These numbers were not invented by the customer. They were provided by the bank and recorded in official complaints.

Aramex’s Written Admission

On June 9, 2025, Aramex customer support (Case 76532739) sent the following explicit admission:

“the mobile number attached to the shipment 49715021705 is incorrect.”

This statement proves that the waybill existed in their system at that time, and that the data attached to it was flawed — leading to the customer receiving no delivery notifications.

One Recorded Minute, Two Waybills

Both shipments were later updated to “Returned to Shipper” at exactly the same minute: July 20, 2025 — 15:57.

The matching minute is evidence of synchronized processing, but the public interface does not reveal whether it resulted from two scans, a container-level event, device synchronization, an administrative update, or batch processing. The internal event logs—not the public timestamp alone—would resolve that question.

The Disappearance

After repeated inquiries, Aramex now claims:

“the waybill number is not found in our system.”

This is a material contradiction. The public response does not establish whether the record was deleted, archived, migrated, or unavailable to the support interface. It does establish the need for a complete event history and a clear retention explanation.

The Record That Requires an Answer

The sequence is clear:

1. Riyad Bank ships cards through Aramex.
2. Aramex attaches the wrong mobile number.
3. The cards’ data is leaked and used on Amazon.com before delivery.
4. Both shipments are recorded as returned in the same minute.
5. The tracking trail later becomes unavailable through the queried channel.
6. Riyad Bank denies any transactions to SAMA.
7. Aramex later states that a previously acknowledged number is not found.

This is no longer a routine customer-service issue. It is an integrity problem in the documentary chain that requires both institutions to produce the underlying logs.

What Now?

The full email metadata from Aramex’s earlier admission has been preserved. The contradictions are published. The world can now see how these entities operate when they believe no one is watching.

This is not a complaint anymore. This is a public record.

HD.39 / Digital Forensics Record