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
- c85676ac29eb63b2d3a2541541649c63484e4b04c3942f2acf070e4fb8cf8bb0
- request
- 905484f38e4e0184b15babddf1c4b77d64c613c97d6e83159c26e6e190a27e7d
- transaction
- acc79932e9fb370c8d5b7ff20f35563e8ea9d1b3971801c61e3604d58a0df66ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 45568
the chainentry 45568
- sealed to the entry before
- edba4ef0dc6dff06cc6983aa308fb63cb872dc43beb79ed01c4695db2fc19a69
- this leaf
- 40872f92e86ae2da3b11d7177e1ae8cd8af80e6869ad0d638dedfd1cc006892e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- N1cwbrWO5qjleFzLfsOrQmA653fqg3Az7WAsa1LbyQt6kU4RdmcqS+WHVOlBh2XuDlrLmQLu5Ankj3/ma5uqBQ==