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
- 62d9209c01859edc1c38a02f4b24c654b1d08de2756c16044587e6b988dee104
- request
- 103da59a607bdda521037fea3827e9359851047dfb3cb3a3b24fbbd9dc21dea2
- transaction
- f72982657bba5cd31e9589c5d8cbfe70019b786fbdff65ae10c40db1e090201bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 48029
the chainentry 48029
- sealed to the entry before
- 273a6ca61d0576fb1c2851de99b62b70a369165fa06daf3d2e7dc1bd55279e93
- this leaf
- 6e599841ceb1e0062456b5b23fa67c69097fda013dd204669cc45baf0a96fdaf
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- CQ3ysgoNuVI1+CYNo/tutFRaZ9k9aF2lMtH721RH4JPGjCN1m2JsyKr1awPNChdRAODqiwMDiq6xVdlELKM9CQ==