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
- eea6405b7431654ee39467549c24baca643019355f9be9a4029971986325e838
- request
- 5bf413506638c70cba100f15d4f2b5ec468a65246cfe54dfe676c794c3ef741c
- transaction
- a21864cf161d835e6f32f8d3aaf7112bd7b289b58ccb96593b1a7e361c12f036computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 37656
the chainentry 37656
- sealed to the entry before
- 8dae9448c7d661dab4b4e321b551c0c67dc473a0431043d98334c756ecf7fc0c
- this leaf
- 4cd78caa4b2ee96421f803aa3d68481746ed2125e9ea467681ff9032de0758e5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 57+r6MSU02adUZrJMZKdka3dJa3gg9YwLzVBaJ6W5AzrTa/I0u9B5j32g6CFklbKqmcMFrbPeKxt8UWqtx3MCg==