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
- 0bc8620beaddbf7c25da912cedebe2a043a1af02f672e8bcd14981e629e4f1d8
- request
- 3529a112c34207ce592889e5739ca902c3d2f8f22a17f722040d328ee252bf7b
- transaction
- 4db927a616d8a37f977bb91d9ecf931a19cd7b7d7185616e42e3109d68837e4acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 61545
the chainentry 61545
- sealed to the entry before
- 9e198a06c2c11212f3fc0c5e4b7544dab17029f8ad6cef108185ee0df9472fd1
- this leaf
- 590fde903fb4e8866c6541a749436669e6e20e0cb6c4c93fd0007b6a37e99898
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- yHNtlXGQCcGYzG1AR1VRgukJCi6zlgUVzrAb8kTvKaF4oDaDtQKq1joQXZUKkADa8c9n3YniEXwae5JF/7/wCA==