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
- b66881fca8a883cb5704184ecfb12cc623a8a36ab74e737a212c7a784e763a0c
- request
- 39d5f43f1cf5134866e3a5dafcb7d34f270616ff76d737f57441980a95e7ac6f
- transaction
- 75205605c87ccb25ec8a248005c7b63749becffcd9e011a8803bba8780cc369acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 61368
the chainentry 61368
- sealed to the entry before
- a4bee7893cab81fa60d316b1474db11f712a14bd3ce3984047bcc206c73b4af3
- this leaf
- 5bd7b217da5080c9b359bff367d07abd6435476655d86aa7cfbc70d3f610ddda
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 1RlRM/42GQma2GeYUzYs33M4uVzoGju27gW91MWQIOjpAKnfgr247HoqAY00qZ8zjr9pbEIbtejlnHiqisQfCA==