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
- 59045cb12362152c09d4052622724e29979c8e54ebd4514462203e2403d93b4d
- request
- a738ae6aa46fb69313763de01a16acdb4f03fdbaf3720e6a7297cce1c91e3621
- transaction
- 40c7354848cf2ab4469c4e04ce4fcb32e51d89220842e4670548d8e277c3ddbccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 76716
the chainentry 76716
- sealed to the entry before
- f86fc20f40443a249e815b8e291b05aa8516956322692323f6c443e6130a23ac
- this leaf
- cea7bb9376d350433e875893229ec476e9562192ba4ebf246b71001060ea4637
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ClCj//XZITJgqShkBchzYXnoq2UvZbP4FSTSogHuRvKnxT6M8WVOyZci2bP5r3xU5VQBwOPRTK3KCADUaENcBQ==