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
- 1d8caf3cd5768362ed1f8b2393bce1e28b9282268951496fcbfb612368612fef
- request
- 6768f1585705f7784bc841ffd94d43f396468c375fefa4975c745eccfe6db28d
- transaction
- 92979e4eab4879a7706dd77b4d69cb1693a3299fedf0a58aea0fa53bc65b36ebcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 40915
the chainentry 40915
- sealed to the entry before
- 24874229d4e276c04206fb377df25cd2a3f87fb50e7d49d0dd70ae21ace3d40f
- this leaf
- 34ce3fcceeb18137dc3f0637eef20ea527162d9642fb2d507ce88bb73165714c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- EyjA6my6Ot50VsQfJc65SPfeUDThoeu3M2OSLk+j8Ohesytd1vwYnNsn8WVv0KDw6R/a8E/ONmQBT56MvAYDCA==