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
- 1831b0ca5001406ed5c2b2ba73afd5ce30a0d9fdbb7ff9d732d105b1795b26e4
- request
- d563ea0023469c9a890e5e7dc4320bf7aea4fcc76e59a3ffc098ef3c5dba08aa
- transaction
- ac51798f7946614e0312b86c11a61d959f5266a52080cf29659dddeacaf084bacomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 3630
the chainentry 3630
- sealed to the entry before
- 94c0ed6c77c4388910b30489954beaa60dd1f17682cbf91cf37e0e1b6581ef7b
- this leaf
- e20faed8017c594b1a55f5dc85d2afdaa79883e54c3d6572385fde85bad5b569
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- jRGVxYmAMrMeFkCD/YHijT8lcHhBeZrFZMX6NSXQgjWod589DEF5KZWdlnDeBjWvc6dWr1zc97i/VYgfCLtwDQ==