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
- ab41393000d930f00b46709c9594abef0dfe3e0eefa01bc5eb8b550bc92ebe48
- request
- 8662086b199e81e47c454b17b2aafa589191ac83934a25969c71ed53fd37b588
- transaction
- 515f66928285fa234599d2f08b186618969f5b54f165cac79175bf1e1a20dcfbcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 34299
the chainentry 34299
- sealed to the entry before
- dcb1f2737b903be9da4d0f1742cb226adf6ac37afb50cb7f3591078e273aad71
- this leaf
- 06fd8dc1ecb3ed44431896a909007c1d6b30664436391bdee56251fdd4084b8c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- dY7a2bGuqmI0fGcwieT03Tkn2pIOQilTVzip1okZc1QdiYP6giOaFxDJX4sYDdLVYdoeBSornSHaSkBZ3K8uAw==