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
- b91b0ba4934f2fc682fddbb91d5b28de4a3b5faf363b1af6413b591725e45bce
- request
- 96ab218de2f2b6ab9bfcd44602fd5775df81713c4c6a58dbe2e94e4e3ded30f4
- transaction
- deb55a5fde69b0209ebb4741621d5926051fb9ea15bf162bf12cf83ab6e15130computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 31484
the chainentry 31484
- sealed to the entry before
- 1acddae846f0082957516b0e77ec97ef2b3528af0473c15e57728575a572fdc0
- this leaf
- 07855d22c88ff9b34e7a8c68d032a75b835eb7bc1fd9d0fbc837330cd31eb668
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 6ok+CkB32WdG0jkkDCEoZRn2+eBadcwhtJvUB9JnaururafLpfQ273WIY3BU+zZ/K1B6fHqAHcsrqPR4e67QAg==