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
- 7966883e0895fc3c664b71354ed205e6ebe9380a2014538c25b0f65ec0bacde9
- request
- 39071afbdbb908de2e23d1cace47b3ea72cb69d91c43d2d2687f7445e439485f
- transaction
- 13b9f9c62458f42ee50f32339579e1793b6195362bf550dd95e9a6d7f62a199dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 3296
the chainentry 3296
- sealed to the entry before
- d370d7bbc53c275c91cfd86ce9746e63d2acab3d5eb8a606407dcfe851015ba0
- this leaf
- e1232237c7c48c2c63c9376bbd02be29b15bbecffe07a650e2f7b0400c11c2cb
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- kjgBXlXBLDbdNSrJdgwhdxKOyq1OgaMWrOlyEDYj5rI0fqHyEdfZMmxutWIzs5RtQKGSHL4YxRdKlYA/4uHzDA==