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
- 329724e66e37b7935244856e298409e4357172acebba05b47b2dab1f84b45765
- request
- a5e4d85902f70095915feeaaf35a9fa2fd93283ed2663928e011ccb1439b19ba
- transaction
- a01089b629ebcfd5c1dd8a32a9b773950b1712b9e20e5220da77712dd5679bf1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 61193
the chainentry 61193
- sealed to the entry before
- c45520a753090ae88517023531658e2af1ed9065adad608e77d2eb51ff6dafd1
- this leaf
- 313a7db042726e1b9544b96edbef23aa89b070dc6a8db89db5bb093124733c66
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 7n5/HBm22UDRRXweHaY1T97sE9uDYapeoVxA45SsSQOM+i5F6c8ucvLqtM715ZxT8UrCJEyjztsPVJ842lA/Bw==