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
- 0e76c325b675bb2140665d4581cbc66206d1e3a4a0db5475e044003e60160101
- request
- 40c03c8063984e7f55496061bf53afea1ead5ff82ba6de223421ac0a79a11de7
- transaction
- 35d486a13ece1d1c61ed61dc2497b40b9f50a5cd7775b24009bdd92b065140b1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 28252
the chainentry 28252
- sealed to the entry before
- 4878aa53f5697b20520fc10131a37e73a1dd4e193c1938875c2f7b10f01b2f11
- this leaf
- 3476c8b0fbc1e8e0b19a6e768a60baee71b650628e8baddcb431b00bd932b457
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- UPQJcSQJntIDCEc9F5WknKuhe+ulfAvFUBZPojpS8u3t2lsk+NMero5eWoWXlLNI/jkCfdvJ6Nv2CnJxE2ARCg==