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
- 674751c2493c12bbe4f57508985e5ca12f71fa76c98a579d931d3d14cbea71e2
- request
- ae2d9a46296b27b90057c4d2a4d17273ae103954a960c8ad96860648865e8948
- transaction
- 50ceb7d2542d680bc5773365f372aba94386469e2c890a150558a9a51a6411eecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 6138
the chainentry 6138
- sealed to the entry before
- 595af533acde20576315616fd19d185c74c88690ad7d48d47724dbc0b59cdae9
- this leaf
- 540f54d77dfead6eaf39fdf6b1e1b5bca2dfaf55123e4023f29a2194674ca136
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- RLw9fNUobaUdVayC8Lc+6VEZOa2jvP4cTN+pFu0zCE5HCc84TAqqNiWWdStcgjIeBaUpasiLfMIp0sjxfHfsAg==