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
- b8b202e9048ee9fcd50623b8184c57fa3d6c2eb846dec55ec06a9ddcdbac25c7
- request
- c800c769e60a947467a6f15ca0d0a18bbbcf5b7be7e3827433a151ff6c701579
- transaction
- 116fb9421b283654085834aaeadc515e8574cd15a44a375eb105bbe68e113071computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 49888
the chainentry 49888
- sealed to the entry before
- 38a57a885cc4a3005cdfb8cc63c7a2d513f1692d8d6f121b17860402f41f8f44
- this leaf
- b0b4959009970a7440c04f02a87b88600babe5ac89160d873a8d9524685e5854
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 5bmGDS6M9LGuCGiKZ8nqtUM1K0ilXkcafvrcmmxyp0sAU5I8jely+a1BLD+4BbDR3W0FyLg5rYhjHNAC3AmQAw==