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
- c8d4a85a5545d686e45fc037da614eb89b8e926a326e93b464651fb3187f853a
- request
- d273803f499ab481b6e2c8985f562849b29b735a4271e8dbb8f89d811992a48d
- transaction
- 9e7327c1e7324ec38e10dc9ffa893e00a9a83acd8ea24e3eee0ff1a70599c49dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 67570
the chainentry 67570
- sealed to the entry before
- 52199bfb3f5738d3c03781ca78449d113c0bc537856367463b75af4c48d179aa
- this leaf
- 04482d182bf95a5c62568504044fb52e1a7b3dd3a00e16e898163550a2d899d9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- bC7JS8V8zZqoCLYPd0yk1XC+0VF2FHvv1LR3WdmjFN0gO+SvkEnSI0dhHo0h5+WS5rXktqedIxBQUXFz80V4AQ==