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
- e8662f347fe57cb82145a08afd22c85008f8155bff465fdc2936e56e93d0dc78
- request
- c8e1d9d34e39e976de7419eae835349b719da11759549615c9db5160d1c9b026
- transaction
- c9c557e5f85cc2a30ef634bf579dd6e722e140196c50e798aa2008d277fc800acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 18297
the chainentry 18297
- sealed to the entry before
- f288a9746cbd6b2d50473ea08a81aad65b82647e9f926ed271fb3329257cb966
- this leaf
- 9d9f514203e20c9505c96713682420820dd1382726dddf061c151d05857da142
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- nSwmp+7fVCI4tbx65XZwdivRTuPVbakO9nF5av9NI8GNJW/IQdQUjJOhdlhzmPjbbfRhWuJb5Jx6O5TPKQYwCA==