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
- cf500a82a4b0962680f712d9a7fd305d695ade1b3ac2533b724cc2bf74f1e575
- request
- d2197de1bd7dcafcde2df413fd9ec7a8a80609db68fcb51daf988baf0062152d
- transaction
- 6b854977176550edf65dcae8b369690c5d69ed46a806b6626fc64ea8545ce2dfcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 23189
the chainentry 23189
- sealed to the entry before
- 0176fb00d6290a2ff15725e50f8cd1349cecd56650aa744ae15a09f098265e8a
- this leaf
- 3e48560ee6299dc29553cba732f90698769ec40bbd1a0adce8eb9d35ef9b3783
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ZMDRB5zVUnqba5jGtnNlb53b+0LVQFh/8/PKpGB4C+sHuutPq4KREdItnR93B9jSGmkToEJj4snt8X6vIOStAg==