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
- f4b7647506a52db2ab5aad6c068784b5916bd1176739f9404699980b8073c6fe
- request
- 91baee4993be0006d832d9835099fc015eb784a434a2df7e288ff4f0e9c6e7e8
- transaction
- 0a274290758254314807082de206fc0e7ce73d78569a39e7ab06b99c57d9f969computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 72571
the chainentry 72571
- sealed to the entry before
- 76dbf2bd0220a03e4bfce9c7f55a7a5a741ce95e5ec4df7fe0b8c8cd2469337a
- this leaf
- b5497bbb92518fcb2b8665c44dbdaa56e758948c4440f53bbce42d848b276b74
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- HqHGtrwIjEDmC4cd51sYAsCLHp649RPihqooNTJF2F+CrxQ1h15Jsr/dJRyez2Ruweb3HiZ1GGCEuGF5DjLRDA==