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
- f30159f11940273339dfd4b6336eafc37f1871f0a670f84b8a598aab1bbc3708
- request
- 5475344049fd3ab553713dcd3dc7c798a848497964887ca4e38f20a1c747eaa6
- transaction
- 9be960e1982c617f1a161c3f502011266d90ed854e0211ba501d2f3ad04a2ff5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 77069
the chainentry 77069
- sealed to the entry before
- 326b1299e92e35bf00ebfdd0c892821f57e29681cdfe2167eda80fe8d2848933
- this leaf
- ebab66e58bd3550b43d661fa1b9c172ff9072da467de0ed2580bf410c31e2b57
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- MHpd5p4X6tG4zEX3g10g8iAsh9OczuPlvuuDnwhmA1atNa0mSGOeIu3voSBuYnSDEpckFQemw2kRBpRgJZkOBA==