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
- 8836c877fb75b336e907c1a87d25e910affad89197f08d75739f2c9f2367b755
- request
- db414ec606e7b5f6879e2a8f978698d980a9a3e0462f12865bdca9a40ab423d3
- transaction
- 8e2020137b88ead0cd384af5f84788d979a9126042dc5fdfc5b010ca117353dccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 66352
the chainentry 66352
- sealed to the entry before
- 59d3490b86cf688db8d78da3e26f6e12690fdd53b80a5793877a4051b0eecc45
- this leaf
- 30ca3146707728bab24e883ae375222845a61b7cd223c16ad82723d7b3a57534
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- RAIty3yoUSF7WGMrAvIxJO6U5OQOUY19tXIKGDpmtZvyKraVXIc9JhXHKe51slD/XCKrP8tN/p0E9W+bzFWECg==