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
- 27519c47a68d574dd1b284aa11832e5e249a4c75a84652a935bf74358c77fc84
- request
- 1907c84960eb2180ded46807621f2e34d7d5acb98358464983ada88ed066652f
- transaction
- 83f4efea52ad8b200b4ae76b72268fd415452a0d095cd5b9e528a8080f906163computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 47329
the chainentry 47329
- sealed to the entry before
- 743fb2f180d52785bde03825dc8e8d0ad8af7ee91cbc76fa70cd3c72aa53ceb1
- this leaf
- 6dfefced84c24b33d3489f0917b5091965d178904fcf620a199fe1a467d3255a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 2wISDLQpHJuN63y45+dAMAYKqp8BayMjdsJ9PsVw4w1/lG7M6w6I9jqZN4fqxy9jHtJTizZCIaDu+bw2uqzAAA==