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
- 2fea911d1fdaa06a7296472984cde20b7e7426cf25684a8f7fa2dfa1b4e95808
- request
- b744799873fd417bf908d18a2a32ee90c6409961522172f4fe994561c9173a9f
- transaction
- 5705138b9a163ea2dbe3ac999096a19a5880dcc8bf55b646b8adce8280056900computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1575
the chainentry 1575
- sealed to the entry before
- c820ba42518f813c0d8f76a5d5b6f38a357de3aac96033cc088bd957c0bd6e47
- this leaf
- 43c3fc9124a311ac144184be0af311685a80d058ad5ded1a298d3cd6a89b66d5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- TBFZPXwa/GMgcCCLIL39rF0tp7We65LEGo2i+8hkdkguYauJfM5vNwzxxaF/H1fnw32Tl9Z1PfMXlVhWoTyBDg==