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
- b2894dd506b30b04dc680b95c305619a863b9cf1b566c8f8942f98b058b3dd35
- request
- 6093d03b41bb978268ce30a93a08deae7c2d1576571bd1fd7c862b54e07dce43
- transaction
- 0acbc158dc0b46e7852cc7a3b3a3fe4850ad55cab5b008eda44085f1aed2b984computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 16015
the chainentry 16015
- sealed to the entry before
- 30c0856a6a443c1d830fbddb72557d937eaf339133f791be9588ce56bd7c6433
- this leaf
- f87d8f69df8e58faa05c05734927de9315956a6c7b0951e93fe72a4f9b45e7a5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- g9OJz391nXfh10J0A6Ixl8ktHvXi4cbv0fnkLMHGCb181xClnD5M9jKcYBHeDwEPXTnV7H6tjGKiarhKzN7EBg==