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
- c55248cdd80be93ede3c2c1570da5edadb1f605c395218b97b490f3f345c5d3a
- request
- d7c0f26fbb85f44d9676e4d4339df457b91874269c3ba844bcffc08bd19010eb
- transaction
- 6623be23e4a9147b30af60e6a3ee01832cb19eacf9159ce009f782abd0eb3ba5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 77513
the chainentry 77513
- sealed to the entry before
- c2dc44ed6f60916f698c3945b1b47cd0033820c1f8d4f681274274bf5ac039d6
- this leaf
- 3494644936c0c9eedcd63ae10ff07279921772a0c5cc8873f0092b7167a3f441
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 3ypQ8QxlcM6rhEiiQ+Ww3Hjl31D33h1dM1Z/RqQ4LQclWSdlf+wCMjKhEo3Cc6hLNKHC+dxaUaEDClBJVNYiCA==