why1 reason
data_leakpayment_card
payment_note carries a payment card number (41************11), which would be written to a permanent public record
what it was decided fromfingerprints
- rule compiled from it
- f3667b615bbfe475922848903949e7eba1438a1f11fc95093a05a5761f8c3258
- request
- 65a2dc6b915285f8600a7526addcf36fc4693ea0e036a9c02c923b3c9c979603
- transaction
- 8385a880ecc5bf002827e9a52f93eec2c69719b585231f24219bb8293053a962computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 69359
the chainentry 69359
- sealed to the entry before
- 0f7f7e0623df932170d303f12e44a1052ce804cd35b4aa769a7db44d3cdc1bbd
- this leaf
- 519b270e428078a4fa3117624ed99288f15f0a7c39ff7de6bcd360df4515532b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- rNgz3SZ5J4K0XJ2K8WCn/7/KlrMgneSpc74TCnLtFmt1LVi8dlujG1Dm1GHFD5cjreXgGHd84QLebUTEz0gPAg==