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
- a1d4d666e2dd8b1a0d971813864378cfdf4749a4f9bf853e8666a136ab3819f3
- request
- d466b32402700619c77a3d12201085608c23379e5a26f7bda08ebc5270c0b58a
- transaction
- f9e75e24770b253193f02cafdefa4a73e71ee1b2b6bfd559dfb5ad7bad54ce47computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 62346
the chainentry 62346
- sealed to the entry before
- 876f919d1c1facffd8e684c6a353fc5177f4771702a5355f163eafe298b28dca
- this leaf
- 5a08aa5b85b52956864ac72a3138d95bc9c07f986cb6b0ca5c447b56c38c548a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 1eO90qgKGmw0C2wI9JLfreP7rfInqiw0cx/OcWWFWbDcmd6J5oUB/2mQ3TAi6KeN1AzuGkury4K7ziLorYTDCQ==