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
- 59da7328cfd41767277dd9fe19a94cf53c93a03cd38f45221b889950ec4f71a3
- request
- ec619d48a88b7dca5d804ca821904966ec73d17fdd2d3aedf9954642115fde23
- transaction
- 4eb25b6484eea9be8e01d1a37e24f06ce4918199f0f7f4761f90e61d42b2ead6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 9286
the chainentry 9286
- sealed to the entry before
- 42a690ef1ce222b11456e2e5a4fd4ce7315ed6ce85b7faea6bfee95c284cdd0b
- this leaf
- 6821c37ba5f3d9184d30c7221d2cc2ee8ef20f8ca45a984a0f14c13d4dc65c5c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- dNGT7hiuq3DWI44dajyUO0eszZW5z0tCerTFkQMUJarAOdpUPkdi4gtquXvB5nwU/M8RaiLYAsRzmgp3ydDQAg==