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
- 0ed7b89a8bdcbc4ea70a74b342b787994f170e78b8de4e2910b882fc4686aa15
- request
- 6def4d2c0cca68a4d9470ade49f30ad4fd4c03d3c35d4538e02652d9d3060339
- transaction
- 7f9112a150632fc8f5082063b87c005c62353a5208f61b1bfdad63acfe0c349dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1330
the chainentry 1330
- sealed to the entry before
- 0fa06ba29a71c15667d2f99f5b58742d529c296cc7806aed6bc189de1a3e2451
- this leaf
- f3bc905c1c3580d38a5aca6f8e3855dc021cddc2dc23e3200358fcdb0fa2d82e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- PI6DRs3d1k9wsPlmcufxI1KQ/e5U4j0kZwbxh31MNgsMa1H5bL1fTBw4nJ2rYCls52EmhHN8+mi5kS9ZqwfcDA==