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
- 5e949ad1c7a3b89ac0310489d5c500b5ed0465689bcee5c951382bfa44f1c7d1
- request
- dcecccf80f2de132dbf35ff05396560ebf22f6fe296c7b5961f414ed1279a0f1
- transaction
- ad186fe8b243af4e37fc3210fa63fb7bf6113191dcec24bc1f1452eac09cb424computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 39379
the chainentry 39379
- sealed to the entry before
- 9f465497f30fd8e88a8a8837bb6e5457071af5a18b7ea662dcfff1e470941ca9
- this leaf
- 04a1e306f8bb95467fc907146a2d9db094a58093eeb62c46af16b61a53031802
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- IcQMsc+gifSHIWykFAiVhkbMpa8ZgmmyPoKjaRMLhfmayagfXJxRpCttlDLSMo9cGaVw/swS4WqFVZ4AL1mfDQ==