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
- 90a663e8a83c63e64beebc86d4268fd305de8ff3d5ac229b46fab503515f2db1
- request
- 2a2cf1efebba8fcbf0d5f063a81ae33f3d7c845146fb418311b82648223f3852
- transaction
- 70e261b20c12384a88bb62a49124e0de21c356ea20ed74ae0fd8add94eb9a52ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 60351
the chainentry 60351
- sealed to the entry before
- 6a37ac928fda09863cd5bfb482e7fb2eed28c4ae677dcc122d6f9336cf5d4284
- this leaf
- e41bf00d843bd8f24eb08b53717e939ce517b19ecae3951b3aed1ebbbe5af2c3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- /38v+7Y6H7SevHNTZy6B7eABjm3Veio7EGEegCtFYrWnnLSEns5MOFjzR0eyEE2z92aZn6XjinKWPFa6ZMxBAw==