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
- 31b499e55d464f6180bb581b3105d8ce7539bbd17a2786bddd3ed42007074b92
- request
- f5a4cccd8a7ff1d1819f84167dc390ef006735feb58a438c97bd3865ea20bee1
- transaction
- b1082c55225826afab8a7b114116e57c4587fdaaf18bb2779870b337f846d676computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 22090
the chainentry 22090
- sealed to the entry before
- ae9ced615c5518838b557fe843874be639bf10d94f5875a32b96f74342325b2a
- this leaf
- 662ce07db23a05f5a08d91cc03e04791b9a66e8ff6a6d77ea28c08df3c010578
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- q6apF9JVfBwnN26bxWOnlrhOBCtQGjDkuLPiRK0ynE0w5EgYpMxqPSVUY1G85R5LAP+N2ZekjQXv3tX3DIeFBQ==