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
- 529e4d575b29c02d729799e6f1604833dcdc2ebf3aefbf1d9804358be692c1af
- request
- 84743c6d139b8b68a452c013c61758a1a9fb2e684fa549e20443ade7e911e81f
- transaction
- 96d8e9fc2da1ee5e9c0ed1640a7a3e9bad1e26b18668aeb8c3850b77cf22a3edcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 70665
the chainentry 70665
- sealed to the entry before
- d35f04a31696c25c4d4612a1aaeffc9ee5878635470179ae3e72c776fc9f6a6d
- this leaf
- 41f65e425624ecffb5ceb7c6270b4271aa3cbc64be53435f73f06481163d66ca
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- hQGAV5zo2OkykJEzw24e4ge+D8rEzjtxIAsvKbg4ynUuS/mfgy6zp0AumvLHT5IGopC1pJtX+AELdRum7/DECA==