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
- de724da8bacea908f02e64a3cf1dcd6ea83eb45ba3f6914c7fb26986c002c711
- request
- f95f0007f64d4f00cc6bfd4cf2510533a7d1cf1290848ebe7dd80fcb02691b09
- transaction
- 6a1a53fd1ffb2d5da65d562d911637a2b02877dc33563f14d5cf654e22b1d4adcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 14739
the chainentry 14739
- sealed to the entry before
- b9abc749d99bac1e5f513b019d00be21fae9aa4370cecaa9273846278a527412
- this leaf
- 12fd6592b74633dba2b2aa21dfa8941162909c5fb36ba65d39c1ce85557000d9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- hivexG23oL8C2Cf3zq/k0WFP83pcWyKqMiYh6UlOpbV+iCfcTEqnZ5rlu6A0Yv4e0wJmf/sCYT2laiNttJYxAQ==