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
- fa64ec3788616905c91d3468b44ccd45d18736f2f32a7d9f829f07fa20f8bd27
- request
- 089e7d149a2b5863c67fc03f58c89886e29d0e87c3723ed431d973145f232690
- transaction
- 4b0e4742a7dff173b1c53185e12c8bef98c44d09fd5d01506024db3807d41f2ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 27804
the chainentry 27804
- sealed to the entry before
- cc6f87109815c81a8b60df5a5eb40965c09f300315d3963140645f663a2f0653
- this leaf
- f159cb8d8c01126a4e35e495ec4dd527ca46e872a0c2331776e841b66ff1d209
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- G+5qxeveRoq3BeRjbEHCjklw7vBdWsoUpxJDoaN3nRUr4kWFO6uYi6VeF3NMlbT2gRL7oa7oMrfiXyYpOf5wBQ==