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
- b3a8ca291f3acd38d4ee18c14ecccd22decb814e277edb8f641a48656a3689ef
- request
- 2ced3bea6b9dff30d85d9fe31f65a8f311d0469aeeda6ca0751cd9f75654c75b
- transaction
- 56d0135b60235194831d07adf0dff53070b5e078b7cba164fce8bf0944eea042computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 77159
the chainentry 77159
- sealed to the entry before
- 0a451d2712966b6eb86b33fe4aa9ae05c3012b9e92d4fa0ff17fe749adeba0cf
- this leaf
- ba241ac5e55a1662db772f3a6ce8b1334acbb575b90ba45697cdcccac5990741
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- fmTK2Q0Ep6JJa4MMzO9+G2T3dP/watwYsjjGTe2sBazXX5EGNwBnQnS7szd/BInI/2igLWE0BNKqyOBHb1ZBDA==