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
- 50cd22eae96ef476874ab11f57cc3e6f92e12b201d97934c29ac28708652f1b1
- request
- 9e205a14bc692d53f2479efb913ff7cdf5d62fc4688c7f22656b66ecb0f613d0
- transaction
- 849033a5b7406bd8f01fc117279ff0487b4669c1cd8ba96e990b907f57b2e4b5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 10766
the chainentry 10766
- sealed to the entry before
- ada48934daaa665b323d0fa264dbfceabaa9f6fb0898e1bd34375c79ef1b6271
- this leaf
- 8856df3a4b307035cc9a7d102e2d09da9288e4687fe09f551e97ff62f3fc8148
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- nDY5PXIfRemdw7dxD3nj0/R3AD0HWGn9zjl3qS2crh3em5FOZ39+YDoS0M6NBsZVxL0yiXVBV1rbuXM3Uyw0Cg==