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
- 5b2720ef1207cf744549f74fe08665a3e98aec19ac695e2ca31b9751e793f76a
- request
- aa6a2745292cc36bb556bb383a20cf84983e145e0f401ccc78d2339d6de85738
- transaction
- 90f470a31d8a12b582af4e272a8a0b0c8c13a811a7fa22d709f7fb92a5a91dddcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 71919
the chainentry 71919
- sealed to the entry before
- fdd9b6208edcd43b6e4959a1dd95bd9a6b77634ea4e59fe8af64c24419469b12
- this leaf
- cdf0db6a7f68e8e414bee04b943560cfbe0aead850b47ff891daa464f621d2f7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- fd/CawXgxmGuzusHT83kzUgzFYAqVyj9cmFkJgsSIf45rDt7Gtwj1Wktk8PBdmxPz4jIBPpk8Bb9z5QPw5upCg==