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
- 872ed08a0c69cdf28e6098adcf9631d2226a1878f942590b03d4a353b5651690
- request
- ae71c4431dcae1ffeda30770b9947a36543dc1060edac8d663a471917d87a83c
- transaction
- a1767ebfa715698b55008c9a74a7e0a2e7df52f6a7410b9aac0e72aab138401ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30968
the chainentry 30968
- sealed to the entry before
- 17110432b3439653f7e728aba6d40b1e8190ed3d14772a23f07e1b1f6bb6cc8e
- this leaf
- 288b34af8a711f2118fce549ffecc59a81d5dc0b4bf6b6ce5f8556f1880821bd
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- OBqNaoVFOUkHojTP6qSMGoc9jT6ZACvFsA9LUB1TCxzYQ1AQlWAH8O8wu2Z35jMlLPKbSXAPlf6yxg43ZspZCA==