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
- db9a0d613c48ed1659e121f9ca423a9407fa1a5ed6eeb20a9e7ca5753d6a81ff
- request
- daa9956983bf4a061e01ef0b3c54b6e90a7a7b687dfa14590783d461b700c948
- transaction
- cdec29a05464d5cb0248b76687843198bb2f0eee21eedf579a38e1310055574fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 29380
the chainentry 29380
- sealed to the entry before
- f7ab81a3c065b68a1083000cec59550a36471d5fcaa28474f04704b19a2a915c
- this leaf
- 3964422f8583fb39166a50dc84ae6590912c560e33625e33c887dd9fd4c0e2a2
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- rmQHeln8Ua2Rd8BqfxZM6xedmpkJjkSNHvLu2xmdrsSppr+4Zluw096vqBXj9POquT5aN+3bHdt6BFtwlNRLCw==