For journalists and researchers
Begin with the chronology, then examine the source records in context before drawing a conclusion.
Open the timelineReferral brief / read in minutes
The case,
without the noise.
This page is a concise entry point to a public record involving two payment cards, two courier waybills, incorrect contact data, Amazon-related alerts, and later compliance correspondence and requests for technical records.
This brief does not determine liability and does not replace the source documents. It identifies what is documented, what the published material cannot establish by itself, and what records would be needed for resolution.
The central question
How did the reported card-data activity arise before delivery was completed?
The available material documents dates, correspondence, and the shipment trail. It does not independently identify the source of the card data or the point at which it became accessible. A verifiable answer requires internal records from the institutions that created, processed, and transported the cards.
The record at a glance
Six traceable record points
Each point is tied to published correspondence or a record and is stated within the limits of that source.
The card sequence
The published record concerns two payment cards associated with two separate courier waybills, neither of which completed delivery to the customer.
Incorrect contact data
On June 9, 2025, Aramex stated in writing that the mobile number attached to one shipment was incorrect and could not be changed without shipper confirmation.
A matching return minute
Published tracking captures show both waybills recorded as “Returned to Shipper” on July 20, 2025 at 15:57.
The Mastercard track
On October 25, 2025, Mastercard confirmed that the case was under internal investigation concerning the issuer’s compliance with regulations.
The records request
A February 2026 request sought technical and processing records. The correspondence presented did not result in disclosure of the requested logs.
The latest Aramex response
Under Case 130955673, Aramex Customer Service stated on September 7, 2026 that both shipment numbers did not appear in its system and referred the inquiry to the sender.
Evidence matrix
What each record establishes—and what it does not
The strength of the file depends on keeping every conclusion within the evidentiary limits of its source.
| Record | What it establishes | What it does not establish by itself |
|---|---|---|
| Aramex response dated June 9, 2025 | A written statement that the mobile number attached to waybill 49715021705 was incorrect. | It does not identify who supplied the number, its source system, or its amendment history. |
| The two published tracking captures | Both waybills displayed a return status in the same recorded minute. | They do not independently explain the matching timestamp or establish improper alteration. |
| Riyad Bank complaint response | The bank linked a card to the delivery process and referred to attempted delivery and later reissue. | It does not explain the source of the reported card-data activity or supply a technical audit trail. |
| Mastercard correspondence — Ref. 5388285 | Mastercard described the matter in October 2025 as an internal investigation concerning issuer compliance. | It does not establish the investigation’s outcome, a finding against the bank, or an enforcement action. |
| Aramex response — Case 130955673 | On September 7, 2026, Customer Service said both shipment numbers did not appear in the system it queried. | It does not state whether the records were archived, migrated, restricted to another interface, or deleted. |
What resolution requires
A customer-service reply cannot close a systems question
Identifying—or excluding—the source of a failure requires a reviewable technical trail. The absence of a completed financial loss, or the failure of a number to appear in one lookup interface, cannot supply that trail.
- 01
The creation, status-change, activation, cancellation, and reissue history for each card.
- 02
The creation and amendment history for both waybills, including the source of the contact data and the account responsible for each change.
- 03
Courier scan events and integration records exchanged between issuer and carrier.
- 04
Retention, archive, migration, and interface-availability records explaining the later lookup result.
- 05
The technical records required to explain the reported Amazon-related activity before delivery was completed.
Reading routes
Enter through your field
These routes allow a specialist to review the record without entering the archive without a map.
For legal and privacy readers
Review the limits of each record and the open questions concerning provenance, retention, and custody.
Read the evidence standardFor audit, risk, and compliance
Use the expanded case file, which separates institutional statements, allegations, and the records needed for resolution.
Open the full case file