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
- fa6fba7f24bd543a56e414ec175d3a8347fafbcd4ceca2d454022de56ffad583
- request
- fdb3a2308b3f7cb3167f14cb466212e5ef3095bcf674f6e91df499689d2e0870
- transaction
- 82844ac4655f2b58c0f4a77d7b6db397e60176dcfe95f2233b1fba9be233799ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 72561
the chainentry 72561
- sealed to the entry before
- f45b6f32cc0cac86f77ecae3b9dfe7e289f6942bb0f9236d1cdb3647862cccea
- this leaf
- d26f6b2daeffe0ceb42e1ea8329ddadce5366129fcb85933a3e545329d9a3f6a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- nUep3bZ1p2sFlhYzHoEYJY34+zio+zFsmALFLdgx5DIm6I7IZSos/jexgthxywvdN2kc5vxHxYi5NKSig3kDAA==