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
- f7042c757449ea151f12ed5bc1c74006a5561788772d6bc5626de12fc7defd3d
- request
- b92bd2a96c30ac56f42ddf3726e41fa1a06f60851d5c00fd424be3a8f2a1c592
- transaction
- c35dcb52b0cff60f82a0b35e87c669ebf00bb5f330bef73894c24acf51f3ca8ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2530
the chainentry 2530
- sealed to the entry before
- a3d3af3c3389b1eee92aeea43b4fd2cb5bd0f6cabb4200558f9a67f215b65c2d
- this leaf
- 360c332d249f9da8c2f459e0d325e3c03eed155c4be8926659929462d2ddc6e8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 9HCQdH37obTSo2tpCrr9dRGuGiUBpAKztoJ0pDc/h2TlW0+UZeTvBtdw2cTb3kIJKUUXWw4Z8uTXz3yOQO0rBA==